Internet Engineering Task Force (IETF) C. Holmberg
Request for Comments: 7976 N. Biondic
Updates: 7315 Ericsson
Category: Informational G. Salgueiro
ISSN: 2070-1721 Cisco
September 2016
Internet Engineering Task Force (IETF) C. Holmberg
Request for Comments: 7976 N. Biondic
Updates: 7315 Ericsson
Category: Informational G. Salgueiro
ISSN: 2070-1721 Cisco
September 2016
Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses
会话启动协议（SIP）请求和响应中专用头（P头）扩展使用的更新
Abstract
摘要
The Third Generation Partnership Project (3GPP) has identified cases where different SIP private header extensions referred to as "P-" header fields, and defined in RFC 7315, need to be included in SIP requests and responses currently not allowed according to RFC 7315. This document updates RFC 7315, in order to allow inclusion of the affected "P-" header fields in such requests and responses.
第三代合作伙伴关系项目（3GPP）已经确定了一些情况，其中RFC 7315中定义的称为“P-”报头字段的不同SIP专用报头扩展需要包括在根据RFC 7315当前不允许的SIP请求和响应中。本文档更新了RFC 7315，以允许在此类请求和响应中包含受影响的“P-”标题字段。
This document also makes updates for RFC 7315 in order to fix misalignments that occurred when RFC 3455 was updated and obsoleted by RFC 7315.
本文件还对RFC 7315进行了更新，以修复RFC 3455更新并被RFC 7315淘汰时出现的偏差。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 7841第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/rfc7976.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7976.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 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. 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Misalignments and 3GPP Use Cases . . . . . . . . . . . . . . 3
2.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Misalignments . . . . . . . . . . . . . . . . . . . . . . 3
2.3. 3GPP Use Cases . . . . . . . . . . . . . . . . . . . . . 4
2.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 4
2.3.2. P-Access-Network-Info . . . . . . . . . . . . . . . . 4
2.3.3. P-Charging-Vector . . . . . . . . . . . . . . . . . . 5
3. Updates to RFC 7315 . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . 7
5.2. Informative References . . . . . . . . . . . . . . . . . 8
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Misalignments and 3GPP Use Cases . . . . . . . . . . . . . . 3
2.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Misalignments . . . . . . . . . . . . . . . . . . . . . . 3
2.3. 3GPP Use Cases . . . . . . . . . . . . . . . . . . . . . 4
2.3.1. General . . . . . . . . . . . . . . . . . . . . . . . 4
2.3.2. P-Access-Network-Info . . . . . . . . . . . . . . . . 4
2.3.3. P-Charging-Vector . . . . . . . . . . . . . . . . . . 5
3. Updates to RFC 7315 . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . 7
5.2. Informative References . . . . . . . . . . . . . . . . . 8
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
The Third Generation Partnership Project (3GPP) has identified cases where different Session Initiation Protocol (SIP) [RFC3261] private header extensions referred to as "P-" header fields, and defined in [RFC7315], need to be included in SIP requests and responses currently not allowed according to RFC 7315. This document updates RFC 7315, in order to allow inclusion of the affected "P-" header fields in such requests and responses.
第三代合作伙伴关系项目（3GPP）已经确定了以下情况：不同的会话发起协议（SIP）[RFC3261]私有报头扩展称为“P-”报头字段，并在[RFC7315]中定义，需要包括在根据RFC 7315目前不允许的SIP请求和响应中。本文档更新了RFC 7315，以允许在此类请求和响应中包含受影响的“P-”标题字段。
This document also makes updates for RFC 7315 in order to fix misalignments that occurred when RFC 3455 [RFC3455] was updated and obsoleted by RFC 7315.
本文件还对RFC 7315进行了更新，以修复RFC 3455[RFC3455]更新并被RFC 7315淘汰时出现的偏差。
As the "P-" header fields are mainly used in (and in most cases, only defined for) networks defined by the 3GPP, where the updates defined in this document are already defined [TS.3GPP.24.229], the updates are not seen to cause backward-compatibility concerns.
由于“P-”头字段主要用于（并且在大多数情况下，仅针对）3GPP定义的网络，其中本文档中定义的更新已经定义[TS.3GPP.24.229]，因此这些更新不会引起向后兼容性问题。
RFC 7315 contains contradicting statements regarding the usage of SIP "P-" header fields in SIP requests and responses, which leave the presence of the SIP "P-" header fields in the SIP requests and responses open to interpretation and different implementations. Statements in Section 5.7 of that RFC are not aligned with the definitions and usage of the SIP "P-" header fields specified in Section 4. This section describes the misalignments that occurred when RFC 3455 was updated and obsoleted by RFC 7315, and how they are fixed.
RFC 7315包含关于在SIP请求和响应中使用SIP“P-”头字段的自相矛盾的声明，这使得SIP请求和响应中存在的SIP“P-”头字段可供解释和不同的实现使用。RFC第5.7节中的声明与第4节中规定的SIP“P-”头字段的定义和用法不一致。本节描述了RFC 7315更新和淘汰RFC 3455时发生的偏差，以及如何修复这些偏差。
NOTE: In the case of the P-Called-Party-ID header field, allowing it in PUBLISH requests was deliberately done in RFC 7315. Therefore, it is not considered a misalignment.
注意：在P-Called-Party-ID头字段的情况下，在RFC 7315中故意在发布请求中允许它。因此，不应将其视为未对准。
Since RFC 7315 was published, 3GPP defined new use cases that require the RFC to be updated. This section describes the 3GPP use cases behind the updates, and the updates needed to RFC 7315 in order to support the use cases.
自RFC 7315发布以来，3GPP定义了需要更新RFC的新用例。本节描述更新背后的3GPP用例，以及RFC 7315支持这些用例所需的更新。
Section 3 updates RFC 7315, based on the misalignments and 3GPP use cases.
第3节根据偏差和3GPP用例更新RFC 7315。
The following updates are needed in order to fix the misalignments between RFCs 7315 and 3455:
需要以下更新来修复RFCs 7315和3455之间的偏差：
o P-Associated-URI: Remove the statement that the header field can appear in the SIP REGISTER method.
o P-Associated-URI：删除头字段可以出现在SIP REGISTER方法中的语句。
o P-Called-Party-ID: Delete the statement that the P-Called-Party-ID header field can appear in SIP responses. Add a statement that the P-Called-Party-ID header field can appear in the SIP REFER method.
o P-Called-Party-ID：删除P-Called-Party-ID头字段可以出现在SIP响应中的语句。添加一条语句，使P-Called-Party-ID头字段可以出现在SIP refere方法中。
o P-Visited-Network-ID: Delete the statement that the P-Visited-Network-ID header field can appear in SIP responses. Add a statement that the P-Visited-Network-ID header field cannot appear in the SIP NOTIFY, PRACK, INFO, and UPDATE methods.
o P-visted-Network-ID：删除P-visted-Network-ID头字段可以出现在SIP响应中的语句。添加一条语句，说明P-visted-Network-ID头字段不能出现在SIP NOTIFY、PRACK、INFO和UPDATE方法中。
o P-Access-Network-Info: Add a statement that the P-Access-Network-Info header field can appear in SIP responses.
o P-Access-Network-Info：添加一条语句，说明P-Access-Network-Info头字段可以出现在SIP响应中。
o P-Charging-Vector: Add a statement that the P-Charging-Vector header field can appear in SIP responses. Add a statement that the P-Charging-Vector header field cannot appear in the SIP ACK method.
o P-Charging-Vector：添加一条语句，说明P-Charging-Vector头字段可以出现在SIP响应中。添加一条语句，说明P-Charging-Vector标头字段不能出现在SIP ACK方法中。
o P-Charging-Function-Addresses: Add a statement that the P-Charging-Function-Addresses header field can appear in SIP responses.
o P-Charging-Function-Addresses：添加一条语句，说明P-Charging-Function-Addresses标头字段可以出现在SIP响应中。
The following updates are needed in order to implement the 3GPP use cases:
为了实现3GPP用例，需要以下更新：
o P-Access-Network-Info: Add statement that the P-Access-Network-Info header field can appear in the SIP ACK method when triggered by a SIP 2xx response.
o P-Access-Network-Info:Add语句，当由SIP 2xx响应触发时，P-Access-Network-Info报头字段可以出现在SIP ACK方法中。
o P-Charging-Vector: Add statement that the P-Charging-Vector header field can appear in the SIP ACK method when triggered by a SIP 2xx response.
o P-Charging-Vector：添加这样一条语句，即当由SIP 2xx响应触发时，P-Charging-Vector头字段可以出现在SIP ACK方法中。
This following sections describe, for individual "P-" header fields, the 3GPP use cases that are the basis for the updates. The use cases are based on the procedures defined in [TS.3GPP.24.229].
以下各节针对单个“P-”标题字段描述作为更新基础的3GPP用例。用例基于[TS.3GPP.24.229]中定义的程序。
The P-Access-Network-Info header field may contain the Network Provided Location Information (NPLI). The NPLI is described in [TS.3GPP.23.228].
P-Access-Network-Info报头字段可能包含网络提供的位置信息（NPLI）。[TS.3GPP.23.228]中描述了NPLI。
A proxy in possession of appropriate information about the access technology might insert a P-Access-Network-Info header field with its own values. Such values are identified by the string "network-provided" defined in RFC 7315. Based on operator policy and/or roaming agreement, the local time of the visited network may be included.
拥有有关访问技术的适当信息的代理可能会插入一个具有自己值的P-access-Network-Info头字段。这些值由RFC 7315中定义的字符串“网络提供”标识。根据运营商政策和/或漫游协议，可包括访问网络的本地时间。
The Call Data Records (CDRs) generated within the IP Multimedia Subsystem (IMS) have to contain the NPLI in order to guarantee correct billing. When an IMS session is modified, the NPLI also needs to be stored as the location of the user at the time when the
IP多媒体子系统（IMS）内生成的呼叫数据记录（CDR）必须包含NPLI，以确保正确计费。当修改IMS会话时，NPLI还需要存储为用户在修改会话时的位置
session is modified may generate a charging event. In case of a session modification event at IMS, the NPLI needs to be provided:
会话被修改可能会生成充电事件。如果IMS发生会话修改事件，则需要提供NPLI：
o when the bearer establishment is triggered, or
o 当触发承载建立时，或
o at session release when the bearer deactivation is triggered, or
o 触发承载停用时的会话释放，或
o when the bearer modification is triggered, e.g., a QoS modification for the use of a newly negotiated codec.
o 当触发承载修改时，例如，用于使用新协商的编解码器的QoS修改。
In some scenarios, the bearer modification may be triggered by the proxy upon reception of a Session Description Protocol (SDP) answer within SIP 2xx response to the SIP INVITE request. In such case, the NPLI needs to be provided within the SIP ACK request. However, RFC 7315 does not allow the usage of the P-Access-Network-Info header field in SIP ACK request.
在一些场景中，当在SIP 2xx响应SIP INVITE请求中接收到会话描述协议（SDP）应答时，代理可以触发承载修改。在这种情况下，需要在SIP ACK请求中提供NPLI。但是，RFC 7315不允许在SIP ACK请求中使用P-Access-Network-Info报头字段。
Upon reception of the SDP answer within SIP 2xx response on the SIP INVITE request, a proxy may initiate procedures to obtain the NPLI and may include the P-Access-Network-Info header field with the NPLI in the SIP ACK request.
当在SIP INVITE请求上的SIP 2xx响应中接收到SDP应答时，代理可以启动获取NPLI的过程，并且可以在SIP ACK请求中包括P-Access-Network-Info报头字段和NPLI。
The P-Access-Network-Info header field shall not be included in SIP ACK requests triggered by non-2xx responses.
P-Access-Network-Info报头字段不应包含在由非2xx响应触发的SIP ACK请求中。
RFC 7315 defines an Inter Operator Identifier (IOI) to enable different operators involved in a SIP dialog or a transaction outside a dialog to identify each other by exchanging operator identification information within the P-Charging-Vector header field.
RFC 7315定义了操作员间标识符（IOI），以使SIP对话或对话外部事务中涉及的不同操作员能够通过在P-Vector报头字段内交换操作员标识信息来相互识别。
In the interconnection scenarios in multi-operator environments, where one or more transit operators are between the originating and terminating operator, the identities of the involved transit operators are represented by a transit-ioi parameter of the P-Charging-Vector header field.
在多运营商环境中的互连场景中，当一个或多个公交运营商位于始发运营商和终止运营商之间时，相关公交运营商的身份由P-Charging-Vector报头字段的公交ioi参数表示。
Transit operators can be selected independently for each SIP method and direction of request. A transit network will only have knowledge of an individual SIP request, and transit network selection will be an independent decision for each request and could be made based on load, cost, percentage, time of day, and other factors. For this reason, it is necessary that the P-Charging-Vector header field, which carries the transit IOI information, is included in each SIP request and response. However, RFC 7315 does not allow the usage of the P-Charging-Vector header field in the SIP ACK request.
可以为每个SIP方法和请求方向独立选择公交运营商。公交网络将只知道单个SIP请求，公交网络选择将是每个请求的独立决定，可以根据负载、成本、百分比、一天中的时间和其他因素进行选择。因此，有必要在每个SIP请求和响应中包括携带传输IOI信息的P-Charging-Vector报头字段。然而，RFC 7315不允许在SIP ACK请求中使用P-Charging-Vector报头字段。
A SIP proxy that supports this extension and receives the SIP ACK request may include a P-Charging-Vector header field in the SIP ACK request.
支持该扩展并接收SIP ACK请求的SIP代理可以在SIP ACK请求中包括P-Charging-Vector报头字段。
The P-Charging-Vector header field shall not be included in SIP ACK requests triggered by SIP non-2xx responses.
P-Charging-Vector报头字段不应包含在由SIP非2xx响应触发的SIP ACK请求中。
This section implements the update to Section 5.7 of RFC 7315, in order to implement the misalignment fixes and the 3GPP requirements described in Section 2.
本节实施对RFC 7315第5.7节的更新，以实施第2节中描述的未对准修复和3GPP要求。
Old text:
旧文本：
The P-Associated-URI header field can appear in SIP REGISTER method and 2xx resonses [sic]. The P-Called-Party-ID header field can appear in SIP INVITE, OPTIONS, PUBLISH, SUBSCRIBE, and MESSAGE methods and all responses. The P-Visited-Network-ID header field can appear in all SIP methods except ACK, BYE, and CANCEL and all responses. The P-Access-Network-Info header field can appear in all SIP methods except ACK and CANCEL. The P-Charging-Vector header field can appear in all SIP methods except CANCEL. The P-Charging-Function-Addresses header field can appear in all SIP methods except ACK and CANCEL.
P-Associated-URI头字段可以出现在SIP REGISTER method和2xx resonses[sic]中。P-Called-Party-ID头字段可以出现在SIP INVITE、OPTIONS、PUBLISH、SUBSCRIBE和MESSAGE方法以及所有响应中。P-visted-Network-ID报头字段可以出现在除ACK、BYE和CANCEL以及所有响应之外的所有SIP方法中。P-Access-Network-Info头字段可以出现在除ACK和CANCEL之外的所有SIP方法中。P-Charging-Vector头字段可以出现在除CANCEL之外的所有SIP方法中。P-Charging-Function-Addresses标头字段可以出现在除ACK和CANCEL之外的所有SIP方法中。
New text:
新案文：
The P-Associated-URI header field can appear in SIP REGISTER 2xx responses. The P-Called-Party-ID header field can appear in the SIP INVITE, OPTIONS, PUBLISH, REFER, SUBSCRIBE, and MESSAGE methods. The P-Visited-Network-ID header field can appear in all SIP methods except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO, and UPDATE. The P-Access-Network-Info header field can appear in all SIP methods and non-100 responses, except in CANCEL methods, CANCEL responses, and ACK methods triggered by non-2xx responses. The P-Charging-Vector header field can appear in all SIP methods and non-100 responses, except in CANCEL methods, CANCEL responses, and ACK methods triggered by non-2xx responses. The P-Charging-Function-Addresses header field can appear in all SIP methods and non-100 responses, except in CANCEL methods, CANCEL responses, and ACK methods.
P-Associated-URI头字段可以出现在SIP寄存器2xx响应中。P-Called-Party-ID头字段可以出现在SIP INVITE、OPTIONS、PUBLISH、reference、SUBSCRIBE和MESSAGE方法中。P-visted-Network-ID头字段可以出现在除ACK、BYE、CANCEL、NOTIFY、PRACK、INFO和UPDATE之外的所有SIP方法中。P-Access-Network-Info报头字段可以出现在所有SIP方法和非100响应中，由非2xx响应触发的取消方法、取消响应和确认方法除外。P-Charging-Vector标头字段可以出现在所有SIP方法和非100响应中，但由非2xx响应触发的取消方法、取消响应和确认方法除外。P-Charging-Function-Addresses标头字段可以出现在所有SIP方法和非100响应中，但CANCEL方法、CANCEL响应和ACK方法除外。
The security considerations for these "P-" header fields are defined in [RFC7315]. This specification allows some header fields to be present in messages where they were previously not allowed, and the security considerations and assumptions described in [RFC7315] (e.g., regarding only sending information to trusted entities) also apply to those messages. In addition, this specification also disallows some header fields to be present in messages where they were previously allowed. That does not cause any security issues, but implementors need to be aware that implementations may not have been updated according to this document, and take proper actions if a header field occurs, or does not occur, in a message where it should occur (or occurs in a message where it should not occur). This document adds the ability to include P-Access-Network-Info in ACK requests. As documented in [RFC7315], P-Access-Network-Info may include privacy sensitive information, including the user's location. The security and privacy considerations for P-Access-Network-Info in ACK requests are similar to those for the other SIP requests discussed in [RFC7315].
[RFC7315]中定义了这些“P-”头字段的安全注意事项。本规范允许某些标头字段出现在以前不允许的消息中，并且[RFC7315]中描述的安全注意事项和假设（例如，仅向受信任实体发送信息）也适用于这些消息。此外，该规范还禁止某些头字段出现在以前允许的消息中。这不会导致任何安全问题，但实现者需要意识到，实现可能尚未根据本文档进行更新，如果头字段出现或未出现在应该出现的消息中（或出现在不应该出现的消息中），则应采取适当的措施。本文档添加了在ACK请求中包含P-Access-Network-Info的功能。如[RFC7315]所述，P-Access-Network-Info可能包括隐私敏感信息，包括用户的位置。ACK请求中P-Access-Network-Info的安全性和隐私考虑与[RFC7315]中讨论的其他SIP请求类似。
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, DOI 10.17487/RFC3261, June 2002, <http://www.rfc-editor.org/info/rfc3261>.
[RFC3261]Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.，和E.Schooler，“SIP：会话启动协议”，RFC 3261，DOI 10.17487/RFC3261，2002年6月<http://www.rfc-editor.org/info/rfc3261>.
[RFC7315] Jesske, R., Drage, K., and C. Holmberg, "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP", RFC 7315, DOI 10.17487/RFC7315, July 2014, <http://www.rfc-editor.org/info/rfc7315>.
[RFC7315]Jesske，R.，Drage，K.，和C.Holmberg，“3GPP会话启动协议（SIP）的专用头（P头）扩展”，RFC 7315，DOI 10.17487/RFC7315，2014年7月<http://www.rfc-editor.org/info/rfc7315>.
[TS.3GPP.23.228] 3GPP, "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3", 3GPP TS 23.228 13.6.0, June 2016, <http://www.3gpp.org/ftp/Specs/html-info/23228.htm>.
[TS.3GPP.23.228]3GPP，“基于会话发起协议（SIP）和会话描述协议（SDP）的IP多媒体呼叫控制协议；第3阶段”，3GPP TS 23.228 13.6.0，2016年6月<http://www.3gpp.org/ftp/Specs/html-info/23228.htm>.
[TS.3GPP.24.229] 3GPP, "IP Multimedia Subsystem (IMS); Stage 2", 3GPP TS 24.229 13.6.0, June 2016, <http://www.3gpp.org/ftp/Specs/html-info/24229.htm>.
[TS.3GPP.24.229]3GPP，“IP多媒体子系统（IMS）；第2阶段”，3GPP TS 24.229 13.6.012016年6月<http://www.3gpp.org/ftp/Specs/html-info/24229.htm>.
[RFC3455] Garcia-Martin, M., Henrikson, E., and D. Mills, "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)", RFC 3455, DOI 10.17487/RFC3455, January 2003, <http://www.rfc-editor.org/info/rfc3455>.
[RFC3455]Garcia Martin，M.，Henrikson，E.，和D.Mills，“第三代合作伙伴关系项目（3GPP）会话启动协议（SIP）的专用头（P头）扩展”，RFC 3455，DOI 10.17487/RFC3455，2003年1月<http://www.rfc-editor.org/info/rfc3455>.
Acknowledgments
致谢
Thanks to Paul Kyzivat, Jean Mahoney, Ben Campbell, and Adam Roach for providing comments on the document.
感谢Paul Kyzivat、Jean Mahoney、Ben Campbell和Adam Roach对该文件的评论。
Authors' Addresses
作者地址
Christer Holmberg Ericsson Hirsalantie 11 Jorvas 02420 Finland
Christer Holmberg Ericsson Hirsalantie 11 Jorvas 02420芬兰
Email: christer.holmberg@ericsson.com
Email: christer.holmberg@ericsson.com
Nevenka Biondic Ericsson Krapinska 45 Zagreb 10002 Croatia
Nevenka Biondic Ericsson Krapinska 45萨格勒布10002克罗地亚
Email: nevenka.biondic@ericsson.com
Email: nevenka.biondic@ericsson.com
Gonzalo Salgueiro Cisco Systems, Inc. 7200-12 Kit Creek Road Research Triangle Park, NC 27709 United States of America
Gonzalo Salgueiro Cisco Systems，Inc.美国北卡罗来纳州Kit Creek Road研究三角公园7200-12号，邮编：27709
Email: gsalguei@cisco.com
Email: gsalguei@cisco.com