radext-11----Page:11
1  2  3  4  5  6  7  8  9  10  11  12  13  14 

Document Outline (cont’d)
Section 3: Data Model Issues
Section 3.1 Vendor Space
Recommendation: IETF should separate review, publication and allocation processes
IETF should encourage publication of SDO RADIUS attribute specifications as RFCs.
IETF should support SDOs in designing their own RADIUS attributes by publishing Design Guidelines and providing review (such as via RADEXT mailing list or AAA Doctors)
RADIUS attribute specifications intended primarily for use within an SDO (or even more than one SDO) should be allocated from the vendor space, not the RADIUS standard space.
Section 3.2 Polymorphic Attributes
Definition: An attribute whose format is dynamic.
Polymorphism is NOT RECOMMENDED.


PPT Version