Internet Engineering Task Force (IETF) S. Hartman, Ed.
Request for Comments: 6677 Painless Security
Category: Standards Track T. Clancy
ISSN: 2070-1721 Virginia Tech
K. Hoeper
Motorola Solutions, Inc.
July 2012
Channel-Binding Support
for Extensible Authentication Protocol (EAP) Methods
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6677.
Hartman, et al. Standards Track [Page 1]
RFC 6677 EAP Channel Binding July 2012
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Hartman, et al. Standards Track [Page 2]
RFC 6677 EAP Channel Binding July 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 5
4. Channel Bindings . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Types of EAP Channel Bindings . . . . . . . . . . . . . . 8
4.2. Channel Bindings in the Secure Association Protocol . . . 9
4.3. Channel-Binding Scope . . . . . . . . . . . . . . . . . . 10
5. Channel-Binding Process . . . . . . . . . . . . . . . . . . . 12
5.1. Protocol Operation . . . . . . . . . . . . . . . . . . . . 12
5.2. Channel-Binding Consistency Check . . . . . . . . . . . . 14
5.3. EAP Protocol . . . . . . . . . . . . . . . . . . . . . . . 15
5.3.1. Channel-Binding Codes . . . . . . . . . . . . . . . . 17
5.3.2. Namespace Identifiers . . . . . . . . . . . . . . . . 17
5.3.3. RADIUS Namespace . . . . . . . . . . . . . . . . . . . 18
6. System Requirements . . . . . . . . . . . . . . . . . . . . . 18
6.1. General Transport Protocol Requirements . . . . . . . . . 18
6.2. EAP Method Requirements . . . . . . . . . . . . . . . . . 19
7. Channel-Binding TLV . . . . . . . . . . . . . . . . . . . . . 19
7.1. Requirements for Lower-Layer Bindings . . . . . . . . . . 19
7.2. EAP Lower-Layer Attribute . . . . . . . . . . . . . . . . 20
8. AAA-Layer Bindings . . . . . . . . . . . . . . . . . . . . . . 20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 21
datatracker.ietf.org