| < draft-ietf-spring-segment-routing-01.txt | draft-ietf-spring-segment-routing-02.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 A. Bashandy | Intended status: Standards Track A. Bashandy | |||
| Expires: August 9, 2015 Cisco Systems, Inc. | Expires: November 6, 2015 Cisco Systems, Inc. | |||
| B. Decraene | B. Decraene | |||
| S. Litkowski | S. Litkowski | |||
| Orange | Orange | |||
| M. Horneffer | M. Horneffer | |||
| Deutsche Telekom | Deutsche Telekom | |||
| R. Shakir | R. Shakir | |||
| British Telecom | British Telecom | |||
| J. Tantsura | J. Tantsura | |||
| Ericsson | Ericsson | |||
| E. Crabbe | E. Crabbe | |||
| Individual | Individual | |||
| February 5, 2015 | May 5, 2015 | |||
| Segment Routing Architecture | Segment Routing Architecture | |||
| draft-ietf-spring-segment-routing-01 | draft-ietf-spring-segment-routing-02 | |||
| 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 local semantic to an SR node or | service-based. A segment can have a local semantic 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 node to the SR domain. | only at the ingress node to the SR domain. | |||
| skipping to change at page 2, line 26 ¶ | skipping to change at page 2, line 26 ¶ | |||
| 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 9, 2015. | This Internet-Draft will expire on November 6, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 12, line 15 ¶ | skipping to change at page 12, line 15 ¶ | |||
| 3.6. Binding Segment | 3.6. Binding Segment | |||
| 3.6.1. Mapping Server | 3.6.1. Mapping Server | |||
| A Remote-Binding SID S advertised by the mapping server M for remote | A Remote-Binding SID S advertised by the mapping server M for remote | |||
| prefix R attached to non-SR-capable node N signals the same | prefix R attached to non-SR-capable node N signals the same | |||
| information as if N had advertised S as a Prefix-SID. Further | information as if N had advertised S as a Prefix-SID. Further | |||
| details are described in the SR/LDP interworking procedures | details are described in the SR/LDP interworking procedures | |||
| ([I-D.filsfils-spring-segment-routing-ldp-interop]. | ([I-D.filsfils-spring-segment-routing-ldp-interop]. | |||
| The segment allocation and SRDB Maintenance rules are the same as | The segment allocation and SRGB Maintenance rules are the same as | |||
| those defined for Prefix-SID. | those defined for Prefix-SID. | |||
| 3.6.2. Tunnel Headend | 3.6.2. Tunnel Headend | |||
| The segment allocation and SRDB Maintenance rules are the same as | The segment allocation and SRGB Maintenance rules are the same as | |||
| those defined for Adj-SID. A tunnel attached to a head-end H acts as | those defined for Adj-SID. A tunnel attached to a head-end H acts as | |||
| an adjacency attached to H. | an adjacency attached to H. | |||
| Note: an alternative would consist in representing tunnels as | Note: an alternative would consist in representing tunnels as | |||
| forwarding-adjacencies ( [RFC4206]). In such case, the tunnel is | forwarding-adjacencies ( [RFC4206]). In such case, the tunnel is | |||
| presented to the routing area as a routing adjacency and will be | presented to the routing area as a routing adjacency and will be | |||
| considered as such by all area routers. The Remote-Binding SID is | considered as such by all area routers. The Remote-Binding SID is | |||
| preferred as it allows to advertise the presence of a tunnel without | preferred as it allows to advertise the presence of a tunnel without | |||
| influencing the LSDB and the SPF computation. | influencing the LSDB and the SPF computation. | |||
| skipping to change at page 15, line 39 ¶ | skipping to change at page 15, line 39 ¶ | |||
| [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. Tantsura, "IS-IS | Litkowski, S., Decraene, B., and J. Tantsura, "IS-IS | |||
| Extensions for Segment Routing", draft-ietf-isis-segment- | Extensions for Segment Routing", draft-ietf-isis-segment- | |||
| routing-extensions-03 (work in progress), October 2014. | routing-extensions-03 (work in progress), October 2014. | |||
| [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-00 (work in progress), August | segment-routing-extensions-02 (work in progress), February | |||
| 2014. | 2015. | |||
| [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-04 (work in progress), February 2015. | routing-extensions-04 (work in progress), February 2015. | |||
| [I-D.previdi-6man-segment-routing-header] | [I-D.previdi-6man-segment-routing-header] | |||
| Previdi, S., Filsfils, C., Field, B., and I. Leung, "IPv6 | Previdi, S., Filsfils, C., Field, B., and I. Leung, "IPv6 | |||
| Segment Routing Header (SRH)", draft-previdi-6man-segment- | Segment Routing Header (SRH)", draft-previdi-6man-segment- | |||
| routing-header-05 (work in progress), January 2015. | routing-header-06 (work in progress), May 2015. | |||
| [I-D.vyncke-6man-segment-routing-security] | [I-D.vyncke-6man-segment-routing-security] | |||
| Vyncke, E. and S. Previdi, "IPv6 Segment Routing Header | Vyncke, E., Previdi, S., and D. Lebrun, "IPv6 Segment | |||
| (SRH) Security Considerations", draft-vyncke-6man-segment- | Routing Security Considerations", draft-vyncke-6man- | |||
| routing-security-01 (work in progress), October 2014. | segment-routing-security-02 (work in progress), February | |||
| 2015. | ||||
| [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, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [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, October 2005. | (GMPLS) Traffic Engineering (TE)", RFC 4206, October 2005. | |||
| 10.2. Informative References | 10.2. Informative References | |||
| skipping to change at page 16, line 31 ¶ | skipping to change at page 16, line 32 ¶ | |||
| shaw@fb.com, s., Ginsburg, D., and D. Afanasiev, "Segment | shaw@fb.com, s., Ginsburg, D., and D. Afanasiev, "Segment | |||
| Routing Centralized Egress Peer Engineering", draft- | Routing Centralized Egress Peer Engineering", draft- | |||
| filsfils-spring-segment-routing-central-epe-03 (work in | filsfils-spring-segment-routing-central-epe-03 (work in | |||
| progress), January 2015. | progress), January 2015. | |||
| [I-D.filsfils-spring-segment-routing-ldp-interop] | [I-D.filsfils-spring-segment-routing-ldp-interop] | |||
| Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., | |||
| Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | |||
| Ytti, S., Henderickx, W., Tantsura, J., and E. Crabbe, | Ytti, S., Henderickx, W., Tantsura, J., and E. Crabbe, | |||
| "Segment Routing interoperability with LDP", draft- | "Segment Routing interoperability with LDP", draft- | |||
| filsfils-spring-segment-routing-ldp-interop-02 (work in | filsfils-spring-segment-routing-ldp-interop-03 (work in | |||
| progress), September 2014. | progress), March 2015. | |||
| [I-D.filsfils-spring-segment-routing-use-cases] | [I-D.filsfils-spring-segment-routing-use-cases] | |||
| Filsfils, C., Francois, P., Previdi, S., Decraene, B., | Filsfils, C., Francois, P., Previdi, S., Decraene, B., | |||
| Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., | |||
| Ytti, S., Henderickx, W., Tantsura, J., Kini, S., and E. | Ytti, S., Henderickx, W., Tantsura, J., Kini, S., and E. | |||
| Crabbe, "Segment Routing Use Cases", draft-filsfils- | Crabbe, "Segment Routing Use Cases", draft-filsfils- | |||
| spring-segment-routing-use-cases-01 (work in progress), | spring-segment-routing-use-cases-01 (work in progress), | |||
| October 2014. | October 2014. | |||
| [I-D.francois-spring-segment-routing-ti-lfa] | [I-D.francois-spring-segment-routing-ti-lfa] | |||
| Francois, P., Filsfils, C., Bashandy, A., and B. Decraene, | Francois, P., Filsfils, C., Bashandy, A., and B. Decraene, | |||
| "Topology Independent Fast Reroute using Segment Routing", | "Topology Independent Fast Reroute using Segment Routing", | |||
| draft-francois-spring-segment-routing-ti-lfa-01 (work in | draft-francois-spring-segment-routing-ti-lfa-01 (work in | |||
| progress), October 2014. | progress), October 2014. | |||
| [I-D.geib-spring-oam-usecase] | [I-D.geib-spring-oam-usecase] | |||
| Geib, R., Filsfils, C., Pignataro, C., and N. Kumar, "Use | Geib, R., Filsfils, C., Pignataro, C., and N. Kumar, "Use | |||
| case for a scalable and topology aware MPLS data plane | case for a scalable and topology aware MPLS data plane | |||
| monitoring system", draft-geib-spring-oam-usecase-03 (work | monitoring system", draft-geib-spring-oam-usecase-04 (work | |||
| in progress), October 2014. | in progress), March 2015. | |||
| [I-D.ietf-pce-segment-routing] | [I-D.ietf-pce-segment-routing] | |||
| Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E., | Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E., | |||
| Raszuk, R., Lopez, V., and J. Tantsura, "PCEP Extensions | Lopez, V., Tantsura, J., Henderickx, W., and J. Hardwick, | |||
| for Segment Routing", draft-ietf-pce-segment-routing-00 | "PCEP Extensions for Segment Routing", draft-ietf-pce- | |||
| (work in progress), October 2014. | segment-routing-03 (work in progress), April 2015. | |||
| [I-D.ietf-spring-ipv6-use-cases] | [I-D.ietf-spring-ipv6-use-cases] | |||
| Brzozowski, J., Leddy, J., Leung, I., Previdi, S., | Brzozowski, J., Leddy, J., Leung, I., Previdi, S., | |||
| Townsley, W., Martin, C., Filsfils, C., and R. Maglione, | Townsley, W., Martin, C., Filsfils, C., and R. Maglione, | |||
| "IPv6 SPRING Use Cases", draft-ietf-spring-ipv6-use- | "IPv6 SPRING Use Cases", draft-ietf-spring-ipv6-use- | |||
| cases-03 (work in progress), November 2014. | cases-04 (work in progress), March 2015. | |||
| [I-D.ietf-spring-resiliency-use-cases] | [I-D.ietf-spring-resiliency-use-cases] | |||
| Francois, P., Filsfils, C., Decraene, B., and R. Shakir, | Francois, P., Filsfils, C., Decraene, B., and R. Shakir, | |||
| "Use-cases for Resiliency in SPRING", draft-ietf-spring- | "Use-cases for Resiliency in SPRING", draft-ietf-spring- | |||
| resiliency-use-cases-00 (work in progress), May 2014. | resiliency-use-cases-01 (work in progress), March 2015. | |||
| [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., Tantsura, J., | Litkowski, S., Horneffer, M., Shakir, R., Tantsura, J., | |||
| and E. Crabbe, "Segment Routing with MPLS data plane", | and E. Crabbe, "Segment Routing with MPLS data plane", | |||
| draft-ietf-spring-segment-routing-mpls-00 (work in | draft-ietf-spring-segment-routing-mpls-00 (work in | |||
| progress), December 2014. | progress), December 2014. | |||
| [I-D.kumar-spring-sr-oam-requirement] | [I-D.kumar-spring-sr-oam-requirement] | |||
| Kumar, N., Pignataro, C., Akiya, N., Geib, R., and G. | Kumar, N., Pignataro, C., Akiya, N., Geib, R., Mirsky, G., | |||
| Mirsky, "OAM Requirements for Segment Routing Network", | and S. Litkowski, "OAM Requirements for Segment Routing | |||
| draft-kumar-spring-sr-oam-requirement-02 (work in | Network", draft-kumar-spring-sr-oam-requirement-03 (work | |||
| progress), December 2014. | in progress), March 2015. | |||
| [RFC5095] Abley, J., Savola, P., and G. Neville-Neil, "Deprecation | [RFC5095] Abley, J., Savola, P., and G. Neville-Neil, "Deprecation | |||
| of Type 0 Routing Headers in IPv6", RFC 5095, December | of Type 0 Routing Headers in IPv6", RFC 5095, December | |||
| 2007. | 2007. | |||
| Authors' Addresses | Authors' Addresses | |||
| Clarence Filsfils (editor) | Clarence Filsfils (editor) | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| Brussels | Brussels | |||
| End of changes. 15 change blocks. | ||||
| 25 lines changed or deleted | 26 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/ | ||||