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
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
marcelo bagnulo braun
marcelo at it.uc3m.es
Fri Apr 1 11:51:35 CEST 2005
Hi, El 30/03/2005, a las 21:30, Hans Petter Holen escribió: > > > Jon Lawrence wrote: > >> >>> PI will come or IPv6 not fly. Face it. >>> >>> > I agree that IPv6 needs multi-homing to fly - but I was hoping there > would be other technical implementations of multi-homing than PI. > I do however undersand how multi-homing works with PI addresses - I am > not shure I can say the same of other proposals. > I think that it is important to distinguish between the different type of sites and their requirements. I mean i guess that there is a difference between the requirements of a big site with multiple locations over the globe and the requirements of a home network multihomed to the ADSL and cable providers. In addition, i guess that the expected number of multihomed home networks is quite higher than the expected number of really big multihomed sites. So we have that multihoming does not mean the same in the different scenarios. We have different requirements and different scalability requirements. I guess that is it important to find a solution for SOHO multihomed that does not impose additional routes in the global routing table, because of the expected number of such sites. Perhaps such solution will not provide all the benefits of current BGP based multihoming (like traffic engineering, provider independence and perhaps some other). However, it will probably will suit the needs of most SOHO multihomed networks. On the other hand, it is possible that certain mutlihomed sites (probably the big ones) won't find that this alternative solution will suit their needs. In this case, i guess that it is reasonable to assign PI to those. So, my take is that the path is to first understand what types of multihomed sites are well serve with an alternative multihoming solution (like the shim being deployed in the IETF) that does not impose additional burden in the inter domain routing. then understand what sites are not well served by this solution and really need BGP based multihoming. At this point i guess we could be ready to define a policy to assign PI addresses for this type of sites that really need it for multihoming. Regards, marcelo > -hph >
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]