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

RE: Revisions to RFC 4005 (was RE: Consideration of draft-lior-radius-attribute-type-extension-02.txt)

9.6.2.  Forwarding a RADIUS VSA as a Diameter Vendor Specific AVP

   The Diameter AVP will consist of the following fields:

      Diameter Flags: V=1, M=0, P=0
      Diameter Vendor code = RADIUS VSA Vendor code
      Diameter AVP code = RADIUS VSA Vendor type code
      Diameter AVP length = length of AVP (header + data)
      Diameter Data = RADIUS VSA vendor data
Won't using a RADIUS VSA Vendor code of 0 result in a conflict between the RADIUS 
"extended" attributes and already allocated Diameter AVPs?



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