idnits 2.17.1 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-14.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: ---------------------------------------------------------------------------- No issues found here. 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 (December 18, 2014) is 3409 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 (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group E. Bellagamba, Ed. 3 Internet-Draft G. Mirsky, Ed. 4 Intended status: Standards Track Ericsson 5 Expires: June 21, 2015 L. Andersson, Ed. 6 Huawei Technologies Co. 7 P. Skoldstrom, Ed. 8 Acreo AB 9 D. Ward 10 Cisco 11 A. Takacs 12 Ericsson 13 December 18, 2014 15 Configuration of Pro-Active Operations, Administration, and Maintenance 16 (OAM) Functions for MPLS-based Transport Networks using RSVP-TE 17 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-14 19 Abstract 21 This specification describes the configuration of pro-active MPLS-TP 22 (MPLS-Transport Profile) Operations, Administration, and Maintenance 23 (OAM) Functions for a given LSP using a set of TLVs that are carried 24 by the GMPLS RSVP-TE protocol based on the OAM Configuration 25 Framework for GMPLS RSVP-TE. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on June 21, 2015. 44 Copyright Notice 46 Copyright (c) 2014 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 62 1.1. Conventions used in this document . . . . . . . . . . . . 4 63 1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 4 64 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 5 65 2. Overview of MPLS OAM for Transport Applications . . . . . . . 5 66 3. Theory of Operations . . . . . . . . . . . . . . . . . . . . 5 67 3.1. MPLS-TP OAM Configuration Operation Overview . . . . . . 5 68 3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 6 69 3.1.2. Configuration of Performance Monitoring . . . . . . . 7 70 3.1.3. Configuration of Fault Management Signals . . . . . . 7 71 3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 8 72 3.2.1. CV Flag Rules of Use . . . . . . . . . . . . . . . . 10 73 3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 10 74 3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 12 75 3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 13 76 3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 14 77 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 15 78 3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 16 79 3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 18 80 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 19 81 4. Summary of MPLS OAM configuration errors . . . . . . . . . . 20 82 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 83 5.1. MPLS OAM Type . . . . . . . . . . . . . . . . . . . . . . 21 84 5.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 22 85 5.3. MPLS OAM Configuration Sub-TLV Types . . . . . . . . . . 22 86 5.4. BFD Configuration Sub-TLV Types . . . . . . . . . . . . . 22 87 5.5. Performance Monitoring sub-TLV Types . . . . . . . . . . 23 88 5.6. New RSVP-TE error codes . . . . . . . . . . . . . . . . . 23 89 6. Contributing Authors . . . . . . . . . . . . . . . . . . . . 24 90 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 91 8. Security Considerations . . . . . . . . . . . . . . . . . . . 24 92 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 93 9.1. Normative References . . . . . . . . . . . . . . . . . . 25 94 9.2. Informative References . . . . . . . . . . . . . . . . . 26 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 97 1. Introduction 99 This document describes the configuration of pro-active MPLS-TP 100 (MPLS-Transport Profile) Operations, Administration, and Maintenance 101 (OAM) Functions for a given LSP using TLVs using GMPLS RSVP-TE 102 [RFC3473]. The use of GMPLS RSVP-TE for the configuration of OAM 103 functions is defined in a technology agnostic way in [RFC7260]. This 104 document specifies the additional mechanisms necessary to establish 105 MPLS-TP OAM entities at the maintenance points for monitoring and 106 performing measurements on an LSP, as well as defining information 107 elements and procedures to configure pro-active MPLS-TP OAM functions 108 running between LERs. Initialization and control of on-demand MPLS- 109 TP OAM functions are expected to be carried out by directly accessing 110 network nodes via a management interface; hence configuration and 111 control of on-demand OAM functions are out-of-scope for this 112 document. 114 MPLS-TP, the Transport Profile of MPLS, must, by definition 115 [RFC5654], be capable of operating without a control plane. 116 Therefore, there are several options for configuring MPLS-TP OAM, 117 without a control plane by either using an NMS or LSP Ping, or with a 118 control plane using signaling protocols such as RSVP-TE. 120 MPLS-TP describes a profile of MPLS that enables operational models 121 typical in transport networks, while providing additional OAM, 122 survivability and other maintenance functions not currently supported 123 by MPLS. [RFC5860] defines the requirements for the OAM 124 functionality of MPLS-TP. 126 Pro-active MPLS-TP OAM is performed by three different protocols, Bi- 127 directional Forwarding Detection (BFD) [RFC6428] for Continuity 128 Check/Connectivity Verification, the delay measurement protocol (DM) 129 [RFC6374] for delay and delay variation (jitter) measurements, and 130 the loss measurement protocol (LM) [RFC6374] for packet loss and 131 throughput measurements. Additionally there is a number of Fault 132 Management Signals that can be configured. 134 BFD is a protocol that provides low-overhead, fast detection of 135 failures in the path between two forwarding engines, including the 136 interfaces, data link(s), and to the extent possible the forwarding 137 engines themselves. BFD can be used to track the liveliness and 138 detect data plane failures of MPLS-TP point-to-point and might also 139 be extended to support point-to-multipoint connections. 141 The delay and loss measurements protocols [RFC6374] use a simple 142 query/response model for performing bidirectional measurements that 143 allows the originating node to measure packet loss and delay in both 144 directions. By timestamping and/or writing current packet counters 145 to the measurement packets at four times (Tx and Rx in both 146 directions) current delays and packet losses can be calculated. By 147 performing successive delay measurements the delay variation (jitter) 148 can be calculated. Current throughput can be calculated from the 149 packet loss measurements by dividing the number of packets sent/ 150 received with the time it took to perform the measurement, given by 151 the timestamp in LM header. Combined with a packet generator the 152 throughput measurement can be used to measure the maximum capacity of 153 a particular LSP. It should be noted that here we are not 154 configuring on-demand throughput estimates based on saturating the 155 connection as defined in [RFC6371]. Rather, we only enable the 156 estimation of the current throughput based on loss measurements. 158 1.1. Conventions used in this document 160 1.1.1. Terminology 162 BFD - Bidirectional Forwarding Detection 164 CV - Connectivity Verification 166 CC - Continuity Check 168 DM - Delay Measurement 170 FMS - Fault Management Signal 172 G-ACh - Generic Associated Channel 174 GMPLS - Generalized Multi-Protocol Label Switching 176 LER - Label switching Edge Router 178 LM - Loss Measurement 180 LSP - Label Switched Path 182 LSR - Label Switching Router 184 MEP - Maintanence Entity Group End Point 186 MPLS - Multi-Protocol Label Switching 188 MPLS-TP - MPLS Transport Profile 190 NMS - Network Management System 192 PM - Performance Measurement 193 RSVP-TE - Reservation Protocol Traffic Engineering 195 1.1.2. Requirements Language 197 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 198 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 199 document are to be interpreted as described in RFC 2119 [RFC2119]. 201 2. Overview of MPLS OAM for Transport Applications 203 [RFC6371] describes how MPLS-TP OAM mechanisms are operated to meet 204 transport requirements outlined in [RFC5860]. 206 [RFC6428] specifies two BFD operation modes: 1) "CC mode", which uses 207 periodic BFD message exchanges with symmetric timer settings, 208 supporting Continuity Check, 2) "CV/CC mode" which sends unique 209 maintenance entity identifiers in the periodic BFD messages 210 supporting Connectivity Verification (CV) as well as Continuity Check 211 (CC). 213 [RFC6374] specifies mechanisms for performance monitoring of LSPs, in 214 particular it specifies loss and delay measurement OAM functions. 216 [RFC6427] specifies fault management signals with which a server LSP 217 can notify client LSPs about various fault conditions to suppress 218 alarms or to be used as triggers for actions in the client LSPs. The 219 following signals are defined: Alarm Indication Signal (AIS), Link 220 Down Indication (LDI) and Lock Report (LKR). 222 [RFC6371] describes the mapping of fault conditions to consequent 223 actions. Some of these mappings may be configured by the operator, 224 depending on the application of the LSP. The following defects are 225 identified: Loss Of Continuity (LOC), Misconnectivity, MEP 226 Misconfiguration and Period Misconfiguration. Out of these defect 227 conditions, the following consequent actions may be configurable: 1) 228 whether or not the LOC defect should result in blocking the outgoing 229 data traffic; 2) whether or not the "Period Misconfiguration defect" 230 should result in a signal fail condition. 232 3. Theory of Operations 234 3.1. MPLS-TP OAM Configuration Operation Overview 236 GMPLS RSVP-TE, or alternatively LSP Ping [LSP-PING-CONF], can be used 237 to simply enable the different OAM functions, by setting the 238 corresponding flags in the "OAM Function Flags sub-TLV" [RFC7260]. 239 For a more detailed configuration one may include sub-TLVs for the 240 different OAM functions in order to specify various parameters in 241 detail. 243 Typically intermediate nodes should not process or modify any of the 244 OAM configuration TLVs but simply forward them to the end-node. 245 There is one exception to this and that is if the "MPLS OAM FMS sub- 246 TLV" is present. This sub-TLV has to be examined even by 247 intermediate nodes, but only acted upon by nodes capable of 248 transmitting FMS signals into the LSP being established. The sub-TLV 249 MAY be present the FMS flag is set in the "OAM Function Flags sub- 250 TLV". If this sub-TLV is present the "OAM MIP entities desired" and 251 "OAM MEP entities desired" flags (described in [RFC7260]) in the "LSP 252 Attributes Flags TLV" MUST be set and the entire OAM Configuration 253 TLV placed either in the LSP_REQUIRED_ATTRIBUTES object or in the 254 LSP_ATTRIBUTES object ensure that capable intermediate nodes process 255 the configuration. If placed in LSP_ATTRIBUTES nodes that are not 256 able to process the OAM Configuration TLV will forward the message 257 without generating an error, this is not the case if placed in the 258 LSP_REQUIRED_ATTRIBUTES object. 260 Finally, if the "MPLS OAM FMS sub-TLV" is not included only the "OAM 261 MEP entities desired" flag is set and the OAM Configuration TLV may 262 be placed in either LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES. 264 3.1.1. Configuration of BFD sessions 266 For this specification, BFD MUST be run in either one of the two 267 modes: 269 - Asynchronous mode, where both sides should be in active mode 271 - Unidirectional mode 273 In the simplest scenario, RSVP-TE, or alternatively LSP Ping [LSP- 274 PING-CONF], is used only to bootstrap a BFD session for an LSP, 275 without any timer negotiation. 277 Timer negotiation can be performed either in subsequent BFD control 278 messages (in this case the operation is similar to LSP Ping based 279 bootstrapping described in [RFC5884]) or directly in the RSVP-TE 280 signaling messages. 282 When BFD Control packets are transported in the G-ACh they are not 283 protected by any end-to-end checksum, only lower-layers are providing 284 error detection/correction. A single bit error, e.g. a flipped bit 285 in the BFD State field could cause the receiving end to wrongly 286 conclude that the link is down and in turn trigger protection 287 switching. To prevent this from happening the "BFD Configuration 288 sub-TLV" has an Integrity flag that when set enables BFD 289 Authentication using Keyed SHA1 with an empty key (all 0s) [RFC5880]. 290 This would ensure that every BFD Control packet carries an SHA1 hash 291 of itself that can be used to detect errors. 293 If BFD Authentication using a pre-shared key / password is desired 294 (i.e. authentication and not only error detection), the "BFD 295 Authentication sub-TLV" MUST be included in the "BFD Configuration 296 sub-TLV". The "BFD Authentication sub-TLV" is used to specify which 297 authentication method should be used and which pre-shared key / 298 password should be used for this particular session. How the key 299 exchange is performed is out of scope of this document. 301 3.1.2. Configuration of Performance Monitoring 303 It is possible to configure Performance Monitoring functionalities 304 such as Loss, Delay, Delay variation (jitter), and Throughput as 305 described in [RFC6374]. 307 When configuring Performance monitoring functionalities it is 308 possible to choose either the default configuration, by only setting 309 the respective flags in the "OAM Function Flags sub-TLV", or a 310 customized configuration. To customize the configuration, one would 311 set the respective flags and including the respective Loss and/or 312 Delay sub-TLVs). 314 By setting the PM/Loss flag in the "OAM Function Flags sub-TLV" and 315 by including the "MPLS OAM PM Loss sub-TLV", one can configure the 316 measurement interval and loss threshold values for triggering 317 protection. 319 Delay measurements are configured by setting PM/Delay flag in the 320 "OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss 321 sub-TLV", one can configure the measurement interval and the delay 322 threshold values for triggering protection. 324 3.1.3. Configuration of Fault Management Signals 326 To configure Fault Management Signals and their refresh time, the FMS 327 flag in the "OAM Function Flags sub-TLV" MUST be set and the "MPLS 328 OAM FMS sub-TLV" included. When configuring Fault Management 329 Signals, an implementation can enable the default configuration by 330 setting the FMS flag in the "OAM Function Flags sub-TLV". If an 331 implementation wishes to modify the default configuration it includes 332 a "MPLS OAM FMS sub-TLV". 334 If an intermediate point is intended to originate fault management 335 signal messages, this means that such an intermediate point is 336 associated to a server MEP through a co-located MPLS-TP client/server 337 adaptation function. Such a server MEP needs to be configured by its 338 own RSVP-TE session (or, alternatively, via an NMS or LSP-ping). 339 However, by setting the "Fault Management subscription" flag in the 340 "MPLS OAM FMS sub-TLV", a client LSP can indicate that it would like 341 an association to be created to the server MEP(s) on any intermediate 342 nodes. 344 3.2. MPLS OAM Configuration sub-TLV 346 The "OAM Configuration TLV", defined in [RFC7260], specifies the OAM 347 functions that are used for the LSP. This document extends the "OAM 348 Configuration TLV" by defining a new OAM Type: "MPLS OAM" (TBA1). 349 The "MPLS OAM" type is set to request the establishment of OAM 350 functions for MPLS-TP LSPs. The specific OAM functions are specified 351 in the "OAM Function Flags sub-TLV" as depicted in [RFC7260]. 353 When an egress LSR receives an "OAM Configuration TLV" indicating the 354 MPLS OAM type, the LSR will first process any present "OAM Function 355 Flags sub-TLV" and then it MUST process technology specific 356 configuration TLVs. This document defines a sub-TLV, the "MPLS OAM 357 Configuration sub-TLV" which is carried in the "OAM Configuration 358 TLV". 360 0 1 2 3 361 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 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | MPLS OAM Conf. sub-TLV (TBA2) | Length | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 365 | | 366 ~ sub-TLVs ~ 367 | | 368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 Type: TBA2, the "MPLS OAM Configuration sub-TLV". 372 Length: indicates the total length in octets, including sub-TLVs as 373 well as the Type and Length fields. 375 The following MPLS OAM specific sub-TLVs MAY be included in the "MPLS 376 OAM Configuration sub-TLV": 378 - "BFD Configuration sub-TLV", which MUST be included if the CC 379 and/or the CV OAM Function flag is set. This sub-TLV carries 380 additional sub-TLVs, failure to include the correct sub-TLVs MUST 381 result in an error being generated: "OAM Problem/Configuration 382 Error". The sub-TLVs are: 384 - "BFD Identifiers sub-TLV", MUST always be included. 386 - "Timer Negotiation Parameters sub-TLV", MUST be included if 387 the N flag is not set. 389 - "BFD Authentication sub-TLV", MAY be included if the I flag 390 is set. 392 - "Performance Monitoring sub-TLV", which MUST be included if any 393 of the PM/Delay, PM/Loss or PM/Throughput flags are set in the 394 "OAM Function Flag sub-TLV". This sub-TLV MAY carry additional 395 sub-TLVs: 397 - "MPLS OAM PM Loss sub-TLV" MAY be included if the PM/Loss OAM 398 Function flag is set. If the "MPLS OAM PM Loss sub-TLV" is not 399 included, default configuration values are used. The same sub- 400 TLV MAY also be included in case the PM/Throughput OAM Function 401 flag is set and there is the need to specify measurement 402 interval different from the default ones. Since throughput 403 measurements use the same tool as loss measurements the same 404 TLV is used. 406 - "MPLS OAM PM Delay sub-TLV" MAY be included if the PM/Delay 407 OAM Function flag is set. If the "MPLS OAM PM Delay sub-TLV" 408 is not included, default configuration values are used. 410 - "MPLS OAM FMS sub-TLV" MAY be included if the FMS OAM Function 411 flag is set. If the "MPLS OAM FMS sub-TLV" is not included, 412 default configuration values are used. 414 Following are some additional rules of processing MPLS OAM 415 Configuration sub-TLV: 417 - MPLS OAM Configuration sub-TLV? MAY be empty, i.e. have no 418 Value. Then its Length MUST be 8. Then all OAM functions that 419 have their corresponding flags set in the ?OAM Function Flags sub- 420 TLV? MUST be assigned their default values or left disabled. 422 - sub-TLV that doesn't have corresponding flag set MUST be 423 silently ignored; 425 - if multiple copies of a sub-TLV are present, then only the first 426 sub-TLV MUST be used and the remaining sub-TLVs MUST be silently 427 ignored. 429 However, not all the values can be derived from the standard RSVP-TE 430 objects, in particular the locally assigned Tunnel ID at the egress 431 cannot be derived by the ingress node. Therefore, the full LSP MEP- 432 ID used by the ingress has to be carried in the "BFD Identifiers sub- 433 TLV" in the Path message and the egress LSP MEP-ID in the same way in 434 the Resv message. 436 3.2.1. CV Flag Rules of Use 438 Moreover, if the CV flag is set, the CC flag MUST be set as well as 439 performing Connectivity Verification implies performing Continuity 440 Check. The format of an MPLS-TP CV/CC message is shown in [RFC6428] 441 and it requires, together with the BFD Control packet information, 442 the "LSP MEP-ID". The "LSP MEP-ID" contain four identifiers: 444 MPLS-TP Global_ID 446 MPLS-TP Node Identifier 448 Tunnel_Num 450 LSP_Num 452 These values need to be correctly set by both ingress and egress when 453 transmitting a CV packet and both ingress and egress needs to know 454 what to expect when receving a CV packet. Most of these values can 455 be derived from the Path and Resv messages [RFC3473], which uses a 456 5-tuple to uniquely identify an LSP within an operator's network. 457 This tuple is composed of a Tunnel Sender Address, Tunnel Endpoint 458 Address, Tunnel_ID, Extended Tunnel ID, and (GMPLS) LSP_ID. 460 3.3. BFD Configuration sub-TLV 462 The "BFD Configuration sub-TLV" (depicted below) is defined for BFD 463 OAM specific configuration parameters. The "BFD Configuration sub- 464 TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-TLV". 466 This TLV accommodates generic BFD OAM information and carries sub- 467 TLVs. 469 0 1 2 3 470 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 471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 472 | BFD Conf. Type (1) | Length | 473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 474 |Vers.| PHB |N|S|I|G|U|B| Reserved (set to all 0s) | 475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 476 | | 477 ~ sub-TLVs ~ 478 | | 479 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 480 Type: 1, the "BFD Configuration sub-TLV". 482 Length: indicates the total length in octets, including sub-TLVs as 483 well as the Type and Length fields. 485 Version: identifies the BFD protocol version. If the egress LSR does 486 not support the version an error MUST be generated: "OAM Problem/ 487 Unsupported BFD Version". 489 PHB: Identifies the Per-Hop Behavior (PHB) to be used for periodic 490 continuity monitoring messages. 492 BFD Negotiation (N): If set timer negotiation/re-negotiation via BFD 493 Control Messages is enabled, when cleared it is disabled. 495 Symmetric session (S): If set the BFD session MUST use symmetric 496 timing values. 498 Integrity (I): If set BFD Authentication MUST be enabled. If the 499 "BFD Configuration sub-TLV" does not include a "BFD Authentication 500 sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre- 501 shared key (all 0s). If the egress LSR does not support BFD 502 Authentication an error MUST be generated: "OAM Problem/BFD 503 Authentication unsupported". 505 Encapsulation Capability (G): if set, shows the capability of 506 encapsulating BFD messages into The G-Ach channel. If both the G bit 507 and U bit are set, configuration gives precedence to the G bit. If 508 the egress LSR does not support any of the ingress LSR Encapsulation 509 Capabilities an error MUST be generated: "OAM Problem/Unsupported BFD 510 Encapsulation format". 512 Encapsulation Capability (U): if set, shows the capability of 513 encapsulating BFD messages into UDP packets. If both the G bit and U 514 bit are set, configuration gives precedence to the G bit. If the 515 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 Bidirectional (B): if set, it configures BFD in the Bidirectional 520 mode. If it is not set it configures BFD in unidirectional mode. In 521 the second case, the source node does not expect any Discriminator 522 values back from the destination node. 524 Reserved: Reserved for future specification and set to 0 on 525 transmission and ignored when received. 527 The "BFD Configuration sub-TLV" MUST include the following sub-TLVs 528 in the Path message: 530 - "BFD Identifiers sub-TLV"; 532 - "Negotiation Timer Parameters sub-TLV" if the N flag is cleared. 534 The "BFD Configuration sub-TLV" MUST include the following sub-TLVs 535 in the Resv message: 537 - "BFD Identifiers sub-TLV;" 539 - "Negotiation Timer Parameters sub-TLV" if: 541 - the N and S flags are cleared, or if: 543 - the N flag is cleared and the S flag is set, and the 544 "Negotiation Timer Parameters sub-TLV" received by the egress 545 contains unsupported values. In this case an updated 546 "Negotiation Timer Parameters sub-TLV", containing values 547 supported by the egress LSR, MUST be returned to the ingress. 549 3.3.1. BFD Identifiers sub-TLV 551 The "BFD Identifiers sub-TLV" is carried as a sub-TLV of the "BFD 552 Configuration sub-TLV" and is depicted below. 554 0 1 2 3 555 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 556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 557 | BFD Identfiers Type (1) | Length | 558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 559 | Local Discriminator | 560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 561 | MPLS-TP Global_ID | 562 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 563 | MPLS-TP Node Identifier | 564 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 565 | Tunnel_Num | LSP_Num | 566 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 Type: 1, "BFD Identifiers sub-TLV". 570 Length: indicates the TLV total length in octets, including the Type 571 and Length fields (20). 573 Local Discriminator: A unique, nonzero discriminator value generated 574 by the transmitting system and referring to itself, used to 575 demultiplex multiple BFD sessions between the same pair of systems as 576 defined in [RFC5880]. 578 MPLS-TP Global_ID, Node Identifier, Tunnel_Num, and LSP_Num: all set 579 as defined in [RFC6370]. 581 3.3.2. Negotiation Timer Parameters sub-TLV 583 The "Negotiation Timer Parameters sub-TLV" is carried as a sub-TLV of 584 the "BFD Configuration sub-TLV" and is depicted below. 586 0 1 2 3 587 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 588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 589 | Nego. Timer Type (2) | Length | 590 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 591 | Acceptable Min. Asynchronous TX interval | 592 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 593 | Acceptable Min. Asynchronous RX interval | 594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 595 | Required Echo TX Interval | 596 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 Type: 2, "Negotiation Timer Parameters sub-TLV". 600 Length: indicates the TLV total length in octets, including Type and 601 Length fields (16). 603 Acceptable Min. Asynchronous TX interval: If the S (symmetric) flag 604 is set in the "BFD Configuration sub-TLV", it expresses the desired 605 time interval (in microseconds) at which the ingress LER intends to 606 both transmit and receive BFD periodic control packets. If the 607 egress LSR can not support the value, it SHOULD reply with a 608 supported interval. 610 If the S (symmetric) flag is cleared in the "BFD Configuration sub- 611 TLV", this field expresses the desired time interval (in 612 microseconds) at which the ingress LSR intends to transmit BFD 613 periodic control packets. 615 Acceptable Min. Asynchronous RX interval: If the S (symmetric) flag 616 is set in the "BFD Configuration sub-TLV", this field MUST be set 617 equal to "Acceptable Min. Asynchronous TX interval" on transmit and 618 MUST be ignored on receipt since it has no additional meaning with 619 respect to the one described for "Acceptable Min. Asynchronous TX 620 interval". 622 If the S (symmetric) flag is cleared in the "BFD Configuration sub- 623 TLV", it expresses the minimum time interval (in microseconds) at 624 which the ingress/egress LSRs can receive periodic BFD control 625 packets. If this value is greater than the "Acceptable Min. 626 Asynchronous TX interval" received from the ingress/egress LSR, the 627 receiving LSR MUST adopt the interval expressed in the "Acceptable 628 Min. Asynchronous RX interval". 630 Required Echo TX Interval: the minimum interval (in microseconds) 631 between received BFD Echo packets that this system is capable of 632 supporting, less any jitter applied by the sender as described in 633 [RFC5880] sect. 6.8.9. This value is also an indication for the 634 receiving system of the minimum interval between transmitted BFD Echo 635 packets. If this value is zero, the transmitting system does not 636 support the receipt of BFD Echo packets. If the LSR node cannot 637 support this value it SHOULD reply with a supported value (which may 638 be zero if Echo is not supported). 640 3.3.3. BFD Authentication sub-TLV 642 The "BFD Authentication sub-TLV" is carried as a sub-TLV of the "BFD 643 Configuration sub-TLV" and is depicted below. 645 0 1 2 3 646 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 647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 648 | BFD Auth. Type (3) | Length | 649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 650 | Auth Type | Auth Key ID | Reserved (0s) | 651 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 653 Type: 3, "BFD Authentication sub-TLV". 655 Length: indicates the TLV total length in octets, including Type and 656 Length fields (8). 658 Auth Type: indicates which type of authentication to use. The same 659 values as are defined in section 4.1 of [RFC5880] are used. If the 660 egress LSR does not support this type an "OAM Problem/Unsupported BFD 661 Authentication Type" error MUST be generated. 663 Auth Key ID: indicates which authentication key or password 664 (depending on Auth Type) should be used. How the key exchange is 665 performed is out of scope of this document.If the egress LSR does not 666 support this Auth Key ID an "OAM Problem/Mismatch of BFD 667 Authentication Key ID" error MUST be generated. 669 Reserved: Reserved for future specification and set to 0 on 670 transmission and ignored when received. 672 3.4. Performance Monitoring sub-TLV 674 If the "OAM Function Flags sub-TLV" has either the PM/Loss, PM/Delay 675 or PM/Throughput flag set, the "Performance Monitoring sub-TLV" MUST 676 be present in the "MPLS OAM Configuration sub-TLV". Failure to 677 include the correct sub-TLVs MUST result in an "OAM Problem/ 678 Configuration Error" error being generated. 680 The "Performance Monitoring sub-TLV" provides the configuration 681 information mentioned in Section 7 of [RFC6374]. It includes support 682 for the configuration of quality thresholds and, as described in 683 [RFC6374], "the crossing of which will trigger warnings or alarms, 684 and result reporting and exception notification will be integrated 685 into the system-wide network management and reporting framework." 687 In case the values need to be different than the default ones the 688 "Performance Monitoring sub-TLV" includes the following sub-TLVs: 690 - "MPLS OAM PM Loss sub-TLV" if the PM/Loss and/or PM/Throughput 691 flag is set in the "OAM Function Flags sub-TLV"; 693 - "MPLS OAM PM Delay sub-TLV" if the PM/Delay flag is set in the 694 "OAM Function Flags sub-TLV"; 696 The "Performance Monitoring sub-TLV" depicted below is carried as a 697 sub-TLV of the "MPLS OAM Configuration sub-TLV". 699 0 1 2 3 700 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 701 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 702 | Perf. Monitoring Type(2) | Length | 703 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 704 |D|L|J|Y|K|C| Reserved (set to all 0s) | 705 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 706 | | 707 ~ sub-TLVs ~ 708 | | 709 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 711 Type: 2, "Performance Monitoring sub-TLV". 713 Length: indicates the TLV total length in octets, including sub-TLVs 714 as well as Type and Length fields. 716 Configuration Flags, for the specific function description please 717 refer to [RFC6374]: 719 - D: Delay inferred/direct (0=INFERRED, 1=DIRECT). If the egress 720 LSR does not support specified mode an "OAM Problem/Unsupported 721 Delay Mode" error MUST be generated. 723 - L: Loss inferred/direct (0=INFERRED, 1=DIRECT). If the egress 724 LSR does not support specified mode an "OAM Problem/Unsupported 725 Loss Mode" error MUST be generated. 727 - J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE). If the 728 egress LSR does not support Delay variation measurements and the J 729 flag is set, an "OAM Problem/Delay variation unsupported" error 730 MUST be generated. 732 - Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does not 733 support Dyadic mode and the Y flag is set, an "OAM Problem/Dyadic 734 mode unsupported" error MUST be generated. 736 - K: Loopback (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does 737 not support Loopback mode and the K flag is set, an "OAM Problem/ 738 Loopback mode unsupported" error MUST be generated. 740 - C: Combined (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does 741 not support Combined mode and the C flag is set, an "OAM Problem/ 742 Combined mode unsupported" error MUST be generated. 744 Reserved: Reserved for future specification and set to 0 on 745 transmission and ignored when received. 747 3.4.1. MPLS OAM PM Loss sub-TLV 749 The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a sub-TLV 750 of the "Performance Monitoring sub-TLV". 752 0 1 2 3 753 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 754 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 755 | PM Loss Type (1) | Length | 756 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 757 | OTF |T|B| Reserved (set to all 0s) | 758 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 759 | Measurement Interval | 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 | Test Interval | 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 763 | Loss Threshold | 764 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 766 Type: 1,"MPLS OAM PM Loss sub-TLV". 768 Length: indicates the length of the parameters in octets, including 769 Type and Length fields (20). 771 OTF: Origin Timestamp Format of the Origin Timestamp field described 772 in [RFC6374]. By default it is set to IEEE 1588 version 1. If the 773 egress LSR cannot support this value an "OAM Problem/Unsupported 774 Timestamp Format" error MUST be generated. 776 Configuration Flags, please refer to [RFC6374] for further details: 778 - T: Traffic-class-specific measurement indicator. Set to 1 when 779 the measurement operation is scoped to packets of a particular 780 traffic class (DSCP value), and 0 otherwise. When set to 1, the 781 DS field of the message indicates the measured traffic class. By 782 default it is set to 1. 784 - B: Octet (byte) count. When set to 1, indicates that the 785 Counter 1-4 fields represent octet counts. When set to 0, 786 indicates that the Counter 1-4 fields represent packet counts. By 787 default it is set to 0. 789 Reserved: Reserved for future specification and set to 0 on 790 transmission and ignored when received. 792 Measurement Interval: the time interval (in milliseconds) at which 793 Loss Measurement query messages MUST be sent on both directions. If 794 the egress LSR cannot support the value, it SHOULD reply with a 795 supported interval. By default it is set to (100) as per [RFC6375]. 797 Test Interval: test messages interval in milliseconds as described in 798 [RFC6374]. By default it is set to (10) as per [RFC6375]. If the 799 egress LSR cannot support the value, it SHOULD reply with a supported 800 interval. 802 Loss Threshold: the threshold value of measured lost packets per 803 measurement over which action(s) SHOULD be triggered. 805 3.4.2. MPLS OAM PM Delay sub-TLV 807 The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a sub- 808 TLV of the "Performance Monitoring sub-TLV". 810 0 1 2 3 811 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 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 | PM Delay Type (2) | Length | 814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 815 | OTF |T|B| Reserved (set to all 0s) | 816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 817 | Measurement Interval | 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 | Test Interval | 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 | Delay Threshold | 822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 Type: 2,"MPLS OAM PM Delay sub-TLV". 826 Length: indicates the length of the parameters in octets, including 827 Type and Length fields (20). 829 OTF: Origin Timestamp Format of the Origin Timestamp field described 830 in [RFC6374]. By default it is set to IEEE 1588 version 1. If the 831 egress LSR cannot support this value an "OAM Problem/Unsupported 832 Timestamp Format" error MUST be generated. 834 Configuration Flags, please refer to [RFC6374] for further details: 836 - T: Traffic-class-specific measurement indicator. Set to 1 when 837 the measurement operation is scoped to packets of a particular 838 traffic class (DSCP value), and 0 otherwise. When set to 1, the 839 DS field of the message indicates the measured traffic class. By 840 default it is set to 1. 842 - B: Octet (byte) count. When set to 1, indicates that the 843 Counter 1-4 fields represent octet counts. When set to 0, 844 indicates that the Counter 1-4 fields represent packet counts. By 845 default it is set to 0. 847 Reserved: Reserved for future specification and set to 0 on 848 transmission and ignored when received. 850 Measurement Interval: the time interval (in milliseconds) at which 851 Delay Measurement query messages MUST be sent on both directions. If 852 the egress LSR cannot support the value, it SHOULD reply with a 853 supported interval. By default it is set to (1000) as per [RFC6375]. 855 Test Interval: test messages interval (in milliseconds) as described 856 in [RFC6374]. By default it is set to (10) as per [RFC6375]. If the 857 egress LSR cannot support the value, it SHOULD reply with a supported 858 interval. 860 Delay Threshold: the threshold value of measured two-way delay (in 861 milliseconds) over which action(s) SHOULD be triggered. 863 3.5. MPLS OAM FMS sub-TLV 865 The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of 866 the "MPLS OAM Configuration sub-TLV". When both working and 867 protection paths are signaled, both LSPs SHOULD be signaled with 868 identical settings of the E flag, T flag, and the refresh timer. 870 0 1 2 3 871 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 872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 | MPLS OAM FMS Type (3) | Length | 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 |E|S|T| Reserved (set to all 0s)| Refresh Timer | PHB | 876 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 878 Type: 3, "MPLS OAM FMS sub-TLV". 880 Length: indicates the TLV total length in octets, including Type and 881 Length fields (8). 883 FMS Signal Flags are used to enable the FMS signals at end point MEPs 884 and the Server MEPs of the links over which the LSP is forwarded. In 885 this document only the S flag pertains to Server MEPs. 887 The following flags are defined: 889 - E: Enable Alarm Indication Signal (AIS) and Lock Report (LKR) 890 signalling as described in [RFC6427]. Default value is 1 891 (enabled). If the egress MEP does not support FMS signal 892 generation an "OAM Problem/Fault management signaling unsupported" 893 error MUST be generated. 895 - S: Indicate to a Server MEP that its should transmit AIS and LKR 896 signals on client LSPs. Default value is 0 (disabled). If a 897 Server MEP which is capable of generating FMS messages is for some 898 reason unable to do so for the LSP being signalled an "OAM 899 Problem/Unable to create fault management association" error MUST 900 be generated. 902 - T: Set timer value, enabled the configuration of a specific 903 timer value. Default value is 0 (disabled). 905 - Remaining bits: Reserved for future specification and set to 0. 907 Refresh Timer: indicates the refresh timer of fault indication 908 messages, in seconds. The value MUST be between 1 to 20 seconds as 909 specified for the Refresh Timer field in [RFC6427]. If the egress 910 LSR cannot support the value it SHOULD reply with a supported timer 911 value. 913 PHB: identifies the per-hop behavior of packets with fault management 914 information. 916 4. Summary of MPLS OAM configuration errors 918 In addition to error values specified in [RFC7260] this document 919 defines the following values for the "OAM Problem" Error Code: 921 - If an egress LSR does not support the specified BFD version, an 922 error MUST be generated: "OAM Problem/Unsupported BFD Version". 924 - If an egress LSR does not support the specified BFD 925 Encapsulation format, an error MUST be generated: "OAM Problem/ 926 Unsupported BFD Encapsulation format". 928 - If an egress LSR does not support BFD Authentication, and it is 929 requested, an error MUST be generated: "OAM Problem/BFD 930 Authentication unsupported". 932 - If an egress LSR does not support the specified BFD 933 Authentication Type, an error MUST be generated: "OAM Problem/ 934 Unsupported BFD Authentication Type". 936 - If an egress LSR is not able to use the specified Authentication 937 Key ID, an error MUST be generated: "OAM Problem/Mismatch of BFD 938 Authentication Key ID". 940 - If an egress LSR does not support the specified Timestamp 941 Format, an error MUST be generated: "OAM Problem/Unsupported 942 Timestamp Format". 944 - If an egress LSR does not support specified Delay mode, an "OAM 945 Problem/Unsupported Delay Mode" error MUST be generated. 947 - If an egress LSR does not support specified Loss mode, an "OAM 948 Problem/Unsupported Loss Mode" error MUST be generated. 950 - If an egress LSR does not support Delay variation measurements, 951 and it is requested, an "OAM Problem/Delay variation unsupported" 952 error MUST be generated. 954 - If an egress LSR does not support Dyadic mode, and it is 955 requested, an "OAM Problem/Dyadic mode unsupported" error MUST be 956 generated. 958 - If an egress LSR does not support Loopback mode, and it is 959 requested, an "OAM Problem/Loopback mode unsupported" error MUST 960 be generated. 962 - If an egress LSR does not support Combined mode, and it is 963 requested, an "OAM Problem/Combined mode unsupported" error MUST 964 be generated. 966 - If an egress LSR does not support Fault Monitoring Signals, and 967 it is requested, an "OAM Problem/Fault management signaling 968 unsupported" error MUST be generated. 970 - If an intermediate server MEP supports Fault Monitoring Signals 971 but is unable to create an association, when requested to do so, 972 an "OAM Problem/Unable to create fault management association" 973 error MUST be generated. 975 5. IANA Considerations 977 5.1. MPLS OAM Type 979 This document specifies new the "MPLS OAM Type". IANA is requested 980 to allocate a new type (TBA1) from the OAM Type space of the RSVP-TE 981 OAM Configuration Registry. 983 +------+-------------+---------------+ 984 | Type | Description | Reference | 985 +------+-------------+---------------+ 986 | TBA1 | MPLS OAM | This document | 987 +------+-------------+---------------+ 989 Table 1: OAM MPLS Type 991 5.2. MPLS OAM Configuration sub-TLV 993 This document specifies the "MPLS OAM Configuration sub-TLV", IANA is 994 requested to allocate a new type (TBA2) from the technology-specific 995 sub-TLV space of the RSVP-TE OAM Configuration Registry. 997 +------+--------------------------------+---------------+ 998 | Type | Description | Reference | 999 +------+--------------------------------+---------------+ 1000 | TBA2 | MPLS OAM Configuration sub-TLV | This document | 1001 +------+--------------------------------+---------------+ 1003 Table 2: MPLS OAM Configuration sub-TLV Type 1005 5.3. MPLS OAM Configuration Sub-TLV Types 1007 IANA is requested to create an "MPLS OAM sub-TLV Types" sub-registry 1008 in the "RSVP-TE OAM Configuration Registry" for the sub-TLVs carried 1009 in the "MPLS OAM Configuration sub-TLV". Values from this new sub- 1010 registry to be allocated through IETF Review except for the Reserved 1011 for Experimental Use range. This document defines the following 1012 types: 1014 +-------------+--------------------------------+---------------+ 1015 | Type | Description | Reference | 1016 +-------------+--------------------------------+---------------+ 1017 | 0 | Reserved | This document | 1018 | 1 | BFD Configuration sub-TLV | This document | 1019 | 2 | Performance Monitoring sub-TLV | This document | 1020 | 3 | MPLS OAM FMS sub-TLV | This document | 1021 | 4-65532 | Unassigned | | 1022 | 65533-65534 | Reserved for Experimental Use | This document | 1023 | 65535 | Reserved | This document | 1024 +-------------+--------------------------------+---------------+ 1026 Table 3: MPLS OAM Configuration sub-TLV Types 1028 5.4. BFD Configuration Sub-TLV Types 1030 IANA is requested to create a "BFD Configuration sub-TLV Types" sub- 1031 registry in the "RSVP-TE OAM Configuration Registry" for the sub-TLV 1032 types carried in the "BFD Configuration sub-TLV". Values from this 1033 new sub-registry to be allocated through IETF Review except for the 1034 Reserved for Experimental Use range. This document defines the 1035 following types: 1037 +-------------+-------------------------------------+---------------+ 1038 | Type | Description | Reference | 1039 +-------------+-------------------------------------+---------------+ 1040 | 0 | Reserved | This document | 1041 | 1 | BFD Identifiers sub-TLV | This document | 1042 | 2 | Negotiation Timer Parameters sub- | This document | 1043 | | TLV | | 1044 | 3 | BFD Authentication sub-TLV | This document | 1045 | 4-65532 | Unassigned | | 1046 | 65533-65534 | Reserved for Experimental Use | This document | 1047 | 65535 | Reserved | This document | 1048 +-------------+-------------------------------------+---------------+ 1050 Table 4: BFD Configuration Sus-TLV Types 1052 5.5. Performance Monitoring sub-TLV Types 1054 IANA is requested to create a "Performance Monitoring sub-TLV Type" 1055 sub-registry in the "RSVP-TE OAM Configuration Registry" for the sub- 1056 TLV types carried in the "Performance Monitoring sub-TLV". Values 1057 from this new sub-registry to be allocated through IETF Review except 1058 for the Reserved for Experimental Use range. This document defines 1059 the following types: 1061 +-------------+-------------------------------+---------------+ 1062 | Type | Description | Reference | 1063 +-------------+-------------------------------+---------------+ 1064 | 0 | Reserved | This document | 1065 | 1 | MPLS OAM PM Loss sub-TLV | This document | 1066 | 2 | MPLS OAM PM Delay sub-TLV | This document | 1067 | 3-65532 | Unassigned | | 1068 | 65533-65534 | Reserved for Experimental Use | This document | 1069 | 65535 | Reserved | This document | 1070 +-------------+-------------------------------+---------------+ 1072 Table 5: Performance Monitoring sub-TLV Types 1074 5.6. New RSVP-TE error codes 1076 The following values need to be assigned under the "OAM Problem" 1077 Error Code [RFC7260 by IETF Review process: 1079 +-----------------+---------------------------------+---------------+ 1080 | Error Value | Description | Reference | 1081 | Sub-codes | | | 1082 +-----------------+---------------------------------+---------------+ 1083 | TBA3 | Unsupported BFD Version | This document | 1084 | TBA4 | Unsupported BFD Encapsulation | This document | 1085 | | format | | 1086 | TBA5 | Unsupported BFD Authentication | This document | 1087 | | Type | | 1088 | TBA6 | Mismatch of BFD Authentication | This document | 1089 | | Key ID | | 1090 | TBA7 | Unsupported Timestamp Format | This document | 1091 | TBA8 | Unsupported Delay Mode | This document | 1092 | TBA9 | Unsupported Loss Mode | This document | 1093 | TBA10 | Delay variation unsupported | This document | 1094 | TBA11 | Dyadic mode unsupported | This document | 1095 | TBA12 | Loopback mode unsupported | This document | 1096 | TBA13 | Combined mode unsupported | This document | 1097 | TBA14 | Fault management signaling | This document | 1098 | | unsupported | | 1099 | TBA15 | Unable to create fault | This document | 1100 | | management association | | 1101 +-----------------+---------------------------------+---------------+ 1103 Table 6: MPLS OAM Configuration Error Codes 1105 6. Contributing Authors 1107 This document is the result of a large team of authors and 1108 contributors. The following is a list of the co-authors: 1110 John Drake 1112 Benoit Tremblay 1114 7. Acknowledgements 1116 The authors would like to thank David Allan, Lou Berger, Annamaria 1117 Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope 1118 for their useful comments. 1120 8. Security Considerations 1122 The signaling of OAM related parameters and the automatic 1123 establishment of OAM entities introduces additional security 1124 considerations to those discussed in [RFC3473]. In particular, a 1125 network element could be overloaded if an attacker were to request 1126 high frequency liveliness monitoring of a large number of LSPs, 1127 targeting a single network element as discussed in [RFC7260] and 1128 [RFC6060]. 1130 9. References 1132 9.1. Normative References 1134 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1135 Requirement Levels", BCP 14, RFC 2119, March 1997. 1137 [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching 1138 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 1139 Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. 1141 [RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., 1142 and S. Ueno, "Requirements of an MPLS Transport Profile", 1143 RFC 5654, September 2009. 1145 [RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for 1146 Operations, Administration, and Maintenance (OAM) in MPLS 1147 Transport Networks", RFC 5860, May 2010. 1149 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 1150 (BFD)", RFC 5880, June 2010. 1152 [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, 1153 "Bidirectional Forwarding Detection (BFD) for MPLS Label 1154 Switched Paths (LSPs)", RFC 5884, June 2010. 1156 [RFC6060] Fedyk, D., Shah, H., Bitar, N., and A. Takacs, 1157 "Generalized Multiprotocol Label Switching (GMPLS) Control 1158 of Ethernet Provider Backbone Traffic Engineering (PBB- 1159 TE)", RFC 6060, March 2011. 1161 [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport 1162 Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. 1164 [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay 1165 Measurement for MPLS Networks", RFC 6374, September 2011. 1167 [RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., 1168 and D. Ward, "MPLS Fault Management Operations, 1169 Administration, and Maintenance (OAM)", RFC 6427, November 1170 2011. 1172 [RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive 1173 Connectivity Verification, Continuity Check, and Remote 1174 Defect Indication for the MPLS Transport Profile", RFC 1175 6428, November 2011. 1177 [RFC7260] Takacs, A., Fedyk, D., and J. He, "GMPLS RSVP-TE 1178 Extensions for Operations, Administration, and Maintenance 1179 (OAM) Configuration", RFC 7260, June 2014. 1181 9.2. Informative References 1183 [LSP-PING-CONF] 1184 Bellagamba, E., Andersson, L., Ward, D., Drake, J., and P. 1185 Skoldstrom, "Configuration of pro-active MPLS-TP 1186 Operations, Administration, and Maintenance (OAM) 1187 Functions Using LSP Ping", 2014, . 1190 [RFC6371] Busi, I. and D. Allan, "Operations, Administration, and 1191 Maintenance Framework for MPLS-Based Transport Networks", 1192 RFC 6371, September 2011. 1194 [RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay 1195 Measurement Profile for MPLS-Based Transport Networks", 1196 RFC 6375, September 2011. 1198 Authors' Addresses 1200 Elisa Bellagamba (editor) 1201 Ericsson 1203 Email: elisa.bellagamba@ericsson.com 1205 Gregory Mirsky (editor) 1206 Ericsson 1208 Email: Gregory.Mirsky@ericsson.com 1210 Loa Andersson (editor) 1211 Huawei Technologies Co. 1213 Email: loa@mail01.huawei.com 1214 Pontus Skoldstrom (editor) 1215 Acreo AB 1216 Electrum 236 1217 Kista 164 40 1218 Sweden 1220 Phone: +46 70 7957731 1221 Email: pontus.skoldstrom@acreo.se 1223 Dave Ward 1224 Cisco 1226 Email: dward@cisco.com 1228 Attila Takacs 1229 Ericsson 1231 Email: attila.takacs@ericsson.com