idnits 2.17.1 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-16.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 28 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 24, 2015) is 3373 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group E. Bellagamba 3 Internet-Draft A. Takacs 4 Intended status: Standards Track G. Mirsky 5 Expires: July 28, 2015 Ericsson 6 L. Andersson 7 Huawei Technologies 8 P. Skoldstrom 9 Acreo AB 10 D. Ward 11 Cisco 12 January 24, 2015 14 Configuration of Pro-Active Operations, Administration, and Maintenance 15 (OAM) Functions for MPLS-based Transport Networks using RSVP-TE 16 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-16 18 Abstract 20 This specification describes the configuration of proactive MPLS-TP 21 (MPLS-Transport Profile) Operations, Administration, and Maintenance 22 (OAM) Functions for a given LSP using a set of TLVs that are carried 23 by the GMPLS RSVP-TE protocol based on the OAM Configuration 24 Framework for GMPLS RSVP-TE. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on July 28, 2015. 43 Copyright Notice 45 Copyright (c) 2015 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. Conventions used in this document . . . . . . . . . . . . 4 62 1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 4 63 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 5 64 2. Overview of MPLS OAM for Transport Applications . . . . . . . 5 65 3. Theory of Operations . . . . . . . . . . . . . . . . . . . . 5 66 3.1. MPLS-TP OAM Configuration Operation Overview . . . . . . 5 67 3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 6 68 3.1.2. Configuration of Performance Monitoring . . . . . . . 7 69 3.1.3. Configuration of Fault Management Signals . . . . . . 7 70 3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 8 71 3.2.1. CV Flag Rules of Use . . . . . . . . . . . . . . . . 10 72 3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 10 73 3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 12 74 3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 13 75 3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 14 76 3.3.4. Traffic Class sub-TLV . . . . . . . . . . . . . . . . 15 77 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 16 78 3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 17 79 3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 19 80 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 20 81 4. Summary of MPLS OAM configuration errors . . . . . . . . . . 21 82 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 83 5.1. MPLS OAM Type . . . . . . . . . . . . . . . . . . . . . . 22 84 5.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 23 85 5.3. MPLS OAM Configuration Sub-TLV Types . . . . . . . . . . 23 86 5.4. BFD Configuration Sub-TLV Types . . . . . . . . . . . . . 24 87 5.5. Performance Monitoring sub-TLV Types . . . . . . . . . . 24 88 5.6. New RSVP-TE error codes . . . . . . . . . . . . . . . . . 25 89 6. Contributing Authors . . . . . . . . . . . . . . . . . . . . 25 90 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 91 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26 92 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 93 9.1. Normative References . . . . . . . . . . . . . . . . . . 26 94 9.2. Informative References . . . . . . . . . . . . . . . . . 27 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 97 1. Introduction 99 This document describes the configuration of proactive MPLS-TP (MPLS- 100 Transport Profile) Operations, Administration, and Maintenance (OAM) 101 Functions for a given LSP using TLVs using GMPLS RSVP-TE [RFC3473]. 102 [RFC7260] defines use of GMPLS RSVP-TE for the configuration of OAM 103 functions in a technology agnostic way. This document specifies the 104 additional mechanisms necessary to establish MPLS-TP OAM entities at 105 the maintenance points for monitoring and performing measurements on 106 an LSP, as well as defining information elements and procedures to 107 configure proactive MPLS-TP OAM functions running between LERs. 108 Initialization and control of on-demand MPLS-TP OAM functions are 109 expected to be carried out by directly accessing network nodes via a 110 management interface; hence configuration and control of on-demand 111 OAM functions are out-of-scope for this document. 113 MPLS-TP, the Transport Profile of MPLS, must, by definition 114 [RFC5654], be capable of operating without a control plane. 115 Therefore, there are several options for configuring MPLS-TP OAM, 116 without a control plane by either using an NMS or LSP Ping, or with a 117 control plane using signaling protocols such as RSVP-TE. 119 MPLS-TP describes a profile of MPLS that enables operational models 120 typical in transport networks, while providing additional OAM, 121 survivability and other maintenance functions not currently supported 122 by MPLS. [RFC5860] defines the requirements for the OAM 123 functionality of MPLS-TP. 125 Proactive MPLS-TP OAM is performed by three different protocols, Bi- 126 directional Forwarding Detection (BFD) [RFC6428] for Continuity 127 Check/Connectivity Verification, the delay measurement protocol (DM) 128 [RFC6374] for delay and delay variation (jitter) measurements, and 129 the loss measurement protocol (LM) [RFC6374] for packet loss and 130 throughput measurements. Additionally, there is a number of Fault 131 Management Signals that can be configured [RFC6427]. 133 BFD is a protocol that provides low-overhead, fast detection of 134 failures in the path between two forwarding engines, including the 135 interfaces, data link(s), and to the extent possible the forwarding 136 engines themselves. BFD can be used to track the liveliness and 137 detect data plane failures of MPLS-TP point-to-point and might also 138 be extended to support point-to-multipoint connections. 140 The delay and loss measurements protocols [RFC6374] use a simple 141 query/response model for performing bidirectional measurements that 142 allows the originating node to measure packet loss and delay in both 143 directions. By timestamping and/or writing current packet counters 144 to the measurement packets at four times (Tx and Rx in both 145 directions) current delays and packet losses can be calculated. By 146 performing successive delay measurements the delay variation (jitter) 147 can be calculated. Current throughput can be calculated from the 148 packet loss measurements by dividing the number of packets sent/ 149 received with the time it took to perform the measurement, given by 150 the timestamp in LM header. Combined with a packet generator the 151 throughput measurement can be used to measure the maximum capacity of 152 a particular LSP. It should be noted that here we are not 153 configuring on-demand throughput estimates based on saturating the 154 connection as defined in [RFC6371]. Rather, we only enable the 155 estimation of the current throughput based on loss measurements. 157 1.1. Conventions used in this document 159 1.1.1. Terminology 161 BFD - Bidirectional Forwarding Detection 163 CV - Connectivity Verification 165 CC - Continuity Check 167 DM - Delay Measurement 169 FMS - Fault Management Signal 171 G-ACh - Generic Associated Channel 173 GMPLS - Generalized Multi-Protocol Label Switching 175 LER - Label switching Edge Router 177 LM - Loss Measurement 179 LSP - Label Switched Path 181 LSR - Label Switching Router 183 MEP - Maintenance Entity Group End Point 185 MPLS - Multi-Protocol Label Switching 187 MPLS-TP - MPLS Transport Profile 189 NMS - Network Management System 191 PM - Performance Measurement 192 RSVP-TE - Reservation Protocol Traffic Engineering 194 TC - Traffic Class 196 1.1.2. Requirements Language 198 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 199 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 200 document are to be interpreted as described in RFC 2119 [RFC2119]. 202 2. Overview of MPLS OAM for Transport Applications 204 [RFC6371] describes how MPLS-TP OAM mechanisms are operated to meet 205 transport requirements outlined in [RFC5860]. 207 [RFC6428] specifies two BFD operation modes: 1) "CC mode", which uses 208 periodic BFD message exchanges with symmetric timer settings, 209 supporting Continuity Check, 2) "CV/CC mode" which sends unique 210 maintenance entity identifiers in the periodic BFD messages 211 supporting Connectivity Verification (CV) as well as Continuity Check 212 (CC). 214 [RFC6374] specifies mechanisms for performance monitoring of LSPs, in 215 particular it specifies loss and delay measurement OAM functions. 217 [RFC6427] specifies fault management signals with which a server LSP 218 can notify client LSPs about various fault conditions to suppress 219 alarms or to be used as triggers for actions in the client LSPs. The 220 following signals are defined: Alarm Indication Signal (AIS), Link 221 Down Indication (LDI) and Lock Report (LKR). 223 [RFC6371] describes the mapping of fault conditions to consequent 224 actions. Some of these mappings may be configured by the operator, 225 depending on the application of the LSP. The following defects are 226 identified: Loss Of Continuity (LOC), Misconnectivity, MEP 227 Misconfiguration and Period Misconfiguration. Out of these defect 228 conditions, the following consequent actions may be configurable: 1) 229 whether or not the LOC defect should result in blocking the outgoing 230 data traffic; 2) whether or not the "Period Misconfiguration defect" 231 should result in a signal fail condition. 233 3. Theory of Operations 235 3.1. MPLS-TP OAM Configuration Operation Overview 237 GMPLS RSVP-TE, or alternatively LSP Ping [LSP-PING-CONF], can be used 238 to simply enable the different OAM functions, by setting the 239 corresponding flags in the "OAM Function Flags sub-TLV" [RFC7260]. 241 For a more detailed configuration one may include sub-TLVs for the 242 different OAM functions in order to specify various parameters in 243 detail. 245 Typically intermediate nodes SHOULD NOT process or modify any of the 246 OAM configuration TLVs but simply forward them to the end-node. 247 There is one exception to this and that is if the "MPLS OAM FMS sub- 248 TLV" is present. This sub-TLV MUST be examined even by intermediate 249 nodes that support these extensions, but only acted upon by nodes 250 capable of transmitting FMS signals into the LSP being established. 251 The sub-TLV MAY be present when the FMS flag is set in the "OAM 252 Function Flags sub-TLV". If this sub-TLV is present, then the "OAM 253 MIP entities desired" and "OAM MEP entities desired" flags (described 254 in [RFC7260]) in the "LSP Attributes Flags TLV" MUST be set and the 255 entire OAM Configuration TLV placed either in the 256 LSP_REQUIRED_ATTRIBUTES object or in the LSP_ATTRIBUTES object in 257 order to ensure that capable intermediate nodes process the 258 configuration. If placed in LSP_ATTRIBUTES object, nodes that are 259 not able to process the OAM Configuration TLV will forward the 260 message without generating an error. If the "MPLS OAM FMS sub-TLV" 261 been placed in the LSP_REQUIRED_ATTRIBUTES object a node that 262 supports the RFC 7260 but does not support the "MPLS OAM FMS sub-TLV" 263 MUST generate PathErr message with "OAM Problem/Configuration Error" 264 [RFC7260]. Otherwise, if the node doesn't support the RFC 7260, it 265 will not raise any errors as described in the Section 4.1 [RFC7260]. 267 Finally, if the "MPLS OAM FMS sub-TLV" is not included only the "OAM 268 MEP entities desired" flag is set and the OAM Configuration TLV may 269 be placed in either LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES. 271 3.1.1. Configuration of BFD sessions 273 For this specification, BFD MUST be run in either one of the two 274 modes: 276 - Asynchronous mode, where both sides should be in active mode 278 - Unidirectional mode 280 In the simplest scenario, RSVP-TE, or alternatively LSP Ping [LSP- 281 PING-CONF], is used only to bootstrap a BFD session for an LSP, 282 without any timer negotiation. 284 Timer negotiation can be performed either in subsequent BFD control 285 messages (in this case the operation is similar to LSP Ping based 286 bootstrapping described in [RFC5884]) or directly in the RSVP-TE 287 signaling messages. 289 When BFD Control packets are transported in the G-ACh they are not 290 protected by any end-to-end checksum, only lower-layers are providing 291 error detection/correction. A single bit error, e.g. a flipped bit 292 in the BFD State field could cause the receiving end to wrongly 293 conclude that the link is down and in turn trigger protection 294 switching. To prevent this from happening the "BFD Configuration 295 sub-TLV" has an Integrity flag that when set enables BFD 296 Authentication using Keyed SHA1 with an empty key (all 0s) [RFC5880]. 297 This would ensure that every BFD Control packet carries an SHA1 hash 298 of itself that can be used to detect errors. 300 If BFD Authentication using a pre-shared key / password is desired 301 (i.e. authentication and not only error detection), the "BFD 302 Authentication sub-TLV" MUST be included in the "BFD Configuration 303 sub-TLV". The "BFD Authentication sub-TLV" is used to specify which 304 authentication method should be used and which pre-shared key / 305 password should be used for this particular session. How the key 306 exchange is performed is out of scope of this document. 308 3.1.2. Configuration of Performance Monitoring 310 It is possible to configure Performance Monitoring functionalities 311 such as Loss, Delay, Delay variation (jitter), and Throughput as 312 described in [RFC6374]. 314 When configuring Performance monitoring functionalities it is 315 possible to choose either the default configuration, by only setting 316 the respective flags in the "OAM Function Flags sub-TLV", or a 317 customized configuration. To customize the configuration, one would 318 set the respective flags and including the respective Loss and/or 319 Delay sub-TLVs). 321 By setting the PM/Loss flag in the "OAM Function Flags sub-TLV" and 322 by including the "MPLS OAM PM Loss sub-TLV", one can configure the 323 measurement interval and loss threshold values for triggering 324 protection. 326 Delay measurements are configured by setting PM/Delay flag in the 327 "OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss 328 sub-TLV", one can configure the measurement interval and the delay 329 threshold values for triggering protection. 331 3.1.3. Configuration of Fault Management Signals 333 To configure Fault Management Signals and their refresh time, the FMS 334 flag in the "OAM Function Flags sub-TLV" MUST be set and the "MPLS 335 OAM FMS sub-TLV" included. When configuring Fault Management 336 Signals, an implementation can enable the default configuration by 337 setting the FMS flag in the "OAM Function Flags sub-TLV". In order 338 to modify the default configuration the "MPLS OAM FMS sub-TLV" MUST 339 be included. 341 If an intermediate point is intended to originate fault management 342 signal messages, this means that such an intermediate point is 343 associated with a server MEP through a co-located MPLS-TP client/ 344 server adaptation function and the "Fault Management subscription" 345 flag in the "MPLS OAM FMS sub-TLV" been set as indication of the 346 request to create the association at each intermediate node of the 347 client LSP. Corresponding server MEP needs to be configured by its 348 own RSVP-TE session (or, alternatively, via an NMS or LSP-ping). 350 3.2. MPLS OAM Configuration sub-TLV 352 The "OAM Configuration TLV", defined in [RFC7260], specifies the OAM 353 functions that are used for the LSP. This document extends the "OAM 354 Configuration TLV" by defining a new OAM Type: "MPLS OAM" (TBA1). 355 The "MPLS OAM" type is set to request the establishment of OAM 356 functions for MPLS-TP LSPs. The specific OAM functions are specified 357 in the "OAM Function Flags sub-TLV" as depicted in [RFC7260]. 359 When an egress LSR receives an "OAM Configuration TLV" indicating the 360 MPLS OAM type, the LSR will first process any present "OAM Function 361 Flags sub-TLV" and then it MUST process technology specific 362 configuration TLVs. This document defines a sub-TLV, the "MPLS OAM 363 Configuration sub-TLV" which is carried in the "OAM Configuration 364 TLV". 366 0 1 2 3 367 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 368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 369 | MPLS OAM Conf. sub-TLV (TBA2) | Length | 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 | | 372 ~ sub-TLVs ~ 373 | | 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 Type: TBA2, the "MPLS OAM Configuration sub-TLV". 378 Length: indicates the total length in octets, including sub-TLVs as 379 well as the Type and Length fields. 381 The following MPLS OAM specific sub-TLVs MAY be included in the "MPLS 382 OAM Configuration sub-TLV": 384 - "BFD Configuration sub-TLV", which MUST be included if either 385 the CC, the CV or both OAM Function flags being set in the OAM 386 Function Flags Sub-TLV [RFC7260]. This sub-TLV carries additional 387 sub-TLVs, failure to include the correct sub-TLVs MUST result in 388 an error being generated: "OAM Problem/Configuration Error". The 389 sub-TLVs are: 391 - "BFD Identifiers sub-TLV", MUST always be included. 393 - "Timer Negotiation Parameters sub-TLV", MUST be included if 394 the N flag is not set. 396 - "BFD Authentication sub-TLV", MAY be included if the I flag 397 is set. 399 - "Performance Monitoring sub-TLV", which MUST be included if any 400 of the PM/Delay, PM/Loss or PM/Throughput flags are set in the 401 "OAM Function Flag sub-TLV" [RFC7260]. This sub-TLV MAY carry 402 additional sub-TLVs: 404 - "MPLS OAM PM Loss sub-TLV" MAY be included if the PM/Loss OAM 405 Function flag is set. If the "MPLS OAM PM Loss sub-TLV" is not 406 included, default configuration values are used. The same sub- 407 TLV MAY also be included in case the PM/Throughput OAM Function 408 flag is set and there is the need to specify measurement 409 interval different from the default ones. Since throughput 410 measurements use the same tool as loss measurements the same 411 TLV is used. 413 - "MPLS OAM PM Delay sub-TLV" MAY be included if the PM/Delay 414 OAM Function flag is set. If the "MPLS OAM PM Delay sub-TLV" 415 is not included, default configuration values are used. 417 - "MPLS OAM FMS sub-TLV" MAY be included if the FMS OAM Function 418 flag is set. If the "MPLS OAM FMS sub-TLV" is not included, 419 default configuration values are used. 421 Following are some additional rules of processing MPLS OAM 422 Configuration sub-TLV: 424 - MPLS OAM Configuration sub-TLV MAY be empty, i.e. have no Value. 425 Then its Length MUST be 8. Then all OAM functions that have their 426 corresponding flags set in the "OAM Function Flags sub-TLV" MUST 427 be assigned their default values or left disabled. 429 - Sub-TLV that doesn't have corresponding flag set MUST be 430 silently ignored. 432 - If multiple copies of a sub-TLV are present, then only the first 433 sub-TLV MUST be used and the remaining sub-TLVs MUST be silently 434 ignored. 436 However, not all the values can be derived from the standard RSVP-TE 437 objects, in particular the locally assigned Tunnel ID at the egress 438 cannot be derived by the ingress node. Therefore, the full LSP MEP- 439 ID used by the ingress has to be carried in the "BFD Identifiers sub- 440 TLV" in the Path message and the egress LSP MEP-ID in the same way in 441 the Resv message. 443 3.2.1. CV Flag Rules of Use 445 If the CV flag is set in the OAM Function Flags Sub-TLV [RFC7260], 446 then the CC flag MUST be set as well because performing Connectivity 447 Verification implies performing Continuity Check as well. The format 448 of an MPLS-TP CV/CC message is shown in [RFC6428]. In order to 449 perform Connectivity Verification the CV/CC message MUST contain the 450 "LSP MEP-ID" in addition to the BFD Control packet information. The 451 "LSP MEP-ID" contains four identifiers: 453 MPLS-TP Global_ID 455 MPLS-TP Node Identifier 457 Tunnel_Num 459 LSP_Num 461 These values need to be correctly set by both ingress and egress when 462 transmitting a CV packet and both ingress and egress needs to know 463 what to expect when receiving a CV packet. Most of these values can 464 be derived from the Path and Resv messages [RFC3473], which uses a 465 5-tuple to uniquely identify an LSP within an operator's network. 466 This tuple is composed of a Tunnel Sender Address, Tunnel Endpoint 467 Address, Tunnel_ID, Extended Tunnel ID, and (GMPLS) LSP_ID. 469 3.3. BFD Configuration sub-TLV 471 The "BFD Configuration sub-TLV" (depicted below) is defined for BFD 472 OAM specific configuration parameters. The "BFD Configuration sub- 473 TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-TLV". 475 This TLV accommodates generic BFD OAM information and carries sub- 476 TLVs. 478 0 1 2 3 479 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 480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 481 | BFD Conf. Type (1) | Length | 482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 483 |Vers.|N|S|I|G|U|B| Reserved (set to all 0s) | 484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 485 | | 486 ~ sub-TLVs ~ 487 | | 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 490 Type: 1, the "BFD Configuration sub-TLV". 492 Length: indicates the total length in octets, including sub-TLVs as 493 well as the Type and Length fields. 495 Version: identifies the BFD protocol version. If the egress LSR does 496 not support the version an error MUST be generated: "OAM Problem/ 497 Unsupported BFD Version". 499 BFD Negotiation (N): If set timer negotiation/re-negotiation via BFD 500 Control Messages is enabled, when cleared it is disabled. 502 Symmetric session (S): If set the BFD session MUST use symmetric 503 timing values. 505 Integrity (I): If set BFD Authentication MUST be enabled. If the 506 "BFD Configuration sub-TLV" does not include a "BFD Authentication 507 sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre- 508 shared key (all 0s). If the egress LSR does not support BFD 509 Authentication an error MUST be generated: "OAM Problem/BFD 510 Authentication unsupported". 512 Encapsulation Capability (G): if set, shows the capability of 513 encapsulating BFD messages into The G-Ach channel. If both the G bit 514 and U bit are set, configuration gives precedence to the G bit. If 515 the egress LSR does not support any of the ingress LSR Encapsulation 516 Capabilities an error MUST be generated: "OAM Problem/Unsupported BFD 517 Encapsulation format". 519 Encapsulation Capability (U): if set, shows the capability of 520 encapsulating BFD messages into UDP packets. If both the G bit and U 521 bit are set, configuration gives precedence to the G bit. If the 522 egress LSR does not support any of the ingress LSR Encapsulation 523 Capabilities an error MUST be generated: "OAM Problem/Unsupported BFD 524 Encapsulation format". 526 Bidirectional (B): if set, it configures BFD in the Bidirectional 527 mode. If it is not set it configures BFD in unidirectional mode. In 528 the second case, the source node does not expect any Discriminator 529 values back from the destination node. 531 Reserved: Reserved for future specification and set to 0 on 532 transmission and ignored when received. 534 The "BFD Configuration sub-TLV" MUST include the following sub-TLVs 535 in the Path message: 537 - "BFD Identifiers sub-TLV"; 539 - "Negotiation Timer Parameters sub-TLV" if the N flag is cleared. 541 The "BFD Configuration sub-TLV" MUST include the following sub-TLVs 542 in the Resv message: 544 - "BFD Identifiers sub-TLV;" 546 - "Negotiation Timer Parameters sub-TLV" if: 548 - the N and S flags are cleared, or if: 550 - the N flag is cleared and the S flag is set, and the 551 "Negotiation Timer Parameters sub-TLV" received by the egress 552 contains unsupported values. In this case an updated 553 "Negotiation Timer Parameters sub-TLV", containing values 554 supported by the egress LSR, MUST be returned to the ingress. 556 3.3.1. BFD Identifiers sub-TLV 558 The "BFD Identifiers sub-TLV" is carried as a sub-TLV of the "BFD 559 Configuration sub-TLV" and is depicted below. 561 0 1 2 3 562 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 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 564 | BFD Identfiers Type (1) | Length | 565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 566 | Local Discriminator | 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 | MPLS-TP Global_ID | 569 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 570 | MPLS-TP Node Identifier | 571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 | Tunnel_Num | LSP_Num | 573 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 575 Type: 1, "BFD Identifiers sub-TLV". 577 Length: indicates the TLV total length in octets, including the Type 578 and Length fields (20). 580 Local Discriminator: A unique, nonzero discriminator value generated 581 by the transmitting system and referring to itself, used to 582 demultiplex multiple BFD sessions between the same pair of systems as 583 defined in [RFC5880]. 585 MPLS-TP Global_ID, Node Identifier, Tunnel_Num, and LSP_Num: all set 586 as defined in [RFC6370]. 588 3.3.2. Negotiation Timer Parameters sub-TLV 590 The "Negotiation Timer Parameters sub-TLV" is carried as a sub-TLV of 591 the "BFD Configuration sub-TLV" and is depicted below. 593 0 1 2 3 594 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 595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 596 | Nego. Timer Type (2) | Length | 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 | Acceptable Min. Asynchronous TX interval | 599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 600 | Acceptable Min. Asynchronous RX interval | 601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 602 | Required Echo TX Interval | 603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 605 Type: 2, "Negotiation Timer Parameters sub-TLV". 607 Length: indicates the TLV total length in octets, including Type and 608 Length fields (16). 610 Acceptable Min. Asynchronous TX interval: If the S (symmetric) flag 611 is set in the "BFD Configuration sub-TLV", it expresses the desired 612 time interval (in microseconds) at which the ingress LER intends to 613 both transmit and receive BFD periodic control packets. If the 614 egress LSR cannot support the value, it SHOULD reply with a supported 615 interval. 617 If the S (symmetric) flag is cleared in the "BFD Configuration sub- 618 TLV", this field expresses the desired time interval (in 619 microseconds) at which the ingress LSR intends to transmit BFD 620 periodic control packets. 622 Acceptable Min. Asynchronous RX interval: If the S (symmetric) flag 623 is set in the "BFD Configuration sub-TLV", this field MUST be set 624 equal to "Acceptable Min. Asynchronous TX interval" on transmit and 625 MUST be ignored on receipt since it has no additional meaning with 626 respect to the one described for "Acceptable Min. Asynchronous TX 627 interval". 629 If the S (symmetric) flag is cleared in the "BFD Configuration sub- 630 TLV", it expresses the minimum time interval (in microseconds) at 631 which the ingress/egress LSRs can receive periodic BFD control 632 packets. If this value is greater than the "Acceptable Min. 633 Asynchronous TX interval" received from the ingress/egress LSR, the 634 receiving LSR MUST adopt the interval expressed in the "Acceptable 635 Min. Asynchronous RX interval". 637 Required Echo TX Interval: the minimum interval (in microseconds) 638 between received BFD Echo packets that this system is capable of 639 supporting, less any jitter applied by the sender as described in 640 [RFC5880] sect. 6.8.9. This value is also an indication for the 641 receiving system of the minimum interval between transmitted BFD Echo 642 packets. If this value is zero, the transmitting system does not 643 support the receipt of BFD Echo packets. If the LSR node cannot 644 support this value it SHOULD reply with a supported value (which may 645 be zero if Echo is not supported). 647 3.3.3. BFD Authentication sub-TLV 649 The "BFD Authentication sub-TLV" is carried as a sub-TLV of the "BFD 650 Configuration sub-TLV" and is depicted below. 652 0 1 2 3 653 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 654 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 655 | BFD Auth. Type (3) | Length | 656 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 657 | Auth Type | Auth Key ID | Reserved (0s) | 658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 660 Type: 3, "BFD Authentication sub-TLV". 662 Length: indicates the TLV total length in octets, including Type and 663 Length fields (8). 665 Auth Type: indicates which type of authentication to use. The same 666 values as are defined in section 4.1 of [RFC5880] are used. If the 667 egress LSR does not support this type an "OAM Problem/Unsupported BFD 668 Authentication Type" error MUST be generated. 670 Auth Key ID: indicates which authentication key or password 671 (depending on Auth Type) should be used. How the key exchange is 672 performed is out of scope of this document. If the egress LSR does 673 not support this Auth Key ID an "OAM Problem/Mismatch of BFD 674 Authentication Key ID" error MUST be generated. 676 Reserved: Reserved for future specification and set to 0 on 677 transmission and ignored when received. 679 3.3.4. Traffic Class sub-TLV 681 The Traffic Class sub-TLV is carried as a sub-TLV of the "BFD 682 Configuration sub-TLV" or "Fault Management Signal sub-TLV" 683 Section 3.5 and is depicted in Figure 1. 685 0 1 2 3 686 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 687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 | Traffic Class sub-Type (4) | Length | 689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 690 | TC | Reserved (set to all 0s) | 691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 693 Figure 1: Traffic Class sub-TLV format 695 Type: 3, "Traffic Class sub-TLV". 697 Length: indicates the length of the Value field in octets . (4) 698 TC: Identifies the Traffic Class (TC) [RFC5462] for periodic 699 continuity monitoring messages or packets with fault management 700 information. 702 If TC sub-TLV is present, then the value of the TC field MUST be used 703 as the value of the TC field of an MPLS label stack entry. If the TC 704 sub-TLV is absent from "BFD Configuration sub-TLV" or "Fault 705 Management Signal sub-TLV", then selection of the TC value is local 706 decision. 708 3.4. Performance Monitoring sub-TLV 710 If the "OAM Function Flags sub-TLV" has either the PM/Loss, PM/Delay 711 or PM/Throughput flag set, the "Performance Monitoring sub-TLV" MUST 712 be present in the "MPLS OAM Configuration sub-TLV". Failure to 713 include the correct sub-TLVs MUST result in an "OAM Problem/ 714 Configuration Error" error being generated. 716 The "Performance Monitoring sub-TLV" provides the configuration 717 information mentioned in Section 7 of [RFC6374]. It includes support 718 for the configuration of quality thresholds and, as described in 719 [RFC6374], "the crossing of which will trigger warnings or alarms, 720 and result reporting and exception notification will be integrated 721 into the system-wide network management and reporting framework." 723 In case the values need to be different than the default ones the 724 "Performance Monitoring sub-TLV" includes the following sub-TLVs: 726 - "MPLS OAM PM Loss sub-TLV" if the PM/Loss and/or PM/Throughput 727 flag is set in the "OAM Function Flags sub-TLV"; 729 - "MPLS OAM PM Delay sub-TLV" if the PM/Delay flag is set in the 730 "OAM Function Flags sub-TLV"; 732 The "Performance Monitoring sub-TLV" depicted below is carried as a 733 sub-TLV of the "MPLS OAM Configuration sub-TLV". 735 0 1 2 3 736 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 737 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 738 | Perf. Monitoring Type(2) | Length | 739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 740 |D|L|J|Y|K|C| Reserved (set to all 0s) | 741 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 742 | | 743 ~ sub-TLVs ~ 744 | | 745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 746 Type: 2, "Performance Monitoring sub-TLV". 748 Length: indicates the TLV total length in octets, including sub-TLVs 749 as well as Type and Length fields. 751 Configuration Flags, for the specific function description please 752 refer to [RFC6374]: 754 - D: Delay inferred/direct (0=INFERRED, 1=DIRECT). If the egress 755 LSR does not support specified mode an "OAM Problem/Unsupported 756 Delay Mode" error MUST be generated. 758 - L: Loss inferred/direct (0=INFERRED, 1=DIRECT). If the egress 759 LSR does not support specified mode an "OAM Problem/Unsupported 760 Loss Mode" error MUST be generated. 762 - J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE). If the 763 egress LSR does not support Delay variation measurements and the J 764 flag is set, an "OAM Problem/Delay variation unsupported" error 765 MUST be generated. 767 - Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does not 768 support Dyadic mode and the Y flag is set, an "OAM Problem/Dyadic 769 mode unsupported" error MUST be generated. 771 - K: Loopback (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does 772 not support Loopback mode and the K flag is set, an "OAM Problem/ 773 Loopback mode unsupported" error MUST be generated. 775 - C: Combined (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does 776 not support Combined mode and the C flag is set, an "OAM Problem/ 777 Combined mode unsupported" error MUST be generated. 779 Reserved: Reserved for future specification and set to 0 on 780 transmission and ignored when received. 782 3.4.1. MPLS OAM PM Loss sub-TLV 784 The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a sub-TLV 785 of the "Performance Monitoring sub-TLV". 787 0 1 2 3 788 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 789 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 790 | PM Loss Type (1) | Length | 791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 792 | OTF |T|B| Reserved (set to all 0s) | 793 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 794 | Measurement Interval | 795 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 796 | Test Interval | 797 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 798 | Loss Threshold | 799 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 801 Type: 1,"MPLS OAM PM Loss sub-TLV". 803 Length: indicates the length of the parameters in octets, including 804 Type and Length fields (20). 806 OTF: Origin Timestamp Format of the Origin Timestamp field described 807 in [RFC6374]. By default it is set to IEEE 1588 version 1. If the 808 egress LSR cannot support this value an "OAM Problem/Unsupported 809 Timestamp Format" error MUST be generated. 811 Configuration Flags, please refer to [RFC6374] for further details: 813 - T: Traffic-class-specific measurement indicator. Set to 1 when 814 the measurement operation is scoped to packets of a particular 815 traffic class (DSCP value), and 0 otherwise. When set to 1, the 816 DS field of the message indicates the measured traffic class. By 817 default it is set to 1. 819 - B: Octet (byte) count. When set to 1, indicates that the 820 Counter 1-4 fields represent octet counts. When set to 0, 821 indicates that the Counter 1-4 fields represent packet counts. By 822 default it is set to 0. 824 Reserved: Reserved for future specification and set to 0 on 825 transmission and ignored when received. 827 Measurement Interval: the time interval (in milliseconds) at which 828 Loss Measurement query messages MUST be sent on both directions. If 829 the egress LSR cannot support the value, it SHOULD reply with a 830 supported interval. By default it is set to (100) as per [RFC6375]. 832 Test Interval: test messages interval in milliseconds as described in 833 [RFC6374]. By default it is set to (10) as per [RFC6375]. If the 834 egress LSR cannot support the value, it SHOULD reply with a supported 835 interval. 837 Loss Threshold: the threshold value of measured lost packets per 838 measurement over which action(s) SHOULD be triggered. 840 3.4.2. MPLS OAM PM Delay sub-TLV 842 The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a sub- 843 TLV of the "Performance Monitoring sub-TLV". 845 0 1 2 3 846 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 847 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 848 | PM Delay Type (2) | Length | 849 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 850 | OTF |T|B| Reserved (set to all 0s) | 851 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 852 | Measurement Interval | 853 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 854 | Test Interval | 855 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 856 | Delay Threshold | 857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 859 Type: 2,"MPLS OAM PM Delay sub-TLV". 861 Length: indicates the length of the parameters in octets, including 862 Type and Length fields (20). 864 OTF: Origin Timestamp Format of the Origin Timestamp field described 865 in [RFC6374]. By default it is set to IEEE 1588 version 1. If the 866 egress LSR cannot support this value an "OAM Problem/Unsupported 867 Timestamp Format" error MUST be generated. 869 Configuration Flags, please refer to [RFC6374] for further details: 871 - T: Traffic-class-specific measurement indicator. Set to 1 when 872 the measurement operation is scoped to packets of a particular 873 traffic class (DSCP value), and 0 otherwise. When set to 1, the 874 DS field of the message indicates the measured traffic class. By 875 default it is set to 1. 877 - B: Octet (byte) count. When set to 1, indicates that the 878 Counter 1-4 fields represent octet counts. When set to 0, 879 indicates that the Counter 1-4 fields represent packet counts. By 880 default it is set to 0. 882 Reserved: Reserved for future specification and set to 0 on 883 transmission and ignored when received. 885 Measurement Interval: the time interval (in milliseconds) at which 886 Delay Measurement query messages MUST be sent on both directions. If 887 the egress LSR cannot support the value, it SHOULD reply with a 888 supported interval. By default it is set to (1000) as per [RFC6375]. 890 Test Interval: test messages interval (in milliseconds) as described 891 in [RFC6374]. By default it is set to (10) as per [RFC6375]. If the 892 egress LSR cannot support the value, it SHOULD reply with a supported 893 interval. 895 Delay Threshold: the threshold value of measured two-way delay (in 896 milliseconds) over which action(s) SHOULD be triggered. 898 3.5. MPLS OAM FMS sub-TLV 900 The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of 901 the "MPLS OAM Configuration sub-TLV". When both working and 902 protection paths are signaled, both LSPs SHOULD be signaled with 903 identical settings of the E flag, T flag, and the refresh timer. 905 0 1 2 3 906 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 907 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 908 | MPLS OAM FMS Type (3) | Length | 909 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 910 |E|S|T| Reserved | Refresh Timer | 911 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 912 | | 913 ~ sub-TLVs ~ 914 | | 915 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 917 Type: 3, "MPLS OAM FMS sub-TLV". 919 Length: indicates the TLV total length in octets, including Type and 920 Length fields (8). 922 FMS Signal Flags are used to enable the FMS signals at end point MEPs 923 and the Server MEPs of the links over which the LSP is forwarded. In 924 this document only the S flag pertains to Server MEPs. 926 The following flags are defined: 928 - E: Enable Alarm Indication Signal (AIS) and Lock Report (LKR) 929 signaling as described in [RFC6427]. Default value is 1 930 (enabled). If the egress MEP does not support FMS signal 931 generation an "OAM Problem/Fault management signaling unsupported" 932 error MUST be generated. 934 - S: Indicate to a Server MEP that it should transmit AIS and LKR 935 signals on client LSPs. Default value is 0 (disabled). If a 936 Server MEP which is capable of generating FMS messages is for some 937 reason unable to do so for the LSP being signaled an "OAM Problem/ 938 Unable to create fault management association" error MUST be 939 generated. 941 - T: Set timer value, enabled the configuration of a specific 942 timer value. Default value is 0 (disabled). 944 - Remaining bits: Reserved for future specification and set to 0. 946 Refresh Timer: indicates the refresh timer of fault indication 947 messages, in seconds. The value MUST be between 1 to 20 seconds as 948 specified for the Refresh Timer field in [RFC6427]. If the egress 949 LSR cannot support the value it SHOULD reply with a supported timer 950 value. 952 FMS sub-TLV MAY include Traffic Class sub-TLV Section 3.3.4. If TC 953 sub-TLV is present, the value of the TC field MUST be used as the 954 value of the TC field of an MPLS label stack entry for FMS messages. 955 If the TC sub-TLV is absent, then selection of the TC value is local 956 decision. 958 4. Summary of MPLS OAM configuration errors 960 In addition to error values specified in [RFC7260] this document 961 defines the following values for the "OAM Problem" Error Code: 963 - If an egress LSR does not support the specified BFD version, an 964 error MUST be generated: "OAM Problem/Unsupported BFD Version". 966 - If an egress LSR does not support the specified BFD 967 Encapsulation format, an error MUST be generated: "OAM Problem/ 968 Unsupported BFD Encapsulation format". 970 - If an egress LSR does not support BFD Authentication, and it is 971 requested, an error MUST be generated: "OAM Problem/BFD 972 Authentication unsupported". 974 - If an egress LSR does not support the specified BFD 975 Authentication Type, an error MUST be generated: "OAM Problem/ 976 Unsupported BFD Authentication Type". 978 - If an egress LSR is not able to use the specified Authentication 979 Key ID, an error MUST be generated: "OAM Problem/Mismatch of BFD 980 Authentication Key ID". 982 - If an egress LSR does not support the specified Timestamp 983 Format, an error MUST be generated: "OAM Problem/Unsupported 984 Timestamp Format". 986 - If an egress LSR does not support specified Delay mode, an "OAM 987 Problem/Unsupported Delay Mode" error MUST be generated. 989 - If an egress LSR does not support specified Loss mode, an "OAM 990 Problem/Unsupported Loss Mode" error MUST be generated. 992 - If an egress LSR does not support Delay variation measurements, 993 and it is requested, an "OAM Problem/Delay variation unsupported" 994 error MUST be generated. 996 - If an egress LSR does not support Dyadic mode, and it is 997 requested, an "OAM Problem/Dyadic mode unsupported" error MUST be 998 generated. 1000 - If an egress LSR does not support Loopback mode, and it is 1001 requested, an "OAM Problem/Loopback mode unsupported" error MUST 1002 be generated. 1004 - If an egress LSR does not support Combined mode, and it is 1005 requested, an "OAM Problem/Combined mode unsupported" error MUST 1006 be generated. 1008 - If an egress LSR does not support Fault Monitoring Signals, and 1009 it is requested, an "OAM Problem/Fault management signaling 1010 unsupported" error MUST be generated. 1012 - If an intermediate server MEP supports Fault Monitoring Signals 1013 but is unable to create an association, when requested to do so, 1014 an "OAM Problem/Unable to create fault management association" 1015 error MUST be generated. 1017 5. IANA Considerations 1019 5.1. MPLS OAM Type 1021 This document specifies new the "MPLS OAM Type". IANA is requested 1022 to allocate a new type (TBA1) from the OAM Type space of the RSVP-TE 1023 OAM Configuration Registry. 1025 +------+-------------+---------------+ 1026 | Type | Description | Reference | 1027 +------+-------------+---------------+ 1028 | TBA1 | MPLS OAM | This document | 1029 +------+-------------+---------------+ 1031 Table 1: OAM MPLS Type 1033 5.2. MPLS OAM Configuration sub-TLV 1035 This document specifies the "MPLS OAM Configuration sub-TLV", IANA is 1036 requested to allocate a new type (TBA2) from the technology-specific 1037 sub-TLV space of the RSVP-TE OAM Configuration Registry. 1039 +------+--------------------------------+---------------+ 1040 | Type | Description | Reference | 1041 +------+--------------------------------+---------------+ 1042 | TBA2 | MPLS OAM Configuration sub-TLV | This document | 1043 +------+--------------------------------+---------------+ 1045 Table 2: MPLS OAM Configuration sub-TLV Type 1047 5.3. MPLS OAM Configuration Sub-TLV Types 1049 IANA is requested to create an "MPLS OAM sub-TLV Types" sub-registry 1050 in the "RSVP-TE OAM Configuration Registry" for the sub-TLVs carried 1051 in the "MPLS OAM Configuration sub-TLV". Values from this new sub- 1052 registry to be allocated through IETF Review except for the Reserved 1053 for Experimental Use range. This document defines the following 1054 types: 1056 +-------------+--------------------------------+---------------+ 1057 | Type | Description | Reference | 1058 +-------------+--------------------------------+---------------+ 1059 | 0 | Reserved | This document | 1060 | 1 | BFD Configuration sub-TLV | This document | 1061 | 2 | Performance Monitoring sub-TLV | This document | 1062 | 3 | MPLS OAM FMS sub-TLV | This document | 1063 | 4-65532 | Unassigned | | 1064 | 65533-65534 | Reserved for Experimental Use | This document | 1065 | 65535 | Reserved | This document | 1066 +-------------+--------------------------------+---------------+ 1068 Table 3: MPLS OAM Configuration sub-TLV Types 1070 5.4. BFD Configuration Sub-TLV Types 1072 IANA is requested to create a "BFD Configuration sub-TLV Types" sub- 1073 registry in the "RSVP-TE OAM Configuration Registry" for the sub-TLV 1074 types carried in the "BFD Configuration sub-TLV". Values from this 1075 new sub-registry to be allocated through IETF Review except for the 1076 Reserved for Experimental Use range. This document defines the 1077 following types: 1079 +-------------+-------------------------------------+---------------+ 1080 | Type | Description | Reference | 1081 +-------------+-------------------------------------+---------------+ 1082 | 0 | Reserved | This document | 1083 | 1 | BFD Identifiers sub-TLV | This document | 1084 | 2 | Negotiation Timer Parameters sub- | This document | 1085 | | TLV | | 1086 | 3 | BFD Authentication sub-TLV | This document | 1087 | 4 | Traffic Class sub-TLV | This document | 1088 | 5-65532 | Unassigned | | 1089 | 65533-65534 | Reserved for Experimental Use | This document | 1090 | 65535 | Reserved | This document | 1091 +-------------+-------------------------------------+---------------+ 1093 Table 4: BFD Configuration Sus-TLV Types 1095 5.5. Performance Monitoring sub-TLV Types 1097 IANA is requested to create a "Performance Monitoring sub-TLV Type" 1098 sub-registry in the "RSVP-TE OAM Configuration Registry" for the sub- 1099 TLV types carried in the "Performance Monitoring sub-TLV". Values 1100 from this new sub-registry to be allocated through IETF Review except 1101 for the Reserved for Experimental Use range. This document defines 1102 the following types: 1104 +-------------+-------------------------------+---------------+ 1105 | Type | Description | Reference | 1106 +-------------+-------------------------------+---------------+ 1107 | 0 | Reserved | This document | 1108 | 1 | MPLS OAM PM Loss sub-TLV | This document | 1109 | 2 | MPLS OAM PM Delay sub-TLV | This document | 1110 | 3-65532 | Unassigned | | 1111 | 65533-65534 | Reserved for Experimental Use | This document | 1112 | 65535 | Reserved | This document | 1113 +-------------+-------------------------------+---------------+ 1115 Table 5: Performance Monitoring sub-TLV Types 1117 5.6. New RSVP-TE error codes 1119 The following values need to be assigned under the "OAM Problem" 1120 Error Code [RFC7260] by IETF Review process: 1122 +-----------------+---------------------------------+---------------+ 1123 | Error Value | Description | Reference | 1124 | Sub-codes | | | 1125 +-----------------+---------------------------------+---------------+ 1126 | TBA3 | Unsupported BFD Version | This document | 1127 | TBA4 | Unsupported BFD Encapsulation | This document | 1128 | | format | | 1129 | TBA5 | Unsupported BFD Authentication | This document | 1130 | | Type | | 1131 | TBA6 | Mismatch of BFD Authentication | This document | 1132 | | Key ID | | 1133 | TBA7 | Unsupported Timestamp Format | This document | 1134 | TBA8 | Unsupported Delay Mode | This document | 1135 | TBA9 | Unsupported Loss Mode | This document | 1136 | TBA10 | Delay variation unsupported | This document | 1137 | TBA11 | Dyadic mode unsupported | This document | 1138 | TBA12 | Loopback mode unsupported | This document | 1139 | TBA13 | Combined mode unsupported | This document | 1140 | TBA14 | Fault management signaling | This document | 1141 | | unsupported | | 1142 | TBA15 | Unable to create fault | This document | 1143 | | management association | | 1144 +-----------------+---------------------------------+---------------+ 1146 Table 6: MPLS OAM Configuration Error Codes 1148 The "Sub-codes - 40, OAM Problem" sub-registry is located in the 1149 "Error Codes and Globally-Defined Error Value Sub-Codes" registry. 1151 6. Contributing Authors 1153 This document is the result of a large team of authors and 1154 contributors. The following is a list of the co-authors: 1156 John Drake 1158 Benoit Tremblay 1160 7. Acknowledgements 1162 The authors would like to thank David Allan, Lou Berger, Annamaria 1163 Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope 1164 for their useful comments. 1166 8. Security Considerations 1168 The signaling of OAM related parameters and the automatic 1169 establishment of OAM entities introduces additional security 1170 considerations to those discussed in [RFC3473]. In particular, a 1171 network element could be overloaded if an attacker were to request 1172 high frequency liveliness monitoring of a large number of LSPs, 1173 targeting a single network element as discussed in [RFC7260] and 1174 [RFC6060]. 1176 Additional discussion of security for MPLS and GMPLS protocols can be 1177 found in [RFC5920]. 1179 9. References 1181 9.1. Normative References 1183 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1184 Requirement Levels", BCP 14, RFC 2119, March 1997. 1186 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 1187 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 1188 Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. 1190 [RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., 1191 and S. Ueno, "Requirements of an MPLS Transport Profile", 1192 RFC 5654, September 2009. 1194 [RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for 1195 Operations, Administration, and Maintenance (OAM) in MPLS 1196 Transport Networks", RFC 5860, May 2010. 1198 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 1199 (BFD)", RFC 5880, June 2010. 1201 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 1202 "Bidirectional Forwarding Detection (BFD) for MPLS Label 1203 Switched Paths (LSPs)", RFC 5884, June 2010. 1205 [RFC6060] Fedyk, D., Shah, H., Bitar, N., and A. Takacs, 1206 "Generalized Multiprotocol Label Switching (GMPLS) Control 1207 of Ethernet Provider Backbone Traffic Engineering (PBB- 1208 TE)", RFC 6060, March 2011. 1210 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 1211 Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. 1213 [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay 1214 Measurement for MPLS Networks", RFC 6374, September 2011. 1216 [RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., 1217 and D. Ward, "MPLS Fault Management Operations, 1218 Administration, and Maintenance (OAM)", RFC 6427, November 1219 2011. 1221 [RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive 1222 Connectivity Verification, Continuity Check, and Remote 1223 Defect Indication for the MPLS Transport Profile", RFC 1224 6428, November 2011. 1226 [RFC7260] Takacs, A., Fedyk, D., and J. He, "GMPLS RSVP-TE 1227 Extensions for Operations, Administration, and Maintenance 1228 (OAM) Configuration", RFC 7260, June 2014. 1230 9.2. Informative References 1232 [LSP-PING-CONF] 1233 Bellagamba, E., Andersson, L., Ward, D., Drake, J., and P. 1234 Skoldstrom, "Configuration of proactive MPLS-TP 1235 Operations, Administration, and Maintenance (OAM) 1236 Functions Using LSP Ping", 2014, . 1239 [RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching 1240 (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic 1241 Class" Field", RFC 5462, February 2009. 1243 [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS 1244 Networks", RFC 5920, July 2010. 1246 [RFC6371] Busi, I. and D. Allan, "Operations, Administration, and 1247 Maintenance Framework for MPLS-Based Transport Networks", 1248 RFC 6371, September 2011. 1250 [RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay 1251 Measurement Profile for MPLS-Based Transport Networks", 1252 RFC 6375, September 2011. 1254 Authors' Addresses 1256 Elisa Bellagamba 1257 Ericsson 1259 Email: elisa.bellagamba@ericsson.com 1260 Attila Takacs 1261 Ericsson 1263 Email: attila.takacs@ericsson.com 1265 Gregory Mirsky 1266 Ericsson 1268 Email: Gregory.Mirsky@ericsson.com 1270 Loa Andersson 1271 Huawei Technologies 1273 Email: loa@mail01.huawei.com 1275 Pontus Skoldstrom 1276 Acreo AB 1277 Electrum 236 1278 Kista 164 40 1279 Sweden 1281 Phone: +46 70 7957731 1282 Email: pontus.skoldstrom@acreo.se 1284 Dave Ward 1285 Cisco 1287 Email: dward@cisco.com