-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathDiff_ draft-ietf-pce-pceps-12.txt - draft-ietf-pce-pceps-13.txt.html
362 lines (353 loc) · 57.5 KB
/
Diff_ draft-ietf-pce-pceps-12.txt - draft-ietf-pce-pceps-13.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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- saved from url=(0049)https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht -->
<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-ietf-pce-pceps-12.txt - draft-ietf-pce-pceps-13.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.hash = "#" + 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-ietf-pce-pceps-12.txt" style="color:#008; text-decoration:none;"><</a> <a href="https://tools.ietf.org/html/draft-ietf-pce-pceps-12.txt" style="color:#008">draft-ietf-pce-pceps-12.txt</a> </th><th> </th><th> <a href="https://tools.ietf.org/html/draft-ietf-pce-pceps-13.txt" style="color:#008">draft-ietf-pce-pceps-13.txt</a> <a href="https://tools.ietf.org/rfcdiff?url1=draft-ietf-pce-pceps-13.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 D. Lopez</td><td> </td><td class="right">PCE Working Group D. Lopez</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Internet-Draft O. Gonzalez de Dios</td><td> </td><td class="right">Internet-Draft O. Gonzalez de Dios</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Updates: 5440 (if approved) Telefonica I+D</td><td> </td><td class="right">Updates: 5440 (if approved) Telefonica I+D</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left">Intended status: Standards Track Q. Wu</td><td> </td><td class="right">Intended status: Standards Track Q. Wu</td><td class="lineno"></td></tr>
<tr id="diff0001"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock">Expires: <span class="delete">October 13, 2017 </span> D. Dhody</td><td> </td><td class="rblock">Expires: <span class="insert">November 13, 2017</span> D. Dhody</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Huawei</td><td> </td><td class="right"> Huawei</td><td class="lineno"></td></tr>
<tr id="diff0002"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">April 11</span>, 2017</td><td> </td><td class="rblock"> <span class="insert"> May 12</span>, 2017</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"> Secure Transport for PCEP</td><td> </td><td class="right"> Secure Transport for PCEP</td><td class="lineno"></td></tr>
<tr id="diff0003"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> draft-ietf-pce-pceps-1<span class="delete">2</span></td><td> </td><td class="rblock"> draft-ietf-pce-pceps-1<span class="insert">3</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><td class="lineno"></td><td class="left"> The Path Computation Element Communication Protocol (PCEP) defines</td><td> </td><td class="right"> The Path Computation Element Communication Protocol (PCEP) defines</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> the mechanisms for the communication between a Path Computation</td><td> </td><td class="right"> the mechanisms for the communication between a Path Computation</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Client (PCC) and a Path Computation Element (PCE), or among PCEs.</td><td> </td><td class="right"> Client (PCC) and a Path Computation Element (PCE), or among PCEs.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> This document describe the usage of Transport Layer Security (TLS) to</td><td> </td><td class="right"> This document describe the usage of Transport Layer Security (TLS) to</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> enhance PCEP security, hence the PCEPS acronym proposed for it. The</td><td> </td><td class="right"> enhance PCEP security, hence the PCEPS acronym proposed for it. The</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> additional security mechanisms are provided by the transport protocol</td><td> </td><td class="right"> additional security mechanisms are provided by the transport protocol</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> supporting PCEP, and therefore they do not affect the flexibility and</td><td> </td><td class="right"> supporting PCEP, and therefore they do not affect the flexibility and</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/tools/rfcdiff/rfcdiff.pyht#part-2"><em> page 1, line 43<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-2"><em> page 1, line 43<span class="hide"> ¶</span></em></a></th><td></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 http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right"> Drafts is at http://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><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"> This Internet-Draft will expire on <span class="delete">Octo</span>ber 13, 2017.</td><td> </td><td class="rblock"> This Internet-Draft will expire on <span class="insert">Novem</span>ber 13, 2017.</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) 2017 IETF Trust and the persons identified as the</td><td> </td><td class="right"> Copyright (c) 2017 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"> (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right"> (http://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"></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/tools/rfcdiff/rfcdiff.pyht#part-3"><em> page 2, line 51<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-3"><em> page 2, line 51<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"> 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12</td><td> </td><td class="right"> 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 6.1. New PCEP Message . . . . . . . . . . . . . . . . . . . . 12</td><td> </td><td class="right"> 6.1. New PCEP Message . . . . . . . . . . . . . . . . . . . . 12</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 6.2. New Error-Values . . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right"> 6.2. New Error-Values . . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right"> 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 8. Manageability Considerations . . . . . . . . . . . . . . . . 14</td><td> </td><td class="right"> 8. Manageability Considerations . . . . . . . . . . . . . . . . 14</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 8.1. Control of Function and Policy . . . . . . . . . . . . . 14</td><td> </td><td class="right"> 8.1. Control of Function and Policy . . . . . . . . . . . . . 14</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 8.2. Information and Data Models . . . . . . . . . . . . . . . 14</td><td> </td><td class="right"> 8.2. Information and Data Models . . . . . . . . . . . . . . . 14</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 8.3. Liveness Detection and Monitoring . . . . . . . . . . . . 15</td><td> </td><td class="right"> 8.3. Liveness Detection and Monitoring . . . . . . . . . . . . 15</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 8.4. Verify Correct Operations . . . . . . . . . . . . . . . . 15</td><td> </td><td class="right"> 8.4. Verify Correct Operations . . . . . . . . . . . . . . . . 15</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 8.5. Requirements on Other Protocols . . . . . . . . . . . . . 15</td><td> </td><td class="right"> 8.5. Requirements on Other Protocols . . . . . . . . . . . . . 15</td><td class="lineno"></td></tr>
<tr id="diff0005"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 8.6. Impact on Network Operation<span class="delete">s </span> . . . . . . . . . . . . . . 15</td><td> </td><td class="rblock"> 8.6. Impact on Network Operation<span class="insert"> .</span> . . . . . . . . . . . . . . 15</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15</td><td> </td><td class="right"> 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15</td><td class="lineno"></td></tr>
<tr id="diff0006"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 10. References . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">15</span></td><td> </td><td class="rblock"> 10. References . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">16</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> 10.1. Normative References . . . . . . . . . . . . . . . . . . <span class="delete">15</span></td><td> </td><td class="rblock"> 10.1. Normative References . . . . . . . . . . . . . . . . . . <span class="insert">16</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 10.2. Informative References . . . . . . . . . . . . . . . . . 17</td><td> </td><td class="right"> 10.2. Informative References . . . . . . . . . . . . . . . . . 17</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18</td><td> </td><td class="right"> Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18</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"> The Path Computation Element Communication Protocol (PCEP) [RFC5440]</td><td> </td><td class="right"> The Path Computation Element Communication Protocol (PCEP) [RFC5440]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> defines the mechanisms for the communication between a Path</td><td> </td><td class="right"> defines the mechanisms for the communication between a Path</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Computation Client (PCC) and a Path Computation Element (PCE), or</td><td> </td><td class="right"> Computation Client (PCC) and a Path Computation Element (PCE), or</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> between two PCEs. These interactions include requests and replies</td><td> </td><td class="right"> between two PCEs. These interactions include requests and replies</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> that can be critical for a sustainable network operation and adequate</td><td> </td><td class="right"> that can be critical for a sustainable network operation and adequate</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/tools/rfcdiff/rfcdiff.pyht#part-4"><em> page 4, line 15<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-4"><em> page 4, line 15<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left">2. Requirements Language</td><td> </td><td class="right">2. 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><td class="lineno"></td><td class="left"> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td> </td><td class="right"> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> document are to be interpreted as described in [RFC2119].</td><td> </td><td class="right"> document are to be interpreted as described in [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">3. Applying PCEPS</td><td> </td><td class="right">3. Applying PCEPS</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.1. Overview</td><td> </td><td class="right">3.1. Overview</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="diff0007"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> The steps involved in <span class="delete">the</span> PCEPS <span class="delete">establishment consists of following</span></td><td> </td><td class="rblock"> The steps involved in <span class="insert">establishing a</span> PCEPS <span class="insert">session are as follows:</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> successive steps:</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"> 1. Establishment of a TCP connection.</td><td> </td><td class="right"> 1. Establishment of a TCP connection.</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. Initiating the TLS procedures by the StartTLS message from PCE to</td><td> </td><td class="right"> 2. Initiating the TLS procedures by the StartTLS message from PCE to</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> PCC and from PCC to PCE.</td><td> </td><td class="right"> PCC and from PCC to 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"> 3. Establishment of TLS connection.</td><td> </td><td class="right"> 3. Establishment of TLS connection.</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. Start exchanging PCEP messages as per [RFC5440].</td><td> </td><td class="right"> 4. Start exchanging PCEP messages as per [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"></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/tools/rfcdiff/rfcdiff.pyht#part-5"><em> page 5, line 22<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-5"><em> page 5, line 22<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"> a StartTLS message for the PCEPS. Note this is a significant change</td><td> </td><td class="right"> a StartTLS message for the PCEPS. Note this is a significant change</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> from [RFC5440] where the first PCEP message is the Open message.</td><td> </td><td class="right"> from [RFC5440] where the first PCEP message is the Open message.</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 PCEP speaker receiving a StartTLS message, after any other PCEP</td><td> </td><td class="right"> A PCEP speaker receiving a StartTLS message, after any other PCEP</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> exchange has taken place (by receiving or sending any other messages</td><td> </td><td class="right"> exchange has taken place (by receiving or sending any other messages</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> from either side) MUST treat it as an unexpected message and reply</td><td> </td><td class="right"> from either side) MUST treat it as an unexpected message and reply</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> with a PCErr message with Error-Type set to [TBA2 by IANA] (PCEP</td><td> </td><td class="right"> with a PCErr message with Error-Type set to [TBA2 by IANA] (PCEP</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> StartTLS failure) and Error-value set to 1 (reception of StartTLS</td><td> </td><td class="right"> StartTLS failure) and Error-value set to 1 (reception of StartTLS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> after any PCEP exchange), and MUST close the TCP connection. A PCEP</td><td> </td><td class="right"> after any PCEP exchange), and MUST close the TCP connection. A PCEP</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> speaker receiving any other message apart from StartTLS, open, or</td><td> </td><td class="right"> speaker receiving any other message apart from StartTLS, open, or</td><td class="lineno"></td></tr>
<tr id="diff0008"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> PCErr MUST treat it as an unexpected message and reply with a PCErr</td><td> </td><td class="rblock"> PCErr <span class="insert">as the first message,</span> MUST treat it as an unexpected message</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> message with Error-Type set to [TBA2 by IANA] (PCEP StartTLS failure)</td><td> </td><td class="rblock"> and reply with a PCErr message with Error-Type set to [TBA2 by IANA]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> and Error-value set to 2 (reception of any other message apart from</td><td> </td><td class="rblock"> (PCEP StartTLS failure) and Error-value set to 2 (reception of any</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"> StartTLS, Open, or PCErr message), and MUST close the TCP connection.</td><td> </td><td class="rblock"> other message apart from StartTLS, Open, or PCErr message), and MUST</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> close the TCP connection.</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 the PCEP speaker that does not support PCEPS, receives a StartTLS</td><td> </td><td class="right"> If the PCEP speaker that does not support PCEPS, receives a StartTLS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> message, it MUST behave according to the existing error mechanism</td><td> </td><td class="right"> message, it MUST behave according to the existing error mechanism</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> described in section 6.2 of [RFC5440] (in case message is received</td><td> </td><td class="right"> described in section 6.2 of [RFC5440] (in case message is received</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> prior to an Open message) or section 6.9 of [RFC5440] (for the case</td><td> </td><td class="right"> prior to an Open message) or section 6.9 of [RFC5440] (for the case</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> of reception of unknown message).</td><td> </td><td class="right"> of reception of unknown message).</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"> After the exchange of startTLS messages, if a PCEP speaker cannot</td><td> </td><td class="right"> After the exchange of startTLS messages, if a PCEP speaker cannot</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> establish a TLS connection for some reason (e.g. the required</td><td> </td><td class="right"> establish a TLS connection for some reason (e.g. the required</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> mechanisms for certificate revocation checking are not available), it</td><td> </td><td class="right"> mechanisms for certificate revocation checking are not available), it</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/tools/rfcdiff/rfcdiff.pyht#part-6"><em> page 6, line 18<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-6"><em> page 6, line 18<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"> Given the asymmetric nature of TLS for connection establishment it is</td><td> </td><td class="right"> Given the asymmetric nature of TLS for connection establishment it is</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> relevant to identify the roles of each of the PCEP peers in it. The</td><td> </td><td class="right"> relevant to identify the roles of each of the PCEP peers in it. The</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> PCC SHALL act as TLS client, and the PCE SHALL act as TLS server,</td><td> </td><td class="right"> PCC SHALL act as TLS client, and the PCE SHALL act as TLS server,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> according to [RFC5246].</td><td> </td><td class="right"> according to [RFC5246].</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"> These procedures minimize the impact of PCEPS support in PCEP</td><td> </td><td class="right"> These procedures minimize the impact of PCEPS support in PCEP</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> implementations without requiring additional dedicated ports for</td><td> </td><td class="right"> implementations without requiring additional dedicated ports for</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> running PCEP with TLS.</td><td> </td><td class="right"> running PCEP with TLS.</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="diff0009"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> <span class="insert">As per the recommendation from [RFC7525] to avoid downgrade attacks,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> PCEP peers that support PCEPS, SHOULD prefer strict TLS configuration</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.e. do not allow non-TLS PCEP sessions to be established.</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">3.3. The StartTLS Message</td><td> </td><td class="right">3.3. The StartTLS Message</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 StartTLS message is used to initiate the TLS procedure for a</td><td> </td><td class="right"> The StartTLS message is used to initiate the TLS procedure for a</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> PCEPS session between the PCEP peers. A PCEP speaker sends the</td><td> </td><td class="right"> PCEPS session between the PCEP peers. A PCEP speaker sends the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> StartTLS message to request negotiation and establishment of TLS</td><td> </td><td class="right"> StartTLS message to request negotiation and establishment of TLS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> connection for PCEP. On receiving a StartTLS message from the PCEP</td><td> </td><td class="right"> connection for PCEP. On receiving a StartTLS message from the PCEP</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> peer (i.e. when the PCEP speaker has sent and received StartTLS</td><td> </td><td class="right"> peer (i.e. when the PCEP speaker has sent and received StartTLS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> message) it is ready to start TLS negotiation and establishment and</td><td> </td><td class="right"> message) it is ready to start TLS negotiation and establishment and</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> move to steps described in Section 3.4.</td><td> </td><td class="right"> move to steps described in Section 3.4.</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-7" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-7"><em> page 10, line 12<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-7"><em> page 10, line 12<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"> * TLS with X.509 certificates using certificate fingerprints:</td><td> </td><td class="right"> * TLS with X.509 certificates using certificate fingerprints:</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Implementations MUST allow the configuration of a list of</td><td> </td><td class="right"> Implementations MUST allow the configuration of a list of</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> trusted certificates, identified via fingerprint of the</td><td> </td><td class="right"> trusted certificates, identified via fingerprint of the</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Distinguished Encoding Rules (DER) encoded certificate octets.</td><td> </td><td class="right"> Distinguished Encoding Rules (DER) encoded certificate octets.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Implementations MUST support SHA-256 as defined by [SHS] as</td><td> </td><td class="right"> Implementations MUST support SHA-256 as defined by [SHS] as</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> the hash algorithm for the fingerprint.</td><td> </td><td class="right"> the hash algorithm for the fingerprint.</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. Start exchanging PCEP messages.</td><td> </td><td class="right"> 3. Start exchanging PCEP messages.</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"> To support TLS re-negotiation both peers MUST support the mechanism</td><td> </td><td class="right"> To support TLS re-negotiation both peers MUST support the mechanism</td><td class="lineno"></td></tr>
<tr id="diff0010"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> described in [RFC5746]. Any attempt <span class="delete">of</span> initiate a TLS handshake to</td><td> </td><td class="rblock"> described in [RFC5746]. Any attempt <span class="insert">to</span> initiate a TLS handshake to</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> establish new cryptographic parameters not aligned with [RFC5746]</td><td> </td><td class="right"> establish new cryptographic parameters not aligned with [RFC5746]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> SHALL be considered a TLS negotiation failure.</td><td> </td><td class="right"> SHALL be considered a TLS negotiation 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">3.5. Peer Identity</td><td> </td><td class="right">3.5. Peer Identity</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"> Depending on the peer authentication method in use, PCEPS supports</td><td> </td><td class="right"> Depending on the peer authentication method in use, PCEPS supports</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> different operation modes to establish peer's identity and whether it</td><td> </td><td class="right"> different operation modes to establish peer's identity and whether it</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> is entitled to perform requests or can be considered authoritative in</td><td> </td><td class="right"> is entitled to perform requests or can be considered authoritative in</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> its replies. PCEPS implementations SHOULD provide mechanisms for</td><td> </td><td class="right"> its replies. PCEPS implementations SHOULD provide mechanisms for</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> associating peer identities with different levels of access and/or</td><td> </td><td class="right"> associating peer identities with different levels of access and/or</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-8" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-8"><em> page 15, line 24<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-8"><em> page 15, line 24<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left">8.4. Verify Correct Operations</td><td> </td><td class="right">8.4. Verify Correct Operations</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 PCEPS implementation SHOULD log error events and provide PCEPS</td><td> </td><td class="right"> A PCEPS implementation SHOULD log error events and provide PCEPS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> failure statistics with reasons.</td><td> </td><td class="right"> failure statistics with reasons.</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">8.5. Requirements on Other Protocols</td><td> </td><td class="right">8.5. Requirements on Other Protocols</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"> Mechanisms defined in this document do not imply any new requirements</td><td> </td><td class="right"> Mechanisms defined in this document do not imply any new requirements</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> on other protocols.</td><td> </td><td class="right"> on other protocols.</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="diff0011"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock">8.6. Impact on Network Operation<span class="delete">s</span></td><td> </td><td class="rblock">8.6. Impact on Network 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 id="diff0012"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> <span class="delete">Mechanisms defined in this document do not have any impact on network</span></td><td> </td><td class="rblock"> <span class="insert">The operator need to develop suitable security policies around PCEP,</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"><span class="delete"> operations in addition</span> to <span class="delete">those already listed</span> in <span class="delete">[RFC5440].</span></td><td> </td><td class="rblock"><span class="insert"> within his network. Further the PCEP peers SHOULD provide ways 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"> the operator to complete following tasks:</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"> o Determine if a PCEP session is protected via PCEPS.</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"> o Determine the version of TLS, mechanism for authentication used.</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"> o Determine if the certificate cannot be verified and the cipher</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> suite used.</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"> o Inspect the certificate offered by the PCEP peer.</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"> o Be warned if StartTLS procedure fails for the PCEP peers, that are</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> known</span> to <span class="insert">support PCEPS (via configurations or capability</span></td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"> advertisements).</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, the backward compatibility considerations are stated</span> in</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> <span class="insert">Section 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">9. Acknowledgements</td><td> </td><td class="right">9. 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"> This specification relies on the analysis and profiling of TLS</td><td> </td><td class="right"> This specification relies on the analysis and profiling of TLS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> included in [RFC6614] and the procedures described for the STARTTLS</td><td> </td><td class="right"> included in [RFC6614] and the procedures described for the STARTTLS</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> command in [RFC4513].</td><td> </td><td class="right"> command in [RFC4513].</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 would like to thank Joe Touch for his suggestions and support</td><td> </td><td class="right"> We would like to thank Joe Touch for his suggestions and support</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> regarding the TLS start mechanisms.</td><td> </td><td class="right"> regarding the TLS start mechanisms.</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"> Thanks to Dan King for reminding the authors about manageability</td><td> </td><td class="right"> Thanks to Dan King for reminding the authors about manageability</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> considerations.</td><td> </td><td class="right"> 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"> Thanks to Cyril Margaria for shepherding this document.</td><td> </td><td class="right"> Thanks to Cyril Margaria for shepherding 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 id="diff0013"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"></td><td> </td><td class="rblock"> <span class="insert">Thanks to Dan Frost for the RTGDIR review.</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">10. References</td><td> </td><td class="right">10. References</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">10.1. Normative References</td><td> </td><td class="right">10.1. Normative References</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"> <http://www.rfc-editor.org/info/rfc2119>.</td><td> </td><td class="right"> <http://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"> [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security</td><td> </td><td class="right"> [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security</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-9" class="change"><td></td><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-9"><em> page 18, line 6<span class="hide"> ¶</span></em></a></th><th> </th><th><small>skipping to change at</small><a href="https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht#part-9"><em> page 18, line 26<span class="hide"> ¶</span></em></a></th><td></td></tr>
<tr><td class="lineno"></td><td class="left"> progress), March 2017.</td><td> </td><td class="right"> progress), March 2017.</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"> [I-D.ietf-pce-pcep-yang]</td><td> </td><td class="right"> [I-D.ietf-pce-pcep-yang]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Dhody, D., Hardwick, J., Beeram, V., and j.</td><td> </td><td class="right"> Dhody, D., Hardwick, J., Beeram, V., and j.</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> [email protected], "A YANG Data Model for Path</td><td> </td><td class="right"> [email protected], "A YANG Data Model for Path</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Computation Element Communications Protocol (PCEP)",</td><td> </td><td class="right"> Computation Element Communications Protocol (PCEP)",</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> draft-ietf-pce-pcep-yang-02 (work in progress), March</td><td> </td><td class="right"> draft-ietf-pce-pcep-yang-02 (work in progress), March</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> 2017.</td><td> </td><td class="right"> 2017.</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"> [I-D.wu-pce-dns-pce-discovery]</td><td> </td><td class="right"> [I-D.wu-pce-dns-pce-discovery]</td><td class="lineno"></td></tr>
<tr id="diff0014"><td></td></tr>
<tr><td class="lineno"></td><td class="lblock"> Wu, <span class="delete">W</span>., Dhody, D., King, D., Lopez, D., and J. Tantsura,</td><td> </td><td class="rblock"> Wu, <span class="insert">Q</span>., Dhody, D., King, D., Lopez, D., and J. Tantsura,</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> "Path Computation Element (PCE) Discovery using Domain</td><td> </td><td class="right"> "Path Computation Element (PCE) Discovery using Domain</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Name System(DNS)", draft-wu-pce-dns-pce-discovery-10 (work</td><td> </td><td class="right"> Name System(DNS)", draft-wu-pce-dns-pce-discovery-10 (work</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> in progress), March 2017.</td><td> </td><td class="right"> in progress), March 2017.</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"> [I-D.wu-pce-discovery-pceps-support]</td><td> </td><td class="right"> [I-D.wu-pce-discovery-pceps-support]</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> Lopez, D., Wu, Q., Dhody, D., and D. King, "IGP extension</td><td> </td><td class="right"> Lopez, D., Wu, Q., Dhody, D., and D. King, "IGP extension</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> for PCEP security capability support in the PCE</td><td> </td><td class="right"> for PCEP security capability support in the PCE</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> discovery", draft-wu-pce-discovery-pceps-support-07 (work</td><td> </td><td class="right"> discovery", draft-wu-pce-discovery-pceps-support-07 (work</td><td class="lineno"></td></tr>
<tr><td class="lineno"></td><td class="left"> in progress), March 2017.</td><td> </td><td class="right"> in progress), March 2017.</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></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. 14 change blocks. </th></tr>
<tr class="stats"><td></td><th><i>18 lines changed or deleted</i></th><th><i> </i></th><th><i>41 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.45. 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>
</body></html>