idnits 2.17.1 draft-zhang-mpls-tp-yang-oam-04.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC6241], [RFC5921], [RFC6020]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 194 has weird spacing: '...peer-ip ine...' == Line 196 has weird spacing: '...vc-type vc-...' == Line 225 has weird spacing: '...peer-ip ine...' == Line 232 has weird spacing: '...-lsr-id ine...' == Line 556 has weird spacing: '...peer-ip ine...' == (3 more instances...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 30, 2017) is 2485 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) == Missing Reference: 'RFC6241' is mentioned on line 2315, but not defined == Missing Reference: 'RFC5921' is mentioned on line 2310, but not defined == Missing Reference: 'RFC6242' is mentioned on line 2320, but not defined == Missing Reference: 'RFC6536' is mentioned on line 2329, but not defined ** Obsolete undefined reference: RFC 6536 (Obsoleted by RFC 8341) == Missing Reference: 'RFC6371' is mentioned on line 2324, but not defined == Unused Reference: 'RFC6374' is defined on line 2286, but no explicit reference was found in the text == Unused Reference: 'RFC6375' is defined on line 2291, but no explicit reference was found in the text == Unused Reference: 'RFC6427' is defined on line 2296, but no explicit reference was found in the text == Unused Reference: 'RFC6428' is defined on line 2302, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 6375 Summary: 3 errors (**), 0 flaws (~~), 17 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group L. Zhang 3 Internet-Draft L. Zheng 4 Intended status: Standards Track Huawei Technologies 5 Expires: January 1, 2018 S. Aldrin 6 Google 7 G. Mirsky 8 ZTE Corp. 9 June 30, 2017 11 YANG Data Model for MPLS-TP Operations, Administration, and Maintenance 12 (OAM) 13 draft-zhang-mpls-tp-yang-oam-04 15 Abstract 17 The Transport Profile of Multiprotocol Label Switching (MPLS-TP) 18 [RFC5921]is a packet-based transport technology based on the MPLS 19 Traffic Engineering (MPLS-TE) and pseudowire (PW) data-plane 20 architectures. A comprehensive set of Operations, Administration, 21 and Maintenance (OAM) procedures that fulfill the MPLS-TP OAM 22 requirements for fault, performance, and protection-switching 23 management had been defined. YANG [RFC6020]is a data definition 24 language that was introduced to define the contents of a conceptual 25 data store that allows networked devices to be managed using NETCONF 26 [RFC6241]. This document presents the YANG Data model for MPLS-TP 27 OAM, including the basic functions of Fault Management and 28 Performance Monitoring. 30 Requirements Language 32 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 33 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 34 document are to be interpreted as described in RFC 2119 [RFC2119]. 36 Status of This Memo 38 This Internet-Draft is submitted in full conformance with the 39 provisions of BCP 78 and BCP 79. 41 Internet-Drafts are working documents of the Internet Engineering 42 Task Force (IETF). Note that other groups may also distribute 43 working documents as Internet-Drafts. The list of current Internet- 44 Drafts is at http://datatracker.ietf.org/drafts/current/. 46 Internet-Drafts are draft documents valid for a maximum of six months 47 and may be updated, replaced, or obsoleted by other documents at any 48 time. It is inappropriate to use Internet-Drafts as reference 49 material or to cite them other than as "work in progress." 51 This Internet-Draft will expire on January 1, 2018. 53 Copyright Notice 55 Copyright (c) 2017 IETF Trust and the persons identified as the 56 document authors. All rights reserved. 58 This document is subject to BCP 78 and the IETF Trust's Legal 59 Provisions Relating to IETF Documents 60 (http://trustee.ietf.org/license-info) in effect on the date of 61 publication of this document. Please review these documents 62 carefully, as they describe your rights and restrictions with respect 63 to this document. Code Components extracted from this document must 64 include Simplified BSD License text as described in Section 4.e of 65 the Trust Legal Provisions and are provided without warranty as 66 described in the Simplified BSD License. 68 Table of Contents 70 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 71 2. Conventions used in this document . . . . . . . . . . . . . . 3 72 3. Design of the Data Model . . . . . . . . . . . . . . . . . . 4 73 3.1. Maintenance Entity Group (MEG) Configuration . . . . . . 4 74 3.2. Maintenance Entities (MEs) Configuration . . . . . . . . 4 75 3.3. MPLS-TP OAM Fault Management And Performance Moinitoring 76 Configuration . . . . . . . . . . . . . . . . . . . . . . 6 77 3.4. Display of ME Status . . . . . . . . . . . . . . . . . . 7 78 3.5. Display of Detect Result . . . . . . . . . . . . . . . . 10 79 4. MPLS-TP OAM Data Hierarchy . . . . . . . . . . . . . . . . . 12 80 5. Interaction with other MPLS OAM Tools Models . . . . . . . . 17 81 6. MPLS-TP OAM YANG module . . . . . . . . . . . . . . . . . . . 17 82 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 47 83 8. Security Considerations . . . . . . . . . . . . . . . . . . . 47 84 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 85 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 48 86 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 48 87 11.1. Normative References . . . . . . . . . . . . . . . . . . 48 88 11.2. Infomative References . . . . . . . . . . . . . . . . . 49 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 49 91 1. Introduction 93 The Transport Profile of Multiprotocol Label Switching (MPLS-TP) 94 [RFC5921] is a packet-based transport technology based on the MPLS 95 Traffic Engineering (MPLS-TE) and pseudowire (PW) data-plane 96 architectures. A comprehensive set of Operations, Administration, 97 and Maintenance (OAM) procedures that fulfill the MPLS-TP OAM 98 requirements for fault, performance, and protection-switching 99 management had been defined. YANG [RFC6020] is a data definition 100 language that was introduced to define the contents of a conceptual 101 data store that allows networked devices to be managed using NETCONF 102 [RFC6241]. This document presents the YANG Data model for MPLS-TP 103 OAM, including the basic functions of Fault Management and 104 Performance Monitoring. 106 The rest of this document is organized as follows. Section 2 107 presents the conventions used in this document. Section 3 provides 108 the design of the MPLS-TP OAM data model in details. Section 4 109 presents the complete data hierarchy of LSP-Ping YANG model. 110 Section 5 discusses the interaction between MPLS-TP OAM data model 111 and other MPLS tools data models. Section 6 specifies the YANG 112 module and section 7 lists examples which conform to the YANG module 113 specified in this document. Finally, security considerations are 114 discussed in Section 8. 116 2. Conventions used in this document 118 CC - Continuity Check 120 CV - Conectivity Verification 122 LM - Loss Measurement 124 ME - Maintenance Entity 126 MEG - Maintenance Entity Group 128 MEP - Maintenance Entity Group End Point 130 MIP - Maintenance Entity Group Intermediate Point 132 PM - Performance Monitoring 134 PW - Pseudowire 136 DM - Packet Delay Measurement 138 AIS - Alarm Indication Signal 140 LKR - Lock Report 142 3. Design of the Data Model 144 This YANG data model is defined to be used to configure and manage 145 MPLS-TP OAM. Under the top level container mplstp-oam is the 146 container meg, which contains the configuration and detect result 147 information of multi instances of Maintenance Entity Group (MEG). 148 Under meg container, configuration of each Maintenance Entity (ME) 149 type are defined in corresponding list for a particular MEG. 150 Different OAM function cofiguration are also defined for each MEG. 151 The ME status and detect result information is also shown on per MEG 152 basis. In order to facilitate zero-touch experience, this document 153 defines a default value of the related detect parameters, such as 154 detection intervals, the exp of OAM packet and OAM packet size. 156 3.1. Maintenance Entity Group (MEG) Configuration 158 The container "meg" holds the configuration and detect result 159 information of multi instances of Maintenance Entity Group (MEG). 160 Each MEG is indexed by meg-name. The data hierarchy for MEG 161 configuration is presented below: 163 module: ietf-mplstpoam 164 +--rw mplstp-oam 165 +--rw ais-enable? enable 166 +--rw meg* [meg-name] 167 +--rw meg-name string 168 +--rw me-type? me-type 169 +--rw meg-id? string 170 +--rw meg-level? uint8 171 +--rw oam-active-state? active-type 173 3.2. Maintenance Entities (MEs) Configuration 175 Within a given Maintenance Entity Group there could be one or more 176 type of Maintenance Entity (ME), cofiguration of different types of 177 MEs are represented in its corresponding list and indexed by its own 178 key.The data hierarchy for ME configuration is presented below: 180 module: ietf-mplstpoam 181 +--rw mplstp-oam 182 +--rw ais-enable? enable 183 +--rw meg* [meg-name] 184 +--rw meg-name string 185 +--rw me-type? me-type 186 +--rw meg-id? string 187 +--rw meg-level? uint8 188 +--rw oam-active-state? active-type 189 +--rw pw* [local-peer-ip local-vc-id local-vc-type 190 remote-peer-ip remote-vc-id remote-vc-type] 191 | +--rw local-peer-ip inet:ip-address 192 | +--rw local-vc-id uint32 193 | +--rw local-vc-type vc-type 194 | +--rw remote-peer-ip inet:ip-address 195 | +--rw remote-vc-id uint32 196 | +--rw remote-vc-type vc-type 197 | +--rw mep-id? uint16 198 | +--rw remote-mep-id? uint16 199 | +--rw vll-ttl? uint8 200 | +--rw gal-enable? enable 201 | +--rw gal-mode? gal-mode 202 +--rw lsp* [tunnel-name tunnel-id ingress-lsr-id] 203 | +--rw tunnel-name string 204 | +--rw tunnel-id uint32 205 | +--rw ingress-lsr-id inet:ip-address 206 | +--rw mep-id? uint16 207 | +--rw remote-mep-id? uint16 208 | +--rw reverse-tunnel-name string 209 | +--rw reverse-tunnel-id? uint16 210 | +--rw reverse-ingress-lsr-id? inet:ip-address 211 | +--rw tunnel-description? string 212 | +--rw tunnel-type? tunnel-type 213 | +--rw tunnel-direction? tunnel-direction-type 214 +--rw section* [section-id] 215 | +--rw section-id uint64 216 | +--rw if-name? string 217 | +--rw peer-ip inet:ip-address 218 | +--rw peer-lsr-id? inet:ip-address 219 | +--rw mep-id? uint16 220 | +--rw remote-mep-id? uint16 221 +--rw pw-spme* [local-peer-ip local-vc-id switch-peer-ip 222 switch-vc-id vc-type instance-name] 223 | +--rw local-peer-ip inet:ip-address 224 | +--rw local-vc-id uint32 225 | +--rw switch-peer-ip inet:ip-address 226 | +--rw switch-vc-id uint32 227 | +--rw vc-type vc-type 228 | +--rw instance-name string 229 +--rw lsp-spme* [tunnel-id local-lsr-id remote-lsr-id] 230 | +--rw tunnel-id uint32 231 | +--rw local-lsr-id inet:ip-address 232 | +--rw remote-lsr-id inet:ip-address 234 3.3. MPLS-TP OAM Fault Management And Performance Moinitoring 235 Configuration 237 Different OAM function cofiguration are also defined for each MEG. 238 The data hierarchy for OAM fuction configuration is presented below: 240 module: ietf-mplstpoam 241 +--rw mplstp-oam 242 +--rw ais-enable? enable 243 +--rw meg* [meg-name] 244 +--rw meg-name string 245 +--rw me-type? me-type 246 +--rw meg-id? string 247 +--rw meg-level? uint8 248 +--rw oam-active-state? active-type 249 +--rw pw* [local-peer-ip local-vc-id local-vc-type 250 remote-peer-ip remote-vc-id remote-vc-type] 251 ... 252 +--rw lsp* [tunnel-name tunnel-id ingress-lsr-id] 253 ... 254 +--rw section* [section-id] 255 | +--rw section-id uint64 256 | +--rw if-name? string 257 | +--rw peer-ip inet:ip-address 258 | +--rw peer-lsr-id? inet:ip-address 259 | +--rw mep-id? uint16 260 | +--rw remote-mep-id? uint16 261 +--rw pw-spme* [local-peer-ip local-vc-id switch-peer-ip 262 switch-vc-id vc-type instance-name] 263 ... 264 +--rw lsp-spme* [tunnel-id local-lsr-id remote-lsr-id] 265 ... 266 +--rw cc 267 | +--rw cc-session-mode? cc-session-mode 268 | +--rw cc-authentication-enable? enable 269 | +--rw cc-exp? uint8 270 | +--rw cc-transmit-interval? cc-interval 271 | +--rw cc-recieve-interval? cc-interval 272 | +--rw cc-detect-multiplier? cc-detect-multiplier 273 | +--rw cc-enable? enable 274 +--rw cv 275 | +--rw cv-session-mode? cc-session-mode 276 | +--rw cv-authentication-enable? enable 277 | +--rw cv-exp? uint8 278 | +--rw cv-interval? cv-interval 279 | +--rw cv-detect-multiplier? cv-detect-multiplier 280 | +--rw cv-enable? enable 281 +--rw ais 282 | +--rw ais-exp? uint8 283 | +--rw ais-interval? ais-interval 284 +--rw lkr 285 | +--rw lkr-exp? uint8 286 | +--rw lkr-interval? lkr-interval 287 | +--rw lkr-enable? enable 288 +--rw one-way-dm-send 289 | +--rw one-dm-send-enable? enable 290 | +--rw one-dm-interval? dm-interval 291 | +--rw one-dm-exp? uint8 292 | +--rw one-dm-packet-size? uint16 293 | +--rw one-dm-pad-value? dm-padding-value 294 +--rw one-way-dm-rcv 295 | +--rw onr-dm-rcv-enable? enable 296 | +--rw one-dm-rcv-enable-type? one-way-rcv-type 297 +--rw two-way-dm-send 298 | +--rw two-dm-send-enable? enable 299 | +--rw two-dm-interval? dm-interval 300 | +--rw two-dm-exp? uint8 301 | +--rw two-dm-packet-size? uint16 302 | +--rw two-dm-pad-value? dm-padding-value 303 | +--rw two-dm-time-stamp? enable 304 +--rw two-way-dm-rcv 305 | +--rw two-dm-rcv-enable? enable 306 +--rw single-lm-send 307 | +--rw slm-send-enable? enable 308 | +--rw slm-interval? lm-interval 309 | +--rw slm-exp? uint8 310 +--rw single-lm-rcv 311 | +--rw slm-rcv-enable? enable 312 +--rw dual-lm 313 | +--rw dlm-enable? enable 315 3.4. Display of ME Status 317 The data hierarchy for display of ME status is presented below: 319 module: ietf-mplstpoam 320 +--rw mplstp-oam 321 +--rw ais-enable? enable 322 +--rw meg* [meg-name] 323 +--rw meg-name string 324 +--rw me-type? me-type 325 +--rw meg-id? string 326 +--rw meg-level? uint8 327 +--rw oam-active-state? active-type 328 +--rw pw* [local-peer-ip local-vc-id local-vc-type 329 remote-peer-ip remote-vc-id remote-vc-type] 330 ... 331 +--rw lsp* [tunnel-name tunnel-id ingress-lsr-id] 332 ... 333 +--rw section* [section-id] 334 ... 335 +--rw pw-spme* [local-peer-ip local-vc-id switch-peer-ip 336 switch-vc-id vc-type instance-name] 337 ... 338 +--rw lsp-spme* [tunnel-id local-lsr-id remote-lsr-id] 339 ... 340 +--rw cc 341 ... 342 +--rw cv 343 ... 344 +--rw ais 345 ... 346 +--rw lkr 347 ... 348 +--rw one-way-dm-send 349 ... 350 +--rw one-way-dm-rcv 351 ... 352 +--rw two-way-dm-send 353 ... 354 +--rw two-way-dm-rcv 355 ... 356 +--rw single-lm-send 357 ... 358 +--rw single-lm-rcv 359 ... 360 +--rw dual-lm 361 ... 362 +--ro status-info 363 | +--ro pw* 364 | | +--ro me-index? uint32 365 | | +--ro me-direction? me-direction 366 | | +--ro me-state? me-state 367 | | +--ro local-state? me-state 368 | | +--ro remote-state? me-state 369 | | +--ro alarm-indicate? string 370 | | +--ro local-defect-status? defect-status-type 371 | | +--ro local-invalid-time? uint32 372 | | +--ro local-defect-location? string 373 | | +--ro local-defect-type? defect-type 374 | | +--ro remote-defect-status? defect-status-type 375 | | +--ro remote-invalid-time? uint32 376 | | +--ro remote-defect-location? string 377 | | +--ro remote-defect-type? defect-type 378 | +--ro lsp* 379 | | +--ro me-index? uint32 380 | | +--ro me-direction? me-direction 381 | | +--ro me-state? me-state 382 | | +--ro local-state? me-state 383 | | +--ro remote-state? me-state 384 | | +--ro alarm-indicate? string 385 | | +--ro local-defect-status? defect-status-type 386 | | +--ro local-invalid-time? uint32 387 | | +--ro local-defect-location? string 388 | | +--ro local-defect-type? defect-type 389 | | +--ro remote-defect-status? defect-status-type 390 | | +--ro remote-invalid-time? uint32 391 | | +--ro remote-defect-location? string 392 | | +--ro remote-defect-type? defect-type 393 | | +--ro me-index-egress? uint32 394 | | +--ro me-direct-egress? me-direction 395 | | +--ro status-board-egress? string 396 | | +--ro state-egress? me-state 397 | | +--ro alarm-egress? string 398 | +--ro section* 399 | | +--ro me-index? uint32 400 | | +--ro me-direction? me-direction 401 | | +--ro me-state? me-state 402 | | +--ro local-state? me-state 403 | | +--ro remote-state? me-state 404 | | +--ro alarm-indicate? string 405 | | +--ro local-defect-status? defect-status-type 406 | | +--ro local-invalid-time? uint32 407 | | +--ro local-defect-location? string 408 | | +--ro local-defect-type? defect-type 409 | | +--ro remote-defect-status? defect-status-type 410 | | +--ro remote-invalid-time? uint32 411 | | +--ro remote-defect-location? string 412 | | +--ro remote-defect-type? defect-type 413 | +--ro pw-spme* 414 | | +--ro me-index? uint32 415 | | +--ro me-direction? me-direction 416 | | +--ro me-state? me-state 417 | | +--ro mip-id? uint16 418 | +--ro lsp-spme* 419 | +--ro me-index? uint32 420 | +--ro me-direction? me-direction 421 | +--ro me-state? me-state 422 | +--ro mip-id? uint16 424 3.5. Display of Detect Result 426 The data hierarchy for display of detect result is presented below: 428 module: ietf-mplstpoam 429 +--rw mplstp-oam 430 +--rw ais-enable? enable 431 +--rw meg* [meg-name] 432 +--rw meg-name string 433 +--rw me-type? me-type 434 +--rw meg-id? string 435 +--rw meg-level? uint8 436 +--rw oam-active-state? active-type 437 +--rw pw* [local-peer-ip local-vc-id local-vc-type 438 remote-peer-ip remote-vc-id remote-vc-type] 439 ... 440 +--rw lsp* [tunnel-name tunnel-id ingress-lsr-id] 441 ... 442 +--rw section* [section-id] 443 ... 444 +--rw pw-spme* [local-peer-ip local-vc-id switch-peer-ip 445 switch-vc-id vc-type instance-name] 446 ... 447 +--rw lsp-spme* [tunnel-id local-lsr-id remote-lsr-id] 448 ... 449 +--rw cc 450 ... 451 +--rw cv 452 ... 453 +--rw ais 454 ... 455 +--rw lkr 456 ... 457 +--rw one-way-dm-send 458 ... 459 +--rw one-way-dm-rcv 460 ... 461 +--rw two-way-dm-send 462 ... 463 +--rw two-way-dm-rcv 464 ... 465 +--rw single-lm-send 466 ... 467 +--rw single-lm-rcv 468 ... 469 +--rw dual-lm 470 ... 471 +--ro status-info 472 ... 473 +--ro detect-result 474 +--ro one-way-dm-result 475 | +--ro send-pkt-num? uint32 476 | +--ro recv-pkt-num? uint32 477 | +--ro delay-min? uint32 478 | +--ro delay-max? uint32 479 | +--ro delay-avg? uint32 480 | +--ro jitter-min? uint32 481 | +--ro jitter-max? uint32 482 | +--ro jitter-avg? uint32 483 | +--ro one-way-dm-data 484 | +--ro one-way-dm-data* [index] 485 | +--ro index uint32 486 | +--ro one-delay? uint32 487 | +--ro one-delay-var? uint32 488 | +--ro error-info? error-info 489 +--ro one-way-send-result 490 | +--ro measure-mode? measure-mode 491 | +--ro status? statistics-status 492 +--ro two-way-dm-result 493 | +--ro measure-mode? measure-mode 494 | +--ro status? statistics-status 495 | +--ro send-pkt-num? uint32 496 | +--ro rcv-pkt-num? uint32 497 | +--ro delay-min? uint32 498 | +--ro delay-max? uint32 499 | +--ro delay-avg? uint32 500 | +--ro jitter-min? uint32 501 | +--ro jitter-max? uint32 502 | +--ro jitter-avg? uint32 503 | +--ro two-way-dm-data 504 | +--ro two-way-dm-data* [index] 505 | +--ro index uint32 506 | +--ro two-delay? uint32 507 | +--ro two-delay-var? uint32 508 | +--ro error-info? error-info 509 +--ro single-lm-result 510 | +--ro measure-mode? measure-mode 511 | +--ro status? statistics-status 512 | +--ro send-pkt-num? uint32 513 | +--ro rcv-pkt-num? uint32 514 | +--ro rmt-loss-ratio-min? uint32 515 | +--ro rmt-loss-ratio-max? uint32 516 | +--ro rmt-loss-atio-avg? uint32 517 | +--ro rmt-loss-count-min? uint32 518 | +--ro rmt-loss-count-max? uint32 519 | +--ro rmt-loss-count-avg? uint32 520 | +--ro single-lm-data 521 | +--ro single-lm-data* [index] 522 | +--ro index uint32 523 | +--ro slm-loss-lcl? uint32 524 | +--ro slm-loss-lcl-rat? string 525 | +--ro slm-loss-rmt? uint32 526 | +--ro slm-loss-rmt-rat? string 527 | +--ro error-info? error-info 528 +--ro dual-lm-data 529 +--ro dual-lm-data* [index] 530 +--ro index uint32 531 +--ro dlm-Loss-lcl? uint32 532 +--ro dlm-loss-lcl-rat? string 533 +--ro dlm-loss-rmt? uint32 534 +--ro dlm-loss-rmt-rat? string 535 +--ro error-info? error-info 537 4. MPLS-TP OAM Data Hierarchy 539 The complete data hierarchy related to the MPLS-TP OAM YANG model is 540 presented below. 542 module: ietf-mplstpoam 543 +--rw mplstp-oam 544 +--rw ais-enable? enable 545 +--rw meg* [meg-name] 546 +--rw meg-name string 547 +--rw me-type? me-type 548 +--rw meg-id? string 549 +--rw meg-level? uint8 550 +--rw oam-active-state? active-type 551 +--rw pw* [local-peer-ip local-vc-id local-vc-type 552 remote-peer-ip remote-vc-id remote-vc-type] 553 | +--rw local-peer-ip inet:ip-address 554 | +--rw local-vc-id uint32 555 | +--rw local-vc-type vc-type 556 | +--rw remote-peer-ip inet:ip-address 557 | +--rw remote-vc-id uint32 558 | +--rw remote-vc-type vc-type 559 | +--rw mep-id? uint16 560 | +--rw remote-mep-id? uint16 561 | +--rw vll-ttl? uint8 562 | +--rw gal-enable? enable 563 | +--rw gal-mode? gal-mode 564 +--rw lsp* [tunnel-name tunnel-id ingress-lsr-id] 565 | +--rw tunnel-name string 566 | +--rw tunnel-id uint32 567 | +--rw ingress-lsr-id inet:ip-address 568 | +--rw mep-id? uint16 569 | +--rw remote-mep-id? uint16 570 | +--rw reverse-tunnel-name string 571 | +--rw reverse-tunnel-id? uint16 572 | +--rw reverse-ingress-lsr-id? inet:ip-address 573 | +--rw tunnel-description? string 574 | +--rw tunnel-type? tunnel-type 575 | +--rw tunnel-direction? tunnel-direction-type 576 +--rw section* [section-id] 577 | +--rw section-id uint64 578 | +--rw if-name? string 579 | +--rw peer-ip inet:ip-address 580 | +--rw peer-lsr-id? inet:ip-address 581 | +--rw mep-id? uint16 582 | +--rw remote-mep-id? uint16 583 +--rw pw-spme* [local-peer-ip local-vc-id switch-peer-ip 584 switch-vc-id vc-type instance-name] 585 | +--rw local-peer-ip inet:ip-address 586 | +--rw local-vc-id uint32 587 | +--rw switch-peer-ip inet:ip-address 588 | +--rw switch-vc-id uint32 589 | +--rw vc-type vc-type 590 | +--rw instance-name string 591 +--rw lsp-spme* [tunnel-id local-lsr-id remote-lsr-id] 592 | +--rw tunnel-id uint32 593 | +--rw local-lsr-id inet:ip-address 594 | +--rw remote-lsr-id inet:ip-address 595 +--rw cc 596 | +--rw cc-session-mode? cc-session-mode 597 | +--rw cc-authentication-enable? enable 598 | +--rw cc-exp? uint8 599 | +--rw cc-transmit-interval? cc-interval 600 | +--rw cc-recieve-interval? cc-interval 601 | +--rw cc-detect-multiplier? cc-detect-multiplier 602 | +--rw cc-enable? enable 603 +--rw cv 604 | +--rw cv-session-mode? cc-session-mode 605 | +--rw cv-authentication-enable? enable 606 | +--rw cv-exp? uint8 607 | +--rw cv-interval? cv-interval 608 | +--rw cv-detect-multiplier? cv-detect-multiplier 609 | +--rw cv-enable? enable 610 +--rw ais 611 | +--rw ais-exp? uint8 612 | +--rw ais-interval? ais-interval 613 +--rw lkr 614 | +--rw lkr-exp? uint8 615 | +--rw lkr-interval? lkr-interval 616 | +--rw lkr-enable? enable 617 +--rw one-way-dm-send 618 | +--rw one-dm-send-enable? enable 619 | +--rw one-dm-interval? dm-interval 620 | +--rw one-dm-exp? uint8 621 | +--rw one-dm-packet-size? uint16 622 | +--rw one-dm-pad-value? dm-padding-value 623 +--rw one-way-dm-rcv 624 | +--rw onr-dm-rcv-enable? enable 625 | +--rw one-dm-rcv-enable-type? one-way-rcv-type 626 +--rw two-way-dm-send 627 | +--rw two-dm-send-enable? enable 628 | +--rw two-dm-interval? dm-interval 629 | +--rw two-dm-exp? uint8 630 | +--rw two-dm-packet-size? uint16 631 | +--rw two-dm-pad-value? dm-padding-value 632 | +--rw two-dm-time-stamp? enable 633 +--rw two-way-dm-rcv 634 | +--rw two-dm-rcv-enable? enable 635 +--rw single-lm-send 636 | +--rw slm-send-enable? enable 637 | +--rw slm-interval? lm-interval 638 | +--rw slm-exp? uint8 639 +--rw single-lm-rcv 640 | +--rw slm-rcv-enable? enable 641 +--rw dual-lm 642 | +--rw dlm-enable? enable 643 +--ro status-info 644 | +--ro pw* 645 | | +--ro me-index? uint32 646 | | +--ro me-direction? me-direction 647 | | +--ro me-state? me-state 648 | | +--ro local-state? me-state 649 | | +--ro remote-state? me-state 650 | | +--ro alarm-indicate? string 651 | | +--ro local-defect-status? defect-status-type 652 | | +--ro local-invalid-time? uint32 653 | | +--ro local-defect-location? string 654 | | +--ro local-defect-type? defect-type 655 | | +--ro remote-defect-status? defect-status-type 656 | | +--ro remote-invalid-time? uint32 657 | | +--ro remote-defect-location? string 658 | | +--ro remote-defect-type? defect-type 659 | +--ro lsp* 660 | | +--ro me-index? uint32 661 | | +--ro me-direction? me-direction 662 | | +--ro me-state? me-state 663 | | +--ro local-state? me-state 664 | | +--ro remote-state? me-state 665 | | +--ro alarm-indicate? string 666 | | +--ro local-defect-status? defect-status-type 667 | | +--ro local-invalid-time? uint32 668 | | +--ro local-defect-location? string 669 | | +--ro local-defect-type? defect-type 670 | | +--ro remote-defect-status? defect-status-type 671 | | +--ro remote-invalid-time? uint32 672 | | +--ro remote-defect-location? string 673 | | +--ro remote-defect-type? defect-type 674 | | +--ro me-index-egress? uint32 675 | | +--ro me-direct-egress? me-direction 676 | | +--ro status-board-egress? string 677 | | +--ro state-egress? me-state 678 | | +--ro alarm-egress? string 679 | +--ro section* 680 | | +--ro me-index? uint32 681 | | +--ro me-direction? me-direction 682 | | +--ro me-state? me-state 683 | | +--ro local-state? me-state 684 | | +--ro remote-state? me-state 685 | | +--ro alarm-indicate? string 686 | | +--ro local-defect-status? defect-status-type 687 | | +--ro local-invalid-time? uint32 688 | | +--ro local-defect-location? string 689 | | +--ro local-defect-type? defect-type 690 | | +--ro remote-defect-status? defect-status-type 691 | | +--ro remote-invalid-time? uint32 692 | | +--ro remote-defect-location? string 693 | | +--ro remote-defect-type? defect-type 694 | +--ro pw-spme* 695 | | +--ro me-index? uint32 696 | | +--ro me-direction? me-direction 697 | | +--ro me-state? me-state 698 | | +--ro mip-id? uint16 699 | +--ro lsp-spme* 700 | +--ro me-index? uint32 701 | +--ro me-direction? me-direction 702 | +--ro me-state? me-state 703 | +--ro mip-id? uint16 704 +--ro detect-result 705 +--ro one-way-dm-result 706 | +--ro send-pkt-num? uint32 707 | +--ro recv-pkt-num? uint32 708 | +--ro delay-min? uint32 709 | +--ro delay-max? uint32 710 | +--ro delay-avg? uint32 711 | +--ro jitter-min? uint32 712 | +--ro jitter-max? uint32 713 | +--ro jitter-avg? uint32 714 | +--ro one-way-dm-data 715 | +--ro one-way-dm-data* [index] 716 | +--ro index uint32 717 | +--ro one-delay? uint32 718 | +--ro one-delay-var? uint32 719 | +--ro error-info? error-info 720 +--ro one-way-send-result 721 | +--ro measure-mode? measure-mode 722 | +--ro status? statistics-status 723 +--ro two-way-dm-result 724 | +--ro measure-mode? measure-mode 725 | +--ro status? statistics-status 726 | +--ro send-pkt-num? uint32 727 | +--ro rcv-pkt-num? uint32 728 | +--ro delay-min? uint32 729 | +--ro delay-max? uint32 730 | +--ro delay-avg? uint32 731 | +--ro jitter-min? uint32 732 | +--ro jitter-max? uint32 733 | +--ro jitter-avg? uint32 734 | +--ro two-way-dm-data 735 | +--ro two-way-dm-data* [index] 736 | +--ro index uint32 737 | +--ro two-delay? uint32 738 | +--ro two-delay-var? uint32 739 | +--ro error-info? error-info 740 +--ro single-lm-result 741 | +--ro measure-mode? measure-mode 742 | +--ro status? statistics-status 743 | +--ro send-pkt-num? uint32 744 | +--ro rcv-pkt-num? uint32 745 | +--ro rmt-loss-ratio-min? uint32 746 | +--ro rmt-loss-ratio-max? uint32 747 | +--ro rmt-loss-atio-avg? uint32 748 | +--ro rmt-loss-count-min? uint32 749 | +--ro rmt-loss-count-max? uint32 750 | +--ro rmt-loss-count-avg? uint32 751 | +--ro single-lm-data 752 | +--ro single-lm-data* [index] 753 | +--ro index uint32 754 | +--ro slm-loss-lcl? uint32 755 | +--ro slm-loss-lcl-rat? string 756 | +--ro slm-loss-rmt? uint32 757 | +--ro slm-loss-rmt-rat? string 758 | +--ro error-info? error-info 759 +--ro dual-lm-data 760 +--ro dual-lm-data* [index] 761 +--ro index uint32 762 +--ro dlm-Loss-lcl? uint32 763 +--ro dlm-loss-lcl-rat? string 764 +--ro dlm-loss-rmt? uint32 765 +--ro dlm-loss-rmt-rat? string 766 +--ro error-info? error-info 768 5. Interaction with other MPLS OAM Tools Models 770 TBA. 772 6. MPLS-TP OAM YANG module 774 file "ietf-mplstpoam@2015-07-02.yang" 775 module ietf-mplstpoam { 776 namespace "urn:ietf:params:xml:ns:yang:ietf-mplstpoam"; 777 //namespace need to be assigned by IANA 778 prefix "mplstpoam"; 779 import ietf-inet-types { 780 prefix inet; 781 } 782 organization "IETF MPLS Working Group"; 783 contact "draft-zhang-mpls-tp-yang-oam"; 784 description "MPLS TP OAM Yang Module"; 785 revision "2015-07-02" { 786 description "01 revision"; 787 reference "draft-zhang-mpls-tp-yang-oam"; 788 } 790 typedef enable { 791 type boolean; 792 description "enable"; 793 } 794 typedef me-type { 795 type enumeration { 796 enum "none" { 797 value 0; 798 description "ME type is not assigned."; 799 } 800 enum "section" { 801 value 1; 802 description "ME type is MPLS-TP Sections (between MPLS 803 LSRs)."; 804 } 805 enum "lsp" { 806 value 2; 807 description "ME type is an end-to-end LSP (between LERs)."; 808 } 809 enum "pw" { 810 value 3; 811 description "ME type is an end-to-end Single-Segment 812 Pseudowire (SS-PW) or MS-PW (between T-PEs)."; 813 } 814 enum "lsp-spme" { 815 value 4; 816 description "ME type is an SPME (between a given pair 817 of LERs and/or LSRs along an LSP)."; 818 } 819 enum "pw-spme" { 820 value 5; 821 description "ME type is an SPME (between a given pair 822 of T-PEs and/or S-PEs along an (MS-)PW)."; 823 } 824 } 825 description "ME type"; 826 } 827 typedef cc-session-mode { 828 type enumeration { 829 enum "coordinated" { 830 value 0; 831 description "coordinated"; 832 } 833 enum "independent" { 834 value 1; 835 description "independent"; 836 } 837 } 838 description "CC session mode"; 839 } 840 typedef cc-interval { 841 type uint32{ 842 range "1..65535"; 843 } 844 description "The value rang for cc packet transmit and receive 845 interval."; 846 } 847 typedef cv-interval { 848 type uint32 { 849 range "1..65535"; 850 } 851 description "The value rang for cv packet transmit interval."; 852 } 853 typedef cc-detect-multiplier { 854 type uint8{ 855 range "1..255"; 856 } 857 description "The value rang for cv packet detect multiplier"; 858 } 859 typedef cv-detect-multiplier { 860 type uint8{ 861 range "1..255"; 862 } 863 description "The value rang for cv packet detect multiplier"; 864 } 865 typedef lkr-interval { 866 type enumeration { 867 enum "interval1000ms" { 868 value 0; 869 description "1000ms"; 870 } 871 enum "interval60000ms" { 872 value 1; 873 description "60000ms"; 874 } 875 } 876 description "lkr-interval"; 877 } 878 typedef ais-interval { 879 type enumeration { 880 enum "interval1000ms" { 881 value 0; 882 description "1000ms"; 883 } 884 enum "interval60000ms" { 885 value 1; 886 description "60000ms"; 887 } 888 } 889 description "ais-interval"; 890 } 891 typedef me-direction { 892 type enumeration { 893 enum "ingress" { 894 value 0; 895 description "The direction to the ME is ingress"; 896 } 897 enum "egress" { 898 value 1; 899 description "The direction to the ME is egress"; 900 } 901 enum "dual" { 902 value 2; 903 description "The direction to the ME is dual"; 904 } 905 enum "none" { 906 value 3; 907 description "The direction to the ME is none"; 908 } 909 } 910 description "me-direction"; 911 } 912 typedef me-state { 913 type enumeration { 914 enum "init" { 915 value 0; 916 description "The me state is init"; 917 } 918 enum "down" { 919 value 1; 920 description "The me state is down"; 921 } 922 enum "up" { 923 value 2; 924 description "The me state is up"; 925 } 926 } 927 description "me-state"; 928 } 929 typedef dm-interval { 930 type uint32 { 931 range "1..65535"; 932 } 933 description "The value rang for dm packet transmit interval"; 934 } 935 typedef dm-padding-value { 936 type enumeration { 937 enum "paddingvalue0" { 938 value 0; 939 description "0"; 940 } 941 enum "paddingvalue1" { 942 value 1; 943 description "1"; 944 } 945 } 946 description "dm-padding-value"; 947 } 948 typedef lm-interval { 949 type uint32 { 950 range "1..65535"; 952 } 953 description "The value rang for lm packet transmit interval"; 954 } 955 typedef measure-mode { 956 type enumeration { 957 enum "on-demand" { 958 value 0; 959 description "on-demand"; 960 } 961 enum "proactive" { 962 value 1; 963 description "proactive"; 964 } 965 } 966 description "measure mode"; 967 } 968 typedef vc-type { 969 type uint16 { 970 range "1..65535"; 971 } 972 description "The namespace of the vc type of pw"; 973 } 974 typedef statistics-status { 975 type enumeration { 976 enum "finished" { 977 value 0; 978 description "finished"; 979 } 980 enum "working" { 981 value 1; 982 description "working"; 983 } 984 } 985 description "statistics status"; 986 } 987 typedef error-info { 988 type enumeration { 989 enum "valid" { 990 value 0; 991 description "valid"; 992 } 993 enum "invalid-loss" { 994 value 1; 995 description "invalid-loss"; 996 } 997 enum "invalid-delay" { 998 value 2; 999 description "invalid-delay"; 1001 } 1002 } 1003 description "error-info"; 1004 } 1005 typedef defect-status-type { 1006 type string { 1007 length "1..8191"; 1008 } 1009 description "The namespace of defect status type"; 1010 } 1011 typedef defect-type { 1012 type string { 1013 length "1..8191"; 1014 } 1015 description "The namespace of defect type"; 1016 } 1017 typedef tunnel-type { 1018 type enumeration { 1019 enum "ingress" { 1020 value 0; 1021 description "ingress"; 1022 } 1023 enum "egress" { 1024 value 1; 1025 description "egress"; 1026 } 1027 enum "bidirectional" { 1028 value 2; 1029 description "bidirectional"; 1030 } 1031 } 1032 description "tunnel type"; 1033 } 1034 typedef tunnel-direction-type { 1035 type enumeration { 1036 enum "unidirectional" { 1037 value 0; 1038 description "unidirectional"; 1039 } 1040 enum "bidirectional" { 1041 value 1; 1042 description "bidirectional"; 1043 } 1044 } 1045 description "tunnel direction type"; 1046 } 1047 typedef active-type { 1048 type enumeration { 1049 enum "deactive" { 1050 value 0; 1051 description "deactive"; 1052 } 1053 enum "active" { 1054 value 1; 1055 description "active"; 1056 } 1057 } 1058 description "active-type"; 1059 } 1060 typedef gal-mode { 1061 type enumeration { 1062 enum "with-13" { 1063 value 0; 1064 description "Gal mode is with label 13"; 1065 } 1066 enum "without-13" { 1067 value 1; 1068 description "Gal mode is without label 13"; 1069 } 1070 } 1071 description "gal mode"; 1072 } 1073 typedef one-way-rcv-type { 1074 type enumeration { 1075 enum "on-demand" { 1076 value 0; 1077 description "The switch of receive eanble takes effect 1078 on-demand one-way delay-measure"; 1079 } 1080 enum "proactive" { 1081 value 1; 1082 description "The switch of receive eanble takes effect 1083 proactive one-way delay-measure"; 1084 } 1085 } 1086 description "one way receive type"; 1087 } 1088 grouping pw { 1089 leaf local-peer-ip { 1090 type inet:ip-address; 1091 mandatory "true"; 1092 description "This object indicates the peer IP address"; 1093 } 1094 leaf local-vc-id { 1095 type uint32 { 1096 range "1..4294967295"; 1098 } 1099 mandatory "true"; 1100 description "This object indicates the vc ID of PW 1101 type ME"; 1102 } 1103 leaf local-vc-type { 1104 type vc-type; 1105 mandatory "true"; 1106 description "This object indicates the vc type of VC 1107 type ME"; 1108 } 1109 leaf remote-peer-ip { 1110 type inet:ip-address; 1111 description "This object indicates the remote peer IP of 1112 PW type ME"; 1113 } 1114 leaf remote-vc-id { 1115 type uint32 { 1116 range "1..4294967295"; 1117 } 1118 description "This object indicates the remote vc ID of 1119 PW type ME"; 1120 } 1121 leaf remote-vc-type { 1122 type vc-type; 1123 description "This object indicates the remote vc type of 1124 PW type ME"; 1125 } 1126 description "pw"; 1127 } 1128 grouping lsp { 1129 leaf tunnel-name { 1130 type string { 1131 length "0..63"; 1132 } 1133 mandatory "true"; 1134 description "The object indicates the name of tunnel"; 1135 } 1136 leaf tunnel-id { 1137 type uint32 { 1138 range "1..65535"; 1139 } 1140 description "The object indicates the tunnel id"; 1141 } 1142 leaf ingress-lsr-id { 1143 type inet:ip-address; 1144 description "The object indicates the ingress LSR-ID"; 1145 } 1146 description "lsp"; 1147 } 1148 grouping pw-spme { 1149 leaf local-peer-ip { 1150 type inet:ip-address; 1151 mandatory "true"; 1152 description "This object indicates the peer IP address of 1153 PW type MIP"; 1154 } 1155 leaf local-vc-id { 1156 type uint32 { 1157 range "1..4294967295"; 1158 } 1159 mandatory "true"; 1160 description "This object indicates the vc ID of PW type MIP"; 1161 } 1162 leaf switch-peer-ip { 1163 type inet:ip-address; 1164 mandatory "true"; 1165 description "This object indicates the peer IP address of 1166 PW switch node"; 1167 } 1168 leaf switch-vc-id { 1169 type uint32 { 1170 range "1..4294967295"; 1171 } 1172 mandatory "true"; 1173 description "This object indicates the vc id of PW switch 1174 node"; 1175 } 1176 leaf vc-type { 1177 type vc-type; 1178 mandatory "true"; 1179 description "This object indicates the vc type of PW type MIP"; 1180 } 1181 leaf instance-name { 1182 type string { 1183 length "1..31"; 1184 } 1185 mandatory "true"; 1186 description "This object specifies the VPWS instance name"; 1187 } 1188 description "pw spme"; 1189 } 1190 grouping me-detect-status { 1191 leaf me-index { 1192 type uint32 { 1193 range "1..65535"; 1195 } 1196 description "The object indicates the index of ME"; 1197 } 1198 leaf me-direction { 1199 type me-direction; 1200 description "The object indicates the direction of ME"; 1201 } 1202 leaf me-state { 1203 type me-state; 1204 description "The object indicates the state of ME"; 1205 } 1206 leaf local-state { 1207 type me-state; 1208 description "The object indicates the local status of ME"; 1209 } 1210 leaf remote-state { 1211 type me-state; 1212 description "The object indicates the remote state of ME"; 1213 } 1214 leaf alarm-indicate { 1215 type string { 1216 length "1..26"; 1217 } 1218 description "The object indicates the alarm of ME"; 1219 } 1220 leaf local-defect-status { 1221 type defect-status-type; 1222 default "init"; 1223 description "This object indicates the local defect status"; 1224 } 1225 leaf local-invalid-time { 1226 type uint32 { 1227 range "0..4294967295"; 1228 } 1229 description "This object indicates the invalid Time of 1230 local detect"; 1231 } 1232 leaf local-defect-location { 1233 type string { 1234 length "1..32"; 1235 } 1236 description "This object indicates the local defect location"; 1237 } 1238 leaf local-defect-type { 1239 type defect-type; 1240 description "This object indicates the local defect type"; 1241 } 1242 leaf remote-defect-status { 1243 type defect-status-type; 1244 default "init"; 1245 description "This object indicates the remote defect status"; 1246 } 1247 leaf remote-invalid-time { 1248 type uint32 { 1249 range "0..4294967295"; 1250 } 1251 description "This object indicates the invalid Time of 1252 remote detect"; 1253 } 1254 leaf remote-defect-location { 1255 type string { 1256 length "1..32"; 1257 } 1258 description "This object indicates the remote defect location"; 1259 } 1260 leaf remote-defect-type { 1261 type defect-type; 1262 description "This object indicates the remote defect type"; 1263 } 1264 description "This node indicate detect status of ME"; 1265 } 1266 grouping gal-set { 1267 leaf gal-enable { 1268 type enable; 1269 default "true"; 1270 description "This object indicates the gal flag"; 1271 } 1272 leaf gal-mode { 1273 type gal-mode; 1274 description "This object indicates the gal flag"; 1275 } 1276 description "This object indicates the gal set"; 1277 } 1279 container mplstp-oam { 1280 description "Top level container."; 1281 leaf ais-enable { 1282 type enable; 1283 default "false"; 1284 description "This object indicates the global ais flag 1285 of mpls-tp oam"; 1286 } 1288 list meg { 1289 key "meg-name"; 1290 description "meg multi instances."; 1291 leaf meg-name { 1292 type string { 1293 length "1..14"; 1294 } 1295 mandatory "true"; 1296 description "The object indicates the name of MEG"; 1297 } 1298 leaf me-type { 1299 type me-type; 1300 default "none"; 1301 description "The object indicates the type of ME"; 1302 } 1303 leaf meg-id { 1304 type string { 1305 length "1..96"; 1306 } 1307 description "The object indicates the ID of MEG"; 1308 } 1309 leaf meg-level { 1310 type uint8 { 1311 range "0..7"; 1312 } 1313 default "7"; 1314 description "The object indicates the level of MEG"; 1315 } 1316 leaf oam-active-state { 1317 type active-type; 1318 default "deactive"; 1319 description "This object indicates the oam active state"; 1320 } 1322 list pw { 1323 key "local-peer-ip local-vc-id local-vc-type remote-peer-ip 1324 remote-vc-id remote-vc-type"; 1325 description "PW"; 1326 uses pw; 1327 leaf mep-id { 1328 type uint16 { 1329 range "1..8191"; 1330 } 1331 description "This object indicates the MEP Id of local ME"; 1332 } 1333 leaf remote-mep-id { 1334 type uint16 { 1335 range "1..8191"; 1336 } 1337 description "This object indicates the MEP Id of remote 1338 ME"; 1340 } 1341 leaf vll-ttl { 1342 type uint8 { 1343 range "1..255"; 1344 } 1345 description "This object indicates the VLL ttl of PW 1346 type ME"; 1347 } 1348 uses gal-set; 1349 } 1351 list lsp { 1352 key "tunnel-name tunnel-id ingress-lsr-id"; 1353 description "LSP"; 1354 uses lsp; 1355 leaf mep-id { 1356 type uint16 { 1357 range "1..8191"; 1358 } 1359 description "This object indicates the MEP Id of 1360 local ME"; 1361 } 1362 leaf remote-mep-id { 1363 type uint16 { 1364 range "1..8191"; 1365 } 1366 description "This object indicates the MEP Id of 1367 remote ME"; 1368 } 1369 leaf reverse-tunnel-name { 1370 type string { 1371 length "0..63"; 1372 } 1373 mandatory "true"; 1374 description "The object indicates the name of 1375 reverse tunnel"; 1376 } 1377 leaf reverse-tunnel-id { 1378 type uint16 { 1379 range "1..65535"; 1380 } 1381 description "The object indicates the ingress 1382 reverse tunnelId"; 1383 } 1384 leaf reverse-ingress-lsr-id { 1385 type inet:ip-address; 1386 description "The object indicates the ingress 1387 reverse LSR-ID"; 1389 } 1390 leaf tunnel-description { 1391 type string { 1392 length "1..32"; 1393 } 1394 description "The object indicates the description 1395 of tunnel"; 1396 } 1397 leaf tunnel-type { 1398 type tunnel-type; 1399 default "ingress"; 1400 description "The object indicates the type of tunnel"; 1401 } 1402 leaf tunnel-direction { 1403 type tunnel-direction-type; 1404 description "The object indicates the direction of tunnel"; 1405 } 1406 } 1408 list section { 1409 key "section-id"; 1410 description "Section"; 1411 leaf section-id { 1412 type uint64 { 1413 range "1..2147483647"; 1414 } 1415 description "This object indicates the section ID"; 1416 } 1417 leaf if-name { 1418 type string { 1419 length "1..63"; 1420 } 1421 description "The object indicates the interface name"; 1422 } 1423 leaf peer-ip { 1424 type inet:ip-address; 1425 mandatory "true"; 1426 description "This object indicates the peer IP address"; 1427 } 1428 leaf peer-lsr-id { 1429 type inet:ip-address; 1430 description "This object indicates the peer lsr ID"; 1431 } 1432 leaf mep-id { 1433 type uint16 { 1434 range "1..8191"; 1435 } 1436 description "This object indicates the MEP Id of 1437 local ME"; 1438 } 1439 leaf remote-mep-id { 1440 type uint16 { 1441 range "1..8191"; 1442 } 1443 description "This object indicates the MEP Id of 1444 remote ME"; 1445 } 1446 } 1448 list pw-spme { 1449 key "local-peer-ip local-vc-id switch-peer-ip 1450 switch-vc-id vc-type instance-name"; 1451 description "PW-SPME"; 1452 uses pw-spme; 1453 } 1455 list lsp-spme { 1456 key "tunnel-id local-lsr-id remote-lsr-id"; 1457 description "LSP-SPME"; 1458 leaf tunnel-id { 1459 type uint32 { 1460 range "1..65535"; 1461 } 1462 description "The object indicates the tunnel id"; 1463 } 1464 leaf local-lsr-id { 1465 type inet:ip-address; 1466 description "The object indicates the ingress LSR-ID"; 1467 } 1468 leaf remote-lsr-id { 1469 type inet:ip-address; 1470 description "The object indicates the egress LSR-ID"; 1471 } 1472 } 1474 container cc { 1475 description "CC"; 1476 leaf cc-session-mode { 1477 type cc-session-mode; 1478 default "coordinated"; 1479 description "This object indicates the session 1480 mode of CC"; 1481 } 1482 leaf cc-authentication-enable { 1483 type enable; 1484 default "true"; 1485 description "CC authentication enable"; 1486 } 1487 leaf cc-exp { 1488 type uint8 { 1489 range "0..7"; 1490 } 1491 default "7"; 1492 description "This object indicates the exp of CC 1493 packet which is sent in the MEG"; 1494 } 1495 leaf cc-transmit-interval { 1496 type cc-interval; 1497 default "1"; 1498 description "The interval of CC packet which is 1499 transmit in the MEG"; 1500 } 1501 leaf cc-recieve-interval { 1502 type cc-interval; 1503 default "1"; 1504 description "The interval of CC packet which is 1505 recieved in the MEG"; 1506 } 1507 leaf cc-detect-multiplier { 1508 type cc-detect-multiplier; 1509 default "3"; 1510 description "The object indicate the detect 1511 multiplier of CC packet"; 1512 } 1513 leaf cc-enable { 1514 type enable; 1515 default "true"; 1516 description "The object indicates whether CC can be 1517 sent by the MEG"; 1518 } 1519 } 1520 container cv { 1521 description "CV"; 1522 leaf cv-session-mode { 1523 type cc-session-mode; 1524 default "coordinated"; 1525 description "This object indicates the session 1526 mode of CC"; 1527 } 1528 leaf cv-authentication-enable { 1529 type enable; 1530 default "true"; 1531 description "CV authentication enable"; 1532 } 1533 leaf cv-exp { 1534 type uint8 { 1535 range "0..7"; 1536 } 1537 default "7"; 1538 description "This object indicates the exp of CV packet 1539 which is sent in the MEG"; 1540 } 1541 leaf cv-interval { 1542 type cv-interval; 1543 default "1"; 1544 description "The interval of CV packet which is sent 1545 in the MEG"; 1546 } 1547 leaf cv-detect-multiplier { 1548 type cv-detect-multiplier; 1549 default "3"; 1550 description "The object indicate the detect multiplier 1551 of CV packet"; 1552 } 1553 leaf cv-enable { 1554 type enable; 1555 default "true"; 1556 description "The object indicates whether CC can be 1557 received by the MEG"; 1558 } 1559 } 1561 container ais { 1562 description "AIS"; 1563 leaf ais-exp { 1564 type uint8 { 1565 range "0..7"; 1566 } 1567 default "7"; 1568 description "This object indicates the exp of AIS packet 1569 which is sent in the MEG"; 1570 } 1571 leaf ais-interval { 1572 type ais-interval; 1573 default "interval1000ms"; 1574 description "This object indicates the interval of AIS 1575 packet which is sent in the MEG"; 1576 } 1577 } 1579 container lkr { 1580 description "LKR"; 1581 leaf lkr-exp { 1582 type uint8 { 1583 range "0..7"; 1584 } 1585 default "7"; 1586 description "This object indicates the exp of lock report 1587 packet which is sent in the MEG"; 1588 } 1589 leaf lkr-interval { 1590 type lkr-interval; 1591 default "interval1000ms"; 1592 description "This object indicates the interval of lock 1593 report packet which is sent in the MEG"; 1594 } 1595 leaf lkr-enable { 1596 type enable; 1597 default "false"; 1598 description "The object indicates whether lock report 1599 is enabled in the MEG"; 1600 } 1601 } 1603 container one-way-dm-send { 1604 description "One way delay measurement send"; 1605 leaf one-dm-send-enable { 1606 type enable; 1607 default "false"; 1608 description "This object indicates the 1DM statistics 1609 is enabled in the MEG"; 1610 } 1611 leaf one-dm-interval { 1612 type dm-interval; 1613 default "1000"; 1614 description "This object indicates the interval of 1615 1DM statistics in the MEG"; 1617 } 1618 leaf one-dm-exp { 1619 type uint8 { 1620 range "0..7"; 1621 } 1622 default "7"; 1623 description "This object indicates the exp of 1DM 1624 packet which is sent in the MEG"; 1625 } 1626 leaf one-dm-packet-size { 1627 type uint16 { 1628 range "64..1518"; 1630 } 1631 description "This object indicates the packet size 1632 of 1DM packet which is sent in the MEG"; 1633 } 1634 leaf one-dm-pad-value { 1635 type dm-padding-value; 1636 default "paddingvalue0"; 1637 description "This object indicates the padding value 1638 of 1DM packet which is sent in the MEG"; 1639 } 1640 } 1642 container one-way-dm-rcv { 1643 description "One way delay measurement received"; 1644 leaf onr-dm-rcv-enable { 1645 type enable; 1646 default "false"; 1647 description "This object indicates the 1DM receive 1648 is enabled in the MEG"; 1649 } 1650 leaf one-dm-rcv-enable-type { 1651 type one-way-rcv-type; 1652 description "This object indicates the 1DM receive type"; 1653 } 1654 } 1656 container two-way-dm-send { 1657 description "Two way delay measurement send"; 1658 leaf two-dm-send-enable { 1659 type enable; 1660 default "false"; 1661 description "This object indicates the 2DM statistics 1662 is enabled in the MEG"; 1663 } 1664 leaf two-dm-interval { 1665 type dm-interval; 1666 default "1000"; 1667 description "This object indicates the interval of 1668 2DM statistics in the MEG"; 1669 } 1670 leaf two-dm-exp { 1671 type uint8 { 1672 range "0..7"; 1673 } 1674 default "7"; 1675 description "This object indicates the exp of 2DM 1676 packet which is sent in the MEG"; 1677 } 1678 leaf two-dm-packet-size { 1679 type uint16 { 1680 range "64..1518"; 1681 } 1682 description "This object indicates the packet size of 1683 2DM packet which is sent in the MEG"; 1684 } 1685 leaf two-dm-pad-value { 1686 type dm-padding-value; 1687 default "paddingvalue0"; 1688 description "This object indicates the padding value of 1689 2DM packet which is sent in the MEG"; 1690 } 1691 leaf two-dm-time-stamp { 1692 type enable; 1693 default "false"; 1694 description "This object indicates whether two-way delay 1695 measurement time stamp is enable in the MEG"; 1696 } 1697 } 1699 container two-way-dm-rcv { 1700 description "Two way delay measurement recieved"; 1701 leaf two-dm-rcv-enable { 1702 type enable; 1703 default "false"; 1704 description "This object indicates the 2DM receiving 1705 statistics is enabled in the MEG"; 1706 } 1707 } 1709 container single-lm-send { 1710 description "Single loss measurment send"; 1711 leaf slm-send-enable { 1712 type enable; 1713 default "false"; 1714 description "This object indicates whether slm send 1715 is enable in the MEG"; 1716 } 1717 leaf slm-interval { 1718 type lm-interval; 1719 default "1000"; 1720 description "This object indicates the interval of 1721 slm statistics in the MEG"; 1722 } 1723 leaf slm-exp { 1724 type uint8 { 1725 range "0..7"; 1727 } 1728 default "7"; 1729 description "This object indicates the exp of slm 1730 packet which is sent in the MEG"; 1731 } 1732 } 1734 container single-lm-rcv { 1735 description "Single loss measurment received"; 1736 leaf slm-rcv-enable { 1737 type enable; 1738 default "false"; 1739 description "This object indicates whether slm 1740 receive is enable in the MEG"; 1741 } 1742 } 1744 container dual-lm { 1745 description "Dual loss measurement"; 1746 leaf dlm-enable { 1747 type enable; 1748 default "false"; 1749 description "This object indicates the dual loss 1750 statistics is enabled in the MEG"; 1751 } 1752 } 1754 container status-info { 1755 config "false"; 1756 description "Status info"; 1757 list pw { 1758 uses me-detect-status; 1759 description "PW"; 1760 } 1761 list lsp { 1762 uses me-detect-status; 1763 leaf me-index-egress { 1764 type uint32 { 1765 range "1..65535"; 1766 } 1767 description "The object indicates the egress index 1768 of ME"; 1769 } 1770 leaf me-direct-egress { 1771 type me-direction; 1772 description "The object indicates the direction of 1773 egress ME"; 1774 } 1775 leaf status-board-egress { 1776 type string { 1777 length "1..19"; 1778 } 1779 description "The object indicates the selected status 1780 board of ME"; 1781 } 1782 leaf state-egress { 1783 type me-state; 1784 description "The object indicates the status of ME"; 1785 } 1786 leaf alarm-egress { 1787 type string { 1788 length "1..26"; 1789 } 1790 description "The object indicates the alarm of ME"; 1791 } 1792 description "LSP"; 1793 } 1794 list section { 1795 uses me-detect-status; 1796 description "Section"; 1797 } 1798 list pw-spme { 1799 leaf me-index { 1800 type uint32 { 1801 range "1..65535"; 1802 } 1803 description "The object indicates the index of MIP"; 1804 } 1805 leaf me-direction { 1806 type me-direction; 1807 description "The object indicates the direction of MIP"; 1808 } 1809 leaf me-state { 1810 type me-state; 1811 description "The object indicates the state of MIP"; 1812 } 1813 leaf mip-id { 1814 type uint16 { 1815 range "1..8191"; 1816 } 1817 description "The object indicates the ID of MIP"; 1818 } 1819 description "PW-SPME"; 1820 } 1821 list lsp-spme{ 1822 leaf me-index { 1823 type uint32 { 1824 range "1..65535"; 1825 } 1826 description "The object indicates the index of te MIP"; 1827 } 1828 leaf me-direction { 1829 type me-direction; 1830 description "The object indicates the direction of 1831 te MIP"; 1832 } 1833 leaf me-state { 1834 type me-state; 1835 description "The object indicates the state of te MIP"; 1836 } 1837 leaf mip-id { 1838 type uint16 { 1839 range "1..8191"; 1840 } 1841 description "The object indicates the ID of te MIP"; 1842 } 1843 description "LSP-SPME"; 1844 } 1845 } 1846 container detect-result { 1847 config "false"; 1848 description "Detect result"; 1849 container one-way-dm-result { 1850 config "false"; 1851 description "One way delay measurement result"; 1852 leaf send-pkt-num { 1853 type uint32 { 1854 range "1..4294967295"; 1855 } 1856 description "Send packet number"; 1857 } 1858 leaf recv-pkt-num { 1859 type uint32 { 1860 range "1..4294967295"; 1861 } 1862 description "Recieved packet number"; 1863 } 1864 leaf delay-min { 1865 type uint32 { 1866 range "1..4294967295"; 1867 } 1868 description "This object indicates the minimum delay 1869 of received LB packets in the MEG"; 1870 } 1871 leaf delay-max { 1872 type uint32 { 1873 range "1..4294967295"; 1874 } 1875 description "This object indicates the maximum delay 1876 of received LB packets in the MEG"; 1877 } 1878 leaf delay-avg { 1879 type uint32 { 1880 range "1..4294967295"; 1881 } 1882 description "This object indicates the average delay 1883 of received LB packets in the MEG"; 1884 } 1885 leaf jitter-min { 1886 type uint32 { 1887 range "1..4294967295"; 1888 } 1889 description "This object indicates the minimum jitter 1890 of received LB packets in the MEG"; 1891 } 1892 leaf jitter-max { 1893 type uint32 { 1894 range "1..4294967295"; 1895 } 1896 description "This object indicates the average jitter 1897 of received LB packets in the MEG"; 1898 } 1899 leaf jitter-avg { 1900 type uint32 { 1901 range "1..4294967295"; 1902 } 1903 description "This object indicates the average jitter 1904 of received LB packets in the MEG"; 1905 } 1907 container one-way-dm-data { 1908 config "false"; 1909 description "One way delay measurement data"; 1910 list one-way-dm-data { 1911 key "index"; 1912 leaf index { 1913 type uint32 { 1914 range "1..4294967295"; 1915 } 1916 description "This object indicates index of 1DM 1917 statistics record in the MEG"; 1918 } 1919 leaf one-delay { 1920 type uint32 { 1921 range "1..4294967295"; 1922 } 1923 description "This object indicates delay of 1DM 1924 statistics in the MEG"; 1925 } 1926 leaf one-delay-var { 1927 type uint32 { 1928 range "1..4294967295"; 1929 } 1930 description "This object indicates delay Variation 1931 of 1DM statistics in the MEG"; 1932 } 1933 leaf error-info { 1934 type error-info; 1935 description "This object indicates the error info 1936 of statistics record in the MEG"; 1937 } 1938 description "One way delay measurement data"; 1939 } 1940 } 1941 } 1943 container one-way-send-result { 1944 config "false"; 1945 description "One way send result"; 1946 leaf measure-mode { 1947 type measure-mode; 1948 default "on-demand"; 1949 description "The flag indicates whether the measurement 1950 is an on-demand or a continue measurement"; 1951 } 1952 leaf status { 1953 type statistics-status; 1954 default "finished"; 1955 description "The flag indicates whether the measurement 1956 is finished"; 1957 } 1958 } 1960 container two-way-dm-result { 1961 config "false"; 1962 description "Two way delay measurement result."; 1963 leaf measure-mode { 1964 type measure-mode; 1965 default "on-demand"; 1966 description "The flag indicates whether the measurement 1967 is an on-demand or a continue measurement"; 1968 } 1969 leaf status { 1970 type statistics-status; 1971 default "finished"; 1972 description "The flag indicates whether the measurement 1973 is finished"; 1974 } 1975 leaf send-pkt-num { 1976 type uint32 { 1977 range "1..4294967295"; 1978 } 1979 description "Send packet number"; 1980 } 1981 leaf rcv-pkt-num { 1982 type uint32 { 1983 range "1..4294967295"; 1984 } 1985 description "Received packet number"; 1986 } 1987 leaf delay-min { 1988 type uint32 { 1989 range "1..4294967295"; 1990 } 1991 description "This object indicates the minimum delay 1992 of received LB packets in the MEG"; 1993 } 1994 leaf delay-max { 1995 type uint32 { 1996 range "1..4294967295"; 1997 } 1998 description "This object indicates the maximum delay 1999 of received LB packets in the MEG"; 2000 } 2001 leaf delay-avg { 2002 type uint32 { 2003 range "1..4294967295"; 2004 } 2005 description "This object indicates the average delay 2006 of received LB packets in the MEG"; 2007 } 2008 leaf jitter-min { 2009 type uint32 { 2010 range "1..4294967295"; 2011 } 2012 description "This object indicates the minimum jitter 2013 of received LB packets in the MEG"; 2014 } 2015 leaf jitter-max { 2016 type uint32 { 2017 range "1..4294967295"; 2018 } 2019 description "This object indicates the average jitter 2020 of received LB packets in the MEG"; 2021 } 2022 leaf jitter-avg { 2023 type uint32 { 2024 range "1..4294967295"; 2025 } 2026 description "This object indicates the average jitter 2027 of received LB packets in the MEG"; 2028 } 2029 container two-way-dm-data { 2030 config "false"; 2031 description "Two way delay measurement data"; 2032 list two-way-dm-data { 2033 key "index"; 2034 leaf index { 2035 type uint32 { 2036 range "1..4294967295"; 2037 } 2038 description "This object indicates index of 2DM 2039 statistics record in the MEG"; 2040 } 2041 leaf two-delay { 2042 type uint32 { 2043 range "1..4294967295"; 2044 } 2045 description "This object indicates delay of 2DM 2046 statistics in the MEG"; 2047 } 2048 leaf two-delay-var { 2049 type uint32 { 2050 range "1..4294967295"; 2051 } 2052 description "This object indicates delay Variation 2053 of 2DM statistics in the MEG"; 2054 } 2055 leaf error-info { 2056 type error-info; 2057 description "This object indicates the error info 2058 of statistics record in the MEG"; 2059 } 2060 description "Two way delay measurement data"; 2061 } 2062 } 2064 } 2066 container single-lm-result { 2067 config "false"; 2068 description "Single loss measurement result."; 2069 leaf measure-mode { 2070 type measure-mode; 2071 default "on-demand"; 2072 description "The flag indicates whether the measurement 2073 is an on-demand or a continue measurement"; 2074 } 2075 leaf status { 2076 type statistics-status; 2077 default "finished"; 2078 description "The flag indicates whether the measurement 2079 is finished"; 2080 } 2081 leaf send-pkt-num { 2082 type uint32 { 2083 range "1..4294967295"; 2084 } 2085 description "Send packet number"; 2086 } 2087 leaf rcv-pkt-num { 2088 type uint32 { 2089 range "1..4294967295"; 2090 } 2091 description "Received packet number"; 2092 } 2093 leaf rmt-loss-ratio-min { 2094 type uint32 { 2095 range "1..4294967295"; 2096 } 2097 description "This object indicates the minimum loss-ratio 2098 of received LB packets in the MEG"; 2099 } 2100 leaf rmt-loss-ratio-max { 2101 type uint32 { 2102 range "1..4294967295"; 2103 } 2104 description "This object indicates the maximum loss-ratio 2105 of received LB packets in the MEG"; 2106 } 2107 leaf rmt-loss-atio-avg { 2108 type uint32 { 2109 range "1..4294967295"; 2110 } 2111 description "This object indicates the average loss-ratio 2112 of received LB packets in the MEG"; 2113 } 2114 leaf rmt-loss-count-min { 2115 type uint32 { 2116 range "1..4294967295"; 2117 } 2118 description "This object indicates the minimum packet 2119 lost of received LB packets in the MEG"; 2120 } 2121 leaf rmt-loss-count-max { 2122 type uint32 { 2123 range "1..4294967295"; 2124 } 2125 description "This object indicates the average packet 2126 lost of received LB packets in the MEG"; 2127 } 2128 leaf rmt-loss-count-avg { 2129 type uint32 { 2130 range "1..4294967295"; 2131 } 2132 description "This object indicates the average packet 2133 lost of received LB packets in the MEG"; 2134 } 2136 container single-lm-data { 2137 config "false"; 2138 description "Single loss measurement data"; 2139 list single-lm-data { 2140 key "index"; 2141 leaf index { 2142 type uint32 { 2143 range "1..4294967295"; 2144 } 2145 description "This object indicates index of slm 2146 statistics record in the MEG"; 2147 } 2148 leaf slm-loss-lcl { 2149 type uint32 { 2150 range "1..4294967295"; 2151 } 2152 description "This object indicates local packet 2153 loss of slm statistics in the MEG"; 2154 } 2155 leaf slm-loss-lcl-rat { 2156 type string { 2157 length "1..24"; 2158 } 2159 description "This object indicates local packet 2160 loss rate of slm statistics in the MEG"; 2161 } 2162 leaf slm-loss-rmt { 2163 type uint32 { 2164 range "1..4294967295"; 2165 } 2166 description "This object indicates remote packet 2167 loss of slm statistics in the MEG"; 2168 } 2169 leaf slm-loss-rmt-rat { 2170 type string { 2171 length "1..24"; 2172 } 2173 description "This object indicates remote packet 2174 loss rate of slm statistics in the MEG"; 2175 } 2176 leaf error-info { 2177 type error-info; 2178 description "This object indicates the error 2179 info of statistics record in the MEG"; 2180 } 2181 description "Single loss measurement data"; 2182 } 2183 } 2184 } 2186 container dual-lm-data { 2187 config "false"; 2188 description "Dula loss measurement data"; 2189 list dual-lm-data { 2190 key "index"; 2191 leaf index { 2192 type uint32 { 2193 range "1..4294967295"; 2194 } 2195 description "This object indicates index of dlm 2196 statistics record in the MEG"; 2197 } 2198 leaf dlm-Loss-lcl { 2199 type uint32 { 2200 range "1..4294967295"; 2201 } 2202 description "This object indicates local packet 2203 loss of dlm statistics in the MEG"; 2204 } 2205 leaf dlm-loss-lcl-rat { 2206 type string { 2207 length "1..24"; 2209 } 2210 description "This object indicates local packet 2211 loss rate of dlm statistics in the MEG"; 2212 } 2213 leaf dlm-loss-rmt { 2214 type uint32 { 2215 range "1..4294967295"; 2216 } 2217 description "This object indicates remote packet 2218 loss of dlm statistics in the MEG"; 2219 } 2220 leaf dlm-loss-rmt-rat { 2221 type string { 2222 length "1..24"; 2223 } 2224 description "This object indicates remote packet 2225 loss rate of dlm statistics in the MEG"; 2226 } 2227 leaf error-info { 2228 type error-info; 2229 description "This object indicates the error info 2230 of statistics record in the MEG"; 2231 } 2232 description "Dual loss measurement data"; 2233 } 2234 } 2235 } 2236 } 2237 } 2238 } 2239 2241 7. Examples 2243 Examples of using Yang module to configure and manage MPLS-TP OAM 2244 will be given here in the update. 2246 8. Security Considerations 2248 The configuration and state data defined in this document is designed 2249 to be accessed via the NETCONF protocol [RFC6241]. The lowest 2250 NETCONF layer is the secure transport layer and the mandatory-to- 2251 implement secure transport is SSH [RFC6242]. The authors recommend 2252 to implement the NETCONF access control model [RFC6536] to restrict 2253 access for particular NETCONF users to a pre-configured subset of all 2254 available NETCONF protocol operations and content. There are a 2255 number of config true nodes defined in the YANG module which are 2256 writable/creatable/deletable. These data nodes may be considered 2257 sensitive or vulnerable in some network environments. Write 2258 operations to these data nodes without proper protection can have a 2259 negative effect on network operations. 2261 9. IANA Considerations 2263 The IANA is requested to as assign a new namespace URI from the IETF 2264 XML registry. 2266 URI:TBA 2268 10. Acknowledgements 2270 TBD 2272 11. References 2274 11.1. Normative References 2276 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2277 Requirement Levels", BCP 14, RFC 2119, 2278 DOI 10.17487/RFC2119, March 1997, 2279 . 2281 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 2282 the Network Configuration Protocol (NETCONF)", RFC 6020, 2283 DOI 10.17487/RFC6020, October 2010, 2284 . 2286 [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay 2287 Measurement for MPLS Networks", RFC 6374, 2288 DOI 10.17487/RFC6374, September 2011, 2289 . 2291 [RFC6375] Frost, D., Ed. and S. Bryant, Ed., "A Packet Loss and 2292 Delay Measurement Profile for MPLS-Based Transport 2293 Networks", RFC 6375, DOI 10.17487/RFC6375, September 2011, 2294 . 2296 [RFC6427] Swallow, G., Ed., Fulignoli, A., Ed., Vigoureux, M., Ed., 2297 Boutros, S., and D. Ward, "MPLS Fault Management 2298 Operations, Administration, and Maintenance (OAM)", 2299 RFC 6427, DOI 10.17487/RFC6427, November 2011, 2300 . 2302 [RFC6428] Allan, D., Ed., Swallow, G., Ed., and J. Drake, Ed., 2303 "Proactive Connectivity Verification, Continuity Check, 2304 and Remote Defect Indication for the MPLS Transport 2305 Profile", RFC 6428, DOI 10.17487/RFC6428, November 2011, 2306 . 2308 11.2. Infomative References 2310 [RFC5921] Bocci, M., Ed., Bryant, S., Ed., Frost, D., Ed., Levrau, 2311 L., and L. Berger, "A Framework for MPLS in Transport 2312 Networks", RFC 5921, DOI 10.17487/RFC5921, July 2010, 2313 . 2315 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 2316 and A. Bierman, Ed., "Network Configuration Protocol 2317 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 2318 . 2320 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 2321 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 2322 . 2324 [RFC6371] Busi, I., Ed. and D. Allan, Ed., "Operations, 2325 Administration, and Maintenance Framework for MPLS-Based 2326 Transport Networks", RFC 6371, DOI 10.17487/RFC6371, 2327 September 2011, . 2329 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 2330 Protocol (NETCONF) Access Control Model", RFC 6536, 2331 DOI 10.17487/RFC6536, March 2012, 2332 . 2334 Authors' Addresses 2336 Li Zhang 2337 Huawei Technologies 2338 China 2340 Email: monica.zhangli@huawei.com 2342 Lianshu Zheng 2343 Huawei Technologies 2344 China 2346 Email: vero.zheng@huawei.com 2347 Sam K. Aldrin 2348 Google 2349 USA 2351 Email: aldrin.ietf@gmail.com 2353 Greg Mirsky 2354 ZTE Corp. 2355 USA 2357 Email: gregimirsky@gmail.com