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] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Previous message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Next message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Thu Apr 16 10:32:06 CEST 2009
Hi Geoff, > Perhaps I may be permitted to add some background data here. Ofcourse! Thank you :) > My interpretation of the relative roles of the RIRs, IANA and the IETF > in this area is that such reservations, as distinct from allocations or > assignments, should be performed by the IANA, and for IANA to undertake > this it should be part of the protocol's address plan, and hence should > be published as an RFC. i.e. as far as I understand the situation such > reservations of number resources for documentation purposes falls to > IANA to perform, and the instructions to IANA are in the form of a > published RFC. The logical inference is that such proposals should head > to the IETF rather than the RIRs. I had the same feeling, but it's good to get this background information. Thanks, Sander
- Previous message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
- Next message (by thread): [address-policy-wg] Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]