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] 2008-02 Moved to Review Phase (Assigning IPv6 PA to Every LIR)
- Previous message (by thread): [address-policy-wg] 2008-02 Moved to Review Phase (Assigning IPv6 PA to Every LIR)
- Next message (by thread): [address-policy-wg] 2008-02 Moved to Review Phase (Assigning IPv6 PA to Every LIR)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
James A. T. Rice
james_r-ripelist at jump.org.uk
Wed Mar 19 16:21:55 CET 2008
> Assigning IPv6 PA to Every LIR > > If this proposal reaches consensus, RIPE NCC will conduct a one-time > operation to allocate an IPv6 block to every LIR that does not have > any existing IPv6 allocation. Yes, go for it. > One can expect to see 4,715 new more entries on the routing system. > However, all these entries would be on the minimum allocation size, so > significant fragmentation/aggregation impact can be expected. I assume the expected fragmentation aspect is due to future requests having to be made since the original assignment to the LIR was only a /32 when something larger would have been useful. Simply keeping the existing system of spacing assignments such that they can be expanded up to a /29 in future if required should avoid this problem. You could probably space assignments for larger members such that they can expand to greater than a /29 in future if needed. Regards James
- Previous message (by thread): [address-policy-wg] 2008-02 Moved to Review Phase (Assigning IPv6 PA to Every LIR)
- Next message (by thread): [address-policy-wg] 2008-02 Moved to Review Phase (Assigning IPv6 PA to Every LIR)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]