[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 6677 on Channel-Binding Support for Extensible Authentication Protocol (EAP) Methods
- To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
- Subject: RFC 6677 on Channel-Binding Support for Extensible Authentication Protocol (EAP) Methods
- From: rfc-editor at rfc-editor.org
- Date: Wed, 18 Jul 2012 17:14:28 -0700 (PDT)
- Cc: emu at ietf.org, rfc-editor at rfc-editor.org
- Delivered-to: ietf-announce at ietfa.amsl.com
- List-archive: <www.ietf.org/mail-archive/web/ietf-announce>
- List-help: <mailto:ietf-announce-request@ietf.org?subject=help>
- List-id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
- List-post: <mailto:ietf-announce@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
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: hartmans-ietf at mit.edu,
tcc at vt.edu,
khoeper at motorolasolutions.com
Pages: 31
Characters: 79805
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-emu-chbind-16.txt
URL: 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
www.ietf.org/mailman/listinfo/ietf-announce
mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see 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 at 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
- Prev by Date:
RFC 6667 on LDP 'Typed Wildcard' Forwarding Equivalence Class (FEC) for PWid and Generalized PWid FEC Elements
- Next by Date:
RFC 6684 on Guidelines and Template for Defining Extensions to the Incident Object Description Exchange Format (IODEF)
- Previous by thread:
RFC 6667 on LDP 'Typed Wildcard' Forwarding Equivalence Class (FEC) for PWid and Generalized PWid FEC Elements
- Next by thread:
RFC 6684 on Guidelines and Template for Defining Extensions to the Incident Object Description Exchange Format (IODEF)
- Index(es):
gipoco.com
is neither affiliated with the authors of this page or responsible
for its contents. This is a safe-cache copy of the original web site.
gipoco.com
is neither affiliated with the authors of this page nor responsible
for its contents. This is a safe-cache copy of the original web site.