RFC 7268 on RADIUS Attributes for IEEE 802 Networks
rfc-editor@rfc-editor.org Thu, 17 July 2014 19:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 849AA1A0103 for <ietf-announce@ietfa.amsl.com>; Thu, 17 Jul 2014 12:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4-A-Ss72uvG for <ietf-announce@ietfa.amsl.com>; Thu, 17 Jul 2014 12:18:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 545531A010C for <ietf-announce@ietf.org>; Thu, 17 Jul 2014 12:18:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4C23A18044F; Thu, 17 Jul 2014 12:17:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7268 on RADIUS Attributes for IEEE 802 Networks
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140717191710.4C23A18044F@rfc-editor.org>
Date: Thu, 17 Jul 2014 12:17:10 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/PIDBYNCPJKMVJI8ubFxwBPIqJGQ
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2014 19:18:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7268
Title: RADIUS Attributes for IEEE 802
Networks
Author: B. Aboba, J. Malinen,
P. Congdon, J. Salowey,
M. Jones
Status: Standards Track
Stream: IETF
Date: July 2014
Mailbox: Bernard_Aboba@hotmail.com,
j@w1.fi,
paul.congdon@tallac.com,
jsalowey@cisco.com,
mark@azu.ca
Pages: 29
Characters: 56686
Updates: RFC 3580, RFC 4072
I-D Tag: draft-ietf-radext-ieee802ext-12.txt
URL: http://www.rfc-editor.org/rfc/rfc7268.txt
RFC 3580 provides guidelines for the use of the Remote Authentication
Dial-In User Service (RADIUS) within IEEE 802 local area networks
(LANs). This document defines additional attributes for use within
IEEE 802 networks and clarifies the usage of the EAP-Key-Name
Attribute and the Called-Station-Id Attribute. This document
updates RFCs 3580 and 4072.
This document is a product of the RADIUS EXTensions Working Group of the IETF.
This is now a Proposed Standard.
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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC