[radext] Fwd: RFC 7268 on RADIUS Attributes for IEEE 802 Networks

Benoit Claise <bclaise@cisco.com> Thu, 17 July 2014 19:26 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E5671A01C5 for <radext@ietfa.amsl.com>; Thu, 17 Jul 2014 12:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 nshBPd7bSOd3 for <radext@ietfa.amsl.com>; Thu, 17 Jul 2014 12:26:41 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B39101A01C6 for <radext@ietf.org>; Thu, 17 Jul 2014 12:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8461; q=dns/txt; s=iport; t=1405625197; x=1406834797; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=POk/aca08avZNdL12eaBPZsiBNdeWra5mT9fLqLABOY=; b=dfzrykPXXqJrPJn9RFgzqv+MesDO2J7k9whyfxSpPkgZsCk9RwKdY0s6 jRtAPJny7JY9VrskIybayFqjQsY2VbSmG7gxmwU9B++PJ8SmK9tV32nYy Qik0tVDlGmmLbE51ZTrTiyjbPvTJnsBB8gCpzULvbR1Rm6/NUo6srjl84 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArYEAOwiyFOtJssW/2dsb2JhbABZg2BXsAuTeQEJh0MBgR12hAMBAQEEAQEBSyoNBBwDAQIKAxMPCQMCAQIBFQoVBwIIBg0GAgEBBQsHAgSIDQMRDcVLF4wcgQKBWkIYBoRABZkggX+BTIVIhnwDhhmDRjsvAYEL
X-IronPort-AV: E=Sophos;i="5.01,679,1400025600"; d="scan'208,217";a="111047763"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 17 Jul 2014 19:26:35 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s6HJQYKg003549 for <radext@ietf.org>; Thu, 17 Jul 2014 19:26:34 GMT
Message-ID: <53C8236A.2010801@cisco.com>
Date: Thu, 17 Jul 2014 21:26:34 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "radext@ietf.org" <radext@ietf.org>
References: <20140717191710.4C23A18044F@rfc-editor.org>
In-Reply-To: <20140717191710.4C23A18044F@rfc-editor.org>
X-Forwarded-Message-Id: <20140717191710.4C23A18044F@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------090902010205030708010009"
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/YlZoeQGkz7fMSwoXf_-26ZeddXc
Subject: [radext] Fwd: RFC 7268 on RADIUS Attributes for IEEE 802 Networks
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2014 19:26:43 -0000

Yes!
Congrats to the authors, the WG chairs, and the WG.

Regards, Benoit


-------- Original Message --------
Subject: 	RFC 7268 on RADIUS Attributes for IEEE 802 Networks
Date: 	Thu, 17 Jul 2014 12:17:10 -0700
From: 	<rfc-editor@rfc-editor.org>
Reply-To: 	<ietf@ietf.org>
To: 	<ietf-announce@ietf.org>rg>, <rfc-dist@rfc-editor.org>
CC: 	<drafts-update-ref@iana.org>rg>, <rfc-editor@rfc-editor.org>



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


.