RE: Issue 190: Relationship of Tunnel and Egress-VLAN attributes

["Bernard Aboba" <bernard_aboba@hotmail.com>]

How about this for Section 2.3?

"The tunnel attributes described in [RFC3580] and the Egress-VLAN-Name
attribute both can be used to configure the egress VLAN for
untagged packets.  These attributes can be used concurrently and MAY
appear in the same RADIUS packet.  When they do appear concurrently,
the list of allowed VLANs is the concatenation of the
Egress-VLAN-Name and the Tunnel-Private-Group-ID (81)
attributes.

The Egress-VLAN-Name attribute does not alter the ingress VLAN for untagged 
traffic
on a port (also known as the PVID).  The tunnel attributes from
[RFC3580] should be relied upon instead to set the PVID."


> From: "Sanchez, Mauricio (ProCurve)" <mauricio.sanchez@hp.com>
> To: "Bernard Aboba" <bernard_aboba@hotmail.com>,<radiusext@ops.ietf.org>
> Subject: Issue 190: Relationship of Tunnel and Egress-VLAN attributes
> Date: Sun, 30 Apr 2006 11:12:36 -0700
>
>
> Bernard,
>
> I'm satisfied with the modification made to section 2.1.  However, I
> also asked that a similar statement be added to section 2.3.  This would
> remove any possibility of ambiguity.
>
> MS



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