[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Duplication: Remove most of section 3.3.2 and all of 3.3.4 ofdraft-ietf-ipsec-ikev2
On Tue, 17 Jun 2003, Theodore Ts'o wrote:
> None of the code points in the IKEV2 document are authoratative; that
> honor belongs to the IANA registry. Yet, they are useful because
> there are a useful guide to initial implementors. It is for that
> reason that I believe a little duplication can be a good thing.
> Otherwise, one could argue that all of the tables in IKEv2 are
> duplicative of the IANA registry, and therefore aren't needed; we
> should just establish the IANA registry and just delete all of the
> tables from the I-D (and from every other RFC that has initial
> codepoint values in them).
FWIW, this position is consistent with a recent IESG decision that
initial versions of IANA-maintained MIB modules (which are a special
type of registry) shall be published in an RFC, but shall be
accompanied by a normative reference to the actual IANA registry URL
and a note stating that the version maintained in that registry is
the definitive one.