Encrypting PANA AVPs
draft-yegin-pana-encr-avp-09
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Active Internet-Draft (individual in int area) | |
| Last updated | 2012-09-04 | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | None | ||
| IESG | IESG state | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Unknown | ||
| Telechat date |
Needs a YES. Needs 10 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Ralph Droms | ||
| IESG note | Robert Cragie (robert.cragie@gridmerge.com) is the document shepherd. | ||
| Send notices to | alper.yegin@yegin.org, robert.cragie@gridmerge.com, draft-yegin-pana-encr-avp@tools.ietf.org | ||
Network Working Group A. Yegin
Internet-Draft Samsung
Intended status: Standards Track R. Cragie
Expires: March 8, 2013 Gridmerge Ltd.
September 4, 2012
Encrypting PANA AVPs
draft-yegin-pana-encr-avp-09
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 March 8, 2013.
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 March 8, 2013 [Page 1]
Internet-Draft PANA AVP Encryption September 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Specification of Requirements . . . . . . . . . . . . . . 3
2. Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Encryption Keys . . . . . . . . . . . . . . . . . . . . . . . 3
4. Encryption-Algorithm AVP . . . . . . . . . . . . . . . . . . . 5
4.1. AES128_CTR Encryption Algorithm . . . . . . . . . . . . . 5
5. Encr-Encap AVP . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Encryption Policy . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Encryption Policy Specification . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7.1. AES-CTR Security Considerations . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8.1. PANA AVP codes . . . . . . . . . . . . . . . . . . . . . . 9
8.2. PANA Encryption-Algorithm AVP values . . . . . . . . . . . 10
8.3. PANA AVP codes encryption policy . . . . . . . . . . . . . 10
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
10. Normative References . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Yegin & Cragie Expires March 8, 2013 [Page 2]
Internet-Draft PANA AVP Encryption September 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 PANA
Attribute-Value Pairs (AVPs). AVPs can be integrity-protected using
the AUTH AVP when EAP authentication generates cryptographic keying
material. 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
This document extends the AVP set defined in Section 8 of [RFC5191]
by defining two new AVPs: the Encryption-Algorithm AVP (see
Section 4) and the Encr-Encap AVP (see Section 5). Two new
Show full document text