Subject: RFC 6677 on Channel-Binding Support for Extensible Authentication Protocol (EAP) Methods

From: [email-masked]
Date: Wed, 18 Jul 2012 17:14:28 -0700 (PDT)

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

        RFC 6677

        Title:      Channel-Binding Support for Extensible Authentication 
                    Protocol (EAP) Methods 
        Author:     S. Hartman, Ed.,
                    T. Clancy, K. Hoeper
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2012
        Mailbox:    [email-masked], 
                    [email-masked], 
                    [email-masked]
        Pages:      31
        Characters: 79805
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-emu-chbind-16.txt

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

This document defines how to implement channel bindings for
Extensible Authentication Protocol (EAP) methods to address the
"lying Network Access Service (NAS)" problem as well as the "lying
provider" problem.  [STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

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/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 [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC