[address-policy-wg] Those pesky ULAs again
JORDI PALET MARTINEZ jordi.palet at consulintel.es
Tue May 29 15:53:35 CEST 2007
The smaller subnet in IPv6, if you want to keep autoconfiguration and other things working, is /64, so why you want something smaller coming from the RIRs ? In addition to that, if you want to allow subneting for your customers and your own network, you need extra bits for that. So that's why typically you will get a minimum of /32 block from the RIR and customers will get a /48 from you. Regards, Jordi > De: Jørgen Hovland <jorgen at hovland.cx> > Responder a: <address-policy-wg-admin at ripe.net> > Fecha: Tue, 29 May 2007 15:11:02 +0200 > Para: 'Roger Jørgensen' <roger at jorgensen.no> > CC: 'Stephen Sprunk' <stephen at sprunk.org>, 'ARIN PPML' <ppml at arin.net>, > <address-policy-wg at ripe.net> > Asunto: RE: [address-policy-wg] Those pesky ULAs again > > > > -----Original Message----- > From: address-policy-wg-admin at ripe.net > [mailto:address-policy-wg-admin at ripe.net] On Behalf Of Roger Jørgensen > >> 1.) get ula-central and know for sure we won´t get into this issue ever >> again. >> >> 2.) administrate our own local version of ULA-central for the organization we >> co-operate with >> >> 3.) get RIR-space with all the add on administration and documentation... >> For me, only option 1.) is a real option, the other two are just >> work-around since we don´t need global routing of the address space in >> question. > > > The RIRs already provide globally unique address space. This is what you want. > Both ULA-C and the RIRs do not guarantee global routability anyway. > > ULA-L is never globally unique, so basically there is no such thing as "Unique > Locally Assigned" addresses. > > > Q: Is it correct that you can get a /26 IPv4 PA block, but you can't get a /96 > IPv6 PA block? Why is that? > > Cheers, > > J > > ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.