Encrypting PANA AVPs
draft-yegin-pana-encr-avp-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-04-10
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           A. Yegin
Internet-Draft                                                   Samsung
Intended status: Standards Track                               R. Cragie
Expires: October 12, 2012                                 Gridmerge Ltd.
                                                          April 10, 2012

                          Encrypting PANA AVPs
                      draft-yegin-pana-encr-avp-02

Abstract

   This document specifies a mechanism for delivering PANA (Protocol for
   Carrying Authentication for Network Access) AVPs (Attribute-Value
   Pairs) in encrypted form.

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 October 12, 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.

Yegin & Cragie          Expires October 12, 2012                [Page 1]
Internet-Draft             PANA AVP Encryption                April 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Specification of Requirements . . . . . . . . . . . . . . . 3
   2.  Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Encryption Key  . . . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Encryption-Algorithm AVP  . . . . . . . . . . . . . . . . . . . 4
   5.  Encr-Encap AVP  . . . . . . . . . . . . . . . . . . . . . . . . 5
   6.  Encryption Policy . . . . . . . . . . . . . . . . . . . . . . . 6
     6.1.  Encryption Policy Specification . . . . . . . . . . . . . . 6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 8
   10. Normative References  . . . . . . . . . . . . . . . . . . . . . 8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

Yegin & Cragie          Expires October 12, 2012                [Page 2]
Internet-Draft             PANA AVP Encryption                April 2012

1.  Introduction

   PANA [RFC5191] is a UDP-based protocol to perform EAP authentication
   between a PaC (PANA Client) and a PAA (PANA Authentication Agent).

   Various types of payloads are exchanged as part of the network access
   authentication and authorization.  These payloads are carried in
   AVPs.  AVPs can be integrity-protected using the AUTH AVP when EAP
   authentication generates cryptographic keying material.  PANA AVPs
   are transmitted in the clear (i.e., not encrypted).

   There are certain types of payloads that need to be delivered
   privately (e.g., network keys, private identifiers, etc.).  This
   document defines a mechanism for applying encryption to selected
   AVPs.

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",
   "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
   are to be interpreted as described in [RFC2119].

2.  Details

   Encr-Encap AVP is used for delivering AVPs in encrypted form.

   Each AVP that requires encryption SHALL be encapsulated inside an
   Encr-Encap AVP.  Encr-Encap AVP can encapsulate one or more AVPs.
Show full document text