| < draft-ietf-spring-segment-routing-11.txt | draft-ietf-spring-segment-routing-12.txt > | |||
|---|---|---|---|---|
| Network Working Group C. Filsfils, Ed. | Network Working Group C. Filsfils, Ed. | |||
| Internet-Draft S. Previdi, Ed. | Internet-Draft S. Previdi, Ed. | |||
| Intended status: Standards Track Cisco Systems, Inc. | Intended status: Standards Track Cisco Systems, Inc. | |||
| Expires: August 20, 2017 B. Decraene | Expires: December 22, 2017 B. Decraene | |||
| S. Litkowski | S. Litkowski | |||
| Orange | Orange | |||
| R. Shakir | R. Shakir | |||
| Google, Inc. | Google, Inc. | |||
| February 16, 2017 | June 20, 2017 | |||
| Segment Routing Architecture | Segment Routing Architecture | |||
| draft-ietf-spring-segment-routing-11 | draft-ietf-spring-segment-routing-12 | |||
| Abstract | Abstract | |||
| Segment Routing (SR) leverages the source routing paradigm. A node | Segment Routing (SR) leverages the source routing paradigm. A node | |||
| steers a packet through an ordered list of instructions, called | steers a packet through an ordered list of instructions, called | |||
| segments. A segment can represent any instruction, topological or | segments. A segment can represent any instruction, topological or | |||
| service-based. A segment can have a semantic local to an SR node or | service-based. A segment can have a semantic local to an SR node or | |||
| global within an SR domain. SR allows to enforce a flow through any | global within an SR domain. SR allows to enforce a flow through any | |||
| topological path and service chain while maintaining per-flow state | topological path and service chain while maintaining per-flow state | |||
| only at the ingress nodes to the SR domain. | only at the ingress nodes to the SR domain. | |||
| 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 http://datatracker.ietf.org/drafts/current/. | Drafts is at http://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 20, 2017. | This Internet-Draft will expire on December 22, 2017. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2017 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 | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://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 24, line 23 ¶ | skipping to change at page 24, line 23 ¶ | |||
| [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) | [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) | |||
| Hierarchy with Generalized Multi-Protocol Label Switching | Hierarchy with Generalized Multi-Protocol Label Switching | |||
| (GMPLS) Traffic Engineering (TE)", RFC 4206, | (GMPLS) Traffic Engineering (TE)", RFC 4206, | |||
| DOI 10.17487/RFC4206, October 2005, | DOI 10.17487/RFC4206, October 2005, | |||
| <http://www.rfc-editor.org/info/rfc4206>. | <http://www.rfc-editor.org/info/rfc4206>. | |||
| 12.2. Informative References | 12.2. Informative References | |||
| [I-D.ietf-6man-segment-routing-header] | [I-D.ietf-6man-segment-routing-header] | |||
| Previdi, S., Filsfils, C., Field, B., Leung, I., Linkova, | Previdi, S., Filsfils, C., Raza, K., Leddy, J., Field, B., | |||
| J., Aries, E., Kosugi, T., Vyncke, E., and D. Lebrun, | daniel.voyer@bell.ca, d., daniel.bernier@bell.ca, d., | |||
| Matsushima, S., Leung, I., Linkova, J., Aries, E., Kosugi, | ||||
| T., Vyncke, E., Lebrun, D., Steinberg, D., and R. Raszuk, | ||||
| "IPv6 Segment Routing Header (SRH)", draft-ietf-6man- | "IPv6 Segment Routing Header (SRH)", draft-ietf-6man- | |||
| segment-routing-header-05 (work in progress), February | segment-routing-header-06 (work in progress), March 2017. | |||
| 2017. | ||||
| [I-D.ietf-isis-segment-routing-extensions] | [I-D.ietf-isis-segment-routing-extensions] | |||
| Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., | Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., | |||
| Litkowski, S., Decraene, B., and j. jefftant@gmail.com, | Litkowski, S., Decraene, B., and j. jefftant@gmail.com, | |||
| "IS-IS Extensions for Segment Routing", draft-ietf-isis- | "IS-IS Extensions for Segment Routing", draft-ietf-isis- | |||
| segment-routing-extensions-09 (work in progress), October | segment-routing-extensions-13 (work in progress), June | |||
| 2016. | 2017. | |||
| [I-D.ietf-mpls-spring-lsp-ping] | [I-D.ietf-mpls-spring-lsp-ping] | |||
| Kumar, N., Swallow, G., Pignataro, C., Akiya, N., Kini, | Kumar, N., Swallow, G., Pignataro, C., Akiya, N., Kini, | |||
| S., Gredler, H., and M. Chen, "Label Switched Path (LSP) | S., Gredler, H., and M. Chen, "Label Switched Path (LSP) | |||
| Ping/Trace for Segment Routing Networks Using MPLS | Ping/Traceroute for Segment Routing Networks with MPLS | |||
| Dataplane", draft-ietf-mpls-spring-lsp-ping-02 (work in | Dataplane", draft-ietf-mpls-spring-lsp-ping-03 (work in | |||
| progress), December 2016. | progress), June 2017. | |||
| [I-D.ietf-ospf-ospfv3-segment-routing-extensions] | [I-D.ietf-ospf-ospfv3-segment-routing-extensions] | |||
| Psenak, P., Previdi, S., Filsfils, C., Gredler, H., | Psenak, P., Previdi, S., Filsfils, C., Gredler, H., | |||
| Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 | Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 | |||
| Extensions for Segment Routing", draft-ietf-ospf-ospfv3- | Extensions for Segment Routing", draft-ietf-ospf-ospfv3- | |||
| segment-routing-extensions-07 (work in progress), October | segment-routing-extensions-09 (work in progress), March | |||
| 2016. | 2017. | |||
| [I-D.ietf-ospf-segment-routing-extensions] | [I-D.ietf-ospf-segment-routing-extensions] | |||
| Psenak, P., Previdi, S., Filsfils, C., Gredler, H., | Psenak, P., Previdi, S., Filsfils, C., Gredler, H., | |||
| Shakir, R., Henderickx, W., and J. Tantsura, "OSPF | Shakir, R., Henderickx, W., and J. Tantsura, "OSPF | |||
| Extensions for Segment Routing", draft-ietf-ospf-segment- | Extensions for Segment Routing", draft-ietf-ospf-segment- | |||
| routing-extensions-10 (work in progress), October 2016. | routing-extensions-16 (work in progress), May 2017. | |||
| [I-D.ietf-pce-segment-routing] | [I-D.ietf-pce-segment-routing] | |||
| Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E., | Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., | |||
| Raszuk, R., Lopez, V., Tantsura, J., Henderickx, W., and | and J. Hardwick, "PCEP Extensions for Segment Routing", | |||
| J. Hardwick, "PCEP Extensions for Segment Routing", draft- | draft-ietf-pce-segment-routing-09 (work in progress), | |||
| ietf-pce-segment-routing-08 (work in progress), October | April 2017. | |||
| 2016. | ||||
| [I-D.ietf-spring-conflict-resolution] | [I-D.ietf-spring-conflict-resolution] | |||
| Ginsberg, L., Psenak, P., Previdi, S., and M. Pilka, | Ginsberg, L., Psenak, P., Previdi, S., and M. Pilka, | |||
| "Segment Routing Conflict Resolution", draft-ietf-spring- | "Segment Routing MPLS Conflict Resolution", draft-ietf- | |||
| conflict-resolution-02 (work in progress), October 2016. | spring-conflict-resolution-04 (work in progress), May | |||
| 2017. | ||||
| [I-D.ietf-spring-ipv6-use-cases] | [I-D.ietf-spring-ipv6-use-cases] | |||
| Brzozowski, J., Leddy, J., Filsfils, C., Maglione, R., and | Brzozowski, J., Leddy, J., Filsfils, C., Maglione, R., and | |||
| W. Townsley, "IPv6 SPRING Use Cases", draft-ietf-spring- | M. Townsley, "IPv6 SPRING Use Cases", draft-ietf-spring- | |||
| ipv6-use-cases-09 (work in progress), February 2017. | ipv6-use-cases-11 (work in progress), June 2017. | |||
| [I-D.ietf-spring-oam-usecase] | [I-D.ietf-spring-oam-usecase] | |||
| Geib, R., Filsfils, C., Pignataro, C., and N. Kumar, "A | Geib, R., Filsfils, C., Pignataro, C., and N. Kumar, "A | |||
| Scalable and Topology-Aware MPLS Dataplane Monitoring | Scalable and Topology-Aware MPLS Dataplane Monitoring | |||
| System", draft-ietf-spring-oam-usecase-05 (work in | System", draft-ietf-spring-oam-usecase-06 (work in | |||
| progress), February 2017. | progress), February 2017. | |||
| [I-D.ietf-spring-resiliency-use-cases] | [I-D.ietf-spring-resiliency-use-cases] | |||
| Filsfils, C., Previdi, S., Decraene, B., and R. Shakir, | Filsfils, C., Previdi, S., Decraene, B., and R. Shakir, | |||
| "Resiliency use cases in SPRING networks", draft-ietf- | "Resiliency use cases in SPRING networks", draft-ietf- | |||
| spring-resiliency-use-cases-08 (work in progress), October | spring-resiliency-use-cases-11 (work in progress), May | |||
| 2016. | 2017. | |||
| [I-D.ietf-spring-segment-routing-central-epe] | [I-D.ietf-spring-segment-routing-central-epe] | |||
| Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev, | Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev, | |||
| "Segment Routing Centralized BGP Peer Engineering", draft- | "Segment Routing Centralized BGP Egress Peer Engineering", | |||
| ietf-spring-segment-routing-central-epe-03 (work in | draft-ietf-spring-segment-routing-central-epe-05 (work in | |||
| progress), November 2016. | progress), March 2017. | |||
| [I-D.ietf-spring-segment-routing-ldp-interop] | [I-D.ietf-spring-segment-routing-ldp-interop] | |||
| Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., and | Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., and | |||
| S. Litkowski, "Segment Routing interworking with LDP", | S. Litkowski, "Segment Routing interworking with LDP", | |||
| draft-ietf-spring-segment-routing-ldp-interop-06 (work in | draft-ietf-spring-segment-routing-ldp-interop-08 (work in | |||
| progress), February 2017. | progress), June 2017. | |||
| [I-D.ietf-spring-segment-routing-mpls] | [I-D.ietf-spring-segment-routing-mpls] | |||
| Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | |||
| Litkowski, S., Horneffer, M., Shakir, R., | Litkowski, S., and R. Shakir, "Segment Routing with MPLS | |||
| jefftant@gmail.com, j., and E. Crabbe, "Segment Routing | data plane", draft-ietf-spring-segment-routing-mpls-09 | |||
| with MPLS data plane", draft-ietf-spring-segment-routing- | (work in progress), June 2017. | |||
| mpls-07 (work in progress), February 2017. | ||||
| [I-D.ietf-spring-sr-oam-requirement] | [I-D.ietf-spring-sr-oam-requirement] | |||
| Kumar, N., Pignataro, C., Akiya, N., Geib, R., Mirsky, G., | Kumar, N., Pignataro, C., Akiya, N., Geib, R., Mirsky, G., | |||
| and S. Litkowski, "OAM Requirements for Segment Routing | and S. Litkowski, "OAM Requirements for Segment Routing | |||
| Network", draft-ietf-spring-sr-oam-requirement-03 (work in | Network", draft-ietf-spring-sr-oam-requirement-03 (work in | |||
| progress), January 2017. | progress), January 2017. | |||
| [I-D.ietf-spring-sr-yang] | [I-D.ietf-spring-sr-yang] | |||
| Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG | Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG | |||
| Data Model for Segment Routing", draft-ietf-spring-sr- | Data Model for Segment Routing", draft-ietf-spring-sr- | |||
| yang-05 (work in progress), October 2016. | yang-06 (work in progress), March 2017. | |||
| [RFC4381] Behringer, M., "Analysis of the Security of BGP/MPLS IP | [RFC4381] Behringer, M., "Analysis of the Security of BGP/MPLS IP | |||
| Virtual Private Networks (VPNs)", RFC 4381, | Virtual Private Networks (VPNs)", RFC 4381, | |||
| DOI 10.17487/RFC4381, February 2006, | DOI 10.17487/RFC4381, February 2006, | |||
| <http://www.rfc-editor.org/info/rfc4381>. | <http://www.rfc-editor.org/info/rfc4381>. | |||
| [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. | [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. | |||
| Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", | Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", | |||
| RFC 4915, DOI 10.17487/RFC4915, June 2007, | RFC 4915, DOI 10.17487/RFC4915, June 2007, | |||
| <http://www.rfc-editor.org/info/rfc4915>. | <http://www.rfc-editor.org/info/rfc4915>. | |||
| skipping to change at page 27, line 41 ¶ | skipping to change at page 27, line 41 ¶ | |||
| Clarence Filsfils (editor) | Clarence Filsfils (editor) | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| Brussels | Brussels | |||
| BE | BE | |||
| Email: cfilsfil@cisco.com | Email: cfilsfil@cisco.com | |||
| Stefano Previdi (editor) | Stefano Previdi (editor) | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| Via Del Serafico, 200 | ||||
| Rome 00142 | ||||
| Italy | Italy | |||
| Email: sprevidi@cisco.com | Email: stefano@previdi.net | |||
| Bruno Decraene | Bruno Decraene | |||
| Orange | Orange | |||
| FR | FR | |||
| Email: bruno.decraene@orange.com | Email: bruno.decraene@orange.com | |||
| Stephane Litkowski | Stephane Litkowski | |||
| Orange | Orange | |||
| FR | FR | |||
| Email: stephane.litkowski@orange.com | Email: stephane.litkowski@orange.com | |||
| Rob Shakir | Rob Shakir | |||
| Google, Inc. | Google, Inc. | |||
| 1600 Amphitheatre Parkway | 1600 Amphitheatre Parkway | |||
| Mountain View, CA 94043 | Mountain View, CA 94043 | |||
| End of changes. 22 change blocks. | ||||
| 42 lines changed or deleted | 40 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/ | ||||