Protocol Action: 'Diameter Extensible Authentication Protocol (EAP) Application' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Tue, 23 November 2004 21:59 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10688; Tue, 23 Nov 2004 16:59:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWilE-0005PH-3M; Tue, 23 Nov 2004 17:03:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWiOt-00005m-9T; Tue, 23 Nov 2004 16:40:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWiCX-0006mv-RH; Tue, 23 Nov 2004 16:27:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05087; Tue, 23 Nov 2004 16:27:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWiGH-0000QO-NI; Tue, 23 Nov 2004 16:31:45 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CWhhn-0003ss-9h; Tue, 23 Nov 2004 15:56:07 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CWhhn-0003ss-9h@megatron.ietf.org>
Date: Tue, 23 Nov 2004 15:56:07 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: aaa chair <john.loughney@nokia.com>, Internet Architecture Board <iab@iab.org>, aaa, aaa chair <david@mitton.com>, chair <aboba@internaut.com>, aaa mailing list <aaa-wg@merit.edu>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'Diameter Extensible Authentication Protocol (EAP) Application' to Proposed Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
The IESG has approved the following document: - 'Diameter Extensible Authentication Protocol (EAP) Application ' <draft-ietf-aaa-eap-10.txt> as a Proposed Standard This document is the product of the Authentication, Authorization and Accounting Working Group. The IESG contact persons are Bert Wijnen and David Kessens. Technical Summary: The Extensible Authentication Protocol (EAP) provides a standard mechanism for support of various authentication methods. This document defines the Command-Codes and AVPs necessary to carry EAP packets between a Network Access Server (NAS) and a back-end authentication server. It therefore provides the same function for Diameter as RFC 3579 does for RADIUS. Working Group Summary The document being advanced represents the culmination of a long effort to standardize support for EAP within Diameter, including key transport. One of the major obstacles that was overcome was the development of a mechanism (using Diameter Redirect) to transport keys without access by intermediaries. There is strong working group consensus relating to this document. The document has been reviewed by participants in both AAA WG and EAP WG, as well as by participants within IEEE 802, 3GPP, and 3GPP2. Protocol Quality: This protocol document was originally part of the Diameter NASREQ specification, but was split off into a separate specification in order to improve clarity and allow EAP-specific security issues to be addressed. Since the split, the clarity of the protocol as well as the level of analysis in the security considerations section has been greatly improved. Bert Wijnen has reviewed this document for the IESG. RFC-Editor note: In sect 4.1.5 fix incorrect notation on 3rd line OLD: contains the value ((Vendor-Id * 232) + Vendor-Type). NEW: contains the value ((Vendor-Id * 2^32) + Vendor-Type). _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce