Re: IANA Considerations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IANA Considerations
- To: Brian E Carpenter <brc at zurich.ibm.com>
- Subject: Re: IANA Considerations
- From: Ned Freed <ned.freed at mrochek.com>
- Date: Mon, 13 Jun 2005 07:33:39 -0700 (PDT)
- Cc: Thomas Narten <narten at us.ibm.com>, Ned Freed <ned.freed at mrochek.com>, Pekka Savola <pekkas at netcore.fi>, John C Klensin <john-ietf at jck.com>, Bruce Lilly <blilly at erols.com>, Steven M Bellovin <smb at cs.columbia.edu>, ietf at ietf.org
- In-reply-to: "Your message dated Mon, 13 Jun 2005 10:03:52 +0200" <42AD3DE8.7040701@zurich.ibm.com>
- List-help: <mailto:ietf-request@ietf.org?subject=help>
- List-id: IETF-Discussion <ietf.ietf.org>
- List-post: <mailto:ietf@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
- References: <ned.freed@mrochek.com> <01LP9982FXHW00004T@mauve.mrochek.com> <200506101135.j5ABZKbF022040@cichlid.raleigh.ibm.com> <01LPAGP5WBT600004T@mauve.mrochek.com> <Pine.LNX.4.61.0506101936510.8038@netcore.fi> <01LPALL0X39A00004T@mauve.mrochek.com> <42AD3DE8.7040701@zurich.ibm.com>
- Sender: ietf-bounces at ietf.org
> It is the requirement that Internet Drafts always contain IANA
> considerations sections that has to go.
Ned, you have not produced any argument for this position, and since
the absence of such a section does not imply the absence of IANA
considerations, your logic continues to escape me.
Repeating for about the fourth time...
The argument against it is that requiring the section in the absence of actual
IANA considerations simply adds to the amount of required stuff we have in our
documents that serves no real purpose. We have way too much of this junk
already and attempts to require more need to be resisted.
The only reason to have it would as an indicator that a check for IANA
considerations was done and none were found. But the problem with that is that
there's no way to distinguish between a careful review leading to the prduction
of "no considerations" text and the text being added with little if any review
just "to make the IESG happy". And we already have at least one example where
this appears to have happened.
The argument for the mandatory presence of such a section is that
it increases the probability that any IANA considerations have been
identified.
I disagree. I don't think it increases the probability much if at all, and in
fact may actually decrease it. And even if it did increase the probability
slightly, the benefit of that increase needs to be weighed against the cost,
and I don't think it measures up.
Ned
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions
of the senders and do not imply endorsement by the IETF.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.