Skip to content

Commit

Permalink
Merge pull request #1525 from yang-catalog/main
Browse files Browse the repository at this point in the history
Cronjob - daily update of yang files.
  • Loading branch information
SlavomirMazurPantheon authored Dec 17, 2023
2 parents c8f58a9 + 47cd282 commit beb4499
Show file tree
Hide file tree
Showing 4 changed files with 105 additions and 137 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ module ietf-eth-tran-service {
namespace "urn:ietf:params:xml:ns:yang:ietf-eth-tran-service";

prefix "ethtsvc";

import ietf-yang-types {
prefix "yang";
reference "RFC 6991 - Common YANG Data Types";
Expand All @@ -12,12 +13,10 @@ module ietf-eth-tran-service {
prefix "nw";
reference "RFC8345 - A YANG Data Model for Network Topologies";
}

import ietf-network-topology {
prefix "nt";
reference "RFC8345 - A YANG Data Model for Network Topologies";
}

import ietf-te-types {
prefix "te-types";
reference "RFC 8776 - Traffic Engineering Common YANG Types";
Expand Down Expand Up @@ -52,13 +51,9 @@ module ietf-eth-tran-service {
Haomian Zheng (zhenghaomian@huawei.com);
Italo Busi (italo.busi@huawei.com);
Aihua Guo (aihuaguo.ietf@gmail.com);
Anton Snitser (antons@sedonasys.com);0
Anton Snitser (asnizar@cisco.com);
Francesco Lazzeri (francesco.lazzeri@ericsson.com);
Yunbin Xu (xuyunbin@caict.ac.cn);
Yang Zhao (zhaoyangyjy@chinamobile.com);
Xufeng Liu (xufeng.liu.ietf@gmail.com);
Giuseppe Fioccola (giuseppe.fioccola@huawei.com);
Chaode Yu (yuchaode@huawei.com)
Chaode Yu (yuchaode@huawei.com);
";

description
Expand All @@ -78,7 +73,7 @@ module ietf-eth-tran-service {
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";

revision 2023-10-23 {
revision 2023-12-15 {
description
"version -04 as an WG document";
reference
Expand Down Expand Up @@ -206,6 +201,7 @@ module ietf-eth-tran-service {

description
"The second outermost VLAN tag to push/swap.";

uses vlan-write;
}
}
Expand Down Expand Up @@ -286,29 +282,25 @@ module ietf-eth-tran-service {
"The identifier of the access node in
the ETH TE topology.";
}

leaf access-node-uri {
type nw:node-id;
description
"The identifier of the access node in the network.";
}

leaf access-ltp-id {
type te-types:te-tp-id;
description
"The TE link termination point identifier, used
together with access-node-id to identify the
access LTP.";
}

leaf access-ltp-uri {
type nt:tp-id;
description
"The link termination point identifier in network topology,
used together with access-node-uri to identify the
access LTP.";
}

leaf access-role {
type identityref {
base etht-types:access-role;
Expand Down Expand Up @@ -480,7 +472,6 @@ module ietf-eth-tran-service {
description
"The Identifier of the ETH service.";
}

leaf user-label {
type string;
description
Expand Down Expand Up @@ -515,6 +506,7 @@ module ietf-eth-tran-service {
uses te-types:te-topology-identifier;

uses resilience-grouping;

list etht-svc-end-points {
key etht-svc-end-point-name;
description
Expand All @@ -526,7 +518,6 @@ module ietf-eth-tran-service {
description "threshold configuration for the E2E client signal";
uses alarm-shreshold-grouping;
}

container underlay {
description
"The unterlay tunnel information that carrying the
Expand Down Expand Up @@ -599,7 +590,6 @@ module ietf-eth-tran-service {
uses error-info-grouping;
}
}

grouping pm-state-grouping {
leaf latency {
description
Expand All @@ -608,32 +598,28 @@ module ietf-eth-tran-service {
units microsecond;
}
}

grouping error-info-grouping {
leaf error-code {
description "error code";
type uint16;
}

leaf error-description {
description "detail message of error";
type string;
}

leaf error-timestamp {
description "the date and time error is happened";
type yang:date-and-time;
}
}

grouping alarm-shreshold-grouping {
leaf latency-threshold {
description "a threshold for the E2E client signal service's
latency. Once the latency value exceed this threshold, an alarm
should be triggered.";
type uint32;
units microsecond;
}
}
}

/*
Expand Down Expand Up @@ -661,6 +647,7 @@ module ietf-eth-tran-service {
uses etht-types:etht-bandwidth-profiles;
}
}

list etht-svc-instances {
key etht-svc-name;
description
Expand Down Expand Up @@ -771,8 +758,8 @@ module ietf-eth-tran-service {
}
container second-tag {
must
'../outer-tag/tag-type = "etht-types:classify-s-vlan" and ' +
'tag-type = "etht-types:classify-c-vlan"'
'../outer-tag/tag-type = "etht-types:classify-s-vlan"' +
' and tag-type = "etht-types:classify-c-vlan"'
{
error-message
"
Expand Down Expand Up @@ -805,6 +792,7 @@ module ietf-eth-tran-service {
type string;
description "Identify a split horizon group";
}

uses bandwidth-profiles;

container vlan-operations {
Expand Down Expand Up @@ -949,6 +937,7 @@ module ietf-eth-tran-service {
}

}

grouping pw-segment-named-or-value-bandwidth-profile {
description
"A grouping to configure a bandwdith profile either by
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,13 +14,9 @@ module ietf-eth-tran-types {
Haomian Zheng (zhenghaomian@huawei.com);
Italo Busi (italo.busi@huawei.com);
Aihua Guo (aihuaguo.ietf@gmail.com);
Anton Snitser (antons@sedonasys.com);
Anton Snitser (asnizar@cisco.com);
Francesco Lazzeri (francesco.lazzeri@ericsson.com);
Yunbin Xu (xuyunbin@caict.ac.cn);
Yang Zhao (zhaoyangyjy@chinamobile.com);
Xufeng Liu (xufeng.liu.ietf@gmail.com);
Giuseppe Fioccola (giuseppe.fioccola@huawei.com);
Chaode Yu (yuchaode@huawei.com)
Chaode Yu (yuchaode@huawei.com);
";

description
Expand All @@ -40,7 +36,7 @@ module ietf-eth-tran-types {
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";

revision 2023-10-23 {
revision 2023-12-15 {
description
"version -05 as a WG draft";
reference
Expand Down Expand Up @@ -127,6 +123,7 @@ module ietf-eth-tran-types {
description
"RFC 2697 Bandwidth Profile";
}

identity rfc-2698-bwp {
base bandwidth-profile-type;
description
Expand Down Expand Up @@ -306,7 +303,8 @@ module ietf-eth-tran-types {
}
leaf coupling-flag {
type boolean;
/* Need to indicate that Coupling Flag is defined only for MEF 10
/* Need to indicate that Coupling Flag is defined only for
MEF 10
must
'../bw-profile-type = "mef-10-bwp"'
Expand All @@ -330,14 +328,16 @@ module ietf-eth-tran-types {

identity access-role {
description
"Indicating whether the access is a working or protection access.";
"Indicating whether the access is a working or protection
access.";
}

identity root-primary {
base access-role;
description
"Designates the primary root UNI of an E-Tree service, and may also
designates the UNI access role of E-LINE and E-LAN service.";
"Designates the primary root UNI of an E-Tree service, and may
also designates the UNI access role of E-LINE and E-LAN
service.";
}

identity root-backup {
Expand All @@ -352,20 +352,17 @@ module ietf-eth-tran-types {
"Designates the leaf UNI of an E-Tree service.";
}

identity leaf-edge {
base access-role;
description "";
}

identity performance {
description
"Placeholder for performance information, for future study.";
}

identity encapsulation-type {
description
"Indicating how the service is encapsulated (to PW), e.g, raw or tag. ";
"Indicating how the service is encapsulated (to PW), e.g, raw or
tag. ";
}

grouping pw-segement-bandwidth-profile-grouping {
description
"bandwidth profile grouping for PW segment. ";
Expand Down
Loading

0 comments on commit beb4499

Please sign in to comment.