Submitter name: Bernard Aboba
Submitter email address: bernard_aboba@hotmail.com
Date first submitted: July 31, 2009
Reference:
Document: Design-Guidelines
Comment type: Editorial
Priority: S
Section: 2.2, 3, 6.1
Rationale/Explanation of issue:
In Section 2.2 and 3 the Design Guidelines document contains normative language relating to the Extended Attributes document. This has resulted in a normative dependency on that document. Given that the Extended Attributes document is not yet completed, and can contain its own usage guidelines, is the normative reference appropriate?
2.2. Extended RADIUS Attributes
The extended RADIUS attribute document [EXTEN] defines a number of extensions to RADIUS. The standard attribute space is extended by permitting standard allocations from within a specific subset of the VSA space; the format of extended attributes is defined; and extended data types are defined within that format. New specifications seeking to extend the standard RADIUS data model SHOULD examine [EXTEN] to see if their needs fit within the extended RADIUS data model.From Section 3:Recent extensions to the RADIUS data model such as [EXTEN] make it possible to minimize the use of complex attributes. New specifications seeking to extend the standard RADIUS data model SHOULD examine [EXTEN] to see if their needs fit within the extended RADIUS data model.Proposed Resolution: Discuss
Join me |