Debian Codegraph @

rfc7324.html

raw
1 <pre>Internet Engineering Task Force (IETF) E. Osborne
2 Request for Comments: 7324 July 2014
3 Updates: <a href="./rfc6378">6378</a>
4 Category: Standards Track
5 ISSN: 2070-1721
6
7
8 <span class="h1">Updates to MPLS Transport Profile Linear Protection</span>
9
10 Abstract
11
12 This document contains a number of updates to the Protection State
13 Coordination (PSC) logic defined in <a href="./rfc6378">RFC 6378</a>, "MPLS Transport Profile
14 (MPLS-TP) Linear Protection". These updates provide some rules and
15 recommendations around the use of TLVs in PSC, address some issues
16 raised in an ITU-T liaison statement, and clarify PSC's behavior in a
17 case not well explained in <a href="./rfc6378">RFC 6378</a>.
18
19 Status of This Memo
20
21 This is an Internet Standards Track document.
22
23 This document is a product of the Internet Engineering Task Force
24 (IETF). It represents the consensus of the IETF community. It has
25 received public review and has been approved for publication by the
26 Internet Engineering Steering Group (IESG). Further information on
27 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
28
29 Information about the current status of this document, any errata,
30 and how to provide feedback on it may be obtained at
31 <a href="http://www.rfc-editor.org/info/rfc7324">http://www.rfc-editor.org/info/rfc7324</a>.
32
33 Copyright Notice
34
35 Copyright (c) 2014 IETF Trust and the persons identified as the
36 document authors. All rights reserved.
37
38 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
39 Provisions Relating to IETF Documents
40 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
41 publication of this document. Please review these documents
42 carefully, as they describe your rights and restrictions with respect
43 to this document. Code Components extracted from this document must
44 include Simplified BSD License text as described in Section 4.e of
45 the Trust Legal Provisions and are provided without warranty as
46 described in the Simplified BSD License.
47
48
49
50
51
52 <span class="grey">Osborne Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
60 <a href="#section-1.1">1.1</a>. Requirements Language . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-2">2</a>. Message Formatting and Error Handling . . . . . . . . . . . . <a href="#page-3">3</a>
62 <a href="#section-2.1">2.1</a>. PSC TLV Format . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
63 <a href="#section-2.2">2.2</a>. Error Handling . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
64 <a href="#section-2.2.1">2.2.1</a>. Malformed Messages . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
65 <a href="#section-2.2.2">2.2.2</a>. Well-Formed but Unknown or Unexpected TLV . . . . . . <a href="#page-4">4</a>
66 <a href="#section-3">3</a>. Incorrect Local Status after Failure . . . . . . . . . . . . <a href="#page-5">5</a>
67 <a href="#section-4">4</a>. Handling a Capabilities Mismatch . . . . . . . . . . . . . . <a href="#page-5">5</a>
68 <a href="#section-4.1">4.1</a>. Protection Type Mismatch . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
69 <a href="#section-4.2">4.2</a>. R Mismatch . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
70 <a href="#section-4.3">4.3</a>. Unsupported Modes . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
71 <a href="#section-5">5</a>. Reversion Deadlock Due to a Race Condition . . . . . . . . . <a href="#page-7">7</a>
72 <a href="#section-6">6</a>. Clarifying PSC's Behavior in the Face of Multiple Inputs . . <a href="#page-8">8</a>
73 <a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
74 <a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
75 <a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
76 <a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
77 <a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
78 <a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
79
80 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
81
82 This document contains a number of updates to PSC [<a href="./rfc6378" title="&quot;MPLS Transport Profile (MPLS-TP) Linear Protection&quot;">RFC6378</a>]. One
83 provides some rules and recommendations around the use of TLVs in
84 PSC. Three of the updates address issues #2, #7, and #8 as
85 identified in the ITU's liaison statement "Recommendation ITU-T
86 G.8131/Y.1382 revision - Linear protection switching for MPLS-TP
87 networks" [<a href="#ref-LIAISON" title="&quot;Liaison Statement: Recommendation ITU-T G.8131/Y.1382 revision - Linear protection switching for MPLS-TP networks&quot;">LIAISON</a>]. Another clears up a behavior that was not well
88 explained in <a href="./rfc6378">RFC 6378</a>. These updates are not changes to the
89 protocol's packet format or to PSC's design; they are corrections and
90 clarifications to specific aspects of the protocol's procedures.
91 This document does not introduce backward compatibility issues with
92 implementations of <a href="./rfc6378">RFC 6378</a>.
93
94 It should be noted that [<a href="./rfc7271" title="&quot;MPLS Transport Profile (MPLS- TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators&quot;">RFC7271</a>] contains protocol mechanisms for an
95 alternate mode of operating MPLS-TP PSC. Those modes are built on
96 the message structures and procedures of [<a href="./rfc6378" title="&quot;MPLS Transport Profile (MPLS-TP) Linear Protection&quot;">RFC6378</a>], and so, while
97 this document does not update [<a href="./rfc7271" title="&quot;MPLS Transport Profile (MPLS- TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators&quot;">RFC7271</a>], it has an impact on that
98 work through its update to [<a href="./rfc6378" title="&quot;MPLS Transport Profile (MPLS-TP) Linear Protection&quot;">RFC6378</a>].
99
100 This document assumes familiarity with <a href="./rfc6378">RFC 6378</a> and its terms,
101 conventions, and acronyms. Any term used in this document but not
102 defined herein can be found in <a href="./rfc6378">RFC 6378</a>. In particular, this
103 document shares the acronyms defined in <a href="./rfc6378#section-2.1">Section&nbsp;2.1 of RFC 6378</a>.
104
105
106
107
108 <span class="grey">Osborne Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
111
112
113 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
114
115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
117 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
118
119 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Message Formatting and Error Handling</span>
120
121 This section covers message formatting as well as some recommended
122 error checking.
123
124 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. PSC TLV Format</span>
125
126 [<a id="ref-RFC6378">RFC6378</a>] provides the capability to carry TLVs in the PSC messages.
127 All fields are encoded in network byte order. Each TLV contains
128 three fields, as follows:
129
130 0 1 2 3
131 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
132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
133 | Type | Length |
134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
135 | Value |
136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
137
138 Type field (T):
139
140 A two-octet field that encodes a type value. The type values are
141 recorded in the IANA registry "MPLS PSC TLV Registry".
142
143 Length field (L):
144
145 A two-octet field that encodes the length in octets of the Value
146 field. The value of this field MUST be a multiple of 4.
147
148 Value field (V):
149
150 The payload of the TLV. The length of this field (which is the value
151 of the Length field) MUST be a multiple of 4 octets, and so this
152 field may contain explicit padding. The length of each single TLV is
153 the sum of the lengths of its three fields: the length of the value
154 field + 4. The overall TLV Length field in the PSC message contains
155 the total length of all TLVs in octets.
156
157
158
159
160
161
162
163
164 <span class="grey">Osborne Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
167
168
169 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Error Handling</span>
170
171 It is recommended to implement error and bounds checking to ensure
172 that received messages, if improperly formatted, are handled in such
173 a way to minimize the impact of this formatting on the behavior of
174 the network and its devices. This section covers two such areas --
175 malformed messages and well-formed but unexpected TLVs.
176
177 This text is not intended to limit the error or bounds checking a
178 device performs. The recommendations herein should be taken as a
179 starting point.
180
181 <span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Malformed Messages</span>
182
183 An implementation SHOULD:
184
185 o Ensure any fields prior to TLV Length are consistent with <a href="./rfc6378">RFC</a>
186 <a href="./rfc6378">6378</a>, particularly <a href="#section-4.2">Section 4.2</a> of that document.
187
188 o Ensure the overall length of the message matches the value in the
189 TLV Length + 12.
190
191 o Check that the sum of the lengths of all TLVs matches the value in
192 the TLV Length.
193
194 If an implementation receives a message that fails any malformed
195 message checks, it MUST drop the message and SHOULD alert the
196 operator to the malformed message. The method(s) used to alert the
197 operator are outside the scope of this document but may include
198 things like syslog or console messages.
199
200 <span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>. Well-Formed but Unknown or Unexpected TLV</span>
201
202 If a message is deemed to be properly formed, an implementation
203 SHOULD check all TLVs to ensure that it knows what to do with them.
204 A well-formed but unknown or unexpected TLV value MUST be ignored,
205 and the rest of the message processed as if the ignored TLV did not
206 exist. An implementation detecting a malformed TLV SHOULD alert the
207 operator as described in <a href="#section-2.2.1">Section 2.2.1</a>.
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Osborne Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
223
224
225 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Incorrect Local Status after Failure</span>
226
227 Issue #2 in the liaison statement identifies a case where a strict
228 reading of <a href="./rfc6378">RFC 6378</a> leaves a node reporting an inaccurate status:
229
230 A node can end up sending incorrect status -- NR(0,1) -- despite the
231 failure of the protection LSP (P-LSP). This is clearly not correct,
232 as a node should not be sending NR if it has a local failure. To
233 address this issue, the fourth bullet in <a href="./rfc6378#section-4.3.3.3">Section&nbsp;4.3.3.3 of RFC 6378</a>
234 is replaced with the following three bullets:
235
236 o If the current state is due to a local or remote Manual Switch, a
237 local Signal Fail indication on the protection path SHALL cause
238 the LER to enter local Unavailable state and begin transmission of
239 an SF(0,0) message.
240
241 o If the LER is in local Protecting Administrative state due to a
242 local Forced Switch, a local Signal Fail indication on the
243 protection path SHALL be ignored.
244
245 o If the LER is in remote Protecting Administrative state due to a
246 remote Forced Switch, a local Signal Fail indication on the
247 protection path SHALL cause the LER to remain in remote Protecting
248 administrative state and transmit an SF(0,1) message.
249
250 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Handling a Capabilities Mismatch</span>
251
252 PSC has no explicit facility to negotiate any properties of the
253 protection domain. It does, however, have the ability to signal two
254 properties of that domain, via the Protection Type (PT) and Revertive
255 (R) bits. <a href="./rfc6378">RFC 6378</a> specifies that if these bits do not match an
256 operator "SHALL [be notified]" (PT, <a href="#section-4.2.3">Section 4.2.3</a>) or "SHOULD be
257 notified" (R, <a href="#section-4.2.4">Section 4.2.4</a>). However, there is no text that
258 specifies the behavior of the end nodes of a protection domain in
259 case of a mismatch. This section provides that text, as requested by
260 issue #7 in the liaison statement.
261
262 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Protection Type Mismatch</span>
263
264 The behavior of the protection domain depends on the exact Protection
265 Type (PT) mismatch. <a href="./rfc6378#section-4.2.3">Section&nbsp;4.2.3 of RFC 6378</a> specifies three
266 protection types -- bidirectional switching using a permanent bridge,
267 bidirectional switching using a selector bridge, and unidirectional
268 switching using a permanent bridge. They are abbreviated here as BP,
269 BS, and UP.
270
271
272
273
274
275
276 <span class="grey">Osborne Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
279
280
281 There are three possible mismatches: {BP, UP}, {BP, BS}, and
282 {UP, BS}. The priority is:
283
284 UP &gt; BS &gt; BP
285
286 In other words:
287
288 o If the PT mismatch is {BP, UP}, the node transmitting BP MUST
289 switch to UP mode if it is supported.
290
291 o If the PT mismatch is {BP, BS}, the node transmitting BP MUST
292 switch to BS mode if it is supported.
293
294 o If the PT mismatch is {UP, BS}, the node transmitting BS MUST
295 switch to UP mode if it is supported.
296
297 If a node does not support a mode to which it is required to switch,
298 then that node MUST behave as in <a href="#section-4.3">Section 4.3</a>.
299
300 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. R Mismatch</span>
301
302 The R bit indicates whether the protection domain is in revertive or
303 non-revertive behavior. If the R bits do not match, the node
304 indicating non-revertive MUST switch to Revertive if it is supported.
305 If it is not supported, a node must behave as in <a href="#section-4.3">Section 4.3</a>.
306
307 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Unsupported Modes</span>
308
309 An implementation may not support all three PT modes and/or both R
310 modes, and thus a pair of nodes may be unable to converge on a common
311 mode. This creates a permanent mismatch, resolvable only by operator
312 intervention. An implementation SHOULD alert the operator to an
313 irreconcilable mismatch.
314
315 It is desirable to allow the protection domain to function in a non-
316 failure mode even if there is a mismatch, as the mismatches of PT or
317 R have to do with how nodes recover from a failure. An
318 implementation SHOULD allow traffic to be sent on the Working LSP as
319 long as there is no failure (e.g., NR state) regardless of any PT or
320 R mismatch.
321
322 If there is a trigger that would cause the protection LSP to be used,
323 such as SF or MS, a node MUST NOT use the protection LSP to carry
324 traffic.
325
326
327
328
329
330
331
332 <span class="grey">Osborne Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
335
336
337 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Reversion Deadlock Due to a Race Condition</span>
338
339 Issue #8 in the liaison statement identifies a deadlock case where
340 each node can end up sending NR(0,1) when it should instead be in the
341 process of recovering from the failure (i.e., entering into WTR or
342 DNR, as appropriate for the protection domain). The root of the
343 issue is that a pair of nodes can simultaneously enter WTR state,
344 receive an out-of-date SF-W indication, transition into a remotely
345 triggered WTR, and remain in remotely triggered WTR waiting for the
346 other end to trigger a change in status.
347
348 In the case identified in issue #8, each node can end up sending
349 NR(0,1), which is an indication that the transmitting node has no
350 local failure, but is instead reacting to the remote SF-W. If a node
351 that receives NR(0,1) is in fact not indicating a local error, the
352 correct behavior for the receiving node is to take the received
353 NR(0,1) as an indication that there is no error in the protection
354 domain, and recovery procedures (WTR or DNR) should begin.
355
356 This is addressed by adding the following text as the penultimate
357 bullet in <a href="./rfc6378#section-4.3.3.4">Section&nbsp;4.3.3.4 of RFC 6378</a>:
358
359 o If a node is in Protecting Failure state due to a remote SF-W and
360 receives NR(0,1), this SHALL cause the node to begin recovery
361 procedures. If the LER is configured for revertive behavior, it
362 enters into Wait-to-Restore state, starts the WTR timer, and
363 begins transmitting WTR(0,1). If the LER is configured for non-
364 revertive behavior, it enters into Do-Not-Revert state and begins
365 transmitting a DNR(0,1) message.
366
367 Additionally, the penultimate bullet in <a href="#section-4.3.3.3">Section 4.3.3.3</a> is changed
368 from
369
370 o A remote NR(0,0) message SHALL be ignored if in local Protecting
371 administrative state.
372
373 to
374
375 o A remote No Request message SHALL be ignored if in local
376 Protecting administrative state.
377
378 This indicates that a remote NR triggers the same behavior regardless
379 of the value of FPath and Path. This change does not directly
380 address issue #8, but it fixes a similar issue -- if a node receives
381 NR while in Remote administrative state, the value of FPath and Path
382 have no bearing on the node's reaction to this NR.
383
384
385
386
387
388 <span class="grey">Osborne Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
391
392
393 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Clarifying PSC's Behavior in the Face of Multiple Inputs</span>
394
395 <a href="./rfc6378">RFC 6378</a> describes the PSC state machine. Figure 1 in <a href="./rfc6378#section-3">Section&nbsp;3 of
396 RFC 6378</a> shows two inputs into the PSC Control logic -- Local Request
397 logic and Remote PSC Request. When there is only one input into the
398 PSC Control logic -- a local request or a remote request but not both
399 -- the PSC Control logic decides what that input signifies and then
400 takes one or more actions, as necessary. This is what the PSC State
401 Machine in <a href="./rfc6378#section-4.3">Section&nbsp;4.3 of RFC 6378</a> describes.
402
403 <a href="./rfc6378">RFC 6378</a> does not sufficiently describe the behavior in the face of
404 multiple inputs into the PSC Control Logic (one Local Request and one
405 Remote Request). This section clarifies the expected behavior.
406
407 There are two cases to think about when considering dual inputs into
408 the PSC Control logic. The first is when the same request is
409 presented from both local and remote sources. One example of this
410 case is a Forced Switch (FS) configured on both ends of an LSP. This
411 will result in the PSC Control logic receiving both a local FS and
412 remove FS. For convenience, this scenario is written as [L(FS),
413 R(FS)] -- that is, Local(Forced Switch) and Remote(Forced Switch).
414
415 The second case, which is handled in exactly the same way as the
416 first, is when the two inputs into the PSC Control logic describe
417 different events. There are a number of variations on this case.
418 One example is when there is a Lockout of Protection from the Local
419 request logic and a Signal Fail on the Working path from the Remote
420 PSC Request. This is shortened to [L(LO), R(SF-W)].
421
422 In both cases, the question is not how the PSC Control logic decides
423 which of these is the one it acts upon. <a href="./rfc6378#section-4.3.2">Section&nbsp;4.3.2 of RFC 6378</a>
424 lists the priority order and prioritizes the local input over the
425 remote input in case both inputs are of the same priority. So, in
426 the first example it is the local SF that drives the PSC Control
427 logic, and in the second example it is the local Lockout that drives
428 the PSC Control logic.
429
430 The point that this section clears up is around what happens when the
431 highest-priority input goes away. Consider the first case.
432 Initially, the PSC Control logic has [L(FS), R(FS)], and L(FS) is
433 driving PSC's behavior. When L(FS) is removed, but R(FS) remains,
434 what does PSC do? A strict reading of the Finite State Machine (FSM)
435 would suggest that PSC transition from PA:F:L into N, and at some
436 future time (perhaps after the remote request refreshes), PSC would
437 transition from N to PA:F:R. This is an unreasonable behavior, as
438 there is no sensible justification for a node behaving as if things
439 were normal (i.e., N state) when it is clear that they are not.
440
441
442
443
444 <span class="grey">Osborne Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
447
448
449 The second case is similar. If a node starts with [L(LO), R(SF-W)]
450 and the local lockout is removed, a strict reading of the state
451 machine would suggest that the node transition from UA:LO:L to N, and
452 then at some future time presumably notice the R(SF-W) and transition
453 from N to PF:W:R. As with the first case, this is clearly not a
454 useful behavior.
455
456 In both cases, the request that was driving PSC's behavior was
457 removed. What should happen is that the PSC Control logic should,
458 upon removal of an input, immediately reevaluate all other inputs to
459 decide on the next course of action. This requires an implementation
460 to store the most recent local and remote inputs regardless of their
461 eventual use as triggers for the PSC Control Logic.
462
463 There is also a third case. Consider a node with [L(FS), R(LO)]. At
464 some point in time, the remote node replaces its Lockout request with
465 a Signal Fail on Working, so that the inputs into the PSC Control
466 logic on the receiving node go to [L(FS), R(SF-W)]. Similar to the
467 first two cases, the node should immediately reevaluate both its
468 local and remote inputs to determine the highest priority among them
469 and act on that input accordingly. That is in fact what happens, as
470 defined in <a href="./rfc6378#section-4.3.3">Section&nbsp;4.3.3 of RFC 6378</a>:
471
472 When a LER is in a remote state, i.e., state transition in
473 reaction to a PSC message received from the far-end LER, and
474 receives a new PSC message from the far-end LER that indicates a
475 contradictory state, e.g., in remote Unavailable state receiving a
476 remote FS(1,1) message, then the PSC Control logic SHALL
477 reevaluate all inputs (both the local input and the remote
478 message) as if the LER is in the Normal state.
479
480 This section extends that paragraph to handle the first two cases.
481 The essence of the quoted paragraph is that when faced with multiple
482 inputs, PSC must reevaluate any changes as if it were in Normal
483 state. So, the quoted paragraph is replaced with the following text:
484
485 The PSC Control logic may simultaneously have Local and Remote
486 requests, and the highest priority of these requests ultimately
487 drives the behavior of the PSC Control logic. When this highest-
488 priority request is removed or is replaced with another input,
489 then the PSC Control logic SHALL immediately reevaluate all inputs
490 (both the local input and the remote message), transitioning into
491 a new state only upon reevaluation of all inputs.
492
493
494
495
496
497
498
499
500 <span class="grey">Osborne Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
503
504
505 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
506
507 These changes and clarifications raise no new security concerns. <a href="./rfc6941">RFC</a>
508 <a href="./rfc6941">6941</a> [<a href="./rfc6941" title="&quot;MPLS Transport Profile (MPLS-TP) Security Framework&quot;">RFC6941</a>] provides the baseline security discussion for MPLS-TP,
509 and PSC (as described in both <a href="./rfc6378">RFC 6378</a> and this document) falls under
510 that umbrella. Additionally, <a href="#section-2.2">Section 2.2</a> clarifies how to react to
511 malformed or unexpected messages.
512
513 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
514
515 IANA has marked the value 0 in the "MPLS PSC TLV Registry" as
516 "Reserved, not to be allocated" and updated the references to show
517 [<a href="./rfc6378" title="&quot;MPLS Transport Profile (MPLS-TP) Linear Protection&quot;">RFC6378</a>] and this document (<a href="./rfc7324">RFC 7324</a>). Note that this document
518 provides documentation of an action already taken by IANA but not
519 recorded in <a href="./rfc6378">RFC 6378</a>.
520
521 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
522
523 The author of this document thanks Taesik Cheung, Alessandro
524 D'Alessandro, Annamaria Fulignoli, Sagar Soni, George Swallow, and
525 Yaacov Weingarten for their contributions and review, and Adrian
526 Farrel for the text of <a href="#section-2">Section 2</a>.
527
528 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
529
530 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
531
532 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
533 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
534
535 [<a id="ref-RFC6378">RFC6378</a>] Weingarten, Y., Bryant, S., Osborne, E., Sprecher, N., and
536 A. Fulignoli, "MPLS Transport Profile (MPLS-TP) Linear
537 Protection", <a href="./rfc6378">RFC 6378</a>, October 2011.
538
539 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
540
541 [<a id="ref-LIAISON">LIAISON</a>] ITU-T SG15, "Liaison Statement: Recommendation ITU-T
542 G.8131/Y.1382 revision - Linear protection switching for
543 MPLS-TP networks", &lt;<a href="https://datatracker.ietf.org/liaison/1205/">https://datatracker.ietf.org/</a>
544 <a href="https://datatracker.ietf.org/liaison/1205/">liaison/1205/</a>&gt;.
545
546 [<a id="ref-RFC6941">RFC6941</a>] Fang, L., Niven-Jenkins, B., Mansfield, S., and R.
547 Graveman, "MPLS Transport Profile (MPLS-TP) Security
548 Framework", <a href="./rfc6941">RFC 6941</a>, April 2013.
549
550
551
552
553
554
555
556 <span class="grey">Osborne Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc7324">RFC 7324</a> PSC Updates July 2014</span>
559
560
561 [<a id="ref-RFC7271">RFC7271</a>] Ryoo, J., Gray, E., van Helvoort, H., D'Alessandro, A.,
562 Cheung, T., and E. Osborne, "MPLS Transport Profile (MPLS-
563 TP) Linear Protection to Match the Operational
564 Expectations of Synchronous Digital Hierarchy, Optical
565 Transport Network, and Ethernet Transport Network
566 Operators", <a href="./rfc7271">RFC 7271</a>, June 2014.
567
568 Author's Address
569
570 Eric Osborne
571
572 EMail: [email protected]
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 Osborne Standards Track [Page 11]
613 </pre>