[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Diameter compatibility of VLAN-00
How would this work?
Fix the typo.
Insert a section 4 that says the following:
4. Diameter Considerations
Diameter needs to define identical attributes with the same Type
values. The attributes should be available as part of the NASREQ
application [RFC4005], as well as the Diameter EAP application
[RFC4072].
Add Informative references to [RFC4005] and [RFC4072].
-----------------------------------------------------------------------------------------
Description of issue: Diameter compatibility of VLAN-00
Submitter name: Greg Weber
Submitter email address: gdweber@cisco.com
Date first submitted: February 21, 2006
Reference: NA
Document: VLAN-00
Comment type: Editorial
Priority: S
Section: NA
Rationale/Explanation of issue:
In the RADEXT charter, I see:
"...all RADEXT WG work items MUST contain a Diameter
compatibility section, outlining how interoperability
with Diameter will be maintained."
The VLAN draft does not contain a Diameter compatibility
section, but does mention (in the abstract) that these
attributes can be used with Diameter.
Requested change:
The table of attributes in section 3 shows which attributes
may be in which RADIUS messages. Maybe another similar
table is needed in a Diameter Compatibility section showing
which Diameter applications/messages may include these attributes.
Also, I see one typo that wasn't in the previous version :)
Section 1.3: 'Unsupported Attribute"' ->
'"Unsupported Attribute"' (missing double quote).
--
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/>