| < draft-ietf-ospf-segment-routing-msd-06.txt | draft-ietf-ospf-segment-routing-msd-07.txt > | |||
|---|---|---|---|---|
| OSPF Working Group J. Tantsura | OSPF Working Group J. Tantsura | |||
| Internet-Draft Individual | Internet-Draft Individual | |||
| Intended status: Standards Track U. Chunduri | Intended status: Standards Track U. Chunduri | |||
| Expires: June 4, 2018 Huawei Technologies | Expires: June 17, 2018 Huawei Technologies | |||
| S. Aldrin | S. Aldrin | |||
| Google, Inc | Google, Inc | |||
| P. Psenak | P. Psenak | |||
| Cisco Systems | Cisco Systems | |||
| December 01, 2017 | December 14, 2017 | |||
| Signaling MSD (Maximum SID Depth) using OSPF | Signaling MSD (Maximum SID Depth) using OSPF | |||
| draft-ietf-ospf-segment-routing-msd-06 | draft-ietf-ospf-segment-routing-msd-07 | |||
| Abstract | Abstract | |||
| This document proposes a way to signal Maximum SID Depth (MSD) | This document proposes a way to signal Maximum SID Depth (MSD) | |||
| supported by a node at node and/or link granularity by an OSPF | supported by a node at node and/or link granularity by an OSPF | |||
| Router. In a Segment Routing (SR) enabled network a centralized | Router. In a Segment Routing (SR) enabled network a centralized | |||
| controller that programs SR tunnels needs to know the MSD supported | controller that programs SR tunnels needs to know the MSD supported | |||
| by the head-end at node and/or link granularity to impose the SID | by the head-end at node and/or link granularity to impose the SID | |||
| stack of an appropriate depth. MSD is relevant to the head-end of a | stack of an appropriate depth. MSD is relevant to the head-end of a | |||
| SR tunnel or Binding-SID anchor node where Binding-SID expansions | SR tunnel or Binding-SID anchor node where Binding-SID expansions | |||
| skipping to change at page 1, line 43 ¶ | skipping to change at page 1, line 43 ¶ | |||
| 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 June 4, 2018. | This Internet-Draft will expire on June 17, 2018. | |||
| 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 | |||
| (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 6, line 9 ¶ | skipping to change at page 6, line 9 ¶ | |||
| 5. Node MSD vs Link MSD conflict resolution | 5. Node MSD vs Link MSD conflict resolution | |||
| When both Node MSD and Link MSD are present, the value in the Link | When both Node MSD and Link MSD are present, the value in the Link | |||
| MSD MUST be used. | MSD MUST be used. | |||
| 6. IANA Considerations | 6. IANA Considerations | |||
| This document includes a request to IANA to allocate TLV type codes | This document includes a request to IANA to allocate TLV type codes | |||
| for the new TLV proposed in Section 3 of this document from OSPF | for the new TLV proposed in Section 3 of this document from OSPF | |||
| Router Information (RI) TLVs Registry as defined by [RFC4970]. Also | Router Information (RI) TLVs Registry as defined by [RFC4970]. For | |||
| for link MSD, we request IANA to allocate new sub-TLV codes as | THE link MSD, we request IANA to allocate new sub-TLV codes as | |||
| proposed in Section 4 from OSPFv2 Extended Link Opaque LSAs Extended | proposed in Section 4 from OSPFv2 Extended Link TLV Sub-TLVs registry | |||
| Link TLV registry and from Router-Link TLV defined in OSPFv3 Extend- | and from Router-Link TLV defined in OSPFv3 Extend-LSA Sub-TLV | |||
| LSA Sub-TLV registry. | registry. | |||
| This document also request IANA to create a new Sub-type registry as | This document also requests IANA to create a new Sub-type registry as | |||
| proposed in Section 3, Section 4. | proposed in Section 3, Section 4. | |||
| Value Name Reference | Value Name Reference | |||
| ----- --------------------- ------------- | ----- --------------------- ------------- | |||
| 0 Reserved This document | 0 Reserved This document | |||
| 1 Base MSD This document | 1 Base MSD This document | |||
| 2-250 Unassigned This document | 2-250 Unassigned This document | |||
| 251-254 Experimental This document | 251-254 Experimental This document | |||
| 255 Reserved This document | 255 Reserved This document | |||
| End of changes. 6 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/ | ||||