![](https://secure.gravatar.com/avatar/43f1e35a4e033375489837028098aaaf.jpg?s=120&d=mm&r=g)
Hi NZNOG :-) IHUG is changing its peering policy for peering over WIX and APE. We will no longer be directly peering with our current peers but will continue to peer with the route reflectors. Customers of IHUG who require APE/WIX peering directly will not be affected by this policy. This change is not because we don't like peering; it's just our way of trying to make our network simpler to manage. We are aware that some isp's are not huge fans of the route reflectors and prefer direct peering. We have heard all the arguments about why direct peering is much better than the "evil route reflectors of doom", but we personally have had no problems with them and they have proven to be reliable. If you have any questions, please contact me off list. Thank you :-) Simon Allard Ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz
![](https://secure.gravatar.com/avatar/1bad9c366ca6cddbe78ed016298c1584.jpg?s=120&d=mm&r=g)
On 18-May-2006, at 19:07, Simon Allard wrote:
IHUG is changing its peering policy for peering over WIX and APE. We will no longer be directly peering with our current peers but will continue to peer with the route reflectors. Customers of IHUG who require APE/WIX peering directly will not be affected by this policy.
It might be worth noting for the sake of clarity that the things at the APE and WIX with which IHUG will continue to peer are route servers, not route reflectors. Route reflectors (per RFC 2796) are a strategy for reducing an IBGP mesh within a single AS. The BGP speakers at the APE and WIX propagate routes using from other ASes with a NEXT_HOP which is a connected route for exchange participants; they serve routing information using *E*BGP towards peers without being involved in carrying any packets which might follow those routes. Hence, route _server_. Joe
participants (2)
-
Joe Abley
-
Simon Allard