draft-ietf-radext-vlan-03.txt   draft-ietf-radext-vlan-04.txt 
Network Working Group Paul Congdon Network Working Group Paul Congdon
INTERNET-DRAFT Mauricio Sanchez INTERNET-DRAFT Mauricio Sanchez
Category: Proposed Standard Hewlett-Packard Company Category: Proposed Standard Hewlett-Packard Company
<draft-ietf-radext-vlan-03.txt> Bernard Aboba <draft-ietf-radext-vlan-04.txt> Bernard Aboba
12 April 2006 Microsoft Corporation 29 April 2006 Microsoft Corporation
RADIUS Attributes for Virtual LAN and Priority Support RADIUS Attributes for Virtual LAN and Priority Support
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 32 skipping to change at page 1, line 32
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 10, 2006. This Internet-Draft will expire on November 10, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society 2006. Copyright (C) The Internet Society 2006.
Abstract Abstract
This document proposes additional RADIUS (Remote Authentication Dial This document proposes additional RADIUS (Remote Authentication Dial
In User Service) attributes for dynamic Virtual LAN assignment and In User Service) attributes for dynamic Virtual LAN assignment and
prioritization, for use in provisioning of access to IEEE 802 local prioritization, for use in provisioning of access to IEEE 802 local
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1.2 Requirements Language ........................... 3 1.2 Requirements Language ........................... 3
1.3 Attribute Interpretation ........................ 3 1.3 Attribute Interpretation ........................ 3
2. Attributes ............................................ 4 2. Attributes ............................................ 4
2.1 Egress-VLANID ................................... 4 2.1 Egress-VLANID ................................... 4
2.2 Ingress-Filters ................................. 5 2.2 Ingress-Filters ................................. 5
2.3 Egress-VLAN-Name ................................ 6 2.3 Egress-VLAN-Name ................................ 6
2.4 User-Priority-Table ............................. 7 2.4 User-Priority-Table ............................. 7
3. Table of Attributes ................................... 9 3. Table of Attributes ................................... 9
4. Diameter Considerations ............................... 9 4. Diameter Considerations ............................... 9
5. IANA Considerations ................................... 9 5. IANA Considerations ................................... 9
6. Security Considerations ............................... 9 6. Security Considerations ............................... 10
7. References ............................................ 10 7. References ............................................ 10
7.1 Normative References ............................ 10 7.1 Normative References ............................ 10
7.2 Informative References .......................... 11 7.2 Informative References .......................... 11
ACKNOWLEDGMENTS .............................................. 11 ACKNOWLEDGMENTS .............................................. 12
AUTHORS' ADDRESSES ........................................... 12 AUTHORS' ADDRESSES ........................................... 12
Intellectual Property Statement............................... 12 Intellectual Property Statement............................... 13
Disclaimer of Validity........................................ 13 Disclaimer of Validity........................................ 13
Full Copyright Statement ..................................... 13 Full Copyright Statement ..................................... 13
1. Introduction 1. Introduction
This document describes Virtual LAN (VLAN) and re-prioritization This document describes Virtual LAN (VLAN) and re-prioritization
attributes that may prove useful for provisioning of access to IEEE attributes that may prove useful for provisioning of access to IEEE
802 local area networks [IEEE-802] with the Remote Authentication 802 local area networks [IEEE-802] with the Remote Authentication
Dialin User Service (RADIUS). Dialin User Service (RADIUS).
skipping to change at page 3, line 36 skipping to change at page 3, line 36
A device that provides an access service for a user to a network. A device that provides an access service for a user to a network.
1.2. Requirements Language 1.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
1.3. Attribute Interpretation 1.3. Attribute Interpretation
The attributes described in this document apply to a single instance
of a NAS port, or more specifically an IEEE 802.1Q bridge port.
[IEEE-802.1Q] [IEEE-802.1D] and [IEEE-802.1X] do not recognize finer
management granularity than "per port". In some cases, such as with
IEEE 802.11 wireless LANs, the concept of a "virtual port" is used in
place of the physical port. Such virtual ports are typically based
on security associations and scoped by station, or MAC address.
The attributes defined in this document are applied on per user basis
and it is expected that there is a single user per port; however in
some cases that port may be a "virtual port". If a NAS
implementation conforming to this document supports "virtual ports",
it may be possible to provision those "virtual ports" with unique
values of the attributes described in this document, allowing
multiple users sharing the same physical port to each have a unique
set of authorization parameters.
If a NAS conforming to this specification receives an Access-Accept If a NAS conforming to this specification receives an Access-Accept
packet containing an attribute defined in this document which it packet containing an attribute defined in this document which it
cannot apply, it MUST act as though it had received an Access-Reject. cannot apply, it MUST act as though it had received an Access-Reject.
[RFC3576] requires that a NAS receiving a Change of Authorization
Similarly, [RFC3576] requires that a NAS receiving a Change of Request (CoA-Request) reply with a CoA-NAK if the Request contains an
Authorization Request (CoA-Request) containing an unsupported unsupported attribute. It is recommended that an Error-Cause
attribute reply with a CoA-NAK. It is recommended that an Error- attribute with value set to "Unsupported Attribute" (401) be included
Cause attribute with value set to "Unsupported Attribute" (401) be in the CoA-NAK. As noted in [RFC3576], authorization changes are
included in the packet. As noted in [RFC3576], authorization changes atomic so that this situation does not result in session termination
are atomic so that this situation does not result in session and the pre-existing configuration remains unchanged. As a result,
termination and the pre-existing configuration remains unchanged. As no accounting packets should be generated.
a result, no accounting packets should be generated.
2. Attributes 2. Attributes
2.1. Egress-VLANID 2.1. Egress-VLANID
Description Description
The Egress-VLANID attribute represents an allowed IEEE 802 Egress The Egress-VLANID attribute represents an allowed IEEE 802 Egress
VLANID for this port, indicating if the VLANID is allowed for VLANID for this port, indicating if the VLANID is allowed for
tagged or untagged packets as well as the VLANID. tagged or untagged frames as well as the VLANID.
As defined in [RFC3580], the VLAN assigned via tunnel attributes
applies both to the ingress VLANID for untagged packets (known as
the PVID) and the egress VLANID for untagged packets. In
contrast, the Egress-VLANID attribute configures only the egress
VLANID for either tagged or untagged packets. The Egress-VLANID
attribute MAY be included in the same RADIUS packet as [RFC3580]
tunnel attributes; however, the Egress-VLANID attribute is not
necessary if it is being used to configure the same untagged
VLANID included in tunnel attributes. To configure an untagged
VLAN for both ingress and egress, the tunnel attrubutes of
[RFC3580] MUST be used.
Multiple Egress-VLANID attributes MAY be included in Access- Multiple Egress-VLANID attributes MAY be included in Access-
Request, Access-Accept, CoA-Request or Accounting-Request packets; Request, Access-Accept, CoA-Request or Accounting-Request packets;
this attribute MUST NOT be sent within an Access-Challenge, this attribute MUST NOT be sent within an Access-Challenge,
Access-Reject, Disconnect-Request, Disconnect-ACK, Disconnect-NAK, Access-Reject, Disconnect-Request, Disconnect-ACK, Disconnect-NAK,
CoA-ACK or CoA-NAK. Each attribute adds the specified VLAN to the CoA-ACK or CoA-NAK. Each attribute adds the specified VLAN to the
list of allowed egress VLANs for the port. list of allowed egress VLANs for the port.
The Egress-VLANID attribute is shown below. The fields are The Egress-VLANID attribute is shown below. The fields are
transmitted from left to right: transmitted from left to right:
skipping to change at page 7, line 39 skipping to change at page 8, line 13
Bridges and MACs in the transmission path... Bridges and MACs in the transmission path...
Under normal circumstances, user priority is not modified in Under normal circumstances, user priority is not modified in
transit through the relay function of a Bridge; however, transit through the relay function of a Bridge; however,
network management can control how user priority is propagated. network management can control how user priority is propagated.
Table 7-1 provides the ability to map incoming user priority Table 7-1 provides the ability to map incoming user priority
values on a per-Port basis. By default, the regenerated user values on a per-Port basis. By default, the regenerated user
priority is identical to the incoming user priority. priority is identical to the incoming user priority.
This attribute represents the IEEE 802 prioritization that will be This attribute represents the IEEE 802 prioritization that will be
applied to packets arriving at this port. There are eight applied to frames arriving at this port. There are eight possible
possible user priorities, according to the [IEEE-802] standard. user priorities, according to the [IEEE-802] standard.
[IEEE-802.1D] clause 14.6.2.3.3 specifies the regeneration table [IEEE-802.1D] clause 14.6.2.3.3 specifies the regeneration table
as 8 values, each an integer in the range 0-7. The management as 8 values, each an integer in the range 0-7. The management
variables are described in clause 14.6.2.2. variables are described in clause 14.6.2.2.
A single User-Priority-Table attribute MAY be included in an A single User-Priority-Table attribute MAY be included in an
Access-Accept or CoA-Request packet; this attribute MUST NOT be Access-Accept or CoA-Request packet; this attribute MUST NOT be
sent within an Access-Request, Access-Challenge, Access-Reject, sent within an Access-Request, Access-Challenge, Access-Reject,
Disconnect-Request, Disconnect-ACK, Disconnect-NAK, CoA-ACK, CoA- Disconnect-Request, Disconnect-ACK, Disconnect-NAK, CoA-ACK, CoA-
NAK or Accounting-Request. Since the regeneration table is only NAK or Accounting-Request. Since the regeneration table is only
maintained by a bridge conforming to [IEEE-802.1D], this attribute maintained by a bridge conforming to [IEEE-802.1D], this attribute
skipping to change at page 8, line 33 skipping to change at page 9, line 7
10 10
String String
The String field is 8 octets in length, and includes a table which The String field is 8 octets in length, and includes a table which
maps the incoming priority (if it is set - the default is 0) into maps the incoming priority (if it is set - the default is 0) into
one of eight regenerated priorities. The first octet maps to one of eight regenerated priorities. The first octet maps to
incoming priority 0, the second octet to incoming priority 1, etc. incoming priority 0, the second octet to incoming priority 1, etc.
The values in each octet represent the regenerated priority of the The values in each octet represent the regenerated priority of the
packet. frame.
It is thus possible to either remap incoming priorities to more It is thus possible to either remap incoming priorities to more
appropriate values; to honor the incoming priorities; or to appropriate values; to honor the incoming priorities; or to
override any incoming priorities, forcing them to all map to a override any incoming priorities, forcing them to all map to a
single chosen priority. single chosen priority.
The [IEEE-8021.D] specification, Annex G, provides a useful The [IEEE-8021.D] specification, Annex G, provides a useful
description of traffic type - traffic class mappings. description of traffic type - traffic class mappings.
3. Table of Attributes 3. Table of Attributes
skipping to change at page 10, line 23 skipping to change at page 10, line 36
or proxy from inserting attributes with malicious intent. or proxy from inserting attributes with malicious intent.
VLAN attributes sent by a RADIUS server or proxy may enable access to VLAN attributes sent by a RADIUS server or proxy may enable access to
unauthorized VLANs. These vulnerabilities can be limited by unauthorized VLANs. These vulnerabilities can be limited by
performing authorization checks at the NAS. For example, a NAS can performing authorization checks at the NAS. For example, a NAS can
be configured to accept only certain VLANIDs from a given RADIUS be configured to accept only certain VLANIDs from a given RADIUS
server/proxy. server/proxy.
Similarly, an attacker gaining control of a RADIUS server or proxy Similarly, an attacker gaining control of a RADIUS server or proxy
can modify the user priority table, causing either degradation of can modify the user priority table, causing either degradation of
quality of service (by downgrading user priority of packets arriving quality of service (by downgrading user priority of frames arriving
at a port), or denial of service (by raising the level of priority of at a port), or denial of service (by raising the level of priority of
traffic at multiple ports of a device, oversubscribing the switch or traffic at multiple ports of a device, oversubscribing the switch or
link capabilities). link capabilities).
7. References 7. References
7.1. Normative references 7.1. Normative references
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March, 1997. Requirement Levels", RFC 2119, March, 1997.
skipping to change at page 11, line 12 skipping to change at page 11, line 27
IEEE Standards for Local and Metropolitan Area Networks: Media IEEE Standards for Local and Metropolitan Area Networks: Media
Access Control (MAC) Bridges, IEEE Std 802.1D-2004, June 2004. Access Control (MAC) Bridges, IEEE Std 802.1D-2004, June 2004.
[IEEE-802.1Q] [IEEE-802.1Q]
IEEE Standards for Local and Metropolitan Area Networks: Draft IEEE Standards for Local and Metropolitan Area Networks: Draft
Standard for Virtual Bridged Local Area Networks, Standard for Virtual Bridged Local Area Networks,
P802.1Q-2003, January 2003. P802.1Q-2003, January 2003.
7.2. Informative references 7.2. Informative references
[IEEE802.1X] [IEEE-802.1X]
IEEE Standards for Local and Metropolitan Area Networks: Port IEEE Standards for Local and Metropolitan Area Networks: Port
based Network Access Control, IEEE Std 802.1X-2004, December based Network Access Control, IEEE Std 802.1X-2004, December
2004. 2004.
[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
Implementation in Roaming", RFC 2607, June 1999. Implementation in Roaming", RFC 2607, June 1999.
[RFC2868] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M. [RFC2868] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M.
and I. Goyret, "RADIUS Attributes for Tunnel Protocol and I. Goyret, "RADIUS Attributes for Tunnel Protocol
Support", RFC 2868, June 2000. Support", RFC 2868, June 2000.
 End of changes. 12 change blocks. 
21 lines changed or deleted 49 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/