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
Sun May 1 23:03:34 CEST 2011
> (And towards Marcin: if these policies stop you from assigning /128 to > end customers, that was partly the intention. Customers are supposed to > receive at least a /64, or better a /56 or /48 - which is why LIRs can get > a huge block of addresses quite easily. Don't return into IPv4 > "single-address-plus-NAT" land!) Well, we have never had used NAT, that's not good when you want to be serious ISP. /128 is just an example. Probably the simplest way will be subnet /64 or smaller, where part of IP will be MAC address of enduser. 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 ]