| < draft-ietf-spring-segment-routing-policy-02.txt | draft-ietf-spring-segment-routing-policy-03.txt > | |||
|---|---|---|---|---|
| SPRING Working Group C. Filsfils | SPRING Working Group C. Filsfils | |||
| Internet-Draft S. Sivabalan, Ed. | Internet-Draft S. Sivabalan, Ed. | |||
| Intended status: Standards Track Cisco Systems, Inc. | Intended status: Standards Track Cisco Systems, Inc. | |||
| Expires: April 25, 2019 D. Voyer | Expires: November 13, 2019 D. Voyer | |||
| Bell Canada | Bell Canada | |||
| A. Bogdanov | A. Bogdanov | |||
| Google, Inc. | Google, Inc. | |||
| P. Mattes | P. Mattes | |||
| Microsoft | Microsoft | |||
| October 22, 2018 | May 12, 2019 | |||
| Segment Routing Policy Architecture | Segment Routing Policy Architecture | |||
| draft-ietf-spring-segment-routing-policy-02.txt | draft-ietf-spring-segment-routing-policy-03.txt | |||
| Abstract | Abstract | |||
| Segment Routing (SR) allows a headend node to steer a packet flow | Segment Routing (SR) allows a headend node to steer a packet flow | |||
| along any path. Intermediate per-flow states are eliminated thanks | along any path. Intermediate per-flow states are eliminated thanks | |||
| to source routing. The headend node steers a flow into an SR Policy. | to source routing. The headend node steers a flow into an SR Policy. | |||
| The header of a packet steered in an SR Policy is augmented with an | The header of a packet steered in an SR Policy is augmented with an | |||
| ordered list of segments associated with that SR Policy. This | ordered list of segments associated with that SR Policy. This | |||
| document details the concepts of SR Policy and steering into an SR | document details the concepts of SR Policy and steering into an SR | |||
| Policy. | Policy. | |||
| skipping to change at page 1, line 48 ¶ | skipping to change at page 1, line 48 ¶ | |||
| 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 25, 2019. | This Internet-Draft will expire on November 13, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2019 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 | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 18, line 39 ¶ | skipping to change at page 18, line 39 ¶ | |||
| 6.2.3. Specified-BSID-only | 6.2.3. Specified-BSID-only | |||
| An implementation MAY support the configuration of the Specified- | An implementation MAY support the configuration of the Specified- | |||
| BSID-only restrictive behavior on the headend for all SR Policies or | BSID-only restrictive behavior on the headend for all SR Policies or | |||
| individual SR Policies. Further, this restrictive behavior MAY also | individual SR Policies. Further, this restrictive behavior MAY also | |||
| be signaled on a per SR Policy basis to the headend. | be signaled on a per SR Policy basis to the headend. | |||
| When this restrictive behavior is enabled, if the candidate path has | When this restrictive behavior is enabled, if the candidate path has | |||
| an unspecified BSID or if the specified BSID is not available when | an unspecified BSID or if the specified BSID is not available when | |||
| the candidate path becomes active then no BSID is bound to it and it | the candidate path becomes active then no BSID is bound to it and it | |||
| is considered invalid. An alert MUST be triggered to notify this | is considered invalid. An alert MUST be triggered for this error. | |||
| error. Other candidate paths MUST then be evaluated for becoming the | Other candidate paths MUST then be evaluated for becoming the active | |||
| active candidate path. | candidate path. | |||
| 6.3. Forwarding Plane | 6.3. Forwarding Plane | |||
| A valid SR Policy installs a BSID-keyed entry in the forwarding plane | A valid SR Policy installs a BSID-keyed entry in the forwarding plane | |||
| with the action of steering the packets matching this entry to the | with the action of steering the packets matching this entry to the | |||
| selected path of the SR Policy. | selected path of the SR Policy. | |||
| If the Specified-BSID-only restrictive behavior is enabled and the | If the Specified-BSID-only restrictive behavior is enabled and the | |||
| BSID of the active path is not available (optionally not in the | BSID of the active path is not available (optionally not in the | |||
| SRLB), then the SR Policy does not install any entry indexed by a | SRLB), then the SR Policy does not install any entry indexed by a | |||
| skipping to change at page 27, line 29 ¶ | skipping to change at page 27, line 29 ¶ | |||
| benefit from TI-LFA automated local protection. The SR Policy with | benefit from TI-LFA automated local protection. The SR Policy with | |||
| Segment-List <3, 9, 6> on node 2 can be locally configured to be a | Segment-List <3, 9, 6> on node 2 can be locally configured to be a | |||
| fast-reroute backup path for the link 2to6. | fast-reroute backup path for the link 2to6. | |||
| 9.3. Using a Candidate Path for Path Protection | 9.3. Using a Candidate Path for Path Protection | |||
| An SR Policy allows for multiple candidate paths, of which at any | An SR Policy allows for multiple candidate paths, of which at any | |||
| point in time there is a single active candidate path that is | point in time there is a single active candidate path that is | |||
| provisioned in the forwarding plane and used for traffic steering. | provisioned in the forwarding plane and used for traffic steering. | |||
| However, another (lower preference) candidate path MAY be designated | However, another (lower preference) candidate path MAY be designated | |||
| as the backup for a specific or all (active) candidate path(s). | as the backup for a specific or all (active) candidate path(s). The | |||
| Following options are possible: | following options are possible: | |||
| o A pair of disjoint candidate paths are provisioned with one of | o A pair of disjoint candidate paths are provisioned with one of | |||
| them as primary and the other is identified as its backup. | them as primary and the other is identified as its backup. | |||
| o A specific candidate path is provisioned as the backup for any | o A specific candidate path is provisioned as the backup for any | |||
| (active) candidate path. | (active) candidate path. | |||
| o The headend picks the next (lower) preference valid candidate path | o The headend picks the next (lower) preference valid candidate path | |||
| as the backup for the active candidate path. | as the backup for the active candidate path. | |||
| The headend MAY compute a-priori and validate such backup candidate | The headend MAY compute a-priori and validate such backup candidate | |||
| paths as well as provision them into forwarding plane as backup for | paths as well as provision them into forwarding plane as backup for | |||
| skipping to change at page 29, line 47 ¶ | skipping to change at page 29, line 47 ¶ | |||
| Ali, Z., Filsfils, C., Talaulikar, K., Sivabalan, S., | Ali, Z., Filsfils, C., Talaulikar, K., Sivabalan, S., | |||
| Horneffer, M., Raszuk, R., Litkowski, S., and d. | Horneffer, M., Raszuk, R., Litkowski, S., and d. | |||
| daniel.voyer@bell.ca, "Traffic Accounting in Segment | daniel.voyer@bell.ca, "Traffic Accounting in Segment | |||
| Routing Networks", draft-ali-spring-sr-traffic- | Routing Networks", draft-ali-spring-sr-traffic- | |||
| accounting-02 (work in progress), June 2018. | accounting-02 (work in progress), June 2018. | |||
| [I-D.anand-spring-poi-sr] | [I-D.anand-spring-poi-sr] | |||
| Anand, M., Bardhan, S., Subrahmaniam, R., Tantsura, J., | Anand, M., Bardhan, S., Subrahmaniam, R., Tantsura, J., | |||
| Mukhopadhyaya, U., and C. Filsfils, "Packet-Optical | Mukhopadhyaya, U., and C. Filsfils, "Packet-Optical | |||
| Integration in Segment Routing", draft-anand-spring-poi- | Integration in Segment Routing", draft-anand-spring-poi- | |||
| sr-06 (work in progress), July 2018. | sr-07 (work in progress), January 2019. | |||
| [I-D.bashandy-rtgwg-segment-routing-ti-lfa] | [I-D.bashandy-rtgwg-segment-routing-ti-lfa] | |||
| Bashandy, A., Filsfils, C., Decraene, B., Litkowski, S., | Bashandy, A., Filsfils, C., Decraene, B., Litkowski, S., | |||
| Francois, P., daniel.voyer@bell.ca, d., Clad, F., and P. | Francois, P., daniel.voyer@bell.ca, d., Clad, F., and P. | |||
| Camarillo, "Topology Independent Fast Reroute using | Camarillo, "Topology Independent Fast Reroute using | |||
| Segment Routing", draft-bashandy-rtgwg-segment-routing-ti- | Segment Routing", draft-bashandy-rtgwg-segment-routing-ti- | |||
| lfa-05 (work in progress), October 2018. | lfa-05 (work in progress), October 2018. | |||
| [I-D.filsfils-spring-sr-policy-considerations] | [I-D.filsfils-spring-sr-policy-considerations] | |||
| Filsfils, C., Talaulikar, K., Krol, P., Horneffer, M., and | Filsfils, C., Talaulikar, K., Krol, P., Horneffer, M., and | |||
| P. Mattes, "SR Policy Implementation and Deployment | P. Mattes, "SR Policy Implementation and Deployment | |||
| Considerations", draft-filsfils-spring-sr-policy- | Considerations", draft-filsfils-spring-sr-policy- | |||
| considerations-02 (work in progress), October 2018. | considerations-03 (work in progress), April 2019. | |||
| [I-D.filsfils-spring-sr-traffic-counters] | [I-D.filsfils-spring-sr-traffic-counters] | |||
| Filsfils, C., Ali, Z., Horneffer, M., | Filsfils, C., Ali, Z., Horneffer, M., | |||
| daniel.voyer@bell.ca, d., Durrani, M., and R. Raszuk, | daniel.voyer@bell.ca, d., Durrani, M., and R. Raszuk, | |||
| "Segment Routing Traffic Accounting Counters", draft- | "Segment Routing Traffic Accounting Counters", draft- | |||
| filsfils-spring-sr-traffic-counters-00 (work in progress), | filsfils-spring-sr-traffic-counters-00 (work in progress), | |||
| June 2018. | June 2018. | |||
| [I-D.filsfils-spring-srv6-network-programming] | [I-D.filsfils-spring-srv6-network-programming] | |||
| Filsfils, C., Camarillo, P., Leddy, J., | Filsfils, C., Camarillo, P., Leddy, J., | |||
| daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 | daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 | |||
| Network Programming", draft-filsfils-spring-srv6-network- | Network Programming", draft-filsfils-spring-srv6-network- | |||
| programming-05 (work in progress), July 2018. | programming-07 (work in progress), February 2019. | |||
| [I-D.ietf-idr-bgp-ls-segment-routing-msd] | [I-D.ietf-idr-bgp-ls-segment-routing-msd] | |||
| Tantsura, J., Chunduri, U., Mirsky, G., and S. Sivabalan, | Tantsura, J., Chunduri, U., Mirsky, G., Sivabalan, S., and | |||
| "Signaling MSD (Maximum SID Depth) using Border Gateway | N. Triantafillis, "Signaling MSD (Maximum SID Depth) using | |||
| Protocol Link-State", draft-ietf-idr-bgp-ls-segment- | Border Gateway Protocol Link-State", draft-ietf-idr-bgp- | |||
| routing-msd-02 (work in progress), August 2018. | ls-segment-routing-msd-04 (work in progress), February | |||
| 2019. | ||||
| [I-D.ietf-idr-bgpls-segment-routing-epe] | [I-D.ietf-idr-bgpls-segment-routing-epe] | |||
| Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray, | Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray, | |||
| S., and J. Dong, "BGP-LS extensions for Segment Routing | S., and J. Dong, "BGP-LS extensions for Segment Routing | |||
| BGP Egress Peer Engineering", draft-ietf-idr-bgpls- | BGP Egress Peer Engineering", draft-ietf-idr-bgpls- | |||
| segment-routing-epe-17 (work in progress), October 2018. | segment-routing-epe-18 (work in progress), March 2019. | |||
| [I-D.ietf-idr-segment-routing-te-policy] | [I-D.ietf-idr-segment-routing-te-policy] | |||
| Previdi, S., Filsfils, C., Jain, D., Mattes, P., Rosen, | Previdi, S., Filsfils, C., Jain, D., Mattes, P., Rosen, | |||
| E., and S. Lin, "Advertising Segment Routing Policies in | E., and S. Lin, "Advertising Segment Routing Policies in | |||
| BGP", draft-ietf-idr-segment-routing-te-policy-04 (work in | BGP", draft-ietf-idr-segment-routing-te-policy-05 (work in | |||
| progress), July 2018. | progress), November 2018. | |||
| [I-D.ietf-idr-te-lsp-distribution] | [I-D.ietf-idr-te-lsp-distribution] | |||
| Previdi, S., Talaulikar, K., Dong, J., Chen, M., Gredler, | Previdi, S., Talaulikar, K., Dong, J., Chen, M., Gredler, | |||
| H., and J. Tantsura, "Distribution of Traffic Engineering | H., and J. Tantsura, "Distribution of Traffic Engineering | |||
| (TE) Policies and State using BGP-LS", draft-ietf-idr-te- | (TE) Policies and State using BGP-LS", draft-ietf-idr-te- | |||
| lsp-distribution-09 (work in progress), June 2018. | lsp-distribution-11 (work in progress), May 2019. | |||
| [I-D.ietf-isis-segment-routing-msd] | [I-D.ietf-isis-segment-routing-msd] | |||
| Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg, | Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg, | |||
| "Signaling MSD (Maximum SID Depth) using IS-IS", draft- | "Signaling MSD (Maximum SID Depth) using IS-IS", draft- | |||
| ietf-isis-segment-routing-msd-19 (work in progress), | ietf-isis-segment-routing-msd-19 (work in progress), | |||
| October 2018. | October 2018. | |||
| [I-D.ietf-lsr-flex-algo] | [I-D.ietf-lsr-flex-algo] | |||
| Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and | Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and | |||
| A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex- | A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex- | |||
| algo-00 (work in progress), May 2018. | algo-01 (work in progress), November 2018. | |||
| [I-D.ietf-ospf-segment-routing-msd] | [I-D.ietf-ospf-segment-routing-msd] | |||
| Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak, | Tantsura, J., Chunduri, U., Aldrin, S., and P. Psenak, | |||
| "Signaling MSD (Maximum SID Depth) using OSPF", draft- | "Signaling MSD (Maximum SID Depth) using OSPF", draft- | |||
| ietf-ospf-segment-routing-msd-25 (work in progress), | ietf-ospf-segment-routing-msd-25 (work in progress), | |||
| October 2018. | October 2018. | |||
| [I-D.ietf-pce-segment-routing] | [I-D.ietf-pce-segment-routing] | |||
| Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., | Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., | |||
| and J. Hardwick, "PCEP Extensions for Segment Routing", | and J. Hardwick, "PCEP Extensions for Segment Routing", | |||
| draft-ietf-pce-segment-routing-14 (work in progress), | draft-ietf-pce-segment-routing-16 (work in progress), | |||
| October 2018. | March 2019. | |||
| [I-D.sivabalan-pce-binding-label-sid] | [I-D.sivabalan-pce-binding-label-sid] | |||
| Sivabalan, S., Filsfils, C., Tantsura, J., Hardwick, J., | Sivabalan, S., Filsfils, C., Tantsura, J., Hardwick, J., | |||
| Previdi, S., and D. Dhody, "Carrying Binding Label/ | Previdi, S., and C. Li, "Carrying Binding Label/Segment-ID | |||
| Segment-ID in PCE-based Networks.", draft-sivabalan-pce- | in PCE-based Networks.", draft-sivabalan-pce-binding- | |||
| binding-label-sid-05 (work in progress), October 2018. | label-sid-06 (work in progress), February 2019. | |||
| [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and | [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and | |||
| dual environments", RFC 1195, DOI 10.17487/RFC1195, | dual environments", RFC 1195, DOI 10.17487/RFC1195, | |||
| December 1990, <https://www.rfc-editor.org/info/rfc1195>. | December 1990, <https://www.rfc-editor.org/info/rfc1195>. | |||
| [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, | [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, | |||
| DOI 10.17487/RFC2328, April 1998, | DOI 10.17487/RFC2328, April 1998, | |||
| <https://www.rfc-editor.org/info/rfc2328>. | <https://www.rfc-editor.org/info/rfc2328>. | |||
| [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering | [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering | |||
| End of changes. 17 change blocks. | ||||
| 27 lines changed or deleted | 28 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/ | ||||