Skip to content

Commit

Permalink
Cronjob - daily check of IETF modules. (#1579)
Browse files Browse the repository at this point in the history 
* Cronjob - daily check of IETF modules.

* Cronjob - daily check of IETF modules.

---------

Co-authored-by: Miroslav Kovac <[email protected]>
  • Loading branch information
@xorrkaz
xorrkaz and Miroslav Kovac authored Aug 22, 2024
1 parent b2d3aa4 commit c0f37c1
Show file tree
Hide file tree
Showing 11 changed files with 739 additions and 619 deletions.
4 changes: 2 additions & 2 deletions ...-YANG-modules/[email protected] → ...-YANG-modules/[email protected]
View file
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ module ietf-ac-svc {
This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices.";

revision 2023-11-13 {
revision 2024-08-06 {
description
"Initial revision.";
reference
Expand Down Expand Up @@ -1102,7 +1102,7 @@ module ietf-ac-svc {
information is created with a set of child ACs
to track dynamic AC information.";
}
leaf-list child-ac-ref {
leaf-list ac-child-ref {
type ac-svc:attachment-circuit-reference;
config false;
description
Expand Down
20 changes: 10 additions & 10 deletions ...G-modules/[email protected] → ...G-modules/[email protected]
View file
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ module ietf-bearer-svc {
This version of this YANG module is part of RFC xxx; see the
RFC itself for full legal notices.";

revision 2023-11-13 {
revision 2024-08-06 {
description
"Initial revision.";
reference
Expand Down Expand Up @@ -137,27 +137,27 @@ module ietf-bearer-svc {
is provided (e.g., geoproximity).";
}

identity syncPHY-type {
identity sync-phy-type {
description
"Base identity for physical layer synchronization.";
}

identity syncE {
base syncPHY-type;
identity sync-e {
base sync-phy-type;
description
"Sync Ethernet (SyncE).";
reference
"ITU-T G.781: Synchronization layer functions for frequency
synchronization based on the physical layer";
}

// Reusabel groupings
// Reusable groupings

grouping location-information {
description
"Basic location information";

leaf location-name {
leaf name {
type string;
description
"Provides a location name. This data node can be mapped,
Expand Down Expand Up @@ -260,8 +260,8 @@ module ietf-bearer-svc {

container locations {
description
"Retrieves the list of available provider locations for
terminating bearers.";
"Retrieves the available provider locations for terminating
bearers for a given customer.";
leaf customer-name {
type string;
description
Expand All @@ -286,7 +286,7 @@ module ietf-bearer-svc {
"Indicates the customer's ASN.";
}
list location {
key "location-name";
key "name";
config false;
description
"Reports the list of available locations.";
Expand Down Expand Up @@ -370,7 +370,7 @@ module ietf-bearer-svc {
leaf sync-phy-type {
when "../sync-phy-enabled='true'";
type identityref {
base syncPHY-type;
base sync-phy-type;
}
description
"Type of the physical layer synchronization.";
Expand Down
120 changes: 91 additions & 29 deletions ...-modules/[email protected] → ...-modules/[email protected]
View file
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ module ietf-http-client {
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";

revision 2024-07-08 {
revision 2024-08-15 {
description
"Initial version";
reference
Expand All @@ -63,29 +63,54 @@ module ietf-http-client {

// Features

feature proxy-connect {
feature tls-supported {
description
"Indicates that the server supports configuring HTTP
clients to connect to a remote HTTP server via a
proxy, per Section 9.3.6 of RFC 9110.";
"Indicates that the server supports configuring
HTTP client certificates.";
reference
"RFC 9110: HTTP Semantics";
}

feature tls-supported {
feature "http-11-supported" {
description
"Indicates that the server supports configuring
HTTP client certificates.";
clients to use the HTTP/1.1 protocol.";
reference
"RFC 9112: HTTP/1.1";
}

feature "http-2-supported" {
description
"Indicates that the server supports configuring
clients to use the HTTP/2 protocol.";
reference
"RFC 9113: HTTP/2";
}

feature "http-3-supported" {
if-feature "tls-supported";
description
"Indicates that the server supports configuring
clients to use the HTTP/3 protocol.";
reference
"RFC 9114 - HTTP/3";
}

feature proxy-connect {
description
"Indicates that the server supports configuring HTTP
clients to connect to a remote HTTP server via a
proxy, per Section 9.3.6 of RFC 9110.";
reference
"RFC 9110: HTTP Semantics";
}

// Groupings

grouping http-client-grouping {
grouping http-client-common-grouping {
description
"A reusable grouping for configuring an HTTP client.";

"A grouping for the 'http-client-grouping' and
its descendant node 'proxy-connect' to use.";
leaf uri {
nacm:default-deny-all;
type inet:uri;
Expand All @@ -105,31 +130,68 @@ module ietf-http-client {
reference
"RFC 3986 URI Generic Syntax";
}
leaf proxy-uri {
if-feature proxy-connect;
type inet:uri;
leaf protocol-versions {
type union {
type enumeration {
enum any {
description
"Indicates the client is willing to use any version";
}
}
type bits {
bit "http-11" {
if-feature "http-11-supported";
description
"Indicates the client is willing to use HTTP/1.1.";
}
bit "http-2" {
if-feature "http-2-supported";
description
"Indicates the client is willing to use HTTP/2.";
}
bit "http-3" {
if-feature "http-3-supported";
description
"Indicates the client is willing to use HTTP/3.";
}
}
}
default "any";
description
"Configures the proxy server the HTTP-client is to
connect through, per Section 9.3.6 of RFC 9110.
As described by RFC 3986, URIs encode:
- scheme: e.g., https
- userinfo: e.g., user@pass
- host: e.g., example.com
- port: e.g., 443
- path: e.g., /foo/bar
- query: e.g., ?query
- fragment: e.g., #fragment
";
reference
"RFC 3986 URI Generic Syntax
RFC 9110: HTTP Semantics";
"HTTP protocol versions the client supports.";
}
container tls-client-parameters {
if-feature "tls-supported";
description
"TLS client parameters.";
uses tlsc:tls-client-grouping;
uses tlsc:tls-client-grouping {
refine server-authentication {
presence
"Indicates that TLS-client parameters have been
configured. This statement is present so the
mandatory descendant nodes do not imply that
this node must be configured.";
}
}
}
}

grouping http-client-grouping {
description
"A reusable grouping for configuring an HTTP client.";
uses http-client-common-grouping;
container proxy-connect {
if-feature proxy-connect;
presence
"Indicates that the HTTP-client connects through a proxy.
This statement is present so the mandatory descendant
nodes do not imply that this node must be configured.";
uses http-client-common-grouping;
description
"Configures the proxy server the HTTP-client is to
connect through, per Section 9.3.6 of RFC 9110.";
reference
"RFC 9110: HTTP Semantics";
}
} // grouping http-client-grouping

Expand Down
13 changes: 5 additions & 8 deletions ...-modules/[email protected] → ...-modules/[email protected]
View file
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,7 @@ module ietf-http-server {
"WG Web: https://datatracker.ietf.org/wg/netconf
WG List: NETCONF WG list <mailto:[email protected]>
Author: Kent Watsen <mailto:[email protected]>";

description
"This module defines reusable groupings for HTTP servers that
can be used as a basis for specific HTTP server instances.
Expand All @@ -71,7 +72,7 @@ module ietf-http-server {
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";

revision 2024-07-08 {
revision 2024-08-15 {
description
"Initial version";
reference
Expand Down Expand Up @@ -113,7 +114,6 @@ module ietf-http-server {
reference
"RFC 9110: HTTP Semantics";
}

feature tls-supported {
description
"Indicates that the server supports configuring HTTP
Expand Down Expand Up @@ -229,10 +229,7 @@ module ietf-http-server {
choice transport {
mandatory true;
description
"Choice amongst various transports type. TCP, with and
without TLS are defined here, with 'feature' statements
so that they may be disabled. Other transports MAY be
augmented in as 'case' statements by future efforts.";
"Choice amongst various transports type.";
case tcp {
if-feature "tcp-supported";
container tcp {
Expand All @@ -246,7 +243,7 @@ module ietf-http-server {
refine "local-bind/local-port" {
default "80";
description
"The HTTP client will attempt to connect
"The HTTP server will attempt to connect
to the IANA-assigned well-known port for
'http' (80) if no value is specified.";
}
Expand All @@ -273,7 +270,7 @@ module ietf-http-server {
refine "local-bind/local-port" {
default "443";
description
"The HTTP client will attempt to connect
"The HTTP server will attempt to connect
to the IANA-assigned well-known port for
'https' (443) if no value is specified.";
}
Expand Down
14 changes: 6 additions & 8 deletions ...dules/[email protected] → ...dules/[email protected]
View file
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ module ietf-netconf-client {
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";

revision 2024-03-16 {
revision 2024-08-14 {
description
"Initial version";
reference
Expand Down Expand Up @@ -245,7 +245,7 @@ module ietf-netconf-client {
"TCP-level server parameters to listen for
NETCONF over SSH Call Home connections.";
uses tcps:tcp-server-grouping {
refine "local-port" {
refine "local-bind/local-port" {
default "4334";
description
"The NETCONF client will listen on the IANA-
Expand Down Expand Up @@ -279,7 +279,7 @@ module ietf-netconf-client {
"TCP-level server parameters to listen for
NETCONF over TLS Call Home connections.";
uses tcps:tcp-server-grouping {
refine "local-port" {
refine "local-bind/local-port" {
default "4335";
description
"The NETCONF client will listen on the IANA-
Expand Down Expand Up @@ -466,11 +466,9 @@ module ietf-netconf-client {
enum last-connected {
description
"Indicates that reconnections should start with
the endpoint last connected to. If no previous
connection has ever been established, then the
first endpoint configured is used. NETCONF
clients SHOULD be able to remember the last
endpoint connected to across reboots.";
the endpoint last connected to, if known. If
no previous connection is known, then the
first endpoint configured is used.";
}
enum random-selection {
description
Expand Down
Loading

0 comments on commit c0f37c1

Please sign in to comment.