RFC 6678 on Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method
rfc-editor@rfc-editor.org Wed, 25 July 2012 18:41 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB1C21F874A; Wed, 25 Jul 2012 11:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.258
X-Spam-Level:
X-Spam-Status: No, score=-102.258 tagged_above=-999 required=5 tests=[AWL=0.342, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GPm14K9mAXSy; Wed, 25 Jul 2012 11:41:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 4278D21F8627; Wed, 25 Jul 2012 11:41:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A6457B1E005; Wed, 25 Jul 2012 11:41:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6678 on Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method
From: rfc-editor@rfc-editor.org
Message-Id: <20120725184114.A6457B1E005@rfc-editor.org>
Date: Wed, 25 Jul 2012 11:41:14 -0700
Cc: emu@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Wed, 25 Jul 2012 18:41:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6678
Title: Requirements for a Tunnel-Based Extensible
Authentication Protocol (EAP) Method
Author: K. Hoeper, S. Hanna,
H. Zhou, J. Salowey, Ed.
Status: Informational
Stream: IETF
Date: July 2012
Mailbox: khoeper@motorolasolutions.com,
shanna@juniper.net,
hzhou@cisco.com,
jsalowey@cisco.com
Pages: 23
Characters: 54446
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-emu-eaptunnel-req-09.txt
URL: http://www.rfc-editor.org/rfc/rfc6678.txt
This memo defines the requirements for a tunnel-based Extensible
Authentication Protocol (EAP) Method. This tunnel 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. This document is not an Internet Standards Track
specification; it is published for informational purposes.
This document is a product of the EAP Method Update Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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/rfcsearch.html.
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