Pre-Authentication Support for the Protocol for Carrying Authentication for Network Access (PANA)
RFC 5873

Document Type RFC - Experimental (May 2010; No errata)
Was draft-ietf-pana-preauth (individual in int area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 5873 (Experimental)
Telechat date
Responsible AD Jari Arkko
Send notices to pana-chairs@ietf.org, draft-ietf-pana-preauth@ietf.org
Internet Engineering Task Force (IETF)                           Y. Ohba
Request for Comments: 5873                                       Toshiba
Category: Experimental                                          A. Yegin
ISSN: 2070-1721                                                  Samsung
                                                                May 2010

            Pre-Authentication Support for the Protocol for
           Carrying Authentication for Network Access (PANA)

Abstract

   This document defines an extension to the Protocol for Carrying
   Authentication for Network Access (PANA) for proactively establishing
   a PANA Security Association between a PANA Client in one access
   network and a PANA Authentication Agent in another access network to
   which the PANA Client may move.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see 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/rfc5873.

Copyright Notice

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

Ohba & Yegin                  Experimental                      [Page 1]
RFC 5873           Pre-Authentication Support for PANA          May 2010

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
     1.1.  Specification of Requirements . . . . . . . . . . . . . . . 2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Pre-Authentication Procedure  . . . . . . . . . . . . . . . . . 3
   4.  PANA Extensions . . . . . . . . . . . . . . . . . . . . . . . . 5
   5.  Backward Compatibility  . . . . . . . . . . . . . . . . . . . . 6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     9.2.  Informative References  . . . . . . . . . . . . . . . . . . 7

1.  Introduction

   The Protocol for Carrying Authentication for Network Access (PANA)
   [RFC5191] carries Extensible Authentication Protocol (EAP) messages
   between a PANA Client (PaC) and a PANA Authentication Agent (PAA) in
   the access network.  If the PaC is a mobile device and is capable of
   moving from one access network to another while running its
   applications, it is critical for the PaC to perform a handover
   seamlessly without degrading the performance of the applications
   during the handover period.  When the handover requires the PaC to
   establish a PANA session with the PAA in the new access network, the
   signaling to establish the PANA session should be completed as fast
   as possible.  See [RFC5836] for the handover latency requirements.

   This document defines an extension to the PANA protocol [RFC5191]
   used for proactively executing EAP authentication and establishing a
   PANA SA (Security Association) between a PaC in an access network and
   a PAA in another access network to which the PaC may move.  The
   extension to the PANA protocol is designed to realize direct
   pre-authentication defined in [RFC5836].  How to realize
   authorization and accounting with the use of the pre-authentication
   extension is out of the scope of this document.

1.1.  Specification of Requirements

   In this document, several words are used to signify the requirements
   of the specification.  These words are often capitalized.  The key
   words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
Show full document text