[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 4675 on RADIUS Attributes for Virtual LAN and Priority Support
A new Request for Comments is now available in online RFC libraries.
RFC 4675
Title: RADIUS Attributes for Virtual LAN
and Priority Support
Author: P. Congdon, M. Sanchez,
B. Aboba
Status: Standards Track
Date: September 2006
Mailbox: paul.congdon@hp.com,
mauricio.sanchez@hp.com,
bernarda@microsoft.com
Pages: 15
Characters: 29751
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-radext-vlan-06.txt
URL: http://www.rfc-editor.org/rfc/rfc4675.txt
This document proposes additional Remote Authentication Dial-In User
Service (RADIUS) attributes for dynamic Virtual LAN assignment and
prioritization, for use in provisioning of access to IEEE 802 local
area networks. These attributes are usable within either RADIUS or
Diameter. [STANDARDS TRACK]
This document is a product of the RADIUS EXTensions
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is
unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
--
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/>