-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathDiff_ draft-sivabalan-pce-binding-label-sid-04.txt - draft-sivabalan-pce-binding-label-sid-05.txt.html
671 lines (662 loc) · 120 KB
/
Diff_ draft-sivabalan-pce-binding-label-sid-04.txt - draft-sivabalan-pce-binding-label-sid-05.txt.html
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
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- saved from url=(0030)https://tools.ietf.org/rfcdiff -->
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="Content-Style-Type" content="text/css">
<title>Diff: draft-sivabalan-pce-binding-label-sid-04.txt - draft-sivabalan-pce-binding-label-sid-05.txt</title>
<style type="text/css">
body { margin: 0.4ex; margin-right: auto; }
tr { }
td { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;}
th { font-size: 0.86em; }
.small { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; }
.left { background-color: #EEE; }
.right { background-color: #FFF; }
.diff { background-color: #CCF; }
.lblock { background-color: #BFB; }
.rblock { background-color: #FF8; }
.insert { background-color: #8FF; }
.delete { background-color: #ACF; }
.void { background-color: #FFB; }
.cont { background-color: #EEE; }
.linebr { background-color: #AAA; }
.lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; }
.elipsis{ background-color: #AAA; }
.left .cont { background-color: #DDD; }
.right .cont { background-color: #EEE; }
.lblock .cont { background-color: #9D9; }
.rblock .cont { background-color: #DD6; }
.insert .cont { background-color: #0DD; }
.delete .cont { background-color: #8AD; }
.stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; }
span.hide { display: none; color: #aaa;} a:hover span { display: inline; } tr.change { background-color: gray; }
tr.change a { text-decoration: none; color: black }
</style>
<script>
var chunk_index = 0;
var old_chunk = null;
function format_chunk(index) {
var prefix = "diff";
var str = index.toString();
for (x=0; x<(4-str.length); ++x) {
prefix+='0';
}
return prefix + str;
}
function find_chunk(n){
return document.querySelector('tr[id$="' + n + '"]');
}
function change_chunk(offset) {
var index = chunk_index + offset;
var new_str;
var new_chunk;
new_str = format_chunk(index);
new_chunk = find_chunk(new_str);
if (!new_chunk) {
return;
}
if (old_chunk) {
old_chunk.style.outline = "";
}
old_chunk = new_chunk;
old_chunk.style.outline = "1px solid red";
window.location.replace("#" + new_str)
window.scrollBy(0,-100);
chunk_index = index;
}
document.onkeydown = function(e) {
switch (e.keyCode) {
case 78:
change_chunk(1);
break;
case 80:
change_chunk(-1);
break;
}
};
</script>
</head>
<body>
<table border="0" cellpadding="0" cellspacing="0">
<tbody><tr id="part-1" bgcolor="orange"><th></th><th><a href="https://tools.ietf.org/rfcdiff?url2=draft-sivabalan-pce-binding-label-sid-04.txt" style="color:#008; text-decoration:none;"><</a> <a href="https://tools.ietf.org/html/draft-sivabalan-pce-binding-label-sid-04.txt" style="color:#008">draft-sivabalan-pce-binding-label-sid-04.txt</a> </th><th> </th><th> <a href="https://tools.ietf.org/html/draft-sivabalan-pce-binding-label-sid-05.txt" style="color:#008">draft-sivabalan-pce-binding-label-sid-05.txt</a> <a href="https://tools.ietf.org/rfcdiff?url1=draft-sivabalan-pce-binding-label-sid-05.txt" style="color:#008; text-decoration:none;">></a></th><th></th></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">PCE Working Group S. Sivabalan</td><td> </td><td class="right">PCE Working Group S. Sivabalan</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Internet-Draft Cisco Systems, Inc.</td><td> </td><td class="right">Internet-Draft Cisco Systems, Inc.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Intended status: Standards Track J. Tantsura</td><td> </td><td class="right">Intended status: Standards Track J. Tantsura</td><td class="lineno"></td></tr>
<tr id="diff0001"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock">Expires: <span class="delete">September 6, 2018</span> Nuage Networks</td><td> </td><td class="rblock">Expires: <span class="insert">February 28, 2019</span> Nuage Networks</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> C. Filsfils</td><td> </td><td class="right"> C. Filsfils</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> S. Previdi</td><td> </td><td class="right"> S. Previdi</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Cisco Systems, Inc.</td><td> </td><td class="right"> Cisco Systems, Inc.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> J. Hardwick</td><td> </td><td class="right"> J. Hardwick</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Metaswitch Networks</td><td> </td><td class="right"> Metaswitch Networks</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> D. Dhody</td><td> </td><td class="right"> D. Dhody</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Huawei Technologies</td><td> </td><td class="right"> Huawei Technologies</td><td class="lineno"></td></tr>
<tr id="diff0002"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete"> March 5</span>, 2018</td><td> </td><td class="rblock"> <span class="insert">August 27</span>, 2018</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Carrying Binding Label/Segment-ID in PCE-based Networks.</td><td> </td><td class="right"> Carrying Binding Label/Segment-ID in PCE-based Networks.</td><td class="lineno"></td></tr>
<tr id="diff0003"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> draft-sivabalan-pce-binding-label-sid-0<span class="delete">4</span></td><td> </td><td class="rblock"> draft-sivabalan-pce-binding-label-sid-0<span class="insert">5</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0004"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> It is possible to associate a <span class="delete">binding label</span> to RSVP-TE signaled</td><td> </td><td class="rblock"> <span class="insert">In order to provide greater scalability, network opacity, and service</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> Traffic Engineering Label Switching Path or binding Segment-ID (SID)</td><td> </td><td class="rblock"><span class="insert"> independence, SR utilizes a Binding Segment Identifier (BSID).</span> It is</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> to Segment Routed Traffic Engineering path. Such a binding label/SID</td><td> </td><td class="rblock"> possible to associate a <span class="insert">BSID</span> to RSVP-TE signaled Traffic Engineering</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> can be used by an upstream node for steering traffic into the</td><td> </td><td class="rblock"> Label Switching Path or binding Segment-ID (SID) to Segment Routed</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> appropriate TE path to enforce <span class="delete">TE</span> policies. This document proposes</td><td> </td><td class="rblock"> <span class="insert">(SR)</span> Traffic Engineering path. Such a binding label/SID can be used</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> an approach for reporting binding label/SID to Path Computation</td><td> </td><td class="rblock"> by an upstream node for steering traffic into the appropriate TE path</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> Element (PCE) for supporting PCE-based Traffic Engineering policies.</td><td> </td><td class="rblock"> to enforce <span class="insert">SR</span> policies. This document proposes an approach for</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> reporting binding label/SID to Path Computation Element (PCE) for</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> supporting PCE-based Traffic Engineering policies.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Requirements Language</td><td> </td><td class="right">Requirements Language</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right"> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno"></td></tr>
<tr id="diff0005"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td> </td><td class="rblock"> "SHOULD", "SHOULD NOT", "RECOMMENDED", <span class="insert">"NOT RECOMMENDED",</span> "MAY", and</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> document are to be interpreted as described in <span class="delete">[RFC2119].</span></td><td> </td><td class="rblock"> "OPTIONAL" in this document are to be interpreted as described in <span class="insert">BCP</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> 14 [RFC2119] [RFC8174] when, and only when, they appear in all</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> capitals, as shown here.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Status of This Memo</td><td> </td><td class="right">Status of This Memo</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> This Internet-Draft is submitted in full conformance with the</td><td> </td><td class="right"> This Internet-Draft is submitted in full conformance with the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> provisions of BCP 78 and BCP 79.</td><td> </td><td class="right"> provisions of BCP 78 and BCP 79.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right"> Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Task Force (IETF). Note that other groups may also distribute</td><td> </td><td class="right"> Task Force (IETF). Note that other groups may also distribute</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> working documents as Internet-Drafts. The list of current Internet-</td><td> </td><td class="right"> working documents as Internet-Drafts. The list of current Internet-</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Drafts is at https://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right"> Drafts is at https://datatracker.ietf.org/drafts/current/.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right"> Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right"> and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> time. It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right"> time. It is inappropriate to use Internet-Drafts as reference</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> material or to cite them other than as "work in progress."</td><td> </td><td class="right"> material or to cite them other than as "work in progress."</td><td class="lineno"></td></tr>
<tr id="diff0006"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> This Internet-Draft will expire on <span class="delete">September 6, 2018.</span></td><td> </td><td class="rblock"> </td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> This Internet-Draft will expire on <span class="insert">February 28, 2019.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Copyright (c) 2018 IETF Trust and the persons identified as the</td><td> </td><td class="right"> Copyright (c) 2018 IETF Trust and the persons identified as the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> document authors. All rights reserved.</td><td> </td><td class="right"> document authors. All rights reserved.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right"> This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Provisions Relating to IETF Documents</td><td> </td><td class="right"> Provisions Relating to IETF Documents</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> (https://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right"> (https://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> publication of this document. Please review these documents</td><td> </td><td class="right"> publication of this document. Please review these documents</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> carefully, as they describe your rights and restrictions with respect</td><td> </td><td class="right"> carefully, as they describe your rights and restrictions with respect</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> to this document. Code Components extracted from this document must</td><td> </td><td class="right"> to this document. Code Components extracted from this document must</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> include Simplified BSD License text as described in Section 4.e of</td><td> </td><td class="right"> include Simplified BSD License text as described in Section 4.e of</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> the Trust Legal Provisions and are provided without warranty as</td><td> </td><td class="right"> the Trust Legal Provisions and are provided without warranty as</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> described in the Simplified BSD License.</td><td> </td><td class="right"> described in the Simplified BSD License.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Table of Contents</td><td> </td><td class="right">Table of Contents</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2</td><td> </td><td class="right"> 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2</td><td class="lineno"></td></tr>
<tr id="diff0007"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">4</span></td><td> </td><td class="rblock"> 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">5</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 3. Path Binding TLV . . . . . . . . . . . . . . . . . . . . . . 5</td><td> </td><td class="right"> 3. Path Binding TLV . . . . . . . . . . . . . . . . . . . . . . 5</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 6</td><td> </td><td class="right"> 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 6</td><td class="lineno"></td></tr>
<tr id="diff0008"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 5. Security Considerations . . . . . . . . . . . . . . . . . . . <span class="delete">7</span></td><td> </td><td class="rblock"> <span class="insert">4.1. PCE based Central Controller . . . . . . . . . . . . . . 7</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <span class="delete">7</span></td><td> </td><td class="rblock"> 5. Security Considerations . . . . . . . . . . . . . . . . . . . <span class="insert">8</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 6.1. TE-PATH-BINDING TLV . . . . . . . . . . . . . . . . . . . <span class="delete">7</span></td><td> </td><td class="rblock"> 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <span class="insert">8</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 6.2. PCEP Error Type and Value . . . . . . . . . . . . . . . . <span class="delete">7</span></td><td> </td><td class="rblock"> 6.1. TE-PATH-BINDING TLV . . . . . . . . . . . . . . . . . . . <span class="insert">9</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <span class="delete">8</span></td><td> </td><td class="rblock"> 6.2. PCEP Error Type and Value . . . . . . . . . . . . . . . . <span class="insert">9</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 8. Normative References . . . . . . . . . . . . . . . . . . . . <span class="delete">8</span></td><td> </td><td class="rblock"> 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <span class="insert">9</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">9</span></td><td> </td><td class="rblock"> 8. <span class="insert">References . . . . . . . . . . . . . . . . . . . . . . . . . 9</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> 8.1.</span> Normative References . . . . . . . . . . . . . . . . . . <span class="insert">9</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> 8.2. Informative References</span> . . <span class="insert">. . . . . . . . . . . . . . . 10</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">11</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">1. Introduction</td><td> </td><td class="right">1. Introduction</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> A PCE can compute Traffic Engineering paths (TE paths) through a</td><td> </td><td class="right"> A PCE can compute Traffic Engineering paths (TE paths) through a</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> network that are subject to various constraints. Currently, TE paths</td><td> </td><td class="right"> network that are subject to various constraints. Currently, TE paths</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> are either set up using the RSVP-TE signaling protocol or Segment</td><td> </td><td class="right"> are either set up using the RSVP-TE signaling protocol or Segment</td><td class="lineno"></td></tr>
<tr id="diff0009"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">Routed</span> (SR). We refer to such paths as RSVP-TE paths and SR-TE paths</td><td> </td><td class="rblock"> <span class="insert">Routing</span> (SR). We refer to such paths as RSVP-TE paths and SR-TE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> respectively in this document.</td><td> </td><td class="rblock"> paths respectively in this document.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Similar to assigning label to a Forwarding Equivalence Class (FEC)</td><td> </td><td class="right"> Similar to assigning label to a Forwarding Equivalence Class (FEC)</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> via Label Distribution Protocol (LDP), a binding label can be</td><td> </td><td class="right"> via Label Distribution Protocol (LDP), a binding label can be</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> assigned to a RSVP-TE LSP. If the topmost label of an incoming</td><td> </td><td class="right"> assigned to a RSVP-TE LSP. If the topmost label of an incoming</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> packet is the binding label, the packet is steered onto the RSVP-TE</td><td> </td><td class="right"> packet is the binding label, the packet is steered onto the RSVP-TE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> LSP. As such, any upstream node can use binding labels to steer the</td><td> </td><td class="right"> LSP. As such, any upstream node can use binding labels to steer the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> packets that it originates to appropriate TE LSPs to enforce TE</td><td> </td><td class="right"> packets that it originates to appropriate TE LSPs to enforce TE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> policy. Similarly, a binding SID, see</td><td> </td><td class="right"> policy. Similarly, a binding SID, see</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [I-D.ietf-isis-segment-routing-extensions],</td><td> </td><td class="right"> [I-D.ietf-isis-segment-routing-extensions],</td><td class="lineno"></td></tr>
<tr id="diff0010"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> [I-D.ietf-idr-segment-routing-te-policy] and</td><td> </td><td class="rblock"> [I-D.ietf-idr-segment-routing-te-policy] and <span class="insert">[RFC8402]</span> can be used to</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> </td><td> </td><td class="rblock"> enforce TE policy with SR-TE path. Note that if an SR-TE path is</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">[I-D.ietf-spring-segment-routing]</span> can be used to enforce TE policy</td><td> </td><td class="rblock"> represented as a <span class="insert">forwarding-adjacency (FA),</span> then the corresponding</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> with SR-TE path. Note that if an SR-TE path is represented as a</td><td> </td><td class="rblock"> adjacency SID can be used as the binding SID. In such case, the path</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">forwarding-adjacency,</span> then the corresponding adjacency SID can be</td><td> </td><td class="rblock"> is advertised using the routing protocols as described in <span class="insert">[RFC4206].</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> used as the binding SID. In such case, the path is advertised using</td><td> </td><td class="rblock"> The binding SID provides an alternate mechanism without additional</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> the routing protocols as described in <span class="delete">[RFC5440].</span> The binding SID</td><td> </td><td class="rblock"> overhead on routing protocols.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> provides an alternate mechanism without additional overhead on</td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> routing protocols.</td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [RFC5440] describes the Path Computation Element Protocol (PCEP) for</td><td> </td><td class="right"> [RFC5440] describes the Path Computation Element Protocol (PCEP) for</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> communication between a Path Computation Client (PCC) and a PCE or</td><td> </td><td class="right"> communication between a Path Computation Client (PCC) and a PCE or</td><td class="lineno"></td></tr>
<tr id="diff0011"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> between a pair of <span class="delete">PCEs.[I-D.ietf-pce-stateful-pce]</span> specifies</td><td> </td><td class="rblock"> between a pair of <span class="insert">PCEs. [RFC8231]</span> specifies extension to PCEP that</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> extension to PCEP that allows a PCC to delegate its LSPs to a PCE.</td><td> </td><td class="rblock"> allows a PCC to delegate its LSPs to a <span class="insert">stateful</span> PCE. <span class="insert">A stateful</span> PCE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">The</span> PCE can then update the state of LSPs delegated to it.</td><td> </td><td class="rblock"> can then update the state of LSPs delegated to it. <span class="insert">[RFC8281]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">[I-D.ietf-pce-pce-initiated-lsp]</span> specifies a mechanism allowing a PCE</td><td> </td><td class="rblock"> specifies a mechanism allowing a PCE to dynamically instantiate an</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> to dynamically instantiate an LSP on a PCC by sending the path and</td><td> </td><td class="rblock"> LSP on a PCC by sending the path and <span class="insert">characteristics.</span> The PCEP</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">characteristics of the LSP.</span> The PCEP extension to setup and maintain</td><td> </td><td class="rblock"> extension to setup and maintain SR-TE paths is specified in</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> SR-TE paths is specified in [I-D.ietf-pce-segment-routing].</td><td> </td><td class="rblock"> [I-D.ietf-pce-segment-routing].</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> <span class="insert">As described in [RFC8402], BSID is bound to an SR Policy,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> instantiation of which may involve a list of SIDs. Any packets</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> received with an active segment equal to BSID are steered onto the</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> bound SR Policy. A BSID may be either a local or a global SID. If</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> local, a BSID is allocated from the SRLB. If global, a BSID is</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> allocated from the SRGB.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Binding label/SID has local significance to the ingress node of the</td><td> </td><td class="right"> Binding label/SID has local significance to the ingress node of the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> corresponding TE path. When a stateful PCE is deployed for setting</td><td> </td><td class="right"> corresponding TE path. When a stateful PCE is deployed for setting</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> up TE paths, it may be desirable to report the binding label or SID</td><td> </td><td class="right"> up TE paths, it may be desirable to report the binding label or SID</td><td class="lineno"></td></tr>
<tr id="diff0012"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> to the PCE for the purpose of enforcing end-to-end TE policy. A</td><td> </td><td class="rblock"> to the <span class="insert">stateful</span> PCE for the purpose of enforcing end-to-end TE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> sample Data Center (DC) use-case is illustrated in the following</td><td> </td><td class="rblock"> policy. A sample Data Center (DC) use-case is illustrated in the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> diagram. In the MPLS DC network, an SR LSP (without traffic</td><td> </td><td class="rblock"> following diagram. In the MPLS DC network, an SR LSP (without</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> engineering) is established using a prefix SID advertised by BGP (see</td><td> </td><td class="rblock"> traffic engineering) is established using a prefix SID advertised by</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> [I-D.ietf-idr-bgp-prefix-sid]). In IP/MPLS WAN, an SR-TE LSP is</td><td> </td><td class="rblock"> BGP (see [I-D.ietf-idr-bgp-prefix-sid]). In IP/MPLS WAN, an SR-TE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> setup using the PCE. The list of SIDs of the SR-TE LSP is {A, B, C,</td><td> </td><td class="rblock"> LSP is setup using the PCE. The list of SIDs of the SR-TE LSP is {A,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> D}. The gateway node 1 (which is the PCC) allocates a binding SID X</td><td> </td><td class="rblock"> B, C, D}. The gateway node 1 (which is the PCC) allocates a binding</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> and reports it to the PCE. In order for the access node to steer the</td><td> </td><td class="rblock"> SID X and reports it to the PCE. In order for the access node to</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> traffic over the SR-TE LSP, the PCE passes the SID stack {Y, X} where</td><td> </td><td class="rblock"> steer the traffic over the SR-TE LSP, the PCE passes the SID stack</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> Y is the prefix SID of the gateway node-1 to the access node. In the</td><td> </td><td class="rblock"> {Y, X} where Y is the prefix SID of the gateway node-1 to the access</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> absence of the binding SID X, the PCE should pass the SID stack {Y,</td><td> </td><td class="rblock"> node. In the absence of the binding SID X, the PCE should pass the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> A, B, C, D} to the access node. This example also illustrates the</td><td> </td><td class="rblock"> SID stack {Y, A, B, C, D} to the access node. This example also</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> additional benefit of using the binding SID to reduce the number of</td><td> </td><td class="rblock"> illustrates the additional benefit of using the binding SID to reduce</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> SIDs imposed on the access nodes with a limited forwarding capacity.</td><td> </td><td class="rblock"> the number of SIDs imposed on the access nodes with a limited</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> forwarding capacity.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> SID stack</td><td> </td><td class="right"> SID stack</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> {Y, X} +-----+</td><td> </td><td class="right"> {Y, X} +-----+</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> _ _ _ _ _ _ _ _ _ _ _ _ _ _| PCE |</td><td> </td><td class="right"> _ _ _ _ _ _ _ _ _ _ _ _ _ _| PCE |</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> | +-----+</td><td> </td><td class="right"> | +-----+</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> | ^</td><td> </td><td class="right"> | ^</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> | | Binding</td><td> </td><td class="right"> | | Binding</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> | .-----. | SID (X) .-----.</td><td> </td><td class="right"> | .-----. | SID (X) .-----.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> | ( ) | ( )</td><td> </td><td class="right"> | ( ) | ( )</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> V .--( )--. | .--( )--.</td><td> </td><td class="right"> V .--( )--. | .--( )--.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="part-2" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-2"><em> page 4, line 26<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-2"><em> page 4, line 29<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left">| Node | ( ==============> ) |Node-1 | ( ================> ) |Node-2 |</td><td> </td><td class="right">| Node | ( ==============> ) |Node-1 | ( ================> ) |Node-2 |</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">+------+ ( SR path ) +-------+ ( SR-TE path ) +-------+</td><td> </td><td class="right">+------+ ( SR path ) +-------+ ( SR-TE path ) +-------+</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> '--( )--' Prefix '--( )--'</td><td> </td><td class="right"> '--( )--' Prefix '--( )--'</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> ( ) SID of ( )</td><td> </td><td class="right"> ( ) SID of ( )</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> '-----' Node-1 '-----'</td><td> </td><td class="right"> '-----' Node-1 '-----'</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> is Y SIDs for SR-TE LSP:</td><td> </td><td class="right"> is Y SIDs for SR-TE LSP:</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> {A, B, C, D}</td><td> </td><td class="right"> {A, B, C, D}</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Figure 1: A sample Use-case of Binding SID</td><td> </td><td class="right"> Figure 1: A sample Use-case of Binding SID</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0013"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> It <span class="delete">may be</span> possible for a PCE to request a PCC to allocate a specific</td><td> </td><td class="rblock"> <span class="insert">A PCC could report the binding label/SID allocated by it to the</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> binding label/SID by sending an <span class="delete">update</span> message. If the PCC can</td><td> </td><td class="rblock"><span class="insert"> stateful PCE via PCRpt message.</span> It <span class="insert">is also</span> possible for a <span class="insert">stateful</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> successfully allocate the specified binding value, it reports the</td><td> </td><td class="rblock"> PCE to request a PCC to allocate a specific binding label/SID by</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> binding value to the PCE. Otherwise, the PCC sends an error message</td><td> </td><td class="rblock"> sending an <span class="insert">PCUpd</span> message. If the PCC can successfully allocate the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> to the PCE indicating the cause of the failure.</td><td> </td><td class="rblock"> specified binding value, it reports the binding value to the PCE.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> Otherwise, the PCC sends an error message to the PCE indicating the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> cause of the failure.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> In this document, we introduce a new OPTIONAL TLV that a PCC can use</td><td> </td><td class="right"> In this document, we introduce a new OPTIONAL TLV that a PCC can use</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> in order to report the binding label/SID associated with a TE LSP, or</td><td> </td><td class="right"> in order to report the binding label/SID associated with a TE LSP, or</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> a PCE to request a PCC to allocate a binding label/SID. This TLV is</td><td> </td><td class="right"> a PCE to request a PCC to allocate a binding label/SID. This TLV is</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> intended for TE LSPs established using RSVP-TE, SR, or any other</td><td> </td><td class="right"> intended for TE LSPs established using RSVP-TE, SR, or any other</td><td class="lineno"></td></tr>
<tr id="diff0014"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> future method. Also, in the case of SR-TE LSPs, the TLV can carry <span class="delete">an</span></td><td> </td><td class="rblock"> future method. Also, in the case of SR-TE LSPs, the TLV can carry <span class="insert">a</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> MPLS label (for SR-TE path with MPLS data-plane) or a binding SID</td><td> </td><td class="rblock"><span class="insert"> binding</span> MPLS label (for SR-TE path with MPLS data-plane) or a binding</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> (e.g., IPv6 address for SR-TE paths with IPv6 data-plane). However,</td><td> </td><td class="rblock"> <span class="insert">IPv6</span> SID (e.g., IPv6 address for SR-TE paths with IPv6 data-plane).</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> use of this TLV for carrying non-MPLS binding SID will be described</td><td> </td><td class="rblock"> However, use of this TLV for carrying non-MPLS binding SID will be</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> in separate document(s). Binding value means either MPLS label or</td><td> </td><td class="rblock"> described in separate document(s). Binding value means either MPLS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> SID throughout this document.</td><td> </td><td class="rblock"> label or SID throughout this document.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> <span class="insert">Additionally, to support the PCE based central controller [RFC8283]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> operation where the PCE would take responsibility for managing some</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> part of the MPLS label space for each of the routers that it</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> controls, the PCE could directly make the binding label/SID</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> allocation and inform the PCC. See Section 4.1 for details.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">2. Terminology</td><td> </td><td class="right">2. Terminology</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> The following terminologies are used in this document:</td><td> </td><td class="right"> The following terminologies are used in this document:</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> LER: Label Edge Router.</td><td> </td><td class="right"> LER: Label Edge Router.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> LSP: Label Switched Path.</td><td> </td><td class="right"> LSP: Label Switched Path.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> LSR: Label Switching Router.</td><td> </td><td class="right"> LSR: Label Switching Router.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="part-3" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-3"><em> page 5, line 24<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-3"><em> page 5, line 38<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> SR: Segment Routing.</td><td> </td><td class="right"> SR: Segment Routing.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> TLV: Type, Length, and Value.</td><td> </td><td class="right"> TLV: Type, Length, and Value.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">3. Path Binding TLV</td><td> </td><td class="right">3. Path Binding TLV</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> The new optional TLV is called "TE-PATH-BINDING TLV" whose format is</td><td> </td><td class="right"> The new optional TLV is called "TE-PATH-BINDING TLV" whose format is</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> shown in the diagram below is defined to carry binding label or SID</td><td> </td><td class="right"> shown in the diagram below is defined to carry binding label or SID</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> for a TE path. This TLV is associated with the LSP object specified</td><td> </td><td class="right"> for a TE path. This TLV is associated with the LSP object specified</td><td class="lineno"></td></tr>
<tr id="diff0015"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> in <span class="delete">([I-D.ietf-pce-stateful-pce]).</span> The type of this TLV is to be</td><td> </td><td class="rblock"> in <span class="insert">([RFC8231]).</span> The type of this TLV is to be allocated by IANA.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> allocated by IANA.</td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 0 1 2 3</td><td> </td><td class="right"> 0 1 2 3</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1</td><td> </td><td class="right"> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td> </td><td class="right"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> | Type | Length |</td><td> </td><td class="right"> | Type | Length |</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td> </td><td class="right"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> | Binding Type (BT) | Binding Value |</td><td> </td><td class="right"> | Binding Type (BT) | Binding Value |</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td> </td><td class="right"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> ~ Binding Value (continued) (variable length) ~</td><td> </td><td class="right"> ~ Binding Value (continued) (variable length) ~</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td> </td><td class="right"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="part-4" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-4"><em> page 5, line 48<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-4"><em> page 6, line 14<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> TE-PATH-BINDING TLV is a generic TLV such that it is able to carry</td><td> </td><td class="right"> TE-PATH-BINDING TLV is a generic TLV such that it is able to carry</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> MPLS label binding as well as other types of future bindings (e.g.,</td><td> </td><td class="right"> MPLS label binding as well as other types of future bindings (e.g.,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> IPv6 SR path). It is formatted according to the rules specified in</td><td> </td><td class="right"> IPv6 SR path). It is formatted according to the rules specified in</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [RFC5440]. The two octet Binding Type (BT) field identifies the type</td><td> </td><td class="right"> [RFC5440]. The two octet Binding Type (BT) field identifies the type</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> of binding included in the TLV. This document specifies the</td><td> </td><td class="right"> of binding included in the TLV. This document specifies the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> following BT values:</td><td> </td><td class="right"> following BT values:</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> o BT = 0: The binding value is an MPLS label carried in the format</td><td> </td><td class="right"> o BT = 0: The binding value is an MPLS label carried in the format</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> specified in [RFC5462] where only the label value is valid, and</td><td> </td><td class="right"> specified in [RFC5462] where only the label value is valid, and</td><td class="lineno"></td></tr>
<tr id="diff0016"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> other fields (TC, S, and TTL)fields MUST be considered invalid.</td><td> </td><td class="rblock"> other fields (TC, S, and TTL)<span class="insert"> </span>fields MUST be considered invalid.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> The Length MUST be set to 6.</td><td> </td><td class="right"> The Length MUST be set to 6.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> o BT = 1: Similar to the case where BT is 0 except that all the</td><td> </td><td class="right"> o BT = 1: Similar to the case where BT is 0 except that all the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> fields on the MPLS label entry are set on transmission. However,</td><td> </td><td class="right"> fields on the MPLS label entry are set on transmission. However,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> the receiver MAY choose to override TC, S, and TTL values</td><td> </td><td class="right"> the receiver MAY choose to override TC, S, and TTL values</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> according its local policy.</td><td> </td><td class="right"> according its local policy.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">4. Operation</td><td> </td><td class="right">4. Operation</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> The binding value is allocated by PCC and reported to PCE via PCRpt</td><td> </td><td class="right"> The binding value is allocated by PCC and reported to PCE via PCRpt</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="part-5" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-5"><em> page 7, line 4<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-5"><em> page 7, line 18<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"> corresponding PCEP session with the reason "Reception of a malformed</td><td> </td><td class="right"> corresponding PCEP session with the reason "Reception of a malformed</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> PCEP message" according ([RFC5440]).</td><td> </td><td class="right"> PCEP message" according ([RFC5440]).</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> If a PCC wishes to withdraw or modify a previously reported binding</td><td> </td><td class="right"> If a PCC wishes to withdraw or modify a previously reported binding</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> value, it MUST send a PCRpt message without any TE-PATH-BINDING TLV</td><td> </td><td class="right"> value, it MUST send a PCRpt message without any TE-PATH-BINDING TLV</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> or with the TE-PATH-BINDING TLV containing the new binding value</td><td> </td><td class="right"> or with the TE-PATH-BINDING TLV containing the new binding value</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> respectively.</td><td> </td><td class="right"> respectively.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> If a PCE wishes to modify a previously requested binding value, it</td><td> </td><td class="right"> If a PCE wishes to modify a previously requested binding value, it</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> MUST send a PCUpd message with TE-PATH-BINDING TLV containing the new</td><td> </td><td class="right"> MUST send a PCUpd message with TE-PATH-BINDING TLV containing the new</td><td class="lineno"></td></tr>
<tr id="diff0017"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> binding value. Absen<span class="delete">s</span>e of TE-PATH-BINDING TLV in PCUpd message means</td><td> </td><td class="rblock"> binding value. Absen<span class="insert">c</span>e of TE-PATH-BINDING TLV in PCUpd message means</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> that the PCE does not specify a binding value in which case the</td><td> </td><td class="right"> that the PCE does not specify a binding value in which case the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> binding value allocation is governed by the PCC's local policy.</td><td> </td><td class="right"> binding value allocation is governed by the PCC's local policy.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> If a PCC receives a valid binding value from a PCE which is different</td><td> </td><td class="right"> If a PCC receives a valid binding value from a PCE which is different</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> than the current binding value, it MUST try to allocate the new</td><td> </td><td class="right"> than the current binding value, it MUST try to allocate the new</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> value. If the new binding value is successfully allocated, the PCC</td><td> </td><td class="right"> value. If the new binding value is successfully allocated, the PCC</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> MUST report the new value to the PCE. Otherwise, it MUST send a</td><td> </td><td class="right"> MUST report the new value to the PCE. Otherwise, it MUST send a</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> PCErr message with Error-Type = TBD ("Binding label/SID failure") and</td><td> </td><td class="right"> PCErr message with Error-Type = TBD ("Binding label/SID failure") and</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Error Value = TBD ("Unable to allocate the specified label/SID").</td><td> </td><td class="right"> Error Value = TBD ("Unable to allocate the specified label/SID").</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> In some cases, a stateful PCE can request the PCC to allocate a</td><td> </td><td class="right"> In some cases, a stateful PCE can request the PCC to allocate a</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> binding value. It may do so by sending a PCUpd message containing an</td><td> </td><td class="right"> binding value. It may do so by sending a PCUpd message containing an</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> empty TE-PATH-BINDING TLV, i.e., no binding value is specified</td><td> </td><td class="right"> empty TE-PATH-BINDING TLV, i.e., no binding value is specified</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> (making the length of the TLV as 2). A PCE can also make the request</td><td> </td><td class="right"> (making the length of the TLV as 2). A PCE can also make the request</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> PCC to allocate a binding at the time of initiatiation by sending a</td><td> </td><td class="right"> PCC to allocate a binding at the time of initiatiation by sending a</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> PCInitiate message with an empty TE-PATH-BINDING TLV.</td><td> </td><td class="right"> PCInitiate message with an empty TE-PATH-BINDING TLV.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0018"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">4.1. PCE based Central Controller</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [RFC8283] introduces the architecture for PCE as a central controller</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> as an extension of the architecture described in [RFC4655] and</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> assumes the continued use of PCEP as the protocol used between PCE</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> and PCC. [RFC8283] further examines the motivations and</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> applicability for PCEP as a Southbound Interface (SBI), and</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> introduces the implications for the protocol.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> As per [RFC8283], PCE as a central controller can allocate and</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> provision the node/prefix/adjacency label (SID) via PCEP. It can</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> also be used to allocate the binding SID as described in this</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> section.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> For the purpose of this document, it is assumed that label range to</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> be used by a PCE is set on both PCEP peers or learned via some means.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Further, a global label range is assumed to be set on all PCEP peers</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> in the SR domain.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> The PCECC Capability as per</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [I-D.zhao-pce-pcep-extension-pce-controller-sr] should also be</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> advertised on the PCEP session, along with the SR sub-TLVs before</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> using this procedure.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> A P flag in LSP object is introduced in [I-D.li-pce-sr-path-segment]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> to indicate the allocation needs to be made by the PCE. The same</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> flag is also set for the binding SID allocation request. A PCC would</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> set this bit to 1 to request for allocation of the binding label/SID</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> by the PCE in the PCReq or PCRpt message. A PCE would also set this</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> bit to 1 to indicate that the binding label/SID is allocated by PCE</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> and encoded in the PCRep, PCUpd or PCInitiate message (the TE-PATH-</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> BINDING TLV is present in LSP object). Further, a PCE would set this</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> bit to 0 to indicate that the path identifier is allocated by the PCC</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> as described above.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> The ingress PCC could request the binding label/SID to be allocated</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> by the PCE via PCRpt message as per [RFC8231]. The delegate flag</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> (D-flag) MUST also be set for this LSP. The TE-PATH-BINDING TLV MAY</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> be included with Binding Value set to 0x00. The PCECC would</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> allocated the binding label/SID and further respond to Ingress PCC</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> with PCUpd message as per [RFC8231] and MUST include the TE-PATH-</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> BINDING TLV in a LSP object. The P flag in the LSP object would be</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> set to 1 to indicate that the allocation is made by the PCE.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> The PCE could allocate the binding label/SID on its own accord for a</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> PCE- Initiated (or delegated LSP). The allocated binding label/SID</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> needs to be informed to the PCC. The PCE would use the PCInitiate</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> message [RFC8281] or PCUpd message [RFC8231] towards the PCC and MUST</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> include the TE-PATH-BINDING TLV in the LSP object. The P flag in the</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> LSP object would be set to 1 to indicate that the allocation is made</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> by the PCE.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">5. Security Considerations</td><td> </td><td class="right">5. Security Considerations</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> The security considerations described in ([RFC5440]) and ([RFC8281])</td><td> </td><td class="right"> The security considerations described in ([RFC5440]) and ([RFC8281])</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> are applicable to this specification. No additional security measure</td><td> </td><td class="right"> are applicable to this specification. No additional security measure</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> is required.</td><td> </td><td class="right"> is required.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">6. IANA Considerations</td><td> </td><td class="right">6. IANA Considerations</td><td class="lineno"></td></tr>
<tr id="diff0019"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> </span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">6.1. TE-PATH-BINDING TLV</td><td> </td><td class="right">6.1. TE-PATH-BINDING TLV</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> IANA is requested to allocate a new TLV type (recommended value is</td><td> </td><td class="right"> IANA is requested to allocate a new TLV type (recommended value is</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 31)for TE-PATH-BINDING TLV specified in this document.</td><td> </td><td class="right"> 31)for TE-PATH-BINDING TLV specified in this document.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> This document requests that a registry is created to manage the value</td><td> </td><td class="right"> This document requests that a registry is created to manage the value</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> of the Binding Type field in the TE-PATH-BINDING TLV.</td><td> </td><td class="right"> of the Binding Type field in the TE-PATH-BINDING TLV.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Value Description Reference</td><td> </td><td class="right"> Value Description Reference</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="part-6" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-6"><em> page 8, line 13<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/rfcdiff#part-6"><em> page 9, line 33<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"> TBD (recommended 22) Binding SID failure:</td><td> </td><td class="right"> TBD (recommended 22) Binding SID failure:</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Error-value = TBD (recommended 1): Invalid SID</td><td> </td><td class="right"> Error-value = TBD (recommended 1): Invalid SID</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Error-value = TBD (recommended 2): Unable to allocate</td><td> </td><td class="right"> Error-value = TBD (recommended 2): Unable to allocate</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> binding SID</td><td> </td><td class="right"> binding SID</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">7. Acknowledgements</td><td> </td><td class="right">7. Acknowledgements</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> We like to thank Milos Fabian for his valuable comments.</td><td> </td><td class="right"> We like to thank Milos Fabian for his valuable comments.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0020"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock">8. <span class="delete">Normative</span> References</td><td> </td><td class="rblock">8. References</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> </td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">[I-D.ietf-idr-bgp-prefix-sid]</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Previdi, S., Filsfils, C., Lindem, A., Sreekantiah, A.,</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> and H. Gredler, "Segment Routing Prefix SID extensions for</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> BGP", draft-ietf-idr-bgp-prefix-sid-17 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> February 2018.</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> [I-D.ietf-idr-segment-routing-te-policy]</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Previdi, S., Filsfils, C., Jain, D., Mattes, P., Rosen,</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> E., and S. Lin, "Advertising Segment Routing Policies in</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> BGP", draft-ietf-idr-segment-routing-te-policy-02 (work in</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> progress), March 2018.</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> [I-D.ietf-isis-segment-routing-extensions]</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura,</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> "IS-IS Extensions for Segment Routing", draft-ietf-isis-</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> segment-routing-extensions-15 (work in progress), December</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> 2017.</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> [I-D.ietf-pce-pce-initiated-lsp]</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Extensions for PCE-initiated LSP Setup in a Stateful PCE</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Model", draft-ietf-pce-pce-initiated-lsp-11 (work in</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> progress), October 2017.</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> [I-D.ietf-pce-segment-routing]</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> and J. Hardwick, "PCEP Extensions for Segment Routing",</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> draft-ietf-pce-segment-routing-11 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> November 2017.</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> [I-D.ietf-pce-stateful-pce]</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Extensions for Stateful PCE", draft-ietf-pce-stateful-</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> pce-21 (work in progress), June 2017.</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0021"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">[I-D.ietf-spring-segment-routing]</span></td><td> </td><td class="rblock"><span class="insert">8.1. Normative References</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Litkowski, S., and R. Shakir, "Segment Routing</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> Architecture", draft-ietf-spring-segment-routing-15 (work</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> in progress), January 2018.</span></td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate</td><td> </td><td class="right"> [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Requirement Levels", BCP 14, RFC 2119,</td><td> </td><td class="right"> Requirement Levels", BCP 14, RFC 2119,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> DOI 10.17487/RFC2119, March 1997,</td><td> </td><td class="right"> DOI 10.17487/RFC2119, March 1997,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> <https://www.rfc-editor.org/info/rfc2119>.</td><td> </td><td class="right"> <https://www.rfc-editor.org/info/rfc2119>.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation</td><td> </td><td class="right"> [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Element (PCE) Communication Protocol (PCEP)", RFC 5440,</td><td> </td><td class="right"> Element (PCE) Communication Protocol (PCEP)", RFC 5440,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> DOI 10.17487/RFC5440, March 2009,</td><td> </td><td class="right"> DOI 10.17487/RFC5440, March 2009,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> <https://www.rfc-editor.org/info/rfc5440>.</td><td> </td><td class="right"> <https://www.rfc-editor.org/info/rfc5440>.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching</td><td> </td><td class="right"> [RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic</td><td> </td><td class="right"> (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Class" Field", RFC 5462, DOI 10.17487/RFC5462, February</td><td> </td><td class="right"> Class" Field", RFC 5462, DOI 10.17487/RFC5462, February</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 2009, <https://www.rfc-editor.org/info/rfc5462>.</td><td> </td><td class="right"> 2009, <https://www.rfc-editor.org/info/rfc5462>.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0022"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> <span class="insert">[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> May 2017, <https://www.rfc-editor.org/info/rfc8174>.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Path</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Computation Element Communication Protocol (PCEP)</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Extensions for Stateful PCE", RFC 8231,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> DOI 10.17487/RFC8231, September 2017,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> <https://www.rfc-editor.org/info/rfc8231>.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path</td><td> </td><td class="right"> [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Computation Element Communication Protocol (PCEP)</td><td> </td><td class="right"> Computation Element Communication Protocol (PCEP)</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Extensions for PCE-Initiated LSP Setup in a Stateful PCE</td><td> </td><td class="right"> Extensions for PCE-Initiated LSP Setup in a Stateful PCE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,</td><td> </td><td class="right"> Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> <https://www.rfc-editor.org/info/rfc8281>.</td><td> </td><td class="right"> <https://www.rfc-editor.org/info/rfc8281>.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0023"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> <span class="insert">[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Decraene, B., Litkowski, S., and R. Shakir, "Segment</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> July 2018, <https://www.rfc-editor.org/info/rfc8402>.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [I-D.ietf-pce-segment-routing]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> and J. Hardwick, "PCEP Extensions for Segment Routing",</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> draft-ietf-pce-segment-routing-12 (work in progress), June</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> 2018.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">8.2. Informative References</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP)</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Hierarchy with Generalized Multi-Protocol Label Switching</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> (GMPLS) Traffic Engineering (TE)", RFC 4206,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> DOI 10.17487/RFC4206, October 2005,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> <https://www.rfc-editor.org/info/rfc4206>.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Element (PCE)-Based Architecture", RFC 4655,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> DOI 10.17487/RFC4655, August 2006,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> <https://www.rfc-editor.org/info/rfc4655>.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [RFC8283] Farrel, A., Ed., Zhao, Q., Ed., Li, Z., and C. Zhou, "An</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Architecture for Use of PCE and the PCE Communication</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Protocol (PCEP) in a Network with Central Control",</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> RFC 8283, DOI 10.17487/RFC8283, December 2017,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> <https://www.rfc-editor.org/info/rfc8283>.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [I-D.ietf-idr-segment-routing-te-policy]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Previdi, S., Filsfils, C., Jain, D., Mattes, P., Rosen,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> E., and S. Lin, "Advertising Segment Routing Policies in</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> BGP", draft-ietf-idr-segment-routing-te-policy-04 (work in</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> progress), July 2018.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [I-D.ietf-isis-segment-routing-extensions]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> "IS-IS Extensions for Segment Routing", draft-ietf-isis-</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> segment-routing-extensions-19 (work in progress), July</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> 2018.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [I-D.ietf-idr-bgp-prefix-sid]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Previdi, S., Filsfils, C., Lindem, A., Sreekantiah, A.,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> and H. Gredler, "Segment Routing Prefix SID extensions for</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> BGP", draft-ietf-idr-bgp-prefix-sid-27 (work in progress),</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> June 2018.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [I-D.li-pce-sr-path-segment]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Li, C., Chen, M., Dong, J., Li, Z., and D. Dhody, "Path</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Computation Element Communication Protocol (PCEP)</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Extension for Path Identification in Segment Routing</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> (SR)", draft-li-pce-sr-path-segment-01 (work in progress),</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> August 2018.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> [I-D.zhao-pce-pcep-extension-pce-controller-sr]</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Zhao, Q., Li, Z., Dhody, D., Karunanithi, S., Farrel, A.,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> and C. Zhou, "PCEP Procedures and Protocol Extensions for</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> Using PCE as a Central Controller (PCECC) of SR-LSPs",</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> draft-zhao-pce-pcep-extension-pce-controller-sr-03 (work</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> in progress), June 2018.</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Authors' Addresses</td><td> </td><td class="right">Authors' Addresses</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Siva Sivabalan</td><td> </td><td class="right"> Siva Sivabalan</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Cisco Systems, Inc.</td><td> </td><td class="right"> Cisco Systems, Inc.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 2000 Innovation Drive</td><td> </td><td class="right"> 2000 Innovation Drive</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Kanata, Ontario K2K 3E8</td><td> </td><td class="right"> Kanata, Ontario K2K 3E8</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Canada</td><td> </td><td class="right"> Canada</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0024"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">Email:</span> [email protected]</td><td> </td><td class="rblock"> <span class="insert">EMail:</span> [email protected]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> </td><td> </td><td class="rblock"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Jeff Tantsura</td><td> </td><td class="right"> Jeff Tantsura</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Nuage Networks</td><td> </td><td class="right"> Nuage Networks</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 755 Ravendale Drive</td><td> </td><td class="right"> 755 Ravendale Drive</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Mountain View, CA 94043</td><td> </td><td class="right"> Mountain View, CA 94043</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> USA</td><td> </td><td class="right"> USA</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0025"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">Email:</span> [email protected]</td><td> </td><td class="rblock"> <span class="insert">EMail:</span> [email protected]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> </td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Clarence Filsfils</td><td> </td><td class="right"> Clarence Filsfils</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Cisco Systems, Inc.</td><td> </td><td class="right"> Cisco Systems, Inc.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Pegasus Parc</td><td> </td><td class="right"> Pegasus Parc</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> De kleetlaan 6a, DIEGEM BRABANT 1831</td><td> </td><td class="right"> De kleetlaan 6a, DIEGEM BRABANT 1831</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> BELGIUM</td><td> </td><td class="right"> BELGIUM</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0026"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> E<span class="delete">m</span>ail: [email protected]</td><td> </td><td class="rblock"> E<span class="insert">M</span>ail: [email protected]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Stefano Previdi</td><td> </td><td class="right"> Stefano Previdi</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Cisco Systems, Inc.</td><td> </td><td class="right"> Cisco Systems, Inc.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0027"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> E<span class="delete">m</span>ail: [email protected]</td><td> </td><td class="rblock"> E<span class="insert">M</span>ail: [email protected]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Jonathan Hardwick</td><td> </td><td class="right"> Jonathan Hardwick</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Metaswitch Networks</td><td> </td><td class="right"> Metaswitch Networks</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 100 Church Street</td><td> </td><td class="right"> 100 Church Street</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Enfield, Middlesex</td><td> </td><td class="right"> Enfield, Middlesex</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> UK</td><td> </td><td class="right"> UK</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0028"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> E<span class="delete">m</span>ail: [email protected]</td><td> </td><td class="rblock"> E<span class="insert">M</span>ail: [email protected]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Dhruv Dhody</td><td> </td><td class="right"> Dhruv Dhody</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Huawei Technologies</td><td> </td><td class="right"> Huawei Technologies</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Divyashree Techno Park, Whitefield</td><td> </td><td class="right"> Divyashree Techno Park, Whitefield</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Bangalore, Karnataka 560066</td><td> </td><td class="right"> Bangalore, Karnataka 560066</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> India</td><td> </td><td class="right"> India</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
<tr id="diff0029"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> E<span class="delete">m</span>ail: [email protected]</td><td> </td><td class="rblock"> E<span class="insert">M</span>ail: [email protected]</td><td class="lineno"></td></tr>
<tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
<tr id="end" bgcolor="gray"><th colspan="5" align="center"> End of changes. 29 change blocks. </th></tr>
<tr class="stats"><td></td><th><i>117 lines changed or deleted</i></th><th><i> </i></th><th><i>223 lines changed or added</i></th><td></td></tr>
<tr><td colspan="5" align="center" class="small"><br>This html diff was produced by rfcdiff 1.47. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/">http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
</tbody></table>
<div contenteditable="false" id="ginger-floatingG-container" style="position: absolute; top: 0px; left: 0px;"><div class="ginger-floatingG ginger-floatingG-closed" style="display: none;"><div class="ginger-floatingG-disabled-main"><div class="ginger-floatingG-bar-tool-tooltip">Enable Ginger</div></div><div class="ginger-floatingG-offline-main"><div class="ginger-floatingG-bar-tool-tooltip"><em>Cannot connect to Ginger</em> Check your internet connection<br> or reload the browser</div></div><div class="ginger-floatingG-enabled-main"><div class="ginger-floatingG-bar"><div class="ginger-floatingG-bar-tool ginger-floatingG-bar-tool-disable"><a></a><div class="ginger-floatingG-bar-tool-tooltip">Disable in this text field</div></div><div class="ginger-floatingG-bar-tool"><a class="ginger-floatingG-bar-tool-edit">Edit</a><div class="ginger-floatingG-bar-tool-tooltip">Edit in Ginger</div></div><div class="ginger-floatingG-bar-tool ginger-floatingG-bar-tool-mistakes"><a><span class="ginger-floatingG-bar-tool-mistakes-count"></span><svg width="14px" height="14px" viewBox="0 0 66 66" class="ginger-floatingG-loader-spinner"><circle class="ginger-floatingG-loader-spinner-path" fill="none" stroke-width="8.5" stroke-linecap="round" cx="33" cy="33" r="28"></circle></svg></a><div class="ginger-floatingG-bar-tool-tooltip">Edit in Ginger</div></div></div></div></div></div><div class="ginger-extension-writer" style="display: none;"><div class="ginger-extension-writer-frame"><iframe src="./Diff_ draft-sivabalan-pce-binding-label-sid-04.txt - draft-sivabalan-pce-binding-label-sid-05.txt_files/index.html"></iframe></div></div><div class="ginger-module-correctionBubble" style="display: none;"><div class="ginger-module-correctionBubble-container ginger-module-correctionBubble-container-loggedout"><div class="ginger-module-correctionBubble-login">Log in</div><div class="ginger-module-correctionBubble-body">to use Ginger</div></div><div class="ginger-module-correctionBubble-container ginger-module-correctionBubble-container-loggedin"><div class="ginger-module-correctionBubble-limited">Limited mode</div><div class="ginger-module-correctionBubble-body"></div><a href="javascript:" class="ginger-module-correctionBubble-close" title="Ignore mistake">×</a></div></div></body></html>