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] [Ext] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
- Previous message (by thread): [address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 Review Phase *extended* (IPv6 Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maximilian Wilhelm
max at rfc2324.org
Wed Nov 8 17:57:25 CET 2017
Anno domini 2017 Andrea Cima scripsit: Hi Andrea, > The RIPE NCC currently reserves a /26 for every allocation up to a /29. For > allocations larger than a /29, the next three bits are reserved. > > This is based on a policy requirement that the RIPE NCC should maximise the > potential for subsequent allocations to be contiguous with previous > allocations: > https://www.ripe.net/publications/docs/ripe-684#aggregation Could you elaborate on what you do behind the scenes for an PI assignment? I guess you reserve more than the /48 for a possible subsequent assignment? Thanks! Best Max -- Alles sollte so einfach wie möglich gemacht sein. Aber nicht einfacher. (Einstein)
- Previous message (by thread): [address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 Review Phase *extended* (IPv6 Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]