Re: Diameter Considerations Section (VLAN/Priority, Delegated Prefix, etc.)

[Jari Arkko <jari.arkko@piuha.net>]

Greg Weber (gdweber) wrote:

>>
>>   When used in Diameter, the attributes defined in this
>>   specification can be used as Diameter AVPs from the
>>   Code space 1-255, i.e., RADIUS attribute compatibility
>>   space. No additional Diameter Code values are therefore
>>   allocated. The data types of the attributes are as
>>   follows:
>>
>>     Egress-VLANID                     OctetString
>>     Ingress-Filters                   Enumerated
>>     Egress-VLAN-Name                  UTF8String
>>     User-Priority-Table               OctetString
>>
>>   The attributes in this specification have no special
>>   translation requirements for Diameter to RADIUS or
>>   RADIUS to Diameter gateways, i.e., the attributes
>>   are copied as is, except for changes relating to
>>   headers, alignment, and padding. See also
>>   [RFC 3588] Section 4.1 and [RFC 4005] Section 9.
>>    
>>
>
>GDW> In section 4.1 of RFC 3588, I see:
>      Unless otherwise noted, AVPs will have the following default AVP
>      Flags field settings:
>
>         The 'M' bit MUST be set.  The 'V' bit MUST NOT be set.
>
>Is the M-bit supposed to be set for these RADIUS attrs?
>  
>
Good question. Based on Section 1.3 of the vlan document,
I believe the M bit may have to be set in AA-Answer message.

There may be other issues like that -- please review the text
carefully.

--Jari


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