| draft-ietf-idr-sr-policy-path-segment-01.txt | draft-ietf-idr-sr-policy-path-segment-02.txt | |||
|---|---|---|---|---|
| Interdomain Routing Working Group C. Li | Interdomain Routing Working Group C. Li | |||
| Internet-Draft Z. Li | Internet-Draft Z. Li | |||
| Intended status: Standards Track Huawei Technologies | Intended status: Standards Track Huawei Technologies | |||
| Expires: February 12, 2021 H. Chen | Expires: May 6, 2021 H. Chen | |||
| China Telecom | China Telecom | |||
| W. Cheng | W. Cheng | |||
| China Mobile | China Mobile | |||
| K. Talaulikar | K. Talaulikar | |||
| Cisco Systems | Cisco Systems | |||
| August 11, 2020 | November 2, 2020 | |||
| SR Policy Extensions for Path Segment and Bidirectional Path | SR Policy Extensions for Path Segment and Bidirectional Path | |||
| draft-ietf-idr-sr-policy-path-segment-01 | draft-ietf-idr-sr-policy-path-segment-02 | |||
| Abstract | Abstract | |||
| A Segment Routing (SR) policy is a set of candidate SR paths | A Segment Routing (SR) policy is a set of candidate SR paths | |||
| consisting of one or more segment lists with necessary path | consisting of one or more segment lists with necessary path | |||
| attributes. For each SR path, it may also have its own path | attributes. For each SR path, it may also have its own path | |||
| attributes, and Path Segment is one of them. A Path Segment is | attributes, and Path Segment is one of them. A Path Segment is | |||
| defined to identify an SR path, which can be used for performance | defined to identify an SR path, which can be used for performance | |||
| measurement, path correlation, and end-2-end path protection. Path | measurement, path correlation, and end-2-end path protection. Path | |||
| Segment can be also used to correlate two unidirectional SR paths | Segment can be also used to correlate two unidirectional SR paths | |||
| skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
| 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 February 12, 2021. | This Internet-Draft will expire on May 6, 2021. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2020 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/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 10, line 23 ¶ | skipping to change at page 10, line 23 ¶ | |||
| [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 | Rosen, E., Jain, D., and S. Lin, "Advertising Segment | |||
| Routing Policies in BGP", draft-ietf-idr-segment-routing- | Routing Policies in BGP", draft-ietf-idr-segment-routing- | |||
| te-policy-09 (work in progress), May 2020. | te-policy-09 (work in progress), May 2020. | |||
| [I-D.ietf-spring-mpls-path-segment] | [I-D.ietf-spring-mpls-path-segment] | |||
| Cheng, W., Li, H., Chen, M., Gandhi, R., and R. Zigler, | Cheng, W., Li, H., Chen, M., Gandhi, R., and R. Zigler, | |||
| "Path Segment in MPLS Based Segment Routing Network", | "Path Segment in MPLS Based Segment Routing Network", | |||
| draft-ietf-spring-mpls-path-segment-02 (work in progress), | draft-ietf-spring-mpls-path-segment-03 (work in progress), | |||
| February 2020. | September 2020. | |||
| [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", draft- | |||
| ietf-spring-segment-routing-policy-08 (work in progress), | ietf-spring-segment-routing-policy-09 (work in progress), | |||
| July 2020. | November 2020. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [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>. | |||
| skipping to change at page 11, line 42 ¶ | skipping to change at page 11, line 42 ¶ | |||
| China | China | |||
| Email: lizhenbin@huawei.com | Email: lizhenbin@huawei.com | |||
| Huanan Chen | Huanan Chen | |||
| China Telecom | China Telecom | |||
| 109 West Zhongshan Ave | 109 West Zhongshan Ave | |||
| Guangzhou | Guangzhou | |||
| China | China | |||
| Email: chenhn8.gd@chinatelecom.cn | Email: chenhuan6@chinatelecom.cn | |||
| Weiqiang Cheng | Weiqiang Cheng | |||
| China Mobile | China Mobile | |||
| Beijing | Beijing | |||
| China | China | |||
| Email: chengweiqiang@chinamobile.com | Email: chengweiqiang@chinamobile.com | |||
| Ketan Talaulikar | Ketan Talaulikar | |||
| Cisco Systems | Cisco Systems | |||
| End of changes. 7 change blocks. | ||||
| 9 lines changed or deleted | 9 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/ | ||||