datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option
RFC 6440

Internet Engineering Task Force (IETF)                           G. Zorn
Request for Comments: 6440                                   Network Zen
Category: Standards Track                                          Q. Wu
ISSN: 2070-1721                                                  Y. Wang
                                                                  Huawei
                                                           December 2011

The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option

Abstract

   In order to derive a Domain-Specific Root Key (DSRK) from the
   Extended Master Session Key (EMSK) generated as a side effect of an
   Extensible Authentication Protocol (EAP) method, the EAP peer must
   discover the name of the domain to which it is attached.

   This document specifies a Dynamic Host Configuration Protocol
   Version 6 (DHCPv6) option designed to allow a DHCPv6 server to inform
   clients using the EAP Re-authentication Protocol (ERP) EAP method of
   the name of the local domain for ERP.

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/rfc6440.

Zorn, et al.                 Standards Track                    [Page 1]
RFC 6440         The ERP Local Domain Name DHCPv6 Option   December 2011

Copyright Notice

   Copyright (c) 2011 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.

Table of Contents

   1. Introduction ....................................................2
   2. Terminology .....................................................3
      2.1. Standards Language .........................................3
      2.2. Acronyms ...................................................3
   3. Option Format ...................................................3
      3.1. DHCPv6 ERP Local Domain Name Option ........................3
   4. Client Behavior .................................................4
   5. Relay Agent Behavior ............................................4
   6. Security Considerations .........................................4
   7. IANA Considerations .............................................4
   8. References ......................................................5
      8.1. Normative References .......................................5
      8.2. Informative References .....................................5

1.  Introduction

   The EAP Re-authentication Protocol (ERP) [RFC5296] is designed to
   allow faster re-authentication of a mobile device that was previously
   authenticated by means of the Extensible Authentication Protocol
   [RFC3748].  Given that the local root key (e.g., a DSRK, as described
   in RFC 5295 [RFC5295]) is generated using the local domain name
   (LDN), LDN discovery is an important part of re-authentication.  As
   described in RFC 5296 [RFC5296], the LDN to be used in ERP can be
   learned by the mobile device through the ERP exchange or via a lower-
   layer mechanism.  However, no lower-layer mechanisms for LDN
   discovery have yet been defined.

   This document specifies an extension to DHCPv6 for LDN to be used
   in ERP.

Zorn, et al.                 Standards Track                    [Page 2]
RFC 6440         The ERP Local Domain Name DHCPv6 Option   December 2011

2.  Terminology

2.1.  Standards Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.2.  Acronyms

[include full document text]