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] RIPE-471 and suballocations
- Previous message (by thread): [address-policy-wg] RIPE-471 and suballocations
- Next message (by thread): [address-policy-wg] Legal advice on final /8 policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Tue Oct 6 15:25:10 CEST 2009
Hello Hank, > I have been looking over RIPE-471 section 9: > http://www.ripe.net/docs/ipv4-policies.html#9 > and noticed that only some "status" categories are listed as "Sub- > allocations cannot be made from this type of address space". > Therefore I would have assumed that any status not listed as "Sub- > allocations cannot be made from this type of address space" would > allow sub-allocations. That is incorrect - for example - ASSIGNED > PI does not allow sub-allocations. Parts of any anything that has been assigned can not be allocated/sub- allocated/assigned. Only parts of allocations can be sub-allocated or assigned. The "Sub-allocations cannot be made from this type of address space." is only meant to mark allocation types that can not contain sub-allocations. I understand your confusion though. > Can the doc please updated so it reflects correctly the s/w? There is work being done to clear up the RIPE documents without changing the meaning. I think this fits nicely into that effort. Once this document gets cleaned up the new proposed version will be posted to this mailing list for review. Thank you, Sander Steffann APWG co-chair
- Previous message (by thread): [address-policy-wg] RIPE-471 and suballocations
- Next message (by thread): [address-policy-wg] Legal advice on final /8 policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]