< draft-li-spring-sr-sfc-control-plane-framework-05.txt   draft-li-spring-sr-sfc-control-plane-framework-06.txt >
SPRING Working Group C. Li SPRING Working Group C. Li
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Informational A. Sawaf Intended status: Informational A. Sawaf
Expires: April 24, 2022 Saudi Telecom Company Expires: 24 October 2022 Saudi Telecom Company
R. Hu R. Hu
Z. Li Z. Li
Huawei Technologies Huawei Technologies
October 21, 2021 22 April 2022
A Framework for Constructing Service Function Chaining Systems Based on A Framework for Constructing Service Function Chaining Systems Based on
Segment Routing Segment Routing
draft-li-spring-sr-sfc-control-plane-framework-05 draft-li-spring-sr-sfc-control-plane-framework-06
Abstract Abstract
Segment Routing (SR) allows for a flexible definition of end-to-end Segment Routing (SR) allows for a flexible definition of end-to-end
paths by encoding paths as sequences of topological sub-paths, called paths by encoding paths as sequences of topological sub-paths, called
"segments". Segment routing architecture can be implemented over an "segments". Segment routing architecture can be implemented over an
MPLS data plane as well as an IPv6 data plane. MPLS data plane as well as an IPv6 data plane.
Service Function Chaining (SFC) provides support for the creation of Service Function Chaining (SFC) provides support for the creation of
composite services that consist of an ordered set of Service composite services that consist of an ordered set of Service
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 April 24, 2022. This Internet-Draft will expire on 24 October 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview of SR Based SFC Control Plane . . . . . . . . . . . 4 2. Overview of SR Based SFC Control Plane . . . . . . . . . . . 4
3. Stateless SR Based SFC . . . . . . . . . . . . . . . . . . . 6 3. Stateless SR Based SFC . . . . . . . . . . . . . . . . . . . 7
3.1. Service Function Instance Route Distribution . . . . . . 6 3.1. Service Function Instance Route Distribution . . . . . . 7
3.2. Service Function Path Route Distribution . . . . . . . . 7 3.2. Service Function Path Route Distribution . . . . . . . . 8
3.3. Steer Packets into SFC . . . . . . . . . . . . . . . . . 7 3.3. Steer Packets into SFC . . . . . . . . . . . . . . . . . 8
4. Stateful SR Based SFC . . . . . . . . . . . . . . . . . . . . 8 4. Stateful SR Based SFC . . . . . . . . . . . . . . . . . . . . 8
4.1. Service Function Route Distribution . . . . . . . . . . . 8 4.1. Service Function Route Distribution . . . . . . . . . . . 8
4.2. Service Function Path Route Distribution . . . . . . . . 8 4.2. Service Function Path Route Distribution . . . . . . . . 9
4.3. Steer Packets into SFC . . . . . . . . . . . . . . . . . 8 4.3. Steer Packets into SFC . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
Segment routing (SR) [RFC8402] is a source routing paradigm that Segment routing (SR) [RFC8402] is a source routing paradigm that
explicitly indicates the forwarding path for packets at the ingress explicitly indicates the forwarding path for packets at the ingress
node by inserting an ordered list of instructions, called segments. node by inserting an ordered list of instructions, called segments.
When segment routing is deployed on MPLS data plane, it is called SR- When segment routing is deployed on MPLS data plane, it is called SR-
MPLS [RFC8660]. When segment routing is deployed on IPv6 data plane, MPLS [RFC8660]. When segment routing is deployed on IPv6 data plane,
it is called SRv6 [RFC8754]. it is called SRv6 [RFC8754].
skipping to change at page 5, line 24 skipping to change at page 5, line 33
+--------------+ +------+ +------+ +--------------+ +------+ +------+
| | SFC Encap/SR | SFF1/| | SFF2/| | | SFC Encap/SR | SFF1/| | SFF2/|
--->|CF/SR ingress |+---------------->| SR |--------| SR |-------> --->|CF/SR ingress |+---------------->| SR |--------| SR |------->
| | | | | | | | | | | |
+--------------+ +------+ +------+ +--------------+ +------+ +------+
SFC-enabled Domain SFC-enabled Domain
Figure 2. SR based SFC architecture. Figure 2. SR based SFC architecture.
o CF/SR ingress: an SR ingress node plays the role of Classifier in * CF/SR ingress: an SR ingress node plays the role of Classifier in
the SFC architecture, and it connects to an SR controller, where the SFC architecture, and it connects to an SR controller, where
the SR policies originate. the SR policies originate.
o SR-C: SR Controller (SR-C) is connected to the SR ingress node, * SR-C: SR Controller (SR-C) is connected to the SR ingress node,
and may be attached to any node in the network. SR-C is capable and may be attached to any node in the network. SR-C is capable
of discovering topology, and calculating constrained paths for of discovering topology, and calculating constrained paths for
SFCs. SFCs.
o SFF/SR nodes: the SFF component in SFC architecture, which enables * SFF/SR nodes: the SFF component in SFC architecture, which enables
SR to steer packets to SFs. SR to steer packets to SFs.
o SFn: Service Functions, can be SR-aware or SR-unaware. If an SF * SFn: Service Functions, can be SR-aware or SR-unaware. If an SF
is SR-unaware then SR proxy is needed. is SR-unaware then SR proxy is needed.
o SR proxy: A proxy between SFF/SR nodes and SR-unaware SF. * SR proxy: A proxy between SFF/SR nodes and SR-unaware SF.
There are two solutions to encode SFC in the SR data plane. There are two solutions to encode SFC in the SR data plane.
[I-D.ietf-spring-sr-service-programming] defines data plane [I-D.ietf-spring-sr-service-programming] defines data plane
functionality required to implement service segments and achieve functionality required to implement service segments and achieve
service programming in SR-enabled MPLS and IP networks. It can be service programming in SR-enabled MPLS and IP networks. It can be
termed "Stateless SFC" since no per-SFC state is maintained on the SR termed "Stateless SFC" since no per-SFC state is maintained on the SR
nodes along the SFP. nodes along the SFP.
The second solution can be termed "Stateful SFC" The second solution can be termed "Stateful SFC"
[I-D.ietf-spring-nsh-sr], since it still maintains per-SFC state on [I-D.ietf-spring-nsh-sr], since it still maintains per-SFC state on
nodes. [I-D.ietf-spring-nsh-sr]describes two modes of operation: nodes. [I-D.ietf-spring-nsh-sr]describes two modes of operation:
o NSH-based SFC with SR-based transport tunnel: SR is used as the * NSH-based SFC with SR-based transport tunnel: SR is used as the
transport tunnel to route packets between classifier and SFF or transport tunnel to route packets between classifier and SFF or
SFFs. Service plane routing relies on NSH. SFFs. Service plane routing relies on NSH.
o SR-based SFC with Integrated NSH Service Plane: The SFP is encoded * SR-based SFC with Integrated NSH Service Plane: The SFP is encoded
within the SR segment-list, while the NSH only maintains the within the SR segment-list, while the NSH only maintains the
service plane context information, which will be used at NSH-aware service plane context information, which will be used at NSH-aware
SFs, and at SFFs as a pointer to cache SR segment-lists. SFs, and at SFFs as a pointer to cache SR segment-lists.
In order to support these data plane encodings, control plane In order to support these data plane encodings, control plane
mechanisms are required. The existing control plane mechanisms are mechanisms are required. The existing control plane mechanisms are
shown in table 1. shown in table 1.
+------------------------------------------------------------+ +------------------------------------------------------------+
| SR based SFC | SFIR | SFPR | Steering policy| | SR based SFC | SFIR | SFPR | Steering policy|
skipping to change at page 8, line 10 skipping to change at page 8, line 24
In SR, packet steering rules are learned through SR policy. Thus, In SR, packet steering rules are learned through SR policy. Thus,
there is no need to install other rules in the classifier, which is there is no need to install other rules in the classifier, which is
the SR source node. the SR source node.
4. Stateful SR Based SFC 4. Stateful SR Based SFC
"Stateful SFC" [I-D.ietf-spring-nsh-sr] proposes two modes of SR "Stateful SFC" [I-D.ietf-spring-nsh-sr] proposes two modes of SR
based SFC: based SFC:
o NSH-based SFC with SR-based transport tunnel * NSH-based SFC with SR-based transport tunnel
o SR-based SFC with Integrated NSH Service Plane * SR-based SFC with Integrated NSH Service Plane
4.1. Service Function Route Distribution 4.1. Service Function Route Distribution
For NSH-based SFC with SR-based transport tunnel, service information For NSH-based SFC with SR-based transport tunnel, service information
is maintained by NSH while SR is only used for transport between is maintained by NSH while SR is only used for transport between
SFFs, so [I-D.ietf-bess-nsh-bgp-control-plane] can be used for this SFFs, so [I-D.ietf-bess-nsh-bgp-control-plane] can be used for this
mode. mode.
To indicate NSH, an SFF label [I-D.ietf-mpls-sfc-encapsulation] To indicate NSH, an SFF label [I-D.ietf-mpls-sfc-encapsulation]
should be inserted as the last label in the label stack in SR-MPLS. should be inserted as the last label in the label stack in SR-MPLS.
skipping to change at page 9, line 37 skipping to change at page 10, line 11
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[I-D.dawra-idr-bgp-ls-sr-service-segments] [I-D.dawra-idr-bgp-ls-sr-service-segments]
Dawra, G., Filsfils, C., Talaulikar, K., Clad, F., Dawra, G., Filsfils, C., Talaulikar, K., Clad, F.,
Bernier, D., Uttaro, J., Decraene, B., Elmalky, H., Xu, Bernier, D., Uttaro, J., Decraene, B., Elmalky, H., Xu,
X., Guichard, J., and C. Li, "BGP-LS Advertisement of X., Guichard, J., and C. Li, "BGP-LS Advertisement of
Segment Routing Service Segments", draft-dawra-idr-bgp-ls- Segment Routing Service Segments", Work in Progress,
sr-service-segments-06 (work in progress), August 2021. Internet-Draft, draft-dawra-idr-bgp-ls-sr-service-
segments-06, 17 August 2021,
<https://www.ietf.org/archive/id/draft-dawra-idr-bgp-ls-
sr-service-segments-06.txt>.
[I-D.ietf-bess-nsh-bgp-control-plane] [I-D.ietf-bess-nsh-bgp-control-plane]
Farrel, A., Drake, J., Rosen, E., Uttaro, J., and L. Farrel, A., Drake, J., Rosen, E., Uttaro, J., and L.
Jalil, "BGP Control Plane for the Network Service Header Jalil, "BGP Control Plane for the Network Service Header
in Service Function Chaining", draft-ietf-bess-nsh-bgp- in Service Function Chaining", Work in Progress, Internet-
control-plane-18 (work in progress), August 2020. Draft, draft-ietf-bess-nsh-bgp-control-plane-18, 21 August
2020, <https://www.ietf.org/archive/id/draft-ietf-bess-
nsh-bgp-control-plane-18.txt>.
[I-D.ietf-idr-bgp-ls-segment-routing-ext] [I-D.ietf-idr-bgp-ls-segment-routing-ext]
Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H., Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H.,
and M. Chen, "Border Gateway Protocol - Link State (BGP- and M. Chen, "Border Gateway Protocol - Link State (BGP-
LS) Extensions for Segment Routing", draft-ietf-idr-bgp- LS) Extensions for Segment Routing", Work in Progress,
ls-segment-routing-ext-18 (work in progress), April 2021. Internet-Draft, draft-ietf-idr-bgp-ls-segment-routing-ext-
18, 15 April 2021, <https://www.ietf.org/archive/id/draft-
ietf-idr-bgp-ls-segment-routing-ext-18.txt>.
[I-D.ietf-idr-bgpls-srv6-ext] [I-D.ietf-idr-bgpls-srv6-ext]
Dawra, G., Filsfils, C., Talaulikar, K., Chen, M., Dawra, G., Filsfils, C., Talaulikar, K., Chen, M.,
Bernier, D., and B. Decraene, "BGP Link State Extensions Bernier, D., and B. Decraene, "BGP Link State Extensions
for SRv6", draft-ietf-idr-bgpls-srv6-ext-08 (work in for SRv6", Work in Progress, Internet-Draft, draft-ietf-
progress), June 2021. idr-bgpls-srv6-ext-09, 10 November 2021,
<https://www.ietf.org/archive/id/draft-ietf-idr-bgpls-
srv6-ext-09.txt>.
[I-D.ietf-idr-segment-routing-te-policy] [I-D.ietf-idr-segment-routing-te-policy]
Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P., Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P.,
Rosen, E., Jain, D., and S. Lin, "Advertising Segment Jain, D., and S. Lin, "Advertising Segment Routing
Routing Policies in BGP", draft-ietf-idr-segment-routing- Policies in BGP", Work in Progress, Internet-Draft, draft-
te-policy-13 (work in progress), June 2021. ietf-idr-segment-routing-te-policy-17, 14 April 2022,
<https://www.ietf.org/archive/id/draft-ietf-idr-segment-
routing-te-policy-17.txt>.
[I-D.ietf-mpls-sfc-encapsulation] [I-D.ietf-mpls-sfc-encapsulation]
Malis, A. G., Bryant, S., Halpern, J. M., and W. Malis, A. G., Bryant, S., Halpern, J. M., and W.
Henderickx, "MPLS Transport Encapsulation for the Service Henderickx, "MPLS Transport Encapsulation for the Service
Function Chaining (SFC) Network Service Header (NSH)", Function Chaining (SFC) Network Service Header (NSH)",
draft-ietf-mpls-sfc-encapsulation-04 (work in progress), Work in Progress, Internet-Draft, draft-ietf-mpls-sfc-
March 2019. encapsulation-04, 24 March 2019,
<https://www.ietf.org/archive/id/draft-ietf-mpls-sfc-
encapsulation-04.txt>.
[I-D.ietf-pce-segment-routing-policy-cp] [I-D.ietf-pce-segment-routing-policy-cp]
Koldychev, M., Sivabalan, S., Barth, C., Peng, S., and H. Koldychev, M., Sivabalan, S., Barth, C., Peng, S., and H.
Bidgoli, "PCEP extension to support Segment Routing Policy Bidgoli, "PCEP extension to support Segment Routing Policy
Candidate Paths", draft-ietf-pce-segment-routing-policy- Candidate Paths", Work in Progress, Internet-Draft, draft-
cp-05 (work in progress), May 2021. ietf-pce-segment-routing-policy-cp-07, 21 April 2022,
<https://www.ietf.org/archive/id/draft-ietf-pce-segment-
routing-policy-cp-07.txt>.
[I-D.ietf-spring-nsh-sr] [I-D.ietf-spring-nsh-sr]
Guichard, J. N. and J. Tantsura, "Integration of Network Guichard, J. N. and J. Tantsura, "Integration of Network
Service Header (NSH) and Segment Routing for Service Service Header (NSH) and Segment Routing for Service
Function Chaining (SFC)", draft-ietf-spring-nsh-sr-09 Function Chaining (SFC)", Work in Progress, Internet-
(work in progress), July 2021. Draft, draft-ietf-spring-nsh-sr-11, 20 April 2022,
<https://www.ietf.org/archive/id/draft-ietf-spring-nsh-sr-
11.txt>.
[I-D.ietf-spring-sr-service-programming] [I-D.ietf-spring-sr-service-programming]
Clad, F., Xu, X., Filsfils, C., Bernier, D., Li, C., Clad, F., Xu, X., Filsfils, C., Bernier, D., Li, C.,
Decraene, B., Ma, S., Yadlapalli, C., Henderickx, W., and Decraene, B., Ma, S., Yadlapalli, C., Henderickx, W., and
S. Salsano, "Service Programming with Segment Routing", S. Salsano, "Service Programming with Segment Routing",
draft-ietf-spring-sr-service-programming-05 (work in Work in Progress, Internet-Draft, draft-ietf-spring-sr-
progress), September 2021. service-programming-05, 10 September 2021,
<https://www.ietf.org/archive/id/draft-ietf-spring-sr-
service-programming-05.txt>.
[I-D.wu-pce-traffic-steering-sfc] [I-D.wu-pce-traffic-steering-sfc]
Wu, Q., Dhody, D., Boucadair, M., Jacquenet, C., and J. Wu, Q., Dhody, D., Boucadair, M., Jacquenet, C., and J.
Tantsura, "PCEP Extensions for Service Function Chaining Tantsura, "PCEP Extensions for Service Function Chaining
(SFC)", draft-wu-pce-traffic-steering-sfc-12 (work in (SFC)", Work in Progress, Internet-Draft, draft-wu-pce-
progress), June 2017. traffic-steering-sfc-12, 30 June 2017,
<https://www.ietf.org/archive/id/draft-wu-pce-traffic-
steering-sfc-12.txt>.
[I-D.xu-isis-service-function-adv] [I-D.xu-isis-service-function-adv]
Xu, X., Wu, N., Shah, H., and L. M. Contreras, Xu, X., Wu, N., Shah, H., and L. M. Contreras,
"Advertising Service Functions Using IS-IS", draft-xu- "Advertising Service Functions Using IS-IS", Work in
isis-service-function-adv-05 (work in progress), May 2017. Progress, Internet-Draft, draft-xu-isis-service-function-
adv-05, 10 May 2017, <https://www.ietf.org/archive/id/
draft-xu-isis-service-function-adv-05.txt>.
[I-D.xu-ospf-service-function-adv] [I-D.xu-ospf-service-function-adv]
Xu, X., Wu, N., Shah, H., and L. M. Contreras, Xu, X., Wu, N., Shah, H., and L. M. Contreras,
"Advertising Service Functions Using OSPF", draft-xu-ospf- "Advertising Service Functions Using OSPF", Work in
service-function-adv-02 (work in progress), June 2014. Progress, Internet-Draft, draft-xu-ospf-service-function-
adv-02, 29 June 2014, <https://www.ietf.org/archive/id/
draft-xu-ospf-service-function-adv-02.txt>.
[RFC4970] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and [RFC4970] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and
S. Shaffer, "Extensions to OSPF for Advertising Optional S. Shaffer, "Extensions to OSPF for Advertising Optional
Router Capabilities", RFC 4970, DOI 10.17487/RFC4970, July Router Capabilities", RFC 4970, DOI 10.17487/RFC4970, July
2007, <https://www.rfc-editor.org/info/rfc4970>. 2007, <https://www.rfc-editor.org/info/rfc4970>.
[RFC4971] Vasseur, JP., Ed., Shen, N., Ed., and R. Aggarwal, Ed., [RFC4971] Vasseur, JP., Ed., Shen, N., Ed., and R. Aggarwal, Ed.,
"Intermediate System to Intermediate System (IS-IS) "Intermediate System to Intermediate System (IS-IS)
Extensions for Advertising Router Information", RFC 4971, Extensions for Advertising Router Information", RFC 4971,
DOI 10.17487/RFC4971, July 2007, DOI 10.17487/RFC4971, July 2007,
skipping to change at page 11, line 51 skipping to change at page 12, line 49
[RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J.,
Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
(SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020,
<https://www.rfc-editor.org/info/rfc8754>. <https://www.rfc-editor.org/info/rfc8754>.
Authors' Addresses Authors' Addresses
Cheng Li Cheng Li
Huawei Technologies Huawei Technologies
Email: c.l@huawei.com Email: c.l@huawei.com
Ahmed El Sawaf Ahmed El Sawaf
Saudi Telecom Company Saudi Telecom Company
Riyadh Riyadh
Saudi Arabia Saudi Arabia
Email: aelsawaf.c@stc.com.sa Email: aelsawaf.c@stc.com.sa
Ruizhao Hu Ruizhao Hu
Huawei Technologies Huawei Technologies
Huawei Campus, No. 156 Beiqing Rd. Huawei Campus, No. 156 Beiqing Rd.
Beijing 100095 Beijing
100095
China China
Email: huruizhao@huawei.com Email: huruizhao@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
 End of changes. 36 change blocks. 
61 lines changed or deleted 83 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/