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/[email protected]/
[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 ]
Leo Vegoda
leo.vegoda at icann.org
Mon May 2 16:55:15 CEST 2011
You wrote: > If you give your customers a single /128, you're forcing *them* to use NAT. This is bad. And they wouldn't be able to use stateless auto-configuration or RFC 3041 privacy extensions. > > 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. Even if they only have one machine there are advantages to assigning at least a /64. Regards, Leo
- 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 ]