RFC 4851 on The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST)

rfc-editor@rfc-editor.org Fri, 04 May 2007 22:59 UTC

Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hk6kh-0005tN-M9; Fri, 04 May 2007 18:59:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hk6ke-0005rf-I2 for ietf-announce@ietf.org; Fri, 04 May 2007 18:59:48 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hk6ke-00024K-79 for ietf-announce@ietf.org; Fri, 04 May 2007 18:59:48 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l44Mxldg016707; Fri, 4 May 2007 15:59:47 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l44MxlfH016706; Fri, 4 May 2007 15:59:47 -0700
Date: Fri, 04 May 2007 15:59:47 -0700
Message-Id: <200705042259.l44MxlfH016706@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4851 on The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST)
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>
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4851

        Title:      The Flexible Authentication via Secure 
                    Tunneling Extensible Authentication Protocol Method 
                    (EAP-FAST) 
        Author:     N. Cam-Winget, D. McGrew,
                    J. Salowey, H. Zhou
        Status:     Informational
        Date:       May 2007
        Mailbox:    ncamwing@cisco.com, 
                    mcgrew@cisco.com, 
                    jsalowey@cisco.com,  hzhou@cisco.com
        Pages:      64
        Characters: 131460
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-cam-winget-eap-fast-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4851.txt

This document defines the Extensible Authentication Protocol (EAP)
based Flexible Authentication via Secure Tunneling (EAP-FAST)
protocol.  EAP-FAST is an EAP method that enables secure
communication between a peer and a server by using the Transport
Layer Security (TLS) to establish a mutually authenticated tunnel.
Within the tunnel, Type-Length-Value (TLV) objects are used to convey
authentication related data between the peer and the EAP server.  This 
memo provides information for the Internet community.


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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce