2005-1: Provider Independent IPv6 Assignments for End-sites

Dernière tentative de recherche: 4 oct. 2026

Identité vérifiée: 4 oct. 2026

Messages de discussion

3

Première activité

27 avr. 2006

Dernière activité

28 avr. 2006

Première position explicite

Proposition alternative

Dernière position explicite

Proposition alternative

Changements de position

0

Cohérence du point de vue

Aucune évaluation de cohérence validée

Autres politiques

1

Première position explicite: Proposition alternative → Dernière position explicite: Proposition alternative · Changements de position: 0

1. 27 avr. 2006 · Question ou clarification

   [ppml] Policy Proposal 2005-1: Provider-independent IPv6

   The routes in the Internet routing table will likely be more specific than a /48 assuming people want to slice and dice their aggregate to do traffic engineering... … I haven't done a study to see how many slices people typically need. … One way to look at it is to consider that since /56s are assigned to soho then maybe this makes the /56 the new /24, and providers will allow more specifics upto /56.

   Faits sourcés ↗
2. 27 avr. 2006 · Proposition alternative

   [ppml] Policy Proposal 2005-1: Provider-independent IPv6

   Yeah, we need an architectural solution. Maybe complete seperation of … locator and ID??? … Large ISPs have been accused of liking the provider lock-in too... I … personally am no in that camp. I think IPv6 needs an architectural … approach to solving PI and and multi-homing. If we could completely … seperate locator and ID with something like 8+8/GSE, have DNS only reflect … the ID, and have the network map one or more routing goops to a site (Yes … I know this needs some protocol), and use only the low order bits for TCP … session termination and firewall filters. Then we have solved both the … provider independant and multi-homing problem.

   Faits sourcés ↗
3. 28 avr. 2006 · Question ou clarification

   [ppml] Policy Proposal 2005-1: Provider-independent IPv6

   Yeah! someone else is actaully thinking about the long term implacations … of PI. :-) These are the types of discussions that need to be fully … flushed out before we all commit to embarking on this path. … Yes, I agree, but I can't figure out how to measure this. … My number assume that all non-contigous blocks from a single AS will be … replaced with one block... this may be too agressive. Take the case … where a single AS exists as 2 seperate stub networks connecting to … two upstream ISPs. Each stub has a non-contigous /24. In IPv6 we give … them a /48, but they will still announce two routes. My calculations … assume only a single route. The same might be true for a single site with … two non-contigous /24, if given a /23 they might still announce 2* /24s … for traffic engineering purposes. … I'm not sure I follow here... the CIDR report shows 179503 routes, that … could be aggregated down to 118693 routes. that meanse 118693 routes … can't easily be aggregate today, but 60837 could be aggregated. To say it … another way 60837 are intentionally not aggregated. … sorry yes, 1.3M in 7 years … The question I am trying to answer is in the long term when there is wide … spread adoption of IPv6 how bad is de-aggregation as a solution for PI and … multi-homing. What would it mean if wide spread adoption happend by … tomarrow? By 7 years from now? and so on. … The next question is do you want to commit to the course of action and … risk the health of your network on faith that routers big enough will be … ready soon enough? … Your numbers are interesting, can you provide 5, 7, 10, and 14 year … numbers? These are the numbers that are interesting to me when discussing … router purchasing. … So all small business will either not multi-home or will use the limited … functionality of shim6 when it is available? … What about Europe, Asia, Latin America, Canada?? … Suppose I built a scenerio like this. There are 1 billion people in … China. 10% of them have a cell phone. Thats 100 million cell … phones. One quarter of these phones will run IPv6, and want mobility. As … IETF hasn't solved the mobility problem yet, lets use PI addresses to make … mobility work. As long as each phone get a PI /64 and advertises it to … their particular Cell provider or particular cell tower, then roaming just … works. Thats 25 million new routes in the table. … You raise an interesting question that i suspect ARIN will not address, … should multi-homers only get one slot in the global routing table … (i.e. 1* /48) or multiple slots to allow for traffic engineering. My … predictions certainly assume multiple slots, and would be less agressive … If there was only one slot. This would make the IPv6 table as large as … the number of ASes in the system which as you point out is linear not … quadratic. :-), but this also does not solve the traffic engineering … problem. … Assume I have to purchase ne routers today. Are the routers I can buy … today big enought to not be upgraded in 7 years. And again in seven years … time, are the routers I can buy big enough to not need to be upgraded in 7 … Yes it is a factor of a bunch of things, and worst offender is IPv4 the … IPv4 Internet table. But the IPv4 de-aggrgegates for traffic engineering … are growing at a faster rate than the total IPv4 table. And sure you can … prevent IPv6 for inheriting this growth by making it commonly accepted … policy that any ASN should only advertise a single aggrgegate to the … Internet table. … Shim6 might ease this a bit when its available for people who haven't … already adopted BGP based traffic engineering. 8+8 GSE may ease this a … bit more for people who haven't already adopted BGP based traffic … engineering and need complex traffic engineer capabilities.

   Faits sourcés ↗

Messages de politique: 5