idnits 2.17.1 draft-gu-sfc-yang-oam-00.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 : ---------------------------------------------------------------------------- ** There are 51 instances of too long lines in the document, the longest one being 72 characters in excess of 72. ** The abstract seems to contain references ([I-D.ietf-lime-yang-connectionless-oam]), 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 == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (January 8, 2017) is 2658 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: 'RFC6020' is mentioned on line 132, but not defined == Missing Reference: 'RFC6241' is mentioned on line 111, but not defined == Unused Reference: 'IEEE.802.1Q-2011' is defined on line 742, but no explicit reference was found in the text == Unused Reference: 'RFC2234' is defined on line 750, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-lime-yang-connectionless-oam-methods' is defined on line 763, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE.802.1Q-2011' ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) == Outdated reference: A later version (-18) exists of draft-ietf-lime-yang-connectionless-oam-03 == Outdated reference: A later version (-13) exists of draft-ietf-lime-yang-connectionless-oam-methods-00 == Outdated reference: A later version (-15) exists of draft-ietf-sfc-oam-framework-01 Summary: 3 errors (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Gu 3 Internet-Draft China Mobile 4 Intended status: Standards Track L. Xia 5 Expires: July 12, 2017 Z. Wang 6 Huawei Technologies 7 D. Kumar 8 Cisco Syestems 9 M. Boucadair 10 France Telecom 11 January 8, 2017 13 YANG Data Model for SFC Operations, Administration, and Maintenance 14 (OAM) 15 draft-gu-sfc-yang-oam-00 17 Abstract 19 This document defines YANG data model for Service Function Chaining 20 (SFC Operations, Administration, and Maintenance). It derives from 21 the basic YANG data model for Layer independent OAM Management 22 defined in [I-D.ietf-lime-yang-connectionless-oam] with SFC 23 technology specifics. It includes SFC OAM related configuration and 24 state data. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on July 12, 2017. 43 Copyright Notice 45 Copyright (c) 2017 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 62 2.1. Terminologies . . . . . . . . . . . . . . . . . . . . . . 4 63 3. Architecture of OAM YANG Model and Relationship with SFC OAM 5 64 4. SFC OAM YANG DATA MODEL OVERVIEW . . . . . . . . . . . . . . 5 65 4.1. SFC type extensions . . . . . . . . . . . . . . . . . . . 6 66 4.2. Configuration Model Extension . . . . . . . . . . . . . . 6 67 4.3. RPC Extension . . . . . . . . . . . . . . . . . . . . . . 7 68 5. SFC OAM YANG Data Hierarchy . . . . . . . . . . . . . . . . . 8 69 6. SFC OAM YANG Module . . . . . . . . . . . . . . . . . . . . . 10 70 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 71 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 72 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 73 9.1. Normative References . . . . . . . . . . . . . . . . . . 17 74 9.2. Informative References . . . . . . . . . . . . . . . . . 17 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 77 1. Introduction 79 YANG [RFC6020] is a data modeling language used to model 80 configuration and state data manipulated by the Network Configuration 81 Protocol (NETCONF) [RFC6241], NETCONF remote procedure calls (RPC), 82 and NETCONF notifications. This document defines the YANG data model 83 for Service Function Chaining (SFC) OAM [I-D.ietf-sfc-oam-framework]. 84 The SFC OAM YANG module involves the OAM configuration, RPCs and 85 notifications, etc. 87 Currently, [I-D.ietf-lime-yang-connectionless-oam] proposes a basic 88 YANG data model for Layer independent OAM Management that can be 89 applied to various OAM technologies. SFC OAM YANG data model can be 90 defined by directly extending the basic model with SFC technology 91 specifics. It can bring some obvious benefits such as unified 92 format, reusable parts, and correlation of defects, faults, network 93 failure at the specific layer. 95 In addition, various components in the SFC technology specific YANG 96 data model defined in [I-D.penno-sfc-yang] can be directly reused in 97 this draft to define the SFC OAM YANG data model. 99 Note that SFC OAM mechanisms are not yet defined or standardized 100 although some of the basic concepts and functions (e.g., fault 101 detection, fault localization, performance measurement, etc) may be 102 similar to traditional OAM mechanisms. This draft should get 103 alignment with the latest development SFC OAM mechanisms. 105 2. Conventions and Terminology 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in [RFC2119]. 111 The following terms are defined in [RFC6241] and are not redefined 112 here: 114 o client 116 o configuration data 118 o server 120 o state data 122 The following terms are defined in [RFC6020] and are not redefined 123 here: 125 o augment 127 o data model 129 o data node 131 The terminology for describing YANG data models is found in 132 [RFC6020]. 134 The following notations are used within the data tree and carry the 135 meaning as noted below. 137 Each node is printed as: 139 141 is one of: 142 + for current 143 x for deprecated 144 o for obsolete 146 is one of: 148 rw for configuration data 149 ro for non-configuration data 150 -x for rpcs 151 -n for notifications 153 is the name of the node 155 If the node is augmented into the tree from another module, its name 156 is printed as :. 158 is one of: 160 ? for an optional leaf or choice 161 ! for a presence container 162 * for a leaf-list or list 163 [] for a list's keys 165 is the name of the type for leafs and leaf-lists 167 In this document, these words will appear with that interpretation 168 only when in ALL CAPS. Lower case uses of these words are not to be 169 interpreted as carrying RFC-2119 significance. 171 2.1. Terminologies 173 OAM Operations, Administration, and Maintenance [RFC6291] 175 LIME Layer Independent OAM Management [I-D.ietf-lime-yang-oam- 176 model] 178 SF Service Function [I-D.penno-sfc-yang] 180 SFC Service Function Chaining [I-D.penno-sfc-yang] 182 SFF Service Function Forwarder [I-D.penno-sfc-yang] 184 RPC Remote Process Call 186 3. Architecture of OAM YANG Model and Relationship with SFC OAM 188 Layer independent OAM YANG model [I-D.ietf-lime-yang-connectionless- 189 oam] is used as the basis for all the other OAM YANG models. This 190 allows users to span across OAM tools of different technologies 191 through a uniform API. The following Figure depicts the relationship 192 of SFC OAM YANG model with the Connectionless OAM YANG Model. 194 +---------------+ 195 | connectionless| 196 | OAM yang model| 197 +---------------+ 198 | 199 | 200 | 201 +-----------+-----------+ 202 | | 203 | | 204 +----+-----+ +-----+------+ 205 | SFC OAM | ......... | Other OAM | 206 | YANG model | YANG model | 207 +----+-----+ +-----+------+ 208 | | 209 +----+-----------------------+-------+ 210 | Unified API | 211 +------------------------------------+ 213 Relationship of SFC OAM YANG model to Layer independent OAM YANG 214 model 216 4. SFC OAM YANG DATA MODEL OVERVIEW 218 There are two main blocks in SFC-OAM YANG data model: Configuration 219 and RPCs. The SFC configuration model is derived from "ietf- 220 connectionless-oam" YANG data model [I-D.ietf-lime-yang- 221 connectionless-oam]. The specific attributes of SFC OAM are defined 222 and inserted into proper anchor point of "ietf-connectionless-oam". 223 Therefore, the monitoring of SFC components, such as SF, SFF, SFP, 224 classifier, etc, can be supported. 226 Meanwhile, the OAM function models, such as continuity check, trace 227 route, etc, are provided by extending the "ietf-connectionless-oam- 228 methods" [draft-ietf-lime-yang-connectionless-oam-methods]. 230 4.1. SFC type extensions 232 A new Technology parameter of SFC is defined here for the purpose of 233 identifying the SFC specific YANG model extension: 235 augment "/nd:networks/nd:network/nd:node/coam:location-type" 236 +"/coam:ipv4-location-type/coam:test-point-ipv4-location-list" 237 +"/coam:test-point-locations/coam:technology/coam:technology-string"{ 238 leaf sfc-oam{ 239 type string; 240 description 241 "sfc oam type"; 242 } 243 description 244 "augment the connectionless oam model to derive service 245 functon oam yang model"; 246 } 248 augment "/nd:networks/nd:network/nd:node/coam:location-type" 249 +"/coam:ipv6-location-type/coam:test-point-ipv6-location-list" 250 +"/coam:test-point-locations/coam:technology/coam:technology-string"{ 251 leaf sfc-oam{ 252 type string; 253 description 254 "sfc oam type"; 255 } 256 description 257 "augment the connectionless oam model to derive service 258 functon oam yang model"; 259 } 261 SFC type extension 263 Only when the Technology parameter is set to the "SFC" value, the SFC 264 specific extensions are applied. 266 4.2. Configuration Model Extension 268 The following section demonstrates how the "ietf-connectionless-oam" 269 model can be extended to support service function chain OAM. For 270 this purpose, SFC OAM specific attributes are defined and inserted 271 into the ipv4/ipv6-test point location. 273 module: ietf-sfc-oam 274 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ipv4-location- 275 type/coam:test-point-ipv4-location-list/coam:test-point-locations/coam:technolog 276 y/coam:technology-string: 277 +--rw sfc-oam? string 278 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ipv4-location-type/coam:test-point-ipv4-location-list/coam:test-point-locations: 279 +--rw sf-name? -> /sfc-sf:service-functions/service-function/name 280 +--rw sf-type? sfc-common:sft-type-name 281 +--rw sfc-name? -> /sfc-sfc:service-function-chains/service-function-chain/name 282 +--rw sfp-name? -> /sfc-sfp:service-function-paths/service-function-path/name 283 +--rw sf-data-plane-locator* [locator-name] 284 +--rw locator-name -> /sfc-sf:service-functions/service-function/sf-data-plane-locator/name 285 +--rw service-function-forwarder? sfc-common:sff-name 287 Configuration Model Extension 289 4.3. RPC Extension 291 The rpc model facilitates issuing commands to a NETCONF server (in 292 this case to the device that needs to execute the OAM command) and 293 obtaining a response. The Continuity-check, continuity-verification, 294 and traceroute are defined in "ietf-connectionless-oam-methods" 295 [draft-ietf-lime-yang-connectionless-oam-methods]. The following 296 section demonstrates the input extensions for SFC-OAM. 298 augment /coam-methods:continuity-check/coam-methods:input/coam-methods:destina 299 tion-tp/coam-methods:tp-address: 300 +--:(sfc-address) 301 +---- sf-name? -> /sfc-sf:service-functions/service- 302 function/name 303 +---- sfc-name? -> /sfc-sfc:service-function-chains/s 304 ervice-function-chain/name 305 +---- sfp-name? -> /sfc-sfp:service-function-paths/se 306 rvice-function-path/name 307 +---- classifier? -> /sfc-sfp:service-function-paths/se 308 rvice-function-path/classifier 309 +---- service-function-forwarder? -> /sfc-sff:service-function-forwarde 310 rs/service-function-forwarder/name 311 augment /coam-methods:path-discovery/coam-methods:input/coam-methods:destinati 312 on-tp/coam-methods:tp-address: 313 +--:(sfc-address) 314 +---- sf-name? -> /sfc-sf:service-functions/service- 315 function/name 316 +---- sfc-name? -> /sfc-sfc:service-function-chains/s 317 ervice-function-chain/name 318 +---- sfp-name? -> /sfc-sfp:service-function-paths/se 319 rvice-function-path/name 320 +---- classifier? -> /sfc-sfp:service-function-paths/se 321 rvice-function-path/classifier 322 +---- service-function-forwarder? -> /sfc-sff:service-function-forwarde 323 rs/service-function-forwarder/name 325 RPC Extension 327 5. SFC OAM YANG Data Hierarchy 329 The complete data hierarchy related to the SFC OAM YANG model is 330 presented below. 332 module: ietf-sfc-oam 333 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ipv4-location- 334 type/coam:test-point-ipv4-location-list/coam:test-point-locations/coam:technolog 335 y/coam:technology-string: 336 +--rw sfc-oam? string 337 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ipv4-location- 338 type/coam:test-point-ipv4-location-list/coam:test-point-locations: 339 +--rw sf-name? -> /sfc-sf:service-functions/service-function 340 /name 341 +--rw sf-type? sfc-common:sft-type-name 342 +--rw sfc-name? -> /sfc-sfc:service-function-chains/service-f 343 unction-chain/name 344 +--rw sfp-name? -> /sfc-sfp:service-function-paths/service-fu 345 nction-path/name 346 +--rw sf-data-plane-locator* [locator-name] 347 +--rw locator-name -> /sfc-sf:service-functions/service- 348 function/sf-data-plane-locator/name 349 +--rw service-function-forwarder? sfc-common:sff-name 350 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ipv6-location- 351 type/coam:test-point-ipv6-location-list/coam:test-point-locations/coam:technolog 352 y/coam:technology-string: 353 +--rw sfc-oam? string 354 augment /nd:networks/nd:network/nd:node/coam:location-type/coam:ipv6-location- 355 type/coam:test-point-ipv6-location-list/coam:test-point-locations: 356 +--rw sf-name? -> /sfc-sf:service-functions/service-function 357 /name 358 +--rw sf-type? sfc-common:sft-type-name 359 +--rw sfc-name? -> /sfc-sfc:service-function-chains/service-f 360 unction-chain/name 361 +--rw sfp-name? -> /sfc-sfp:service-function-paths/service-fu 362 nction-path/name 363 +--rw classifier? -> /sfc-sfp:service-function-paths/service-fu 364 nction-path/classifier 365 +--rw sf-data-plane-locator* [locator-name] 366 +--rw locator-name -> /sfc-sf:service-functions/service- 367 function/sf-data-plane-locator/name 368 +--rw service-function-forwarder? -> /sfc-sff:service-function-forwarde 369 rs/service-function-forwarder/name 371 RPCs: 372 augment /coam-methods:continuity-check/coam-methods:input/coam-methods:destina 373 tion-tp/coam-methods:tp-address: 374 +--:(sfc-address) 375 +---- sf-name? -> /sfc-sf:service-functions/service- 376 function/name 377 +---- sfc-name? -> /sfc-sfc:service-function-chains/s 378 ervice-function-chain/name 379 +---- sfp-name? -> /sfc-sfp:service-function-paths/se 380 rvice-function-path/name 381 +---- classifier? -> /sfc-sfp:service-function-paths/se 382 rvice-function-path/classifier 383 +---- service-function-forwarder? -> /sfc-sff:service-function-forwarde 384 rs/service-function-forwarder/name 385 augment /coam-methods:path-discovery/coam-methods:input/coam-methods:destinati 386 on-tp/coam-methods:tp-address: 387 +--:(sfc-address) 388 +---- sf-name? -> /sfc-sf:service-functions/service- 389 function/name 390 +---- sfc-name? -> /sfc-sfc:service-function-chains/s 391 ervice-function-chain/name 392 +---- sfp-name? -> /sfc-sfp:service-function-paths/se 394 rvice-function-path/name 395 +---- classifier? -> /sfc-sfp:service-function-paths/se 396 rvice-function-path/classifier 397 +---- service-function-forwarder? -> /sfc-sff:service-function-forwarde 398 rs/service-function-forwarder/name 400 Data hierarchy of SFC OAM 402 6. SFC OAM YANG Module 404 file "ietf-sfc-oam@2016-11-21.yang" 405 module ietf-sfc-oam { 406 namespace "urn:ietf:params:xml:ns:yang:ietf-sfc-oam"; 407 prefix sfc-oam; 409 import ietf-network{ 410 prefix nd; 411 } 413 import ietf-connectionless-oam{ 414 prefix "coam"; 415 } 417 import ietf-connectionless-oam-methods{ 418 prefix "coam-methods"; 419 } 421 import service-function-chain{ 422 prefix "sfc-sfc"; 423 } 424 import sfc-common{ 425 prefix sfc-common; 426 } 428 import service-function { 429 prefix sfc-sf; 430 } 432 import service-function-forwarder { 433 prefix sfc-sff; 434 } 436 import service-function-path{ 437 prefix sfc-sfp; 438 } 440 organization "IETF SFC Working Group"; 441 contact 443 "Gu Rong "; 445 description 446 "The YANG module defines a SFC OAM configuration model."; 448 revision 2016-11-21 { 449 description 450 "Initial vision. - 00 version"; 451 reference ""; 452 } 454 /*service function oam blocks*/ 456 /*test point ipv4 extension*/ 458 /*oam type extension*/ 460 augment "/nd:networks/nd:network/nd:node/coam:location-type" 461 +"/coam:ipv4-location-type/coam:test-point-ipv4-location-list" 462 +"/coam:test-point-locations/coam:technology/coam:technology-string"{ 463 leaf sfc-oam{ 464 type string; 465 description 466 "sfc oam type"; 467 } 468 description 469 "augment the connectionless oam model to derive service 470 functon oam yang model"; 471 } 473 /*service function*/ 475 augment "/nd:networks/nd:network/nd:node/coam:location-type" 476 +"/coam:ipv4-location-type/coam:test-point-ipv4-location-list" 477 +"/coam:test-point-locations"{ 478 leaf sf-name { 479 type leafref{ 480 path "/sfc-sf:service-functions/sfc-sf:service-function" 481 +"/sfc-sf:name"; 482 } 483 description 484 "The name of the service function."; 485 } 487 leaf sf-type{ 488 type sfc-common:sft-type-name; 489 description 490 "The type of the service function"; 491 } 492 leaf sfc-name { 493 type leafref{ 494 path "/sfc-sfc:service-function-chains" 495 +"/sfc-sfc:service-function-chain/sfc-sfc:name"; 496 } 497 description 498 "service function chain name"; 499 } 500 leaf sfp-name { 501 type leafref{ 502 path "/sfc-sfp:service-function-paths" 503 +"/sfc-sfp:service-function-path/sfc-sfp:name"; 504 } 505 description 506 "Service function path name"; 507 } 508 list sf-data-plane-locator { 509 key "locator-name"; 510 leaf locator-name{ 511 type leafref{ 512 path "/sfc-sf:service-functions/sfc-sf:service-function" 513 +"/sfc-sf:sf-data-plane-locator/sfc-sf:name"; 514 } 515 description 516 "The sf data plane locator name"; 517 } 519 leaf service-function-forwarder{ 520 type sfc-common:sff-name; 521 description 522 "The name of teh service function forwarder"; 523 } 525 description 526 "list for service function data plane locator"; 527 } 528 description 529 "augment connectionless oam model to derive service 530 function oam yang model"; 531 } 533 /*test point ipv6 extension*/ 535 /*oam type extension*/ 536 augment "/nd:networks/nd:network/nd:node/coam:location-type" 537 +"/coam:ipv6-location-type/coam:test-point-ipv6-location-list" 538 +"/coam:test-point-locations/coam:technology/coam:technology-string"{ 539 leaf sfc-oam{ 540 type string; 541 description 542 "sfc oam type"; 543 } 544 description 545 "augment the connectionless oam model to derive service 546 functon oam yang model"; 547 } 549 /*service function*/ 551 augment "/nd:networks/nd:network/nd:node/coam:location-type" 552 +"/coam:ipv6-location-type/coam:test-point-ipv6-location-list" 553 +"/coam:test-point-locations"{ 554 leaf sf-name { 555 type leafref{ 556 path "/sfc-sf:service-functions/sfc-sf:service-function" 557 +"/sfc-sf:name"; 558 } 559 description 560 "The name of the service function."; 561 } 562 leaf sf-type{ 563 type sfc-common:sft-type-name; 564 description 565 "The type of the service function"; 566 } 567 leaf sfc-name { 568 type leafref{ 569 path "/sfc-sfc:service-function-chains" 570 +"/sfc-sfc:service-function-chain/sfc-sfc:name"; 571 } 572 description 573 "service function chain name"; 574 } 575 leaf sfp-name { 576 type leafref{ 577 path "/sfc-sfp:service-function-paths" 578 +"/sfc-sfp:service-function-path/sfc-sfp:name"; 579 } 580 description 581 "Service function path name"; 583 } 584 leaf classifier{ 585 type leafref{ 586 path "/sfc-sfp:service-function-paths" 587 +"/sfc-sfp:service-function-path/sfc-sfp:classifier"; 588 } 589 description 590 "SFC classifier."; 591 } 592 list sf-data-plane-locator { 593 key "locator-name"; 594 leaf locator-name{ 595 type leafref{ 596 path "/sfc-sf:service-functions/sfc-sf:service-function" 597 +"/sfc-sf:sf-data-plane-locator/sfc-sf:name"; 598 } 599 description 600 "The sf data plane locator name"; 601 } 602 leaf service-function-forwarder{ 603 type leafref{ 604 path "/sfc-sff:service-function-forwarders" 605 +"/sfc-sff:service-function-forwarder/sfc-sff:name"; 606 } 607 description 608 "The name of teh service function forwarder"; 609 } 610 description 611 "List for service function data plane locator"; 612 } 613 description 614 "augment connectionless oam model to derive service 615 function oam yang model"; 616 } 618 augment "/coam-methods:continuity-check/coam-methods:input" 619 +"/coam-methods:destination-tp/coam-methods:tp-address"{ 620 case sfc-address{ 622 leaf sf-name { 623 type leafref{ 624 path "/sfc-sf:service-functions/sfc-sf:service-function" 625 +"/sfc-sf:name"; 626 } 627 description 628 "The name of the service function."; 629 } 631 leaf sfc-name { 632 type leafref{ 634 path "/sfc-sfc:service-function-chains" 635 +"/sfc-sfc:service-function-chain/sfc-sfc:name"; 636 } 637 description 638 "service function chain name"; 639 } 641 leaf sfp-name { 642 type leafref{ 643 path "/sfc-sfp:service-function-paths" 644 +"/sfc-sfp:service-function-path/sfc-sfp:name"; 645 } 646 description 647 "Service function path name"; 648 } 650 leaf classifier{ 651 type leafref{ 652 path "/sfc-sfp:service-function-paths" 653 +"/sfc-sfp:service-function-path/sfc-sfp:classifier"; 654 } 655 description 656 "SFC classifier"; 657 } 658 leaf service-function-forwarder{ 659 type leafref{ 660 path "/sfc-sff:service-function-forwarders" 661 +"/sfc-sff:service-function-forwarder/sfc-sff:name"; 662 } 663 description 664 "service function forwarder"; 665 } 666 description 667 "SFC address"; 668 } 669 description 670 "Augment base with SFC address"; 671 } 673 augment "/coam-methods:path-discovery/coam-methods:input" 674 +"/coam-methods:destination-tp/coam-methods:tp-address"{ 675 case sfc-address{ 677 leaf sf-name { 678 type leafref{ 679 path "/sfc-sf:service-functions/sfc-sf:service-function" 680 +"/sfc-sf:name"; 681 } 682 description 683 "The name of the service function."; 684 } 686 leaf sfc-name { 687 type leafref{ 689 path "/sfc-sfc:service-function-chains" 690 +"/sfc-sfc:service-function-chain/sfc-sfc:name"; 691 } 692 description 693 "service function chain name"; 694 } 696 leaf sfp-name { 697 type leafref{ 698 path "/sfc-sfp:service-function-paths" 699 +"/sfc-sfp:service-function-path/sfc-sfp:name"; 700 } 701 description 702 "Service function path name"; 703 } 705 leaf classifier{ 706 type leafref{ 707 path "/sfc-sfp:service-function-paths" 708 +"/sfc-sfp:service-function-path/sfc-sfp:classifier"; 709 } 710 description 711 "SFC classifier"; 712 } 713 leaf service-function-forwarder{ 714 type leafref{ 715 path "/sfc-sff:service-function-forwarders" 716 +"/sfc-sff:service-function-forwarder/sfc-sff:name"; 717 } 718 description 719 "Service function forwarder"; 720 } 721 description 722 "SFC address"; 723 } 724 description 725 "Augment base model with SFC address"; 726 } 727 } 728 730 7. Security Considerations 732 TBD. 734 8. IANA Considerations 736 TBD. 738 9. References 740 9.1. Normative References 742 [IEEE.802.1Q-2011] 743 Institute of Electrical and Electronics Engineers, "Media 744 Access Control (MAC) Bridges and Virtual Bridged Local 745 Area Networks", IEEE Standard 802.1Q, August 2011. 747 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 748 Requirement Levels", March 1997. 750 [RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 751 Specifications: ABNF", RFC 2234, DOI 10.17487/RFC2234, 752 November 1997, . 754 9.2. Informative References 756 [I-D.ietf-lime-yang-connectionless-oam] 757 Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan, 758 "Generic YANG Data Model for Connectionless Operations, 759 Administration, and Maintenance(OAM) protocols", draft- 760 ietf-lime-yang-connectionless-oam-03 (work in progress), 761 December 2016. 763 [I-D.ietf-lime-yang-connectionless-oam-methods] 764 Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan, 765 "Retrieval Methods YANG Data Model for Connectionless 766 Operations, Administration, and Maintenance(OAM) 767 protocols", draft-ietf-lime-yang-connectionless-oam- 768 methods-00 (work in progress), October 2016. 770 [I-D.ietf-sfc-oam-framework] 771 Aldrin, S., Krishnan, R., Akiya, N., Pignataro, C., and A. 772 Ghanwani, "Service Function Chaining Operation, 773 Administration and Maintenance Framework", draft-ietf-sfc- 774 oam-framework-01 (work in progress), February 2016. 776 [I-D.penno-sfc-yang] 777 Penno, R., Quinn, P., Zhou, D., and J. Li, "Yang Data 778 Model for Service Function Chaining", draft-penno-sfc- 779 yang-15 (work in progress), June 2016. 781 [RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu, 782 D., and S. Mansfield, "Guidelines for the Use of the "OAM" 783 Acronym in the IETF", BCP 161, RFC 6291, 784 DOI 10.17487/RFC6291, June 2011, 785 . 787 [Y.1731] "OAM functions and mechanisms for Ethernet based 788 networks", ITU G.8013/Y.1731, July 2011. 790 Authors' Addresses 792 Rong Gu 793 China Mobile 794 32 Xuanwumen West Ave, Xincheng District 795 Beijing 100053 796 China 798 Email: gurong@chinamobile.com 800 Liang Xia 801 Huawei Technologies 802 101 Software Avenue, Yuhua District 803 Nanjing 804 China 806 Email: frank.xialiang@huawei.com 808 Zitao Wang 809 Huawei Technologies 810 101 Software Avenue, Yuhua District 811 Nanjing 812 China 814 Email: wangzitao@huawei.com 815 Deepak Kumar 816 Cisco Systems 817 510 McCarthy Blvd Milpitas 818 CA 819 USA 821 Email: dekumar@cisco.com 823 Mohamed Boucadair 824 France Telecom 825 Rennes 35000 826 France 828 Email: mohamed.boucadair@orange.com