This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Previous message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael.Dillon at radianz.com
Michael.Dillon at radianz.com
Thu Mar 31 17:23:36 CEST 2005
> Geographical hierachies require a interconnection concept > which is radically different from the concept required for a > *competitive* ISP market. They would require "leading" > operators and "sub-level" operators dependent from them. Not true. Geographical addressing means that a provider uses addresses from a city aggregate for all infrastructure and customers in that city. The city aggregate would be determined and administered by RIPE. All providers who have infrastructure in Paris, for instance, would ask RIPE for the number of Paris addresses that they need, regardless of the size of the operator or their dominance in the market. There already are "leading" operators and "sub-level" operators in the Internet access market. Geo addressing does not change this because geo-addressing is a technical solution to a technical problem of packet routing. > >New routers? Since when does BGP or any routing protocol > >have to run on the routers themselves. Look inside a modern > >router and you will often see that the routing and > >packet forwarding decisions are done on separate CPUs. > >And there are boxes on the market that do "route optimization" > >which is just a way of taking the routing decisions outside > >of the routers themselves. > At the end of day one > - might require an update of a underdimensioned forwarding engine. > - a new router because $VENDOR might not be willing to implement > "IPv6-BGP 4+x" on an old box. The vendor doesn't need to implement IPv6-BGP-4+x on the router if servers in the operator's management systems are doing the IPv6-BGP 4+x function and passing the instructions to the routers using plain BGP4. And the whole point of geo addressing is to avoid the update of underdimensioned forwarding engines when insurance companies require every company to be multihomed in order to qualify for business insurance. Why is it necessary for routers to speak BGP in order to maintain a view of the relatively stable mesh of AS interconnections? Why don't more people do this work with servers which are faster and cheaper and easier to swap(upgrade) than routers? --Michael Dillon
- Previous message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]