Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cronjob - daily update of yang files. #1445

Merged
merged 1 commit into from
Jul 7, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
118 changes: 118 additions & 0 deletions experimental/ietf-extracted-YANG-modules/[email protected]
Original file line number Diff line number Diff line change
@@ -0,0 +1,118 @@
module ietf-netconf-otlp-context {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:otlp-context";
prefix ietf-netconf-otlp-context;

import ietf-yang-structure-ext {
prefix sx;
reference "RFC8791: YANG Data Structure Extensions";
}

organization
"IETF NETCONF (Network Configuration) Working Group";

contact
"WG Web: <http://tools.ietf.org/wg/netconf/>
WG List: <mailto:[email protected]>";

description
"When propagating tracing information across applications,
client and servers needs to share some specific contextual
information. This NETCONF extensions aligns the NETCONF
protocol to the W3C trace-context document:
https://www.w3.org/TR/2021/REC-trace-context-1-20211123

Copyright (c) <year> IETF Trust and the persons identified as
authors of the code. All rights reserved.

Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).

This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices

The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.";

revision 2023-07-01 {
description
"Initial revision";
reference
"RFC XXXX";
}

identity meta-error {
description "Base identity for otlp attribute errors.";
}

identity missing {
base meta-error;
description "Indicates an attribute or header that is required
(in the current situation) is missing.";
}
identity bad-format {
base meta-error;
description "Indicates an attribute or header value where the
value is incorrectly formatted.";
}
identity processing-error {
base meta-error;
description "Indicates that the server encountered a processing
error while processing the attribute or header value.";
}

typedef meta-error-type {
type identityref {
base meta-error;
}
description "Error type";
}

sx:structure otlp-trace-context-error-info {
container otlp-trace-context-error-info {
description
"This error is returned by a NETCONF or RESTCONF server
when a client sends a NETCONF RPC with additonal
attributes or RESTCONF RPC with additional headers
for trace context processing, and there is an error
related to them. The server has aborted the RPC.";
leaf meta-name {
type string;
description
"The name of the problematic or missing meta information.
In NETCONF, the qualified XML attribute name.
In RESTCONF, the HTTP header name.
If a client sent a NETCONF RPC with the attribute
w3ctc:traceparent='incorrect-format'
this leaf would have the value 'w3ctc:traceparent'";
}
leaf meta-value {
type string;
description
"The value of the problematic meta information received
by the server.
If a client sent a NETCONF RPC with the attribute
w3ctc:traceparent='incorrect-format'
this leaf would have the value 'incorrect-format'.";
}
leaf error-type {
type meta-error-type;
description
"Indicates the type of OTLP meta information problem
detected by the server.
If a client sent an RPC annotated with the attribute
w3ctc:traceparent='incorrect-format'
this leaf might have the value
'ietf-netconf-otlp-context:bad-format'.";
}
}
}
}
Loading