[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: draft-aboba-radius-iana-04.txt



--On tirsdag, april 08, 2003 17:53:46 -0500 Thomas Narten <narten@us.ibm.com> wrote:

Here are my comments on this draft.


Where a specification is required, this MUST be an Internet-Draft or
RFC. For Designated Expert with Specification Required, the request is
posted to the AAA WG mailing list (or a successor designated by the Area
Director) for comment and review, and MUST include an Internet-Draft or
RFC.

Note. "Specification Required" as defined in 2434 does not allow an ID
to be used, as IDs are not (supposed to be) "permanent". 2434 says:


      Specification Required - Values and their meaning must be
            documented in an RFC or other permanent and readily available
            reference, in sufficient detail so that interoperability
            between independent implementations is possible.

I suspect what you are intending here is an ID with the intention of
publishing it as an RFC. But that is a bit tricky to specify. Is that
what the intention is?
I think the missing words are that for Specification Required with an RFC, allocation will happen as part of the RFC publication process.
For non-RFC specs, there is a deadlock problem if they want the assigned number in the spec but can't get the number before the spec is published - no shining ideas on how that should be solved.

Also, one would be requesting a radius code point for an existing RFC?
That seems odd, but is also implied as normal by the above.

Also, the document needs a security considerations section.

Thomas