<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=DE-CH link=blue vlink=purple> <div class=Section1> Dear RIPE Routing Working Group,<o:p></o:p> <o:p> </o:p> 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 ( <a href="http://www.ripe.net/ripe/maillists/archives/routing-wg/2009/msg00120.html">http://www.ripe.net/ripe/maillists/archives/routing-wg/2009/msg00120.html</a> ).<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> 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?<o:p></o:p> <o:p> </o:p> 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)?<o:p></o:p> John Collins Eidgen�ssisches Finanzdepartement Bundesamt f�r Informatik und Telekommunikation BIT Netzplanung und Engineering BPTKE Monbijoustrasse 74, CH-3003 Bern<o:p></o:p> <o:p> </o:p> <o:p></o:p> </div> </body> </html>