1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
|
<pre>Internet Engineering Task Force (IETF) J. Tantsura
Request for Comments: 8491 Apstra, Inc.
Category: Standards Track U. Chunduri
ISSN: 2070-1721 Huawei Technologies
S. Aldrin
Google, Inc.
L. Ginsberg
Cisco Systems
November 2018
<span class="h1">Signaling Maximum SID Depth (MSD) Using IS-IS</span>
Abstract
This document defines a way for an Intermediate System to
Intermediate System (IS-IS) router to advertise multiple types of
supported Maximum SID Depths (MSDs) at node and/or link granularity.
Such advertisements allow entities (e.g., centralized controllers) to
determine whether a particular Segment ID (SID) stack can be
supported in a given network. This document only defines one type of
MSD: Base MPLS Imposition. However, it defines an encoding that can
support other MSD types. This document focuses on MSD use in a
network that is Segment Routing (SR) enabled, but MSD may also be
useful when SR is not enabled.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8491">https://www.rfc-editor.org/info/rfc8491</a>.
<span class="grey">Tantsura, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. Requirements Language . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Node MSD Advertisement . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Link MSD Advertisement . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
4. Procedures for Defining and Using Node and Link MSD
Advertisements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Base MPLS Imposition MSD . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
When Segment Routing (SR) paths are computed by a centralized
controller, it is critical that the controller learn the Maximum SID
Depth (MSD) that can be imposed at each node/link of a given SR path.
This ensures that the Segment Identifier (SID) stack depth of a
computed path does not exceed the number of SIDs the node is capable
of imposing.
[<a id="ref-PCEP-EXT">PCEP-EXT</a>] defines how to signal MSD in the Path Computation Element
Communication Protocol (PCEP). However, if PCEP is not supported/
configured on the head-end of an SR tunnel or a Binding-SID anchor
node, and the controller does not participate in IGP routing, it has
no way of learning the MSD of nodes and links. BGP-LS (Distribution
<span class="grey">Tantsura, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
of Link-State and TE Information Using Border Gateway Protocol)
[<a href="./rfc7752" title=""North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP"">RFC7752</a>] defines a way to expose topology and associated attributes
and capabilities of the nodes in that topology to a centralized
controller. MSD signaling by BGP-LS has been defined in [<a href="#ref-MSD-BGP" title=""Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link-State"">MSD-BGP</a>].
Typically, BGP-LS is configured on a small number of nodes that do
not necessarily act as head-ends. In order for BGP-LS to signal MSD
for all the nodes and links in the network for which MSD is relevant,
MSD capabilities SHOULD be advertised by every Intermediate System to
Intermediate System (IS-IS) router in the network.
Other types of MSDs are known to be useful. For example, [<a href="#ref-ELC-ISIS" title=""Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS"">ELC-ISIS</a>]
defines Entropy Readable Label Depth (ERLD), which is used by a head-
end to insert an Entropy Label (EL) at a depth where it can be read
by transit nodes.
This document defines an extension to IS-IS used to advertise one or
more types of MSDs at node and/or link granularity. It also creates
an IANA registry for assigning MSD-Type identifiers and defines the
Base MPLS Imposition MSD-Type. In the future, it is expected that
new MSD-Types will be defined to signal additional capabilities,
e.g., entropy labels, SIDs that can be imposed through recirculation,
or SIDs associated with another data plane such as IPv6.
MSD advertisements MAY be useful even if Segment Routing itself is
not enabled. For example, in a non-SR MPLS network, MSD defines the
maximum label depth.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
BMI: Base MPLS Imposition is the number of MPLS labels that can be
imposed inclusive of all service/transport/special labels.
MSD: Maximum SID Depth is the number of SIDs supported by a node or
a link on a node.
SID: Segment Identifier is defined in [<a href="./rfc8402" title=""Segment Routing Architecture"">RFC8402</a>].
Label Imposition: Imposition is the act of modifying and/or adding
labels to the outgoing label stack associated with a packet.
This includes:
* replacing the label at the top of the label stack with a new
label
* pushing one or more new labels onto the label stack
<span class="grey">Tantsura, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
The number of labels imposed is then the sum of the number of labels
that are replaced and the number of labels that are pushed. See
[<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>] for further details.
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all
capitals, as shown here.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Node MSD Advertisement</span>
The Node MSD sub-TLV is defined within the body of the IS-IS Router
CAPABILITY TLV [<a href="./rfc7981" title=""IS-IS Extensions for Advertising Router Information"">RFC7981</a>] to carry the provisioned SID depth of the
router originating the IS-IS Router CAPABILITY TLV. Node MSD is the
smallest MSD supported by the node on the set of interfaces
configured for use by the advertising IGP instance. MSD values may
be learned via a hardware API or may be provisioned.
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MSD-Type | MSD-Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// ................... //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MSD-Type | MSD-Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Node MSD Sub-TLV
Type: 23
Length: variable (multiple of 2 octets); represents the total length
of the Value field
Value: field consists of one or more pairs of a 1-octet MSD-Type and
1-octet MSD-Value
MSD-Type: value defined in the "IGP MSD-Types" registry created by
the IANA Considerations section of this document <a href="#section-6">Section 6</a>
<span class="grey">Tantsura, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
MSD-Value: number in the range of 0-255 (for all MSD-Types, 0
represents the lack of ability to support a SID stack of any depth;
any other value represents that of the node. This value MUST
represent the lowest value supported by any link configured for use
by the advertising IS-IS instance.)
This sub-TLV is optional. The scope of the advertisement is specific
to the deployment.
If there exist multiple Node MSD advertisements for the same MSD-Type
originated by the same router, the procedures defined in [<a href="./rfc7981" title=""IS-IS Extensions for Advertising Router Information"">RFC7981</a>]
apply. These procedures may result in different MSD values being
used, for example, by different controllers. This does not, however,
create any interoperability issue.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Link MSD Advertisement</span>
The Link MSD sub-TLV is defined for TLVs 22, 23, 25, 141, 222, and
223 to carry the MSD of the interface associated with the link. MSD
values may be signaled by the forwarding plane or may be provisioned.
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MSD-Type | MSD-Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// ................... //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MSD-Type | MSD-Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Link MSD Sub-TLV
Type: 15
Length: variable (multiple of 2 octets); represents the total length
of the Value field
Value: field consists of one or more pairs of a 1-octet MSD-Type and
1-octet MSD-Value
MSD-Type: value defined in the "IGP MSD-Types" registry created by
the IANA Considerations section of this document <a href="#section-6">Section 6</a>
<span class="grey">Tantsura, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
MSD-Value: number in the range of 0-255 (for all MSD-Types, 0
represents the lack of ability to support a SID stack of any depth;
any other value represents that of the particular link when used as
an outgoing interface.)
This sub-TLV is optional.
If multiple Link MSD advertisements for the same MSD-Type and the
same link are received, the procedure to select which copy to use is
undefined.
If the advertising router performs label imposition in the context of
the ingress interface, it is not possible to meaningfully advertise
per-link values. In such a case, only the Node MSD SHOULD be
advertised.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Procedures for Defining and Using Node and Link MSD Advertisements</span>
When Link MSD is present for a given MSD-Type, the value of the Link
MSD MUST take precedence over the Node MSD. If a Link MSD-Type is
not signaled, but the Node MSD-Type is, then the Node MSD-Type value
MUST be considered to be the MSD value for that link.
In order to increase flooding efficiency, it is RECOMMENDED that
routers with homogenous Link MSD values advertise just the Node MSD
value.
The meaning of the absence of both Node and Link MSD advertisements
for a given MSD-Type is specific to the MSD-Type. Generally, it can
only be inferred that the advertising node does not support
advertisement of that MSD-Type. In some cases, however, the lack of
advertisement might imply that the functionality associated with the
MSD-Type is not supported. The correct interpretation MUST be
specified when an MSD-Type is defined.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Base MPLS Imposition MSD</span>
Base MPLS Imposition MSD (BMI-MSD) signals the total number of MPLS
labels that can be imposed, including all service/transport/special
labels.
The absence of BMI-MSD advertisements indicates only that the
advertising node does not support advertisement of this capability.
<span class="grey">Tantsura, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
IANA has allocated a sub-TLV type for the new sub-TLV proposed in
<a href="#section-2">Section 2</a> of this document from the "Sub-TLVs for TLV 242 (IS-IS
Router CAPABILITY TLV)" registry as defined by [<a href="./rfc7981" title=""IS-IS Extensions for Advertising Router Information"">RFC7981</a>].
IANA has allocated the following value:
Value Description Reference
----- --------------- -------------
23 Node MSD This document
Figure 3: Node MSD
IANA has allocated a sub-TLV type as defined in <a href="#section-3">Section 3</a> from the
"Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223 (Extended IS
reachability, IS Neighbor Attribute, L2 Bundle Member Attributes,
inter-AS reachability information, MT-ISN, and MT IS Neighbor
Attribute TLVs)" registry.
IANA has allocated the following value:
Value Description Reference
----- --------------- -------------
15 Link MSD This document
Figure 4: Link MSD
Per-TLV information where Link MSD sub-TLV can be part of:
TLV 22 23 25 141 222 223
--- --------------------
y y y y y y
Figure 5: TLVs Where LINK MSD Sub-TLV Can Be Present
<span class="grey">Tantsura, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
IANA has created an IANA-managed registry titled "IGP MSD-Types"
under the "Interior Gateway Protocol (IGP) Parameters" registry to
identify MSD-Types as proposed in Sections <a href="#section-2">2</a> and <a href="#section-3">3</a>. The registration
procedure is "Expert Review" as defined in [<a href="./rfc8126" title="">RFC8126</a>]. Types are an
unsigned 8-bit number. The following values are defined by this
document:
Value Name Reference
----- --------------------- -------------
0 Reserved This document
1 Base MPLS Imposition MSD This document
2-250 Unassigned
251-254 Experimental Use This document
255 Reserved This document
Figure 6: MSD-Types Codepoints Registry
General guidance for the designated experts is defined in [<a href="./rfc7370" title=""Updates to the IS-IS TLV Codepoints Registry"">RFC7370</a>].
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
Security considerations as specified by [<a href="./rfc7981" title=""IS-IS Extensions for Advertising Router Information"">RFC7981</a>] are applicable to
this document.
The advertisement of an incorrect MSD value may have negative
consequences. If the value is smaller than supported, path
computation may fail to compute a viable path. If the value is
larger than supported, an attempt to instantiate a path that can't be
supported by the head-end (the node performing the SID imposition)
may occur.
The presence of this information may also inform an attacker of how
to induce any of the aforementioned conditions.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC3031">RFC3031</a>] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", <a href="./rfc3031">RFC 3031</a>,
DOI 10.17487/RFC3031, January 2001,
<<a href="https://www.rfc-editor.org/info/rfc3031">https://www.rfc-editor.org/info/rfc3031</a>>.
<span class="grey">Tantsura, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
[<a id="ref-RFC7370">RFC7370</a>] Ginsberg, L., "Updates to the IS-IS TLV Codepoints
Registry", <a href="./rfc7370">RFC 7370</a>, DOI 10.17487/RFC7370, September 2014,
<<a href="https://www.rfc-editor.org/info/rfc7370">https://www.rfc-editor.org/info/rfc7370</a>>.
[<a id="ref-RFC7981">RFC7981</a>] Ginsberg, L., Previdi, S., and M. Chen, "IS-IS Extensions
for Advertising Router Information", <a href="./rfc7981">RFC 7981</a>,
DOI 10.17487/RFC7981, October 2016,
<<a href="https://www.rfc-editor.org/info/rfc7981">https://www.rfc-editor.org/info/rfc7981</a>>.
[<a id="ref-RFC8126">RFC8126</a>] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>,
<a href="./rfc8126">RFC 8126</a>, DOI 10.17487/RFC8126, June 2017,
<<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>>.
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>.
[<a id="ref-RFC8402">RFC8402</a>] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", <a href="./rfc8402">RFC 8402</a>, DOI 10.17487/RFC8402,
July 2018, <<a href="https://www.rfc-editor.org/info/rfc8402">https://www.rfc-editor.org/info/rfc8402</a>>.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-ELC-ISIS">ELC-ISIS</a>] Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S.
Litkowski, "Signaling Entropy Label Capability and Entropy
Readable Label Depth Using IS-IS", Work in Progress,
<a href="./draft-ietf-isis-mpls-elc-06">draft-ietf-isis-mpls-elc-06</a>, September 2018.
[<a id="ref-MSD-BGP">MSD-BGP</a>] Tantsura, J., Chunduri, U., Mirsky, G., and S. Sivabalan,
"Signaling MSD (Maximum SID Depth) using Border Gateway
Protocol Link-State", Work in Progress, <a href="./draft-ietf-idr-bgp-ls-segment-routing-msd-02">draft-ietf-idr-</a>
<a href="./draft-ietf-idr-bgp-ls-segment-routing-msd-02">bgp-ls-segment-routing-msd-02</a>, August 2018.
[<a id="ref-PCEP-EXT">PCEP-EXT</a>] Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,
and J. Hardwick, "PCEP Extensions for Segment Routing",
Work in Progress, <a href="./draft-ietf-pce-segment-routing-13">draft-ietf-pce-segment-routing-13</a>,
October 2018.
[<a id="ref-RFC7752">RFC7752</a>] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", <a href="./rfc7752">RFC 7752</a>,
DOI 10.17487/RFC7752, March 2016,
<<a href="https://www.rfc-editor.org/info/rfc7752">https://www.rfc-editor.org/info/rfc7752</a>>.
<span class="grey">Tantsura, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc8491">RFC 8491</a> Signaling MSD Using IS-IS November 2018</span>
Acknowledgements
The authors would like to thank Acee Lindem, Ketan Talaulikar,
Stephane Litkowski, and Bruno Decraene for their reviews and valuable
comments.
Contributors
The following people contributed to this document:
Peter Psenak
Email: ppsenak@cisco.com
Authors' Addresses
Jeff Tantsura
Apstra, Inc.
Email: jefftant.ietf@gmail.com
Uma Chunduri
Huawei Technologies
Email: uma.chunduri@huawei.com
Sam Aldrin
Google, Inc.
Email: aldrin.ietf@gmail.com
Les Ginsberg
Cisco Systems
Email: ginsberg@cisco.com
Tantsura, et al. Standards Track [Page 10]
</pre>
|
