| < draft-filsfils-spring-srv6-interop-01.txt | draft-filsfils-spring-srv6-interop-02.txt > | |||
|---|---|---|---|---|
| SPRING C. Filsfils | SPRING C. Filsfils | |||
| Internet-Draft F. Clad, Ed. | Internet-Draft F. Clad, Ed. | |||
| Intended status: Informational P. Camarillo, Ed. | Intended status: Informational P. Camarillo, Ed. | |||
| Expires: March 15, 2019 Cisco Systems, Inc. | Expires: September 5, 2019 Cisco Systems, Inc. | |||
| A. AbdelSalam | A. AbdelSalam | |||
| Gran Sasso Science Institute | Gran Sasso Science Institute | |||
| S. Salsano | S. Salsano | |||
| Universita di Roma "Tor Vergata" | Universita di Roma "Tor Vergata" | |||
| O. Bonaventure | O. Bonaventure | |||
| Universite catholique de Louvain | Universite catholique de Louvain | |||
| J. Horn | J. Horn | |||
| J. Liste | J. Liste | |||
| Cisco | Cisco | |||
| September 11, 2018 | March 4, 2019 | |||
| SRv6 interoperability report | SRv6 interoperability report | |||
| draft-filsfils-spring-srv6-interop-01 | draft-filsfils-spring-srv6-interop-02 | |||
| Abstract | Abstract | |||
| Segment Routing (SR) can be applied to the IPv6 data plane by | Segment Routing (SR) can be applied to the IPv6 data plane by | |||
| leveraging a new type of routing extension header, called Segment | leveraging a new type of routing extension header, called Segment | |||
| Routing Header (SRH). An SRH contains an ordered list, or sequence, | Routing Header (SRH). An SRH contains an ordered list, or sequence, | |||
| of segments representing topological or service-based instructions, | of segments representing topological or service-based instructions, | |||
| or any combination of those. | or any combination of those. | |||
| This draft provides an overview of IPv6 Segment Routing (SRv6) | This draft provides an overview of IPv6 Segment Routing (SRv6) | |||
| 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 March 15, 2019. | This Internet-Draft will expire on September 5, 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 8, line 19 ¶ | skipping to change at page 8, line 19 ¶ | |||
| 8. Security Considerations | 8. Security Considerations | |||
| This document does not introduce any security consideration. | This document does not introduce any security consideration. | |||
| 9. Informative References | 9. Informative References | |||
| [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-6man-segment-routing-header] | [I-D.ietf-6man-segment-routing-header] | |||
| Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and | Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and | |||
| d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header | d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header | |||
| (SRH)", draft-ietf-6man-segment-routing-header-14 (work in | (SRH)", draft-ietf-6man-segment-routing-header-16 (work in | |||
| progress), June 2018. | progress), February 2019. | |||
| [I-D.ietf-dmm-srv6-mobile-uplane] | [I-D.ietf-dmm-srv6-mobile-uplane] | |||
| Matsushima, S., Filsfils, C., Kohno, M., Camarillo, P., | Matsushima, S., Filsfils, C., Kohno, M., Camarillo, P., | |||
| daniel.voyer@bell.ca, d., and C. Perkins, "Segment Routing | daniel.voyer@bell.ca, d., and C. Perkins, "Segment Routing | |||
| IPv6 for Mobile User Plane", draft-ietf-dmm-srv6-mobile- | IPv6 for Mobile User Plane", draft-ietf-dmm-srv6-mobile- | |||
| uplane-02 (work in progress), July 2018. | uplane-03 (work in progress), October 2018. | |||
| [I-D.xuclad-spring-sr-service-programming] | [I-D.xuclad-spring-sr-service-programming] | |||
| Clad, F., Xu, X., Filsfils, C., daniel.bernier@bell.ca, | Clad, F., Xu, X., Filsfils, C., daniel.bernier@bell.ca, | |||
| d., Li, C., Decraene, B., Ma, S., Yadlapalli, C., | d., Li, C., Decraene, B., Ma, S., Yadlapalli, C., | |||
| Henderickx, W., and S. Salsano, "Service Programming with | Henderickx, W., and S. Salsano, "Service Programming with | |||
| Segment Routing", draft-xuclad-spring-sr-service- | Segment Routing", draft-xuclad-spring-sr-service- | |||
| programming-00 (work in progress), July 2018. | programming-01 (work in progress), October 2018. | |||
| [ref-1] "Implementing IPv6 Segment Routing in the Linux Kernel", | [ref-1] "Implementing IPv6 Segment Routing in the Linux Kernel", | |||
| July 2017, <https://doi.org/10.1145/3106328.3106329>. | July 2017, <https://doi.org/10.1145/3106328.3106329>. | |||
| [ref-2] "Reaping the Benefits of IPv6 Segment Routing", October | [ref-2] "Reaping the Benefits of IPv6 Segment Routing", October | |||
| 2017, <https://inl.info.ucl.ac.be/publications/ | 2017, <https://inl.info.ucl.ac.be/publications/ | |||
| reaping-benefits-ipv6-segment-routing>. | reaping-benefits-ipv6-segment-routing>. | |||
| [ref-3] "Add support for Segment Routing (Type 4) Extension | [ref-3] "Add support for Segment Routing (Type 4) Extension | |||
| Header", June 2016, <https://code.wireshark.org/review/git | Header", June 2016, <https://code.wireshark.org/review/git | |||
| End of changes. 9 change blocks. | ||||
| 10 lines changed or deleted | 10 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/ | ||||