5807
PROPOSED STANDARD
Definition of Master Key between PANA Client and Enforcement Point
Authors: Y. Ohba, A. Yegin
Date: March 2010
Working Group: NON WORKING GROUP
Stream: IETF
Abstract
This document defines a master key used between a client of the Protocol for carrying Authentication for Network Access (PANA) and an enforcement point, for bootstrapping lower-layer ciphering. The master key is derived from the Master Session Key of the Extensible Authentication Protocol as a result of successful PANA authentication. The master key guarantees cryptographic independence among enforcement points bootstrapped from PANA authentication across different address families. [STANDARDS-TRACK]
RFC 5807
PROPOSED STANDARD
Internet Engineering Task Force (IETF) Y. Ohba
Request for Comments: 5807 Toshiba
Category: Standards Track A. Yegin
ISSN: 2070-1721 Samsung
March 2010
<span class="h1">Definition of Master Key between PANA Client and Enforcement Point</span>
Abstract
This document defines a master key used between a client of the
Protocol for carrying Authentication for Network Access (PANA) and an
enforcement point, for bootstrapping lower-layer ciphering. The
master key is derived from the Master Session Key of the Extensible
Authentication Protocol as a result of successful PANA
authentication. The master key guarantees cryptographic independence
among enforcement points bootstrapped from PANA authentication across
different address families.
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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc5807">http://www.rfc-editor.org/info/rfc5807</a>.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Ohba & Yegin Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc5807">RFC 5807</a> PaC-EP Master Key March 2010</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Specification of Requirements . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. PaC-EP Master Key . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Key Name of PEMK . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Scope of PEMK . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3">3.3</a>. Context of PEMK . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.4">3.4</a>. Lifetime of PEMK . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. Channel Binding . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4.2">4.2</a>. Guideline for Distributing PEMK from PAA to EP . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<span class="grey">Ohba & Yegin Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc5807">RFC 5807</a> PaC-EP Master Key March 2010</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Protocol for carrying Authentication for Network Access (PANA)
[<a href="./rfc5191" title=""Protocol for Carrying Authentication for Network Access (PANA)"">RFC5191</a>] is designed to facilitate network access authentication and
authorization of clients in access networks. It carries Extensible
Authentication Protocol (EAP) [<a href="./rfc3748" title=""Extensible Authentication Protocol (EAP)"">RFC3748</a>] between a PANA Client (PaC)
and a PANA Authentication Agent (PAA) where the PAA functions as an
authentication gateway to the Authentication Server (AS). The PANA
framework [<a href="./rfc5193" title=""Protocol for Carrying Authentication for Network Access (PANA) Framework"">RFC5193</a>] defines an another entity referred to as an
Enforcement Point (EP), which resides in the access network and
allows access (data traffic) of authorized PaCs while preventing
access of others depending on the PANA authentication and
authorization result (Figure 1). The EP and PAA may be implemented
on the same device or separate devices.
RADIUS,
Diameter,
+-----+ PANA +-----+ LDAP, API, etc. +-----+
| PaC |<----------------->| PAA |<------------------->| AS |
+-----+ +-----+ +-----+
^ ^
| |
| +-----+ |
IKE, +-------->| EP |<--------+ ANCP, API, etc.
4-way handshake, +-----+
etc. .
.
.
v
Data traffic
Figure 1: PANA Functional Model
The EP uses non-cryptographic or cryptographic filters to selectively
allow and discard data packets. These filters may be applied at the
link-layer or the IP-layer [<a href="#ref-PANA-IPSEC" title=""PANA Enabling IPsec based Access Control"">PANA-IPSEC</a>]. When cryptographic access
control is used, a secure association protocol [<a href="./rfc3748" title=""Extensible Authentication Protocol (EAP)"">RFC3748</a>] needs to run
between the PaC and EP. After completion of the secure association
protocol, link- or network-layer per-packet security (for example,
IPsec ESP) is enabled for integrity protection, data origin
authentication, replay protection, and optionally confidentiality
protection.
This document defines the PaC-EP Master Key (PEMK) that is used by a
secure association protocol as the pre-shared secret between the PaC
and EP to enable cryptographic filters in the access network. The
PEMK is defined to guarantee cryptographic independence among EPs
bootstrapped from PANA authentication across different address
<span class="grey">Ohba & Yegin Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc5807">RFC 5807</a> PaC-EP Master Key March 2010</span>
families. This document also describes a guideline for distributing
PEMKs from the PAA to EP.
This document does not specify a mechanism for a PaC to know whether
the lower layer requires a secure association protocol or the pre-
shared secret for the secure association protocol needs to be
bootstrapped from PANA authentication. Such a mechanism may be
defined by each lower-layer protocol.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Specification of Requirements</span>
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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
This document reuses the following terms defined in [<a href="./rfc5191" title=""Protocol for Carrying Authentication for Network Access (PANA)"">RFC5191</a>]: PaC
(PANA Client), PAA (PANA Authentication Agent), EP (Enforcement
Point), MSK (Master Session Key), PANA Session, and Session
Identifier.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. PaC-EP Master Key</span>
A PEMK (PaC-EP Master Key) is derived from an available MSK. The
PEMK is 64 octets in length and is calculated as follows:
PEMK = prf+(MSK, "IETF PEMK" | SID | KID | EPID)
where | denotes concatenation.
o The prf+ function is defined in IKEv2 [<a href="./rfc4306" title=""Internet Key Exchange (IKEv2) Protocol"">RFC4306</a>]. The pseudo-
random function used for the prf+ function is specified in the
PRF-Algorithm AVP carried in a PANA-Auth-Request message with 'S'
(Start) bit set.
o "IETF PEMK" is the ASCII code representation of the non-NULL
terminated string (excluding the double quotes around it).
o SID is a four-octet Session Identifier [<a href="./rfc5191" title=""Protocol for Carrying Authentication for Network Access (PANA)"">RFC5191</a>].
o KID is the content of the Key-ID AVP [<a href="./rfc5191" title=""Protocol for Carrying Authentication for Network Access (PANA)"">RFC5191</a>] associated with the
MSK.
o EPID is the identifier of the EP. The first two octets represents
the AddressType, which contains an Address Family defined in
[<a href="#ref-IANAADFAM" title=""Address Family Numbers"">IANAADFAM</a>]. The remaining octets encode the address value. The
<span class="grey">Ohba & Yegin Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc5807">RFC 5807</a> PaC-EP Master Key March 2010</span>
length of the address value is determined by the AddressType. The
AddressType is used to discriminate the content and format of the
remaining octets for the address value. The use of the
combination of address family and address value guarantees the
cryptographic independence of PEMKs among multiple EPs that are
bootstrapped from PANA authentication across multiple address
families. How a PaC discovers an EPID is out of the scope of this
document.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Key Name of PEMK</span>
The key name of the PEMK is defined as follows.
PEMKname = SHA1(EPID | SID | KID), where SHA1 denotes the SHA-1
algorithm specified in [<a href="#ref-SHS" title=""Secure Hash Standard"">SHS</a>]. Inclusion of the EPID, SID, and KID
provides uniqueness of PEMK names among multiple PaC-EP pairs under a
given PAA.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Scope of PEMK</span>
One PEMK is used between one PaC and one EP. A PEMK MUST NOT be
shared among multiple PaCs or EPs.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Context of PEMK</span>
A PEMK is used as the pre-shared key of the secure association
protocol in the scope of the PEMK. A PEMK MUST NOT be used for any
other usage.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Lifetime of PEMK</span>
The lifetime of a PEMK MUST be less than or equal to the lifetime of
the MSK from which it is derived. At the end of the lifetime, the
PEMK and its associated states MUST be deleted.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
The following considerations are specifically made to follow the
Authentication, Authorization, and Accounting (AAA) key management
guidance [<a href="./rfc4962" title=""Guidance for Authentication, Authorization, and Accounting (AAA) Key Management"">RFC4962</a>]. Other AAA key management requirements such as
key lifetime, key scope, key context, and key name are described in
<a href="#section-3">Section 3</a>.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Channel Binding</span>
Since the device identifier of the EP is involved in the key
derivation function, Channel Binding on a PEMK is made between the
PaC and PAA at the time when the PEMK is generated. If a malicious
<span class="grey">Ohba & Yegin Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc5807">RFC 5807</a> PaC-EP Master Key March 2010</span>
EP advertises a different device identifier than that registered with
the PAA, the malicious attempt will not succeed since the secure
association protocol will fail due to the difference in the PEMK
values calculated by the PaC and the EP.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Guideline for Distributing PEMK from PAA to EP</span>
When an EP is implemented on the same device as the PAA, no protocol
needs to be used for distributing a PEMK from the PAA to the EP.
In the case where the EP is implemented on a separate device from the
PAA, a protocol is needed to distribute a PEMK from the PAA to the
EP. Such a key distribution protocol may depend on the architecture
and deployment using PANA. A key distribution protocol for a PEMK
MUST ensure that the PEMK is encrypted as well as integrity and
replay protected, with a security association between the PAA and EP,
where the security association MUST be cryptographically bound to the
identities of the PAA and EP known to the PaC.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
We would like to thank Jari Arkko, Basavaraj Patil, Pasi Eronen, Russ
Mundy, Alexey Melnikov, and all members of the PANA working group for
their valuable comments to this document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC3748">RFC3748</a>] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and
H. Levkowetz, "Extensible Authentication Protocol
(EAP)", <a href="./rfc3748">RFC 3748</a>, June 2004.
[<a id="ref-RFC4306">RFC4306</a>] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
<a href="./rfc4306">RFC 4306</a>, December 2005.
[<a id="ref-RFC5191">RFC5191</a>] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and
A. Yegin, "Protocol for Carrying Authentication for
Network Access (PANA)", <a href="./rfc5191">RFC 5191</a>, May 2008.
[<a id="ref-SHS">SHS</a>] National Institute of Standards and Technology, U.S.
Department of Commerce, "Secure Hash Standard", NIST
FIPS PUB 180-2, August 2002.
[<a id="ref-IANAADFAM">IANAADFAM</a>] IANA, "Address Family Numbers", <a href="http://www.iana.org">http://www.iana.org</a>.
<span class="grey">Ohba & Yegin Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc5807">RFC 5807</a> PaC-EP Master Key March 2010</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC4962">RFC4962</a>] Housley, R. and B. Aboba, "Guidance for Authentication,
Authorization, and Accounting (AAA) Key Management",
<a href="https://www.rfc-editor.org/bcp/bcp132">BCP 132</a>, <a href="./rfc4962">RFC 4962</a>, July 2007.
[<a id="ref-RFC5193">RFC5193</a>] Jayaraman, P., Lopez, R., Ohba, Y., Parthasarathy, M.,
and A. Yegin, "Protocol for Carrying Authentication for
Network Access (PANA) Framework", <a href="./rfc5193">RFC 5193</a>, May 2008.
[<a id="ref-PANA-IPSEC">PANA-IPSEC</a>] Parthasarathy, M., "PANA Enabling IPsec based Access
Control", Work in Progress, July 2005.
Authors' Addresses
Yoshihiro Ohba
Toshiba Corporate Research and Development Center
1 Komukai-Toshiba-cho
Saiwai-ku, Kawasaki, Kanagawa 212-8582
Japan
Phone: +81 44 549 2230
EMail: [email protected]
Alper Yegin
Samsung
Istanbul
Turkey
EMail: [email protected]
Ohba & Yegin Standards Track [Page 7]
Annotations
Select text to annotate