3GPP IP Multimedia Subsystems (IMS) Option for the Internet Key Exchange Protocol Version 2 (IKEv2)
RFC 7651

Document Type RFC - Informational (September 2015; No errata)
Last updated 2015-10-14
Stream ISE
Formats plain text pdf html bibtex
IETF conflict review conflict-review-gundavelli-ipsecme-3gpp-ims-options
Stream ISE state Published RFC
Consensus Boilerplate Unknown
Document shepherd Nevil Brownlee
Shepherd write-up Show (last changed 2015-06-18)
IESG IESG state RFC 7651 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Independent Submission                                     A. Dodd-Noble
Request for Comments: 7651                                 S. Gundavelli
Category: Informational                                            Cisco
ISSN: 2070-1721                                              J. Korhonen
                                                             F. Baboescu
                                                    Broadcom Corporation
                                                                 B. Weis
                                                                   Cisco
                                                          September 2015

               3GPP IP Multimedia Subsystems (IMS) Option
        for the Internet Key Exchange Protocol Version 2 (IKEv2)

Abstract

   This document defines two new configuration attributes for the
   Internet Key Exchange Protocol version 2 (IKEv2).  These attributes
   can be used for carrying the IPv4 address and IPv6 address of the
   Proxy-Call Session Control Function (P-CSCF).  When an IPsec gateway
   delivers these attributes to an IPsec client, the IPsec client can
   obtain the IPv4 and/or IPv6 address of the P-CSCF server located in
   the 3GPP network.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not 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/rfc7651.

Dodd-Noble, et al.            Informational                     [Page 1]
RFC 7651                3GPP IMS Option for IKEv2         September 2015

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   4
     2.1.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  P_CSCF_IP4_ADDRESS Configuration Attribute  . . . . . . . . .   4
   4.  P_CSCF_IP6_ADDRESS Configuration Attribute  . . . . . . . . .   5
   5.  Example Scenario  . . . . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The Third Generation Partnership Project (3GPP) S2b reference point
   [TS23402], specified by the 3GPP system architecture, defines a
   mechanism for allowing a mobile node (MN) attached in an untrusted,
   non-3GPP IP access network to securely connect to a 3GPP network and
   access IP services.  In this scenario, the mobile node establishes an
   IPsec Encapsulating Security Payload (ESP) tunnel [RFC4303]  to the
   security gateway called the Evolved Packet Data Gateway (ePDG) that
   in turn establishes a Proxy Mobile IPv6 (PMIPv6) [RFC5213] or GPRS
   Tunneling Protocol (GTP) [TS23402] tunnel to the Packet Data Network
   Gateway (PGW) [TS23402] where the mobile node's session is anchored.

   The below figure shows the interworking option for non-3GPP access
   over an untrusted access network.  The Mobile Access Gateway (MAG)
   and the Local Mobility Anchor (LMA) functions are defined in
   [RFC5213].  The ePDG and PGW functions are defined in [TS23402].  The
   IPsec ESP tunnel is used between the MN and the ePDG; either a PMIP
   or GTP tunnel is used between the ePDG and PGW.

Dodd-Noble, et al.            Informational                     [Page 2]
RFC 7651                3GPP IMS Option for IKEv2         September 2015
Show full document text