| draft-ietf-ospf-segment-routing-msd-14.txt | draft-ietf-ospf-segment-routing-msd-15.txt | |||
|---|---|---|---|---|
| OSPF Working Group J. Tantsura | OSPF Working Group J. Tantsura | |||
| Internet-Draft Nuage Networks | Internet-Draft Nuage Networks | |||
| Intended status: Standards Track U. Chunduri | Intended status: Standards Track U. Chunduri | |||
| Expires: November 29, 2018 Huawei Technologies | Expires: January 25, 2019 Huawei Technologies | |||
| S. Aldrin | S. Aldrin | |||
| Google, Inc | Google, Inc | |||
| P. Psenak | P. Psenak | |||
| Cisco Systems | Cisco Systems | |||
| May 28, 2018 | July 24, 2018 | |||
| Signaling MSD (Maximum SID Depth) using OSPF | Signaling MSD (Maximum SID Depth) using OSPF | |||
| draft-ietf-ospf-segment-routing-msd-14 | draft-ietf-ospf-segment-routing-msd-15 | |||
| Abstract | Abstract | |||
| This document defines a way for an OSPF Router to advertise multiple | This document defines a way for an OSPF Router to advertise multiple | |||
| types of supported Maximum SID Depths (MSDs) at node and/or link | types of supported Maximum SID Depths (MSDs) at node and/or link | |||
| granularity. Such advertisements allow entities (e.g., centralized | granularity. Such advertisements allow entities (e.g., centralized | |||
| controllers) to determine whether a particular SID stack can be | controllers) to determine whether a particular SID stack can be | |||
| supported in a given network. This document defines only one type of | supported in a given network. This document defines only one type of | |||
| MSD, but defines an encoding that can support other MSD types. Here | MSD, but defines an encoding that can support other MSD types. Here | |||
| the term OSPF means both OSPFv2 and OSPFv3. | the term OSPF means both OSPFv2 and OSPFv3. | |||
| skipping to change at page 1, line 41 ¶ | skipping to change at page 1, line 41 ¶ | |||
| 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 November 29, 2018. | This Internet-Draft will expire on January 25, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 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 4, line 40 ¶ | skipping to change at page 4, line 40 ¶ | |||
| Figure 1: Node MSD TLV | Figure 1: Node MSD TLV | |||
| The Type: TBD1 | The Type: TBD1 | |||
| Length: variable (minimum of 2, multiple of 2 octets) and represents | Length: variable (minimum of 2, multiple of 2 octets) and represents | |||
| the total length of value field. | the total length of value field. | |||
| Value: consists of one or more pairs of a 1 octet MSD-type and 1 | Value: consists of one or more pairs of a 1 octet MSD-type and 1 | |||
| octet MSD-Value. | octet MSD-Value. | |||
| MSD-Type: one of the values defined in the MSD Types registry defined | MSD-Type: one of the values defined in the IGP MSD Types registry | |||
| in [I-D.ietf-isis-segment-routing-msd]. | defined in [I-D.ietf-isis-segment-routing-msd]. | |||
| MSD-Value: a number in the range of 0-255. For all MSD-Types, 0 | MSD-Value: a number in the range of 0-255. For all MSD-Types, 0 | |||
| represents lack of the ability to impose MSD stack of any depth; any | represents lack of the ability to impose MSD stack of any depth; any | |||
| other value represents that of the node. This value MUST represent | other value represents that of the node. This value MUST represent | |||
| the lowest value supported by any link configured for use by the | the lowest value supported by any link configured for use by the | |||
| advertising OSPF instance. | advertising OSPF instance. | |||
| This TLV is applicable to OSPFv2 and to OSPFv3 [RFC5838] and is | This TLV is applicable to OSPFv2 and to OSPFv3 [RFC5838] and is | |||
| optional. The scope of the advertisement is specific to the | optional. The scope of the advertisement is specific to the | |||
| deployment. | deployment. | |||
| skipping to change at page 9, line 14 ¶ | skipping to change at page 9, line 14 ¶ | |||
| [I-D.ietf-ospf-mpls-elc] | [I-D.ietf-ospf-mpls-elc] | |||
| Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S. | Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S. | |||
| Litkowski, "Signaling Entropy Label Capability and | Litkowski, "Signaling Entropy Label Capability and | |||
| Readable Label-stack Depth Using OSPF", draft-ietf-ospf- | Readable Label-stack Depth Using OSPF", draft-ietf-ospf- | |||
| mpls-elc-05 (work in progress), January 2018. | mpls-elc-05 (work in progress), January 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-11 (work in progress), | draft-ietf-pce-segment-routing-12 (work in progress), June | |||
| November 2017. | 2018. | |||
| [RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and | [RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and | |||
| R. Aggarwal, "Support of Address Families in OSPFv3", | R. Aggarwal, "Support of Address Families in OSPFv3", | |||
| RFC 5838, DOI 10.17487/RFC5838, April 2010, | RFC 5838, DOI 10.17487/RFC5838, April 2010, | |||
| <https://www.rfc-editor.org/info/rfc5838>. | <https://www.rfc-editor.org/info/rfc5838>. | |||
| [RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security | [RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security | |||
| According to the Keying and Authentication for Routing | According to the Keying and Authentication for Routing | |||
| Protocols (KARP) Design Guide", RFC 6863, | Protocols (KARP) Design Guide", RFC 6863, | |||
| DOI 10.17487/RFC6863, March 2013, | DOI 10.17487/RFC6863, March 2013, | |||
| End of changes. 6 change blocks. | ||||
| 8 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||