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

RE: [Issue] Diameter compatibility of VLAN-00

Good point.  For example, RFC 4372 Section 4 says:

"   Diameter needs to define an identical attribute with the same Type
  value.  The CUI should be available as part of the NASREQ application
  [RFC4005]."
Something along those lines might work here. Since the RADIUS Type values would already have been allocated, Diameter would inherit these attributes, but still needs to define their behavior. It seems like these attributes would be used primarily with the Diameter EAP application (wouldn't CUI be used there too?), and perhaps Diameter NASREQ. 

One question comes to mind though.
Diameter requires a new application ID to be allocated when mandatory attributes are added. I'm not sure whether use of these attributes with Diameter EAP or Diameter NASREQ would require that, however. 



From: "Greg Weber (gdweber)" <gdweber@cisco.com>
To: <radiusext@ops.ietf.org>
Subject: [Issue]  Diameter compatibility of VLAN-00
Date: Tue, 21 Feb 2006 17:34:42 -0500


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




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