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 ]
Gert Doering
gert at space.net
Wed Apr 27 08:36:00 CEST 2011
Hi, On Tue, Apr 26, 2011 at 11:10:15PM -0400, Martin Millnert wrote: > Personally I'd much prefer if the policies were aligned with reality > better, since it would allow us to get rid of the more or less > arbitrary policy-interpreting role the IPRA:s at the RIPE NCC has for > v6 resources today. This would make the landscape much more honest and > just. After all, it's just bits anyway. It's on our agenda for next week's APWG meeting, in the Thursday 11:00-12:30 time slot. (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!) Gert Doering -- NetMaster -- did you enable IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
- 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 ]