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/address-policy-wg@ripe.net/
[address-policy-wg] getting second IPv6 PA as a LIR
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marcin Kuczera
marcin at leon.pl
Mon May 2 20:37:35 CEST 2011
> If you give your customers a single /128, you're forcing *them* to use > NAT. This is bad. > >> Probably the simplest way will be subnet /64 or smaller, where part of >> IP will be MAC address of enduser. > > The strong recommendation is to give your customers something between > a /48 and a /64. NO LESS, unless you know for sure(!) that they only > have a single machine, and no network behind it. ok, I understand the concept.. still have to wait for proper BRAS and CPE implementations... And I understand, that i.e. /64 for subscribers network is something that in IPv4 PI world would be forbidden (i.e. /29). If all of us agree, that there is enough address space for every toothbrush, subscribers can get something between /48 an /64 and this is will be usual, and even in IPv6 PA space there will be no every subnet registration (as I understand, and as it is requiured for IPv4 PA) - why IPv6 PI can not be similar to IPv6 PA then ??? Regards, Marcin
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]