Document Action: 'Requirements for a Tunnel Based EAP Method' to Informational RFC (draft-ietf-emu-eaptunnel-req-09.txt)

The IESG <iesg-secretary@ietf.org> Tue, 11 January 2011 17:32 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE09B3A6A64; Tue, 11 Jan 2011 09:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.431
X-Spam-Level:
X-Spam-Status: No, score=-102.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkwSURKM3+66; Tue, 11 Jan 2011 09:32:59 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ED3428C28A; Tue, 11 Jan 2011 09:32:58 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Requirements for a Tunnel Based EAP Method' to Informational RFC (draft-ietf-emu-eaptunnel-req-09.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110111173258.10518.44681.idtracker@localhost>
Date: Tue, 11 Jan 2011 09:32:58 -0800
Cc: Internet Architecture Board <iab@iab.org>, emu mailing list <emu@ietf.org>, emu chair <emu-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 11 Jan 2011 17:32:59 -0000

The IESG has approved the following document:
- 'Requirements for a Tunnel Based EAP Method'
  (draft-ietf-emu-eaptunnel-req-09.txt) as an Informational RFC

This document is the product of the EAP Method Update Working Group.

The IESG contact persons are Sean Turner and Tim Polk.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-emu-eaptunnel-req/



Technical Summary

This memo defines the requirements for a tunnel-based Extensible Authentication Protocol (EAP) Method. This method will use Transport Layer Security (TLS) to establish a secure tunnel. The tunnel will provide support for password authentication, EAP authentication and the transport of additional data for other purposes.

Working Group Summary

The document has had substantial review from a number of working group participants. The working group is ready to start working on protocols.

Document Quality

The document is a requirements document that has had contributions from Working group participants from different vendors. Discussion in the Working group has resulted in improvements to the document.

Personnel

Alan DeKok (aland@deployingradius.com) is the document shepherd.
Sean Turner (turners@ieca.com) is the responsible Area Director.