-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
184 additions
and
68 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,53 @@ | ||
| module ietf-trace-context-traceparent-version-1.0 { | ||
| namespace "urn:ietf:params:xml:ns:yang:traceparent:1.0"; | ||
| namespace "urn:ietf:params:xml:ns:yang:ietf-trace-context-traceparent-version-1.0"; | ||
| prefix ietf-trace-context-traceparent-version-1.0; | ||
|
|
||
| organization | ||
| "IETF NETCONF (Network Configuration) Working Group"; | ||
| contact | ||
| "WG Web: <https://datatracker.ietf.org/wg/netconf/> | ||
| WG List: <mailto:[email protected]> | ||
| Authors: Roque Gagliano | ||
| <mailto:[email protected]> | ||
| Jan Lindblad | ||
| <mailto:[email protected]> | ||
| Kristian Larsson | ||
| <mailto:[email protected]> | ||
| "; | ||
| description | ||
| "This module documents the support for trace context traceparent | ||
| versiom 1.0 in alignment with W3C versions: | ||
| https://www.w3.org/TR/2021/REC-trace-context-1-20211123 | ||
| Copyright (c) 2024 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 2024-11-07 { | ||
| description | ||
| "Initial revision"; | ||
| reference | ||
| "RFC XXXX: | ||
| NETCONF Extension to support Trace Context propagation"; | ||
| } | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,53 @@ | ||
| module ietf-trace-context-tracestate-version-1.0 { | ||
| namespace "urn:ietf:params:xml:ns:yang:tracestate:1.0"; | ||
| namespace "urn:ietf:params:xml:ns:yang:ietf-trace-context-tracestate-version-1.0"; | ||
| prefix ietf-trace-context-tracestate-version-1.0; | ||
|
|
||
| organization | ||
| "IETF NETCONF (Network Configuration) Working Group"; | ||
| contact | ||
| "WG Web: <https://datatracker.ietf.org/wg/netconf/> | ||
| WG List: <mailto:[email protected]> | ||
| Authors: Roque Gagliano | ||
| <mailto:[email protected]> | ||
| Jan Lindblad | ||
| <mailto:[email protected]> | ||
| Kristian Larsson | ||
| <mailto:[email protected]> | ||
| "; | ||
| description | ||
| "This module documents the support for trace context tracestate | ||
| versiom 1.0 in alignment with W3C versions: | ||
| https://www.w3.org/TR/2021/REC-trace-context-1-20211123 | ||
| Copyright (c) 2024 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 2024-11-07 { | ||
| description | ||
| "Initial revision"; | ||
| reference | ||
| "RFC XXXX: | ||
| NETCONF Extension to support Trace Context propagation"; | ||
| } | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,118 +1,135 @@ | ||
| module ietf-trace-context { | ||
| yang-version 1.1; | ||
| namespace "urn:ietf:params:xml:ns:yang:trace-context"; | ||
| namespace "urn:ietf:params:xml:ns:yang:ietf-trace-context"; | ||
| prefix ietf-trace-context; | ||
|
|
||
| import ietf-yang-structure-ext { | ||
| prefix sx; | ||
| reference "RFC8791: YANG Data Structure Extensions"; | ||
| reference | ||
| "RFC8791: YANG Data Structure Extensions"; | ||
| } | ||
|
|
||
| organization | ||
| "IETF NETCONF (Network Configuration) Working Group"; | ||
|
|
||
| "IETF NETCONF (Network Configuration) Working Group"; | ||
| contact | ||
| "WG Web: <https://datatracker.ietf.org/wg/netconf/> | ||
| WG List: <mailto:[email protected]>"; | ||
|
|
||
| description | ||
| WG List: <mailto:[email protected]> | ||
| Authors: Roque Gagliano | ||
| <mailto:[email protected]> | ||
| Jan Lindblad | ||
| <mailto:[email protected]> | ||
| Kristian Larsson | ||
| <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) 2024 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. | ||
| client and servers needs to share some specific contextual | ||
| information. This extensions aligns the NETCONF and RESTCONF | ||
| protocols to the W3C trace-context document: | ||
| https://www.w3.org/TR/2021/REC-trace-context-1-20211123 | ||
| Copyright (c) 2024 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 { | ||
|
|
||
| revision 2024-11-07 { | ||
| description | ||
| "Initial revision"; | ||
| reference | ||
| "RFC XXXX"; | ||
| "RFC XXXX: | ||
| NETCONF Extension to support Trace Context propagation"; | ||
| } | ||
|
|
||
| identity meta-error { | ||
| description "Base identity for otlp attribute errors."; | ||
| description | ||
| "Base identity for trace context attribute errors."; | ||
| } | ||
|
|
||
| identity missing { | ||
| base meta-error; | ||
| description "Indicates an attribute or header that is required | ||
| (in the current situation) is missing."; | ||
| 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."; | ||
| 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."; | ||
| 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"; | ||
| description | ||
| "Error type"; | ||
| } | ||
|
|
||
| sx:structure trace-context-error-info { | ||
| container trace-context-error-info { | ||
| description | ||
| "This error is returned by a NETCONF or RESTCONF server | ||
| when a client sends a NETCONF RPC with additonal | ||
| "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'"; | ||
| 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'."; | ||
| "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'."; | ||
| "Indicates the type of 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-trace-contextt:bad-format'."; | ||
| } | ||
| } | ||
| } | ||
|
|
||