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
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)
互联网密钥交换协议版本2（IKEv2）的3GPP IP多媒体子系统（IMS）选项
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.
本文档为Internet密钥交换协议版本2（IKEv2）定义了两个新的配置属性。这些属性可用于承载代理呼叫会话控制功能（P-CSCF）的IPv4地址和IPv6地址。当IPsec网关将这些属性传递给IPsec客户端时，IPsec客户端可以获得位于3GPP网络中的P-CSCF服务器的IPv4和/或IPv6地址。
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.
这是对RFC系列的贡献，独立于任何其他RFC流。RFC编辑器已选择自行发布此文档，并且未声明其对实现或部署的价值。RFC编辑批准发布的文件不适用于任何级别的互联网标准；见RFC 5741第2节。
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.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7651.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
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 . . . . . . . . . . . . . . . . . . . . . . . . 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
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.
由3GPP系统架构指定的第三代合作伙伴关系项目（3GPP）S2b参考点[TS23402]定义了一种机制，用于允许连接在不受信任的非3GPP IP接入网络中的移动节点（MN）安全地连接到3GPP网络并接入IP服务。在该场景中，移动节点建立到称为演进分组数据网关（ePDG）的安全网关的IPsec封装安全有效载荷（ESP）隧道[RFC4303]，该安全网关反过来建立到分组数据网络网关（PGW）[TS23402]的代理移动IPv6（PMIPv6）[RFC5213]或GPRS隧道协议（GTP）[TS23402]隧道其中移动节点的会话被锚定。
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.
下图显示了通过不受信任的接入网络进行非3GPP接入的互通选项。[RFC5213]中定义了移动接入网关（MAG）和本地移动锚（LMA）功能。[TS23402]中定义了ePDG和PGW功能。在MN和ePDG之间使用IPsec ESP隧道；ePDG和PGW之间使用PMIP或GTP隧道。
+------------+
| ePDG |
| +--------+ |
+------+ _----_ | | IPsec | | _----_ +-----+
| MN | _( )_ | | Module | | _( )_ | LMA |
| |<====( Internet )=====| +--------+ |===( Operator )===|(PGW)|
+------+ (_ _) | : | (_Network_) +-----+
'----' | +--------+ | '----'
IPsec Tunnel | | PMIPv6 | | PMIPv6/GTP Tunnel
| | MAG | |
| +--------+ |
+------------+
+------------+
| ePDG |
| +--------+ |
+------+ _----_ | | IPsec | | _----_ +-----+
| MN | _( )_ | | Module | | _( )_ | LMA |
| |<====( Internet )=====| +--------+ |===( Operator )===|(PGW)|
+------+ (_ _) | : | (_Network_) +-----+
'----' | +--------+ | '----'
IPsec Tunnel | | PMIPv6 | | PMIPv6/GTP Tunnel
| | MAG | |
| +--------+ |
+------------+
|<------------ IKEv2/IPsec ------> | <------ PMIPv6/GTP ----->|
|<------------ IKEv2/IPsec ------> | <------ PMIPv6/GTP ----->|
Figure 1: Exchange of IPv4 Traffic Offload Selectors
图1:IPv4流量卸载选择器的交换
A mobile node in this scenario may potentially need to access the IP Multimedia Subsystem (IMS) services in the 3GPP network. The 3GPP IMS architecture is described in [TS23228] and [TS24229]. Currently, there are no attributes in IKEv2 [RFC7296] that can be used for carrying these information elements. In the absence of these attributes, the mobile node needs to be statically configured with this information and this is proving to be an operational challenge. Any other approaches for discovering these functions (such as using DNS or DHCP) would result in obtaining configuration from the access network and not from the home network. Given that the above referenced 3GPP interface is primarily for allowing the mobile node to connect to the 3GPP network through an untrusted access network, the access network may not have any relation with the home network provider and may be unable to deliver the mobile node's home network configuration.
该场景中的移动节点可能需要访问3GPP网络中的IP多媒体子系统（IMS）服务。[TS23228]和[TS24229]中描述了3GPP IMS体系结构。目前，IKEv2[RFC7296]中没有可用于承载这些信息元素的属性。在缺少这些属性的情况下，移动节点需要使用这些信息进行静态配置，这被证明是一个操作挑战。发现这些功能的任何其他方法（例如使用DNS或DHCP）都会导致从接入网络而不是家庭网络获取配置。鉴于上述3GPP接口主要用于允许移动节点通过不受信任的接入网络连接到3GPP网络，接入网络可能与家庭网络提供商没有任何关系，并且可能无法交付移动节点的家庭网络配置。
This specification therefore defines two new IKEv2 attributes [RFC7296] that allow an IPsec gateway to provide the IPv4 and/or IPv6 address of the P-CSCF server. These attributes can be exchanged by IKEv2 peers as part of the configuration payload exchange. The attributes follow the configuration attribute format defined in Section 3.15.1 of [RFC7296]. Furthermore, providing the P-CSCF server address(es) in IKEv2 as a standard attribute(s) enables clients to directly access IMS services behind a VPN gateway without going through the 3GPP-specific interfaces.
因此，本规范定义了两个新的IKEv2属性[RFC7296]，允许IPsec网关提供P-CSCF服务器的IPv4和/或IPv6地址。作为配置有效负载交换的一部分，IKEv2对等方可以交换这些属性。属性遵循[RFC7296]第3.15.1节中定义的配置属性格式。此外，在IKEv2中提供P-CSCF服务器地址作为标准属性使客户端能够在VPN网关后面直接访问IMS服务，而无需通过3GPP特定接口。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
All the IKEv2-related terms used in this document are to be interpreted as defined in [RFC7296] and [RFC5739]. All the mobility-related terms are to be interpreted as defined in [RFC5213] and [RFC5844]. Additionally, this document uses the following terms:
本文件中使用的所有IKEv2相关术语应按照[RFC7296]和[RFC5739]中的定义进行解释。所有移动性相关术语应按照[RFC5213]和[RFC5844]中的定义进行解释。此外，本文件使用以下术语：
Proxy-Call Session Control Function (P-CSCF)
代理呼叫会话控制功能（P-CSCF）
The P-CSCF is the entry point to the 3GPP IMS and serves as the SIP outbound proxy for the mobile node. The mobile node performs SIP registration to 3GPP IMS and initiates SIP sessions via a P-CSCF.
P-CSCF是3GPP IMS的入口点，并用作移动节点的SIP出站代理。移动节点向3GPP IMS执行SIP注册，并经由P-CSCF发起SIP会话。
Evolved Packet Data Gateway (ePDG)
演进分组数据网关（ePDG）
This is a security gateway defined by the 3GPP system architecture. The protocol interfaces it supports include IKEv2 [RFC7296].
这是由3GPP系统架构定义的安全网关。它支持的协议接口包括IKEv2[RFC7296]。
The P_CSCF_IP4_ADDRESS configuration attribute is formatted as follows:
P_CSCF_IP4_地址配置属性的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R| Attribute Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R| Attribute Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: IPv4 Address of P-CSCF
图2:P-CSCF的IPv4地址
Reserved (1 bit) Refer to the IKEv2 specification [RFC7296]
保留（1位）参考IKEv2规范[RFC7296]
Attribute Type (15 bits) 20
属性类型（15位）20
Length (2 octets) Length of the IPv4 address field that follows. Possible values are (0) and (4). A value of (4) indicates the size of the 4-octet IPv4 address that follows. A value of (0) indicates that it's an empty attribute with a zero-length IPv4 address field primarily used as a request indicator.
长度（2个八位字节）后面IPv4地址字段的长度。可能的值为（0）和（4）。值（4）表示后面的4个八位IPv4地址的大小。值（0）表示它是一个空属性，其零长度IPv4地址字段主要用作请求指示符。
IPv4 Address (4 octets) An IPv4 address of the P-CSCF server.
IPv4地址（4个八位字节）P-CSCF服务器的IPv4地址。
The P_CSCF_IP4_ADDRESS configuration attribute provides an IPv4 address of a P-CSCF server within the network. If an instance of an empty P_CSCF_IP4_ADDRESS attribute with a zero-length IPv4 Address field is included by the mobile node, the responder MAY respond with zero, one, or more P_CSCF_IP4_ADDRESS attributes. If several P_CSCF_IP4_ADDRESS attributes are provided in one IKEv2 message, there is no implied order among the P_CSCF_IP4_ADDRESS attributes. However, a system architecture using this specification may be able to enforce some order at both the peers.
P_CSCF_IP4_地址配置属性提供网络内P-CSCF服务器的IPv4地址。如果移动节点包括具有零长度IPv4地址字段的空P_CSCF_IP4_地址属性的实例，则响应者可以使用零、一个或多个P_CSCF_IP4_地址属性进行响应。如果在一条IKEv2消息中提供了多个P_CSCF_IP4_地址属性，则P_CSCF_IP4_地址属性之间没有隐含顺序。然而，使用此规范的系统架构可能能够在两个对等点上强制执行某些命令。
The P_CSCF_IP6_ADDRESS configuration attribute is formatted as follows:
P_CSCF_IP6_地址配置属性的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R| Attribute Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| IPv6 Address |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R| Attribute Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
| IPv6 Address |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: IPv6 Address of P-CSCF
图3:P-CSCF的IPv6地址
Reserved (1 bit) Refer to the IKEv2 specification [RFC7296]
保留（1位）参考IKEv2规范[RFC7296]
Attribute Type (15 bits) 21
属性类型（15位）21
Length (2 octets) Length of the IPv6 address field that follows. Possible values are (0) and (16). A value of (16) indicates the size of the 16-octet IPv6 address that follows. A value of (0) indicates that it's an empty attribute with a zero-length IPv6 address field primarily used as a request indicator.
长度（2个八位字节）以下IPv6地址字段的长度。可能的值为（0）和（16）。值（16）表示后面的16个八位组IPv6地址的大小。值（0）表示它是一个空属性，其零长度IPv6地址字段主要用作请求指示符。
IPv6 Address (16 octets) An IPv6 address of the P-CSCF server.
IPv6地址（16个八位字节）P-CSCF服务器的IPv6地址。
The P_CSCF_IP6_ADDRESS configuration attribute provides an IPv6 address of a P-CSCF server within the network. If an instance of an empty P_CSCF_IP6_ADDRESS attribute with a zero-length IPv6 Address field is included by the mobile node, the responder MAY respond with zero, one, or more P_CSCF_IP6_ADDRESS attributes. If several P_CSCF_IP6_ADDRESS attributes are provided in one IKEv2 message, there is no implied order among the P_CSCF_IP6_ADDRESS attributes. However, a system architecture using this specification may be able to enforce some order at both the peers.
P_CSCF_IP6_地址配置属性提供网络内P-CSCF服务器的IPv6地址。如果移动节点包括具有零长度IPv6地址字段的空P_CSCF_IP6_地址属性的实例，则响应者可以使用零、一个或多个P_CSCF_IP6_地址属性进行响应。如果在一条IKEv2消息中提供了多个P_CSCF_IP6_地址属性，则P_CSCF_IP6_地址属性之间没有隐含顺序。然而，使用此规范的系统架构可能能够在两个对等点上强制执行某些命令。
The mobile node MAY request the IP address of an P-CSCF server as shown below.
移动节点可以请求P-CSCF服务器的IP地址，如下所示。
Client Gateway
-------- ---------
Client Gateway
-------- ---------
HDR(IKE_SA_INIT), SAi1, KEi, Ni -->
HDR(IKE_SA_INIT), SAi1, KEi, Ni -->
<-- HDR(IKE_SA_INIT), SAr1, KEr, Nr, [CERTREQ]
<--HDR（IKE_SA_INIT），SAr1，KEr，Nr，[CERTREQ]
HDR(IKE_AUTH),
SK { IDi, CERT, [CERTREQ], AUTH, [IDr],
CP(CFG_REQUEST) =
{ INTERNAL_IP4_ADDRESS(),
INTERNAL_IP4_DNS(),
P_CSCF_IP4_ADDRESS() }, SAi2,
TSi = (0, 0-65535, 0.0.0.0-255.255.255.255),
TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) } -->
HDR(IKE_AUTH),
SK { IDi, CERT, [CERTREQ], AUTH, [IDr],
CP(CFG_REQUEST) =
{ INTERNAL_IP4_ADDRESS(),
INTERNAL_IP4_DNS(),
P_CSCF_IP4_ADDRESS() }, SAi2,
TSi = (0, 0-65535, 0.0.0.0-255.255.255.255),
TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) } -->
<-- HDR(IKE_AUTH),
SK { IDr, CERT, AUTH,
CP(CFG_REPLY) =
{ INTERNAL_IP4_ADDRESS(192.0.2.234),
P_CSCF_IP4_ADDRESS(192.0.2.1),
P_CSCF_IP4_ADDRESS(192.0.2.4),
INTERNAL_IP4_DNS(198.51.100.33) },
SAr2,
TSi = (0, 0-65535, 192.0.2.234-192.0.2.234),
TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) }
<-- HDR(IKE_AUTH),
SK { IDr, CERT, AUTH,
CP(CFG_REPLY) =
{ INTERNAL_IP4_ADDRESS(192.0.2.234),
P_CSCF_IP4_ADDRESS(192.0.2.1),
P_CSCF_IP4_ADDRESS(192.0.2.4),
INTERNAL_IP4_DNS(198.51.100.33) },
SAr2,
TSi = (0, 0-65535, 192.0.2.234-192.0.2.234),
TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) }
Figure 4: P-CSCF Attribute Exchange
图4：P-CSCF属性交换
Per this document, the following IANA actions have been completed.
根据本文件，已完成以下IANA行动。
o Action 1: This specification defines a new IKEv2 attribute for carrying the IPv4 address of the P-CSCF server. This attribute is defined in Section 3. It has been assigned value 20 from the "IKEv2 Configuration Payload Attribute Types" namespace defined in [RFC7296].
o 操作1：此规范定义了一个新的IKEv2属性，用于承载P-CSCF服务器的IPv4地址。该属性在第3节中定义。它已从[RFC7296]中定义的“IKEv2配置有效负载属性类型”命名空间中分配了值20。
o Action 2: This specification defines a new IKEv2 attribute for carrying the IPv6 address of the P-CSCF server. This attribute is defined in Section 4. It has been assigned value 21 from the "IKEv2 Configuration Payload Attribute Types" namespace defined in [RFC7296].
o 操作2：此规范定义了一个新的IKEv2属性，用于承载P-CSCF服务器的IPv6地址。该属性在第4节中定义。它已从[RFC7296]中定义的“IKEv2配置有效负载属性类型”命名空间中分配了值21。
This document is an extension to IKEv2 [RFC7296] and therefore it inherits all the security properties of IKEv2.
此文档是IKEv2[RFC7296]的扩展，因此它继承了IKEv2的所有安全属性。
The two new IKEv2 attributes defined in this specification are for carrying the IPv4 and IPv6 address of the P-CSCF server. These attributes can be exchanged by IKE peers as part of the configuration payload, and the currently defined IKEv2 security framework provides the needed integrity and privacy protection for these attributes. Therefore, this specification does not introduce any new security vulnerabilities.
本规范中定义的两个新IKEv2属性用于承载P-CSCF服务器的IPv4和IPv6地址。IKE对等方可以将这些属性作为配置负载的一部分进行交换，当前定义的IKEv2安全框架为这些属性提供了所需的完整性和隐私保护。因此，本规范不会引入任何新的安全漏洞。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, DOI 10.17487/RFC4303, December 2005, <http://www.rfc-editor.org/info/rfc4303>.
[RFC4303]Kent，S.，“IP封装安全有效载荷（ESP）”，RFC 4303，DOI 10.17487/RFC4303，2005年12月<http://www.rfc-editor.org/info/rfc4303>.
[RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. Kivinen, "Internet Key Exchange Protocol Version 2 (IKEv2)", STD 79, RFC 7296, DOI 10.17487/RFC7296, October 2014, <http://www.rfc-editor.org/info/rfc7296>.
[RFC7296]Kaufman，C.，Hoffman，P.，Nir，Y.，Eronen，P.，和T.Kivinen，“互联网密钥交换协议版本2（IKEv2）”，STD 79，RFC 7296，DOI 10.17487/RFC72962014年10月<http://www.rfc-editor.org/info/rfc7296>.
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, DOI 10.17487/RFC5213, August 2008, <http://www.rfc-editor.org/info/rfc5213>.
[RFC5213]Gundavelli，S.，Ed.，Leung，K.，Devarapalli，V.，Chowdhury，K.，和B.Patil，“代理移动IPv6”，RFC 5213，DOI 10.17487/RFC5213，2008年8月<http://www.rfc-editor.org/info/rfc5213>.
[RFC5739] Eronen, P., Laganier, J., and C. Madson, "IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)", RFC 5739, DOI 10.17487/RFC5739, February 2010, <http://www.rfc-editor.org/info/rfc5739>.
[RFC5739]Eronen，P.，Laganier，J.，和C.Madson，“互联网密钥交换协议版本2（IKEv2）中的IPv6配置”，RFC 5739，DOI 10.17487/RFC5739，2010年2月<http://www.rfc-editor.org/info/rfc5739>.
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010, <http://www.rfc-editor.org/info/rfc5844>.
[RFC5844]Wakikawa，R.和S.Gundavelli，“代理移动IPv6的IPv4支持”，RFC 5844，DOI 10.17487/RFC5844，2010年5月<http://www.rfc-editor.org/info/rfc5844>.
[TS23228] 3GPP, "IP Multimedia Subsystem (IMS); Stage 2", 3GPP TS 23.228, Version 13.3.0, June 2015.
[TS23228]3GPP，“IP多媒体子系统（IMS）；第2阶段”，3GPP TS 23.228，版本13.3.0，2015年6月。
[TS23402] 3GPP, "Architecture enhancements for non-3GPP accesses", 3GPP TS 23.402, Version 13.2.0, June 2015.
[TS23402]3GPP，“非3GPP接入的架构增强”，3GPP TS 23.402，版本13.2.0，2015年6月。
[TS24229] 3GPP, "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3", 3GPP TS 24.229, Version 13.2.1, June 2015.
[TS24229]3GPP，“基于会话发起协议（SIP）和会话描述协议（SDP）的IP多媒体呼叫控制协议；第3阶段”，3GPP TS 24.229，版本13.2.11915年6月。
Acknowledgements
致谢
The authors would like to specially thank Tero Kivinen for the detailed reviews. The authors would also like to thank Vojislav Vucetic, Heather Sze, Sebastian Speicher, Maulik Vaidya, Ivo Sedlacek, Pierrick Siete, and Hui Deng for all the discussions related to this topic.
作者要特别感谢Tero Kivinen的详细评论。作者还要感谢Vojislav Vucetic、Heather Sze、Sebastian Speicher、Maulik Vaidya、Ivo Sedracek、Pierrick Siete和Hui Deng与本主题相关的所有讨论。
Authors' Addresses
作者地址
Aeneas Noble Cisco 30 International Pl Tewksbury, MA 95134 United States
Aeneas Noble Cisco 30 International Pl Tewksbury，马萨诸塞州，美国95134
Email: noblea@cisco.com
Email: noblea@cisco.com
Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134 United States
美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
Email: sgundave@cisco.com
Email: sgundave@cisco.com
Jouni Korhonen Broadcom Corporation 3151 Zanker Road San Jose, CA 95134 United States
Jouni Korhonen Broadcom Corporation美国加利福尼亚州圣何塞市赞克路3151号，邮编95134
Email: jouni.nospam@gmail.com
Email: jouni.nospam@gmail.com
Florin Baboescu Broadcom Corporation 100 Mathilda Place Sunnyvale, CA 94086 United States
Florin Baboescu Broadcom Corporation美国加利福尼亚州桑尼维尔市马蒂尔达广场100号，邮编94086
Email: baboescu@broadcom.com
Email: baboescu@broadcom.com
Brian Weis Cisco 170 West Tasman Drive San Jose, CA 95134 United States
美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
Email: bew@cisco.com
Email: bew@cisco.com