< draft-li-pce-controlled-id-space-10.txt   draft-li-pce-controlled-id-space-11.txt >
Network Working Group C. Li Network Working Group C. Li
Internet-Draft M. Chen Internet-Draft H. Shi
Intended status: Experimental Huawei Technologies Intended status: Experimental Huawei Technologies
Expires: August 29, 2022 A. Wang Expires: 22 September 2022 A. Wang
China Telecom China Telecom
W. Cheng W. Cheng
China Mobile China Mobile
C. Zhou C. Zhou
HPE HPE
February 25, 2022 21 March 2022
PCE Controlled ID Space PCE Controlled ID Space
draft-li-pce-controlled-id-space-10 draft-li-pce-controlled-id-space-11
Abstract Abstract
The Path Computation Element Communication Protocol (PCEP) provides a The Path Computation Element Communication Protocol (PCEP) provides a
mechanisms for the Path Computation Elements (PCEs) to perform path mechanisms for the Path Computation Elements (PCEs) to perform path
computations in response to Path Computation Clients (PCCs) requests. computations in response to Path Computation Clients (PCCs) requests.
The Stateful PCE extensions allow stateful control of Multiprotocol The Stateful PCE extensions allow stateful control of Multiprotocol
Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
(LSPs) using PCEP. Furthermore, PCE can be used for computing paths (LSPs) using PCEP. Furthermore, PCE can be used for computing paths
in the SR networks. in the SR networks.
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 29, 2022. This Internet-Draft will expire on 22 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents (https://trustee.ietf.org/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Revised BSD License text as
include Simplified BSD License text as described in Section 4.e of described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Revised BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. PCE-based Central Control . . . . . . . . . . . . . . . . 4 3.1. PCE-based Central Control . . . . . . . . . . . . . . . . 4
3.1.1. PCECC for MPLS/SR-MPLS . . . . . . . . . . . . . . . 4 3.1.1. PCECC for MPLS/SR-MPLS . . . . . . . . . . . . . . . 4
3.1.2. PCECC for SRv6 . . . . . . . . . . . . . . . . . . . 5 3.1.2. PCECC for SRv6 . . . . . . . . . . . . . . . . . . . 5
3.2. Binding SID Allocation . . . . . . . . . . . . . . . . . 5 3.2. Binding SID Allocation . . . . . . . . . . . . . . . . . 5
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Open Object . . . . . . . . . . . . . . . . . . . . . . . 7 5.1. Open Object . . . . . . . . . . . . . . . . . . . . . . . 7
5.1.1. LABEL-CONTROL-SPACE TLV . . . . . . . . . . . . . . . 7 5.1.1. LABEL-CONTROL-SPACE TLV . . . . . . . . . . . . . . . 7
5.1.2. FUNCT-ID-CONTROL-SPACE TLV . . . . . . . . . . . . . 9 5.1.2. FUNCT-ID-CONTROL-SPACE TLV . . . . . . . . . . . . . 9
6. Other Considerations . . . . . . . . . . . . . . . . . . . . 11 6. Other Considerations . . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . 11 7.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . 11
7.2. LABEL-CONTROL-SPACE TLV's Flag field . . . . . . . . . . 11 7.2. LABEL-CONTROL-SPACE TLV's Flag field . . . . . . . . . . 11
7.3. FUNCT-ID-CONTROL-SPACE TLV's Flag field . . . . . . . . . 12 7.3. FUNCT-ID-CONTROL-SPACE TLV's Flag field . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 16 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
[RFC5440] defines the stateless Path Computation Element [RFC5440] defines the stateless Path Computation Element
Communication Protocol (PCEP) for the Path Computation Elements Communication Protocol (PCEP) for the Path Computation Elements
(PCEs) to perform path computation in response to Path Computation (PCEs) to perform path computation in response to Path Computation
Clients (PCCs) requests. For supporting stateful operations, Clients (PCCs) requests. For supporting stateful operations,
[RFC8231] specifies a set of extensions to PCEP to enable stateful [RFC8231] specifies a set of extensions to PCEP to enable stateful
control of LSPs within and across PCEP sessions in compliance with control of LSPs within and across PCEP sessions in compliance with
[RFC4657]. Furthermore, [RFC8281] describes the setup, maintenance, [RFC4657]. Furthermore, [RFC8281] describes the setup, maintenance,
skipping to change at page 6, line 15 skipping to change at page 6, line 23
to inform the corresponding ID space information that it wants the to inform the corresponding ID space information that it wants the
PCE to control. This TLV MUST NOT be included by the PCE and MUST be PCE to control. This TLV MUST NOT be included by the PCE and MUST be
ignored on receipt by a PCC. This is an optional TLV, the PCE could ignored on receipt by a PCC. This is an optional TLV, the PCE could
be aware of the ID space from some other means outside of PCEP. be aware of the ID space from some other means outside of PCEP.
For delegating multiple types of ID space, multiple TLVs For delegating multiple types of ID space, multiple TLVs
corresponding to each ID type MUST be included in an Open message. corresponding to each ID type MUST be included in an Open message.
The ID type can be MPLS label or other type of ID. The following ID- The ID type can be MPLS label or other type of ID. The following ID-
CONTROL-SPACE TLV is defined in this document - CONTROL-SPACE TLV is defined in this document -
o LABEL-CONTROL-SPACE TLV - for MPLS Labels (including for SR-MPLS) * LABEL-CONTROL-SPACE TLV - for MPLS Labels (including for SR-MPLS)
o FUNCTION-ID-CONTROL-SPACE TLV - for SRv6 SID Function ID * FUNCTION-ID-CONTROL-SPACE TLV - for SRv6 SID Function ID
The procedure of ID space control to PCE is shown below: The procedure of ID space control to PCE is shown below:
+-+-+ +-+-+ +-+-+ +-+-+
|PCC| |PCE| |PCC| |PCE|
+-+-+ +-+-+ +-+-+ +-+-+
| | | |
| Open msg (LABEL-CONTROL-SPACE,etc) | | Open msg (LABEL-CONTROL-SPACE,etc) |
| | | |
|-------- | |-------- |
skipping to change at page 9, line 51 skipping to change at page 9, line 48
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Range (n) | | Range (n) |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loc Size | Locator (variable)... | | Loc Size | Locator (variable)... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: FUNCT-ID-CONTROL-SPACE TLV Figure 3: FUNCT-ID-CONTROL-SPACE TLV
The type (16 bits) of the TLV is TBD2. The length field (16 bits) The type (16 bits) of the TLV is TBD2. The length field (16 bits)
and has a variable value. and has a variable value.
Block(8 bits): the number of ID blocks. The range of a block is Block(8 bits): the number of ID blocks. The range of a block is
described by a start field and a range field. described by a start field and a range field.
Flags (24 bits): Following flags are currently defined Flags (24 bits): Following flags are currently defined
o L-flag: Locator flag, set when the locator information is included * L-flag: Locator flag, set when the locator information is included
in this TLV. If L-flag is unset, Loc Size and variable Locator in this TLV. If L-flag is unset, Loc Size and variable Locator
field MUST NOT be included in this TLV, and the ID spaces are field MUST NOT be included in this TLV, and the ID spaces are
applicable to all Locators. applicable to all Locators.
The unassigned bits of Flags field MUST be set to 0 on transmission The unassigned bits of Flags field MUST be set to 0 on transmission
and MUST be ignored on receipt. and MUST be ignored on receipt.
SID Structure: 64-bit field formatted as per "SID Structure" in SID Structure: 64-bit field formatted as per "SID Structure" in
[I-D.ietf-pce-segment-routing-ipv6]. [I-D.ietf-pce-segment-routing-ipv6].
skipping to change at page 12, line 5 skipping to change at page 12, line 5
TBD2 | FUNCT-ID-CONTROL-SPACE TLV | [This.I-D] TBD2 | FUNCT-ID-CONTROL-SPACE TLV | [This.I-D]
7.2. LABEL-CONTROL-SPACE TLV's Flag field 7.2. LABEL-CONTROL-SPACE TLV's Flag field
This document defines the LABEL-CONTROL-SPACE TLV and requests that This document defines the LABEL-CONTROL-SPACE TLV and requests that
IANA to create a new sub-registry to manage the value of the LABEL- IANA to create a new sub-registry to manage the value of the LABEL-
CONTROL-SPACE TLV's 24-bits Flag field. New values are to be CONTROL-SPACE TLV's 24-bits Flag field. New values are to be
assigned by Standards Action [RFC8126]. Each bit should be tracked assigned by Standards Action [RFC8126]. Each bit should be tracked
with the following qualities: with the following qualities:
o Bit number (counting from bit 0 as the most significant bit) * Bit number (counting from bit 0 as the most significant bit)
o Capability description * Capability description
o Defining RFC * Defining RFC
Currently, there is no allocation in this registry. Currently, there is no allocation in this registry.
Bit | Name | Reference Bit | Name | Reference
--------+------------------------------+------------- --------+------------------------------+-------------
0-23 | Unassigned | [This.I-D] 0-23 | Unassigned | [This.I-D]
7.3. FUNCT-ID-CONTROL-SPACE TLV's Flag field 7.3. FUNCT-ID-CONTROL-SPACE TLV's Flag field
This document defines the FUNCT-ID-CONTROL-SPACE TLV and requests This document defines the FUNCT-ID-CONTROL-SPACE TLV and requests
that IANA to create a new sub-registry to manage the value of the that IANA to create a new sub-registry to manage the value of the
FUNCT-ID-CONTROL-SPACE TLV's 24-bits Flag field. New values are to FUNCT-ID-CONTROL-SPACE TLV's 24-bits Flag field. New values are to
be assigned by Standards Action [RFC8126]. Each bit should be be assigned by Standards Action [RFC8126]. Each bit should be
tracked with the following qualities: tracked with the following qualities:
o Bit number (counting from bit 0 as the most significant bit) * Bit number (counting from bit 0 as the most significant bit)
o Capability description * Capability description
o Defining RFC * Defining RFC
Currently, there is no allocation in this registry. Currently, there is no allocation in this registry.
Bit | Name | Reference Bit | Name | Reference
--------+------------------------------+------------- --------+------------------------------+-------------
23 | L-Bit | [This.I-D] 23 | L-Bit | [This.I-D]
0-22 | Unassigned | [This.I-D] 0-22 | Unassigned | [This.I-D]
8. Security Considerations 8. Security Considerations
skipping to change at page 14, line 14 skipping to change at page 14, line 20
[RFC8283] Farrel, A., Ed., Zhao, Q., Ed., Li, Z., and C. Zhou, "An [RFC8283] Farrel, A., Ed., Zhao, Q., Ed., Li, Z., and C. Zhou, "An
Architecture for Use of PCE and the PCE Communication Architecture for Use of PCE and the PCE Communication
Protocol (PCEP) in a Network with Central Control", Protocol (PCEP) in a Network with Central Control",
RFC 8283, DOI 10.17487/RFC8283, December 2017, RFC 8283, DOI 10.17487/RFC8283, December 2017,
<https://www.rfc-editor.org/info/rfc8283>. <https://www.rfc-editor.org/info/rfc8283>.
[I-D.ietf-pce-segment-routing-ipv6] [I-D.ietf-pce-segment-routing-ipv6]
Li, C., Negi, M., Sivabalan, S., Koldychev, M., Li, C., Negi, M., Sivabalan, S., Koldychev, M.,
Kaladharan, P., and Y. Zhu, "PCEP Extensions for Segment Kaladharan, P., and Y. Zhu, "PCEP Extensions for Segment
Routing leveraging the IPv6 data plane", draft-ietf-pce- Routing leveraging the IPv6 data plane", Work in Progress,
segment-routing-ipv6-11 (work in progress), January 2022. Internet-Draft, draft-ietf-pce-segment-routing-ipv6-12, 6
March 2022, <https://www.ietf.org/internet-drafts/draft-
ietf-pce-segment-routing-ipv6-12.txt>.
10.2. Informative References 10.2. Informative References
[RFC4657] Ash, J., Ed. and J. Le Roux, Ed., "Path Computation [RFC4657] Ash, J., Ed. and J.L. Le Roux, Ed., "Path Computation
Element (PCE) Communication Protocol Generic Element (PCE) Communication Protocol Generic
Requirements", RFC 4657, DOI 10.17487/RFC4657, September Requirements", RFC 4657, DOI 10.17487/RFC4657, September
2006, <https://www.rfc-editor.org/info/rfc4657>. 2006, <https://www.rfc-editor.org/info/rfc4657>.
[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer "Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <https://www.rfc-editor.org/info/rfc7525>. 2015, <https://www.rfc-editor.org/info/rfc7525>.
skipping to change at page 15, line 7 skipping to change at page 15, line 14
[RFC9050] Li, Z., Peng, S., Negi, M., Zhao, Q., and C. Zhou, "Path [RFC9050] Li, Z., Peng, S., Negi, M., Zhao, Q., and C. Zhou, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Procedures and Extensions for Using the PCE as a Central Procedures and Extensions for Using the PCE as a Central
Controller (PCECC) of LSPs", RFC 9050, Controller (PCECC) of LSPs", RFC 9050,
DOI 10.17487/RFC9050, July 2021, DOI 10.17487/RFC9050, July 2021,
<https://www.rfc-editor.org/info/rfc9050>. <https://www.rfc-editor.org/info/rfc9050>.
[I-D.ietf-pce-pcep-extension-pce-controller-sr] [I-D.ietf-pce-pcep-extension-pce-controller-sr]
Li, Z., Peng, S., Negi, M. S., Zhao, Q., and C. Zhou, Li, Z., Peng, S., Negi, M. S., Zhao, Q., and C. Zhou,
"PCEP Procedures and Protocol Extensions for Using PCE as "Path Computation Element Communication Protocol (PCEP)
a Central Controller (PCECC) for Segment Routing (SR) MPLS Procedures and Extensions for Using PCE as a Central
Segment Identifier (SID) Allocation and Distribution.", Controller (PCECC) for Segment Routing (SR) MPLS Segment
draft-ietf-pce-pcep-extension-pce-controller-sr-03 (work Identifier (SID) Allocation and Distribution.", Work in
in progress), September 2021. Progress, Internet-Draft, draft-ietf-pce-pcep-extension-
pce-controller-sr-04, 6 March 2022,
<https://www.ietf.org/archive/id/draft-ietf-pce-pcep-
extension-pce-controller-sr-04.txt>.
[I-D.ietf-pce-state-sync] [I-D.ietf-pce-state-sync]
Litkowski, S., Sivabalan, S., Li, C., and H. Zheng, "Inter Litkowski, S., Sivabalan, S., Li, C., and H. Zheng, "Inter
Stateful Path Computation Element (PCE) Communication Stateful Path Computation Element (PCE) Communication
Procedures.", draft-ietf-pce-state-sync-01 (work in Procedures.", Work in Progress, Internet-Draft, draft-
progress), October 2021. ietf-pce-state-sync-01, 20 October 2021,
<https://www.ietf.org/archive/id/draft-ietf-pce-state-
sync-01.txt>.
[I-D.ietf-spring-segment-routing-policy] [I-D.ietf-spring-segment-routing-policy]
Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and
P. Mattes, "Segment Routing Policy Architecture", draft- P. Mattes, "Segment Routing Policy Architecture", Work in
ietf-spring-segment-routing-policy-18 (work in progress), Progress, Internet-Draft, draft-ietf-spring-segment-
February 2022. routing-policy-21, 19 March 2022,
<https://www.ietf.org/archive/id/draft-ietf-spring-
segment-routing-policy-21.txt>.
[I-D.dhody-pce-pcep-extension-pce-controller-srv6] [I-D.dhody-pce-pcep-extension-pce-controller-srv6]
Li, Z., Peng, S., Geng, X., and M. Negi, "Path Computation Li, Z., Peng, S., Geng, X., and M. Negi, "Path Computation
Element Communication Protocol (PCEP) Procedures and Element Communication Protocol (PCEP) Procedures and
Extensions for Using the PCE as a Central Controller Extensions for Using the PCE as a Central Controller
(PCECC) for SRv6 SID Allocation and Distribution.", draft- (PCECC) for SRv6 SID Allocation and Distribution.", Work
dhody-pce-pcep-extension-pce-controller-srv6-07 (work in in Progress, Internet-Draft, draft-dhody-pce-pcep-
progress), August 2021. extension-pce-controller-srv6-08, 6 March 2022,
<https://www.ietf.org/internet-drafts/draft-dhody-pce-
pcep-extension-pce-controller-srv6-08.txt>.
[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,
D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 D., Matsushima, S., and Z. Li, "Segment Routing over IPv6
(SRv6) Network Programming", RFC 8986, (SRv6) Network Programming", RFC 8986,
DOI 10.17487/RFC8986, February 2021, DOI 10.17487/RFC8986, February 2021,
<https://www.rfc-editor.org/info/rfc8986>. <https://www.rfc-editor.org/info/rfc8986>.
[I-D.ietf-pce-binding-label-sid] [I-D.ietf-pce-binding-label-sid]
Sivabalan, S., Filsfils, C., Tantsura, J., Previdi, S., Sivabalan, S., Filsfils, C., Tantsura, J., Previdi, S.,
and C. L. (editor), "Carrying Binding Label/Segment and C. L. (editor), "Carrying Binding Label/Segment
Identifier (SID) in PCE-based Networks.", draft-ietf-pce- Identifier (SID) in PCE-based Networks.", Work in
binding-label-sid-13 (work in progress), February 2022. Progress, Internet-Draft, draft-ietf-pce-binding-label-
sid-14, 3 March 2022, <https://www.ietf.org/archive/id/
draft-ietf-pce-binding-label-sid-14.txt>.
Appendix A. Contributors Appendix A. Contributors
Dhruv Dhody Dhruv Dhody
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560066 Bangalore, Karnataka 560066
India India
EMail: dhruv.ietf@gmail.com EMail: dhruv.ietf@gmail.com
Mach Chen
Huawei Technologies
China
EMail: Mach.chen@huawei.com
Zhenbin Li Zhenbin Li
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
EMail: lizhenbin@huawei.com EMail: lizhenbin@huawei.com
Jie Dong Jie Dong
Huawei Technologies Huawei Technologies
skipping to change at page 16, line 36 skipping to change at page 17, line 10
Beijing 100095 Beijing 100095
China China
EMail: jie.dong@huawei.com EMail: jie.dong@huawei.com
Authors' Addresses Authors' Addresses
Cheng Li Cheng Li
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
Beijing 100095 Beijing
100095
China China
Email: c.l@huawei.com
EMail: c.l@huawei.com Hang Shi
Mach(Guoyi) Chen
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
Beijing 100095 Beijing
100095
China China
Email: shihang9@huawei.com
EMail: Mach.chen@huawei.com
Aijun Wang Aijun Wang
China Telecom China Telecom
Beiqijia Town, Beiqijia Town,
Beijing, Changping District 102209 Beijing
Changping District, 102209
China China
Email: wangaj3@chinatelecom.cn
EMail: wangaj3@chinatelecom.cn
Weiqiang Cheng Weiqiang Cheng
China Mobile China Mobile
Email: chengweiqiang@chinamobile.com
EMail: chengweiqiang@chinamobile.com
Chao Zhou Chao Zhou
HPE HPE
Email: chaozhou_us@yahoo.com
EMail: chaozhou_us@yahoo.com
 End of changes. 36 change blocks. 
54 lines changed or deleted 72 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/