Last comments on design guidelines document

[Alan DeKok <aland@deployingradius.com>]

  The following text should be added to the document during the RFC
editor process, as suggested in the call last week:


1) Note on "MUST" and "MUST NOT" in the text.  Section 1.3, before the
final paragraph, add the following new sentence:


   The suggestions given below specify no mandatory behavior
   on new implementations.  The uses of "MUST" and "MUST NOT" in this
   document are limited to (a) requirements to follow the IETF process
   for IETF standards, and (b) quotes from other documents.

   The advice in this document applies to attributes used to encode
   ...


2) Notes on attributes for authentication and security.  Section A.2.2.
 Current text:

   * That a RADIUS server and/or client is expected to parse?
     i.e. A type that cannot be treated as opaque data (Section A.1.3)

Replacement text:

   * That a RADIUS server and/or client is expected to parse, validate,
     or create the contents of via a computation?
     i.e. A type that cannot be treated as opaque data (Section A.1.3)

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>