EAP Extensions for EAP Re-authentication Protocol (ERP)
draft-ietf-hokey-rfc5296bis-06

The information below is for an old version of the document
Document Type Active Internet-Draft (hokey WG)
Last updated 2012-04-12 (latest revision 2011-11-15)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Stephen Farrell
Send notices to hokey-chairs@tools.ietf.org, draft-ietf-hokey-rfc5296bis@tools.ietf.org
Network Working Group                                         Q. Wu, Ed.
Internet-Draft                                                    Huawei
Obsoletes: 5296 (if approved)                                     Z. Cao
Intended status: Standards Track                            China Mobile
Expires: May 18, 2012                                       G. Zorn, Ed.
                                                             Network Zen
                                                                  Y. Shi
                                                                     H3C
                                                                   B. He
                                                                    CATR
                                                       November 15, 2011

        EAP Extensions for EAP Re-authentication Protocol (ERP)
                     draft-ietf-hokey-rfc5296bis-06

Abstract

   The Extensible Authentication Protocol (EAP) is a generic framework
   supporting multiple types of authentication methods.  In systems
   where EAP is used for authentication, it is desirable to avoid
   repeating the entire EAP exchange with another authenticator.  This
   document specifies extensions to EAP and the EAP keying hierarchy to
   support an EAP method-independent protocol for efficient re-
   authentication between the peer and an EAP re-authentication server
   through any authenticator.  The re-authentication server may be in
   the home network or in the local network to which the peer is
   connecting.

   This memo obsoletes RFC 5296.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 18, 2012.

Wu, et al.                Expires May 18, 2012                  [Page 1]
Internet-Draft                     ERP                     November 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.

Wu, et al.                Expires May 18, 2012                  [Page 2]
Internet-Draft                     ERP                     November 2011

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  ERP Description  . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  ERP With the Home ER Server  . . . . . . . . . . . . . . .  9
     3.2.  ERP with a Local ER Server . . . . . . . . . . . . . . . . 10
   4.  ER Key Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 12
     4.1.  rRK Derivation . . . . . . . . . . . . . . . . . . . . . . 13
     4.2.  rRK Properties . . . . . . . . . . . . . . . . . . . . . . 14
     4.3.  rIK Derivation . . . . . . . . . . . . . . . . . . . . . . 14
     4.4.  rIK Properties . . . . . . . . . . . . . . . . . . . . . . 15
     4.5.  rIK Usage  . . . . . . . . . . . . . . . . . . . . . . . . 15
     4.6.  rMSK Derivation  . . . . . . . . . . . . . . . . . . . . . 16
     4.7.  rMSK Properties  . . . . . . . . . . . . . . . . . . . . . 16
   5.  Protocol Details . . . . . . . . . . . . . . . . . . . . . . . 17
     5.1.  ERP Bootstrapping  . . . . . . . . . . . . . . . . . . . . 17
     5.2.  Steps in ERP . . . . . . . . . . . . . . . . . . . . . . . 20
       5.2.1.  Multiple Simultaneous Runs of ERP  . . . . . . . . . . 22
       5.2.2.  ERP Failure Handling . . . . . . . . . . . . . . . . . 23
     5.3.  New EAP Packets  . . . . . . . . . . . . . . . . . . . . . 24
       5.3.1.  EAP-Initiate/Re-auth-Start Packet  . . . . . . . . . . 25
Show full document text