draft-ietf-teas-te-service-mapping-yang-00.txt   draft-ietf-teas-te-service-mapping-yang-01.txt 
skipping to change at page 1, line 22 skipping to change at page 1, line 22
Giuseppe Fioccola Giuseppe Fioccola
Huawei Huawei
Qin Wu Qin Wu
Huawei Huawei
March 5, 2019 March 5, 2019
Traffic Engineering and Service Mapping Yang Model Traffic Engineering and Service Mapping Yang Model
draft-ietf-teas-te-service-mapping-yang-00 draft-ietf-teas-te-service-mapping-yang-01
Abstract Abstract
This document provides a YANG data model to map customer service This document provides a YANG data model to map customer service
models (e.g., the L3VPM Service Model) to Traffic Engineering (TE) models (e.g., the L3VPM Service Model) to Traffic Engineering (TE)
models (e.g., the TE Tunnel or the Abstraction and Control of models (e.g., the TE Tunnel or the Abstraction and Control of
Traffic Engineered Networks Virtual Network model). This model is Traffic Engineered Networks Virtual Network model). This model is
referred to as TE Service Mapping Model and is applicable referred to as TE Service Mapping Model and is applicable
generically to the operator's need for seamless control and generically to the operator's need for seamless control and
management of their VPN services with TE tunnel support. management of their VPN services with TE tunnel support.
skipping to change at page 13, line 16 skipping to change at page 13, line 16
module: ietf-l1csm-te-service-mapping module: ietf-l1csm-te-service-mapping
augment /l1:l1-connectivity/l1:services/l1:service: augment /l1:l1-connectivity/l1:services/l1:service:
+-rw te-service-mapping! +-rw te-service-mapping!
augment /l1:l1-connectivity/l1:services/l1:service: augment /l1:l1-connectivity/l1:services/l1:service:
+-rw te-mapping +-rw te-mapping
+-rw map-type? identityref +-rw map-type? identityref
+-rw availability-type? identityref +-rw availability-type? identityref
+-rw (te)? +-rw (te)?
+-:(actn-vn) +-:(actn-vn)
| +-rw actn-vn-ref? -> /vn:actn/vn/vn-list/vn-id | +-rw actn-vn-ref? -> /vn:vn/vn-list/vn-id
+-:(te-topo) +-:(te-topo)
| +-rw vn-topology-id? te-types:te-topology-id | +-rw vn-topology-id? te-types:te-topology-id
| +-rw abstract-node? -> /nw:networks/network/node/node-id | +-rw abstract-node? -> /nw:networks/network/node/node-id
+-:(te-tunnel) +-:(te-tunnel)
+-rw te-tunnel-list* te:tunnel-ref +-rw te-tunnel-list* te:tunnel-ref
augment /l1:l1-connectivity/l1:services/l1:service/l1:endpoint-1: augment /l1:l1-connectivity/l1:services/l1:service/l1:endpoint-1:
+-rw (te)? +-rw (te)?
+-:(actn-vn) +-:(actn-vn)
| +-rw actn-vn-ref? -> /vn:actn/ap/access-point-list/access-point-id | +-rw actn-vn-ref? -> /vn:ap/access-point-list/access-point-id
+-:(te) +-:(te)
+-rw ltp? te-types:te-tp-id +-rw ltp? te-types:te-tp-id
augment /l1:l1-connectivity/l1:services/l1:service/l1:endpoint-2: augment /l1:l1-connectivity/l1:services/l1:service/l1:endpoint-2:
+-rw (te)? +-rw (te)?
+-:(actn-vn) +-:(actn-vn)
| +-rw actn-vn-ref? -> /vn:actn/ap/access-point-list/access-point-id | +-rw actn-vn-ref? -> /vn:ap/access-point-list/access-point-id
+-:(te) +-:(te)
+-rw ltp? te-types:te-tp-id +-rw ltp? te-types:te-tp-id
module: ietf-l2sm-te-service-mapping module: ietf-l2sm-te-service-mapping
augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/l2vpn-svc:vpn-service: augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/l2vpn-svc:vpn-service:
+-rw te-service-mapping! +-rw te-service-mapping!
augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/l2vpn-svc:vpn-service: augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/l2vpn-svc:vpn-service:
+-rw te-mapping +-rw te-mapping
+-rw map-type? identityref +-rw map-type? identityref
+-rw availability-type? identityref +-rw availability-type? identityref
+-rw (te)? +-rw (te)?
+-:(actn-vn) +-:(actn-vn)
| +-rw actn-vn-ref? -> /vn:actn/vn/vn-list/vn-id | +-rw actn-vn-ref? -> /vn:vn/vn-list/vn-id
+-:(te-topo) +-:(te-topo)
| +-rw vn-topology-id? te-types:te-topology-id | +-rw vn-topology-id? te-types:te-topology-id
| +-rw abstract-node? -> /nw:networks/network/node/node-id | +-rw abstract-node? -> /nw:networks/network/node/node-id
+-:(te-tunnel) +-:(te-tunnel)
+-rw te-tunnel-list* te:tunnel-ref +-rw te-tunnel-list* te:tunnel-ref
augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site/l2vpn-svc:site-network- augment /l2vpn-svc:l2vpn-svc/l2vpn-svc:sites/l2vpn-svc:site/l2vpn-svc:site-network-
accesses/l2vpn-svc:site-network-access: accesses/l2vpn-svc:site-network-access:
+-rw (te)? +-rw (te)?
+-:(actn-vn) +-:(actn-vn)
| +-rw actn-vn-ref? -> /vn:actn/ap/access-point-list/access-point-id | +-rw actn-vn-ref? -> /vn:ap/access-point-list/access-point-id
+-:(te) +-:(te)
+-rw ltp? te-types:te-tp-id +-rw ltp? te-types:te-tp-id
module: ietf-l3sm-te-service-mapping module: ietf-l3sm-te-service-mapping
augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services/l3vpn-svc:vpn-service: augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services/l3vpn-svc:vpn-service:
+-rw te-service-mapping! +-rw te-service-mapping!
augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services/l3vpn-svc:vpn-service: augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services/l3vpn-svc:vpn-service:
+-rw te-mapping +-rw te-mapping
+-rw map-type? identityref +-rw map-type? identityref
+-rw availability-type? identityref +-rw availability-type? identityref
+-rw (te)? +-rw (te)?
+-:(actn-vn) +-:(actn-vn)
| +-rw actn-vn-ref? -> /vn:actn/vn/vn-list/vn-id | +-rw actn-vn-ref? -> /vn:vn/vn-list/vn-id
+-:(te-topo) +-:(te-topo)
| +-rw vn-topology-id? te-types:te-topology-id | +-rw vn-topology-id? te-types:te-topology-id
| +-rw abstract-node? -> /nw:networks/network/node/node-id | +-rw abstract-node? -> /nw:networks/network/node/node-id
+-:(te-tunnel) +-:(te-tunnel)
+-rw te-tunnel-list* te:tunnel-ref +-rw te-tunnel-list* te:tunnel-ref
augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site/l3vpn-svc:site- augment /l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site/l3vpn-svc:site-
network-accesses/l3vpn-svc:site-network-access: network-accesses/l3vpn-svc:site-network-access:
+-rw (te)? +-rw (te)?
+-:(actn-vn) +-:(actn-vn)
| +-rw actn-vn-ref? -> /vn:actn/ap/access-point-list/access-point-id | +-rw actn-vn-ref? -> /vn:ap/access-point-list/access-point-id
+-:(te) +-:(te)
+-rw ltp? te-types:te-tp-id +-rw ltp? te-types:te-tp-id
7. YANG Data Models 7. YANG Data Models
The YANG codes are as follows: The YANG codes are as follows:
<CODE BEGINS> file "ietf-te-service-mapping-types@2018-12-30.yang" <CODE BEGINS> file "ietf-te-service-mapping-types@2019-03-05.yang"
module ietf-te-service-mapping-types { module ietf-te-service-mapping-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-service-mapping-types";
prefix "tsm"; prefix "tsm";
import ietf-te-types { import ietf-te-types {
prefix "te-types"; prefix "te-types";
} }
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
} }
import ietf-te { import ietf-te {
prefix "te"; prefix "te";
} }
import ietf-vn { import ietf-vn {
prefix "vn"; prefix "vn";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
skipping to change at page 15, line 32 skipping to change at page 15, line 25
contact contact
"Editor: Young Lee <leeyoung@huawei.com> "Editor: Young Lee <leeyoung@huawei.com>
Dhruv Dhody <dhruv.ietf@gmail.com> Dhruv Dhody <dhruv.ietf@gmail.com>
Qin Wu <bill.wu@huawei.com>"; Qin Wu <bill.wu@huawei.com>";
description description
"This module contains a YANG module for TE & Service mapping "This module contains a YANG module for TE & Service mapping
parameters and policies as a common grouping applicable to parameters and policies as a common grouping applicable to
variuous service models (e.g., L1CSM, L2SM, L3SM, etc.)"; variuous service models (e.g., L1CSM, L2SM, L3SM, etc.)";
revision 2018-12-30 { revision 2019-03-05 {
description description
"initial version."; "initial version.";
reference reference
"TBD"; "TBD";
} }
/* /*
* Identity for map-type * Identity for map-type
*/ */
identity map-type { identity map-type {
skipping to change at page 17, line 40 skipping to change at page 17, line 35
grouping te-ref { grouping te-ref {
description description
"The reference to TE."; "The reference to TE.";
choice te { choice te {
description description
"The TE"; "The TE";
case actn-vn { case actn-vn {
leaf actn-vn-ref { leaf actn-vn-ref {
type leafref { type leafref {
path "/vn:actn/vn:vn/vn:vn-list/vn:vn-id"; path "/vn:vn/vn:vn-list/vn:vn-id";
} }
description description
"The reference to ACTN VN"; "The reference to ACTN VN";
} }
} }
case te-topo { case te-topo {
leaf vn-topology-id{ leaf vn-topology-id{
type te-types:te-topology-id; type te-types:te-topology-id;
description description
"An identifier to the TE Topology Model "An identifier to the TE Topology Model
skipping to change at page 18, line 38 skipping to change at page 18, line 33
grouping te-endpoint-ref { grouping te-endpoint-ref {
description description
"The reference to TE endpoints."; "The reference to TE endpoints.";
choice te { choice te {
description description
"The TE"; "The TE";
case actn-vn { case actn-vn {
leaf actn-vn-ref { leaf actn-vn-ref {
type leafref { type leafref {
path "/vn:actn/vn:ap/vn:access-point-list" path "/vn:ap/vn:access-point-list"
+ "/vn:access-point-id"; + "/vn:access-point-id";
} }
description description
"The reference to ACTN VN"; "The reference to ACTN VN";
} }
} }
case te { case te {
leaf ltp { leaf ltp {
type te-types:te-tp-id; type te-types:te-tp-id;
description description
skipping to change at page 19, line 35 skipping to change at page 19, line 30
description description
"Availability Requirement for the Service"; "Availability Requirement for the Service";
} }
uses te-ref; uses te-ref;
} }
} }
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "ietf-l1csm-te-service-mapping@2018-10-05.yang" <CODE BEGINS> file "ietf-l1csm-te-service-mapping@2019-03-05.yang"
module ietf-l1csm-te-service-mapping { module ietf-l1csm-te-service-mapping {
namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping"; namespace "urn:ietf:params:xml:ns:yang:ietf-l1csm-te-service-mapping";
prefix "tm"; prefix "tm";
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix "tsm-types"; prefix "tsm-types";
} }
skipping to change at page 20, line 16 skipping to change at page 20, line 13
Working Group"; Working Group";
contact contact
"Editor: Young Lee <leeyoung@huawei.com> "Editor: Young Lee <leeyoung@huawei.com>
Dhruv Dhody <dhruv.ietf@gmail.com> Dhruv Dhody <dhruv.ietf@gmail.com>
Qin Wu <bill.wu@huawei.com>"; Qin Wu <bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of "This module contains a YANG module for the mapping of
Layer 1 Connectivity Service Module (L1CSM) to the TE and VN "; Layer 1 Connectivity Service Module (L1CSM) to the TE and VN ";
revision 2018-10-05 { revision 2019-03-05 {
description description
"initial version."; "initial version.";
reference reference
"TBD"; "TBD";
} }
/* /*
* Configuration data nodes * Configuration data nodes
*/ */
augment "/l1:l1-connectivity/l1:services/l1:service" { augment "/l1:l1-connectivity/l1:services/l1:service" {
skipping to change at page 21, line 12 skipping to change at page 21, line 7
augment "/l1:l1-connectivity/l1:services/l1:service/l1:endpoint-2" { augment "/l1:l1-connectivity/l1:services/l1:service/l1:endpoint-2" {
description description
"This augment is only valid for TE mapping -- "This augment is only valid for TE mapping --
endpoint-2 te-reference is added"; endpoint-2 te-reference is added";
uses tsm-types:te-endpoint-ref; uses tsm-types:te-endpoint-ref;
} }
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "ietf-l2sm-te-service-mapping@2018-10-05.yang" <CODE BEGINS> file "ietf-l2sm-te-service-mapping@2019-03-05.yang"
module ietf-l2sm-te-service-mapping { module ietf-l2sm-te-service-mapping {
namespace "urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping"; namespace "urn:ietf:params:xml:ns:yang:ietf-l2sm-te-service-mapping";
prefix "tm"; prefix "tm";
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix "tsm-types"; prefix "tsm-types";
} }
skipping to change at page 21, line 40 skipping to change at page 21, line 35
Working Group"; Working Group";
contact contact
"Editor: Young Lee <leeyoung@huawei.com> "Editor: Young Lee <leeyoung@huawei.com>
Dhruv Dhody <dhruv.ietf@gmail.com> Dhruv Dhody <dhruv.ietf@gmail.com>
Qin Wu <bill.wu@huawei.com>"; Qin Wu <bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of "This module contains a YANG module for the mapping of
Layer 2 Service Model (L1CSM) to the TE and VN "; Layer 2 Service Model (L1CSM) to the TE and VN ";
revision 2018-10-05 { revision 2019-03-05 {
description description
"initial version."; "initial version.";
reference reference
"TBD"; "TBD";
} }
/* /*
* Configuration data nodes * Configuration data nodes
*/ */
augment "/l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/l2vpn-svc:vpn-service" { augment "/l2vpn-svc:l2vpn-svc/l2vpn-svc:vpn-services/l2vpn-svc:vpn-service" {
description description
"l2sm augmented to include TE parameters and mapping"; "l2sm augmented to include TE parameters and mapping";
container te-service-mapping { container te-service-mapping {
presence "indicates l2 service to te mapping"; presence "indicates l2 service to te mapping";
description description
"Container to augment l2sm to TE parameters and mapping"; "Container to augment l2sm to TE parameters and mapping";
skipping to change at page 22, line 35 skipping to change at page 22, line 30
+"/l2vpn-svc:site-network-accesses/l2vpn-svc:site-network-access" { +"/l2vpn-svc:site-network-accesses/l2vpn-svc:site-network-access" {
description description
"This augment is only valid for TE mapping -- "This augment is only valid for TE mapping --
network-access te-reference is added"; network-access te-reference is added";
uses tsm-types:te-endpoint-ref; uses tsm-types:te-endpoint-ref;
} }
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "ietf-l3sm-te-service-mapping@2018-10-05.yang" <CODE BEGINS> file "ietf-l3sm-te-service-mapping@2019-03-05.yang"
module ietf-l3sm-te-service-mapping { module ietf-l3sm-te-service-mapping {
namespace "urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping"; namespace "urn:ietf:params:xml:ns:yang:ietf-l3sm-te-service-mapping";
prefix "tm"; prefix "tm";
import ietf-te-service-mapping-types { import ietf-te-service-mapping-types {
prefix "tsm-types"; prefix "tsm-types";
} }
import ietf-l3vpn-svc { import ietf-l3vpn-svc {
prefix "l3vpn-svc"; prefix "l3vpn-svc";
} }
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"Editor: Young Lee <leeyoung@huawei.com> "Editor: Young Lee <leeyoung@huawei.com>
Dhruv Dhody <dhruv.ietf@gmail.com> Dhruv Dhody <dhruv.ietf@gmail.com>
Qin Wu <bill.wu@huawei.com>"; Qin Wu <bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of "This module contains a YANG module for the mapping of
skipping to change at page 23, line 23 skipping to change at page 23, line 16
Working Group"; Working Group";
contact contact
"Editor: Young Lee <leeyoung@huawei.com> "Editor: Young Lee <leeyoung@huawei.com>
Dhruv Dhody <dhruv.ietf@gmail.com> Dhruv Dhody <dhruv.ietf@gmail.com>
Qin Wu <bill.wu@huawei.com>"; Qin Wu <bill.wu@huawei.com>";
description description
"This module contains a YANG module for the mapping of "This module contains a YANG module for the mapping of
Layer 3 Service Model (L3SM) to the TE and VN "; Layer 3 Service Model (L3SM) to the TE and VN ";
revision 2018-10-05 { revision 2019-03-05 {
description description
"initial version."; "initial version.";
reference reference
"TBD"; "TBD";
} }
/* /*
* Configuration data nodes * Configuration data nodes
*/ */
augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services/l3vpn-svc:vpn-service" { augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:vpn-services/l3vpn-svc:vpn-service" {
 End of changes. 25 change blocks. 
23 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/