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

RE: Revised Resolution to Issue 319

A few comments:

Section A.1.1 states:

"   The following data also qualifies as "simple data types":

      * Attributes grouped into a logical container, using the
        [RFC2868] tagging mechanism.  This approach is NOT
        RECOMMENDED (see Section 2.1.2), but is permissible where
        the alternatives are worse."

However, Section A.2.1 states:

"      * Tagged data types as described in [RFC2868].
        These data types SHOULD NOT be used in new specifications."

These two paragraphs appear to be in conflict; suggest deletion of the A.2.1
text. 

Section A.2 states:

"   All data types other than the ones described above in Appendix A.1
   and Appendix B SHOULD NOT be used.  This section describes in detail
   a number of data types that are NOT RECOMMENDED in new RADIUS
   specifications."

Similarly, Section A.2.2 states:

"   Does the attribute:

   * define a complex data type not described in Appendix B,"

However, Section A.2.1 states:

"      * Complex data structures defined only within RADIUS.
        SHOULD NOT be used.  This recommendation does not apply to new
        attributes for authentication or security, as described below
        in Section A.2.2."

Recommendation is to delete the material in Section A.2.1 or sync it with
A.2. 



-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of Alan DeKok
Sent: Friday, October 30, 2009 11:20 AM
To: Bernard Aboba
Cc: 'radext mailing list'
Subject: Re: Revised Resolution to Issue 319

Bernard Aboba wrote:
> In looking at the text of Sections 2 and 2.1.1, I would propose to make
> the following changes in Section 2 and 2.1.1 to resolve Issue 319.
> 
> Required changes in Appendix A will following in a separate post.

  I've re-worked both Section 2 and Appendix A to address these
concerns.  A proposed version is available online at:

http://git.freeradius.org/draft-ietf-radext-design-10.txt

  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/>


--
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/>