IPv6 Routing request
Dear RIPE Routing Working Group, In the run up to the RIPE conference in Prague concerning the issue of IPv6 routing I would like to ask for consideration of a wish to be able to de-aggregate a /32 PA block to a "depth" of 8 bits instead of the proposed 4 bits ( http://www.ripe.net/ripe/maillists/archives/routing-wg/2009/msg00120.html ). We provide a network for the interconnection of about thirty (30) autonomous government organizations. For the needs of these organizations we were allocated a /32 PA block by RIPE some years ago. We are currently developing an address plan. The idea is that larger organizations (about five) would receive a /37 block, medium sized organizations (about ten) a /38 block and smaller organizations (the rest) a /39 block from the /32 block. Through the use of the /32 PA block, the benefits of long term IPv6 address stability for routing, server, gateway and firewall systems are being sought. Every organization is autonomous in terms of its IT infrastructure and in terms of its connection to the Internet. Each organization has the freedom to choose its own ISP for access to the Internet. Effectively this means that chosen ISPs would have to propagate the de-aggregated routes (/39, /38 and /37) of our /32 PA route into the internet. The inter-organizational network (/32) can then be viewed as having up to 30 different connection points (/39, /38 and /37) to the Internet, one for each autonomous organizational unit. Several statements have been made that routes for /39, /38 and /37 de-aggregated blocks will not be accepted by higher Tier Carriers when lower tier ISPs forward these routes via BGP to the higher tiers of the Internet. Other statements have been made that routes to blocks which whose prefixes lengths are smaller than or equal to /48 (comparable to of /24 in IPv4 in terms or routing ) will be forwarded and freely accepted. We wish to ask RIPE what the policy of the Internet Authorities (RIPE and IANA) is regarding the routing of de-aggregated blocks of an IPv6 /32 PA Block. Can you make a statement regarding this theme? Can you inform about the policies which higher Tier Carriers will (or must) follow in this regard? The proposal to allow up to prefix /36 routes de-aggregations (up to a 4 bit depth) of a /32 block was read with interest, but for our intent does not go far enough. Why not allow de-aggregation up to an 8 bit depth (to /40 for a /32 PA block)? John Collins Eidgenössisches Finanzdepartement Bundesamt für Informatik und Telekommunikation BIT Netzplanung und Engineering BPTKE Monbijoustrasse 74, CH-3003 Bern
I'll be interested in hearing what the rest of the working group has to say on this. When the document was last presented to the group, at the meeting in Lisbon, it was felt that /36 was an appropriate level to limit the worst cases of deaggregation. Is there still a demand for this document to progress?
Every organization is autonomous in terms of its IT infrastructure and in terms of its connection to the Internet.
Is PI a more appropriate fit for this? Rob
Hi, On Mon, Apr 19, 2010 at 04:05:06PM +0100, Rob Evans wrote:
Is there still a demand for this document to progress?
Given this sort of question, I think the answer is obvious: guidance is needed, and not provided yet.
Every organization is autonomous in terms of its IT infrastructure and in terms of its connection to the Internet. Is PI a more appropriate fit for this?
That might be one possible outcome of the recommendation document. Gert Doering -- IPv6 wrangler & APWG chair -- Total number of prefixes smaller than registry allocations: 150584 SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
Hi all,
I'll be interested in hearing what the rest of the working group has to say on this. When the document was last presented to the group, at the meeting in Lisbon, it was felt that /36 was an appropriate level to limit the worst cases of deaggregation.
There was a consensus in Lisbon that /36 deagregation was a reasonnable first step forward. We never said there wouldn't be a second step afterward :)
Is there still a demand for this document to progress?
Yes. I am still facing the same problem as you know and that prevents me for deploying IPv6 in some parts of my network. /40 limit is much clearer and really helps for addressing plans. And remember that does not mean that everyone has to implement this limit: everyone is free to say it doesn't want to see part of the internet. Regards, Jerome -- ------------------------------------------------------------- Jerome Durand Responsable des services aux usagers Services operations & support manager Réseau National de Télécommunications pour la Technologie, l'Enseignement et la Recherche Tel: +33 (0) 1 53 94 20 40 | GIP RENATER Fax: +33 (0) 1 53 94 20 41 | c/o ENSAM E-mail: jdurand@renater.fr | 151 Boulevard de l'Hôpital http://www.renater.fr | 75013 PARIS --------------------------------------------------------------
participants (4)
-
Gert Doering
-
Jerome Durand
-
John.Collins@BIT.admin.ch
-
Rob Evans