NETCONF P. Andersson Internet-Draft Ionio Systems Intended status: Standards Track M. T. Valaphil Expires: 3 May 2027 Equinix 30 October 2026 Error List and Error Identities Registries for YANG-driven protocols draft-ietf-netconf-error-registries-01 Abstract This document defines IANA registries for the YANG Protocol Error List and YANG Protocol Error Identities. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 3 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Andersson & Valaphil Expires 3 May 2027 [Page 1] Internet-Draft YANG Procotol Error Registries October 2026 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 2 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 3.1. YANG Protocol Error List Registry . . . . . . . . . . . . 2 3.2. YANG Protocol Error Identities Registry . . . . . . . . . 7 4. Normative References . . . . . . . . . . . . . . . . . . . . 8 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction In order to have a canonical source for all errors and error identities for YANG-driven procotols such as NETCONF [RFC6241] and RESTCONF [RFC8040], two IANA registries are defined: YANG Protocol Error List and YANG Protocol Error Identities. These registries can be extended and updated as needed. It is an advantage for protocol evolution to have canonical sources to extend, instead of a set of documents that need to be compiled and referenced. 2. Conventions and Definitions 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. IANA Considerations 3.1. YANG Protocol Error List Registry This document defines a registry for the YANG Protocol Error List defined in Appendix A of [RFC6241] and an error from [RFC8783]. The name of the registry is "YANG Protocol Error List". The review policy for this registry is "IETF Review" [RFC8126]. The registry shall record the following for each entry: * error-tag, mandatory * error-app-tag, optional * error-type, mandatory * error-severity, mandatory Andersson & Valaphil Expires 3 May 2027 [Page 2] Internet-Draft YANG Procotol Error Registries October 2026 * error-info, optional: auxilary information described as data nodes (XML tags). * Description, mandatory * Reference: The reference for the document registering the value. Mandatory. The initial contents of the registry is defined in [RFC6241] and inlined below: error-tag: in-use error-type: protocol, application error-severity: error error-info: none Description: The request requires a resource that already is in use. Reference: RFC 6241 error-tag: invalid-value error-type: protocol, application error-severity: error error-info: none Description: The request specifies an unacceptable value for one or more parameters. Reference: RFC 6241 error-tag: too-big error-type: transport, rpc, protocol, application error-severity: error error-info: none Description: The request or response (that would be generated) is too large for the implementation to handle. Reference: RFC 6241 error-tag: missing-attribute error-type: rpc, protocol, application error-severity: error error-info: : name of the missing attribute : name of the element that is supposed to contain the missing attribute Description: An expected attribute is missing. Reference: RFC 6241 error-tag: bad-attribute error-type: rpc, protocol, application error-severity: error error-info: : name of the attribute w/ bad value Andersson & Valaphil Expires 3 May 2027 [Page 3] Internet-Draft YANG Procotol Error Registries October 2026 : name of the element that contains the attribute with the bad value Description: An attribute value is not correct; e.g., wrong type, out of range, pattern mismatch. Reference: RFC 6241 error-tag: unknown-attribute error-type: rpc, protocol, application error-severity: error error-info: : name of the unexpected attribute : name of the element that contains the unexpected attribute Description: An unexpected attribute is present. Reference: RFC 6241 error-tag: missing-element error-type: protocol, application error-severity: error error-info: : name of the missing element Description: An expected element is missing. Reference: RFC 6241 error-tag: bad-element error-type: protocol, application error-severity: error error-info: : name of the element w/ bad value Description: An element value is not correct; e.g., wrong type, out of range, pattern mismatch. Reference: RFC 6241 error-tag: unknown-element error-type: protocol, application error-severity: error error-info: : name of the unexpected element Description: An unexpected element is present. Reference: RFC 6241 error-tag: unknown-namespace error-type: protocol, application error-severity: error error-info: : name of the element that contains the unexpected namespace : name of the unexpected namespace Description: An unexpected namespace is present. Reference: RFC 6241 error-tag: access-denied error-type: protocol, application Andersson & Valaphil Expires 3 May 2027 [Page 4] Internet-Draft YANG Procotol Error Registries October 2026 error-severity: error error-info: none Description: Access to the requested protocol operation or data model is denied because authorization failed. Reference: RFC 6241 error-tag: lock-denied error-type: protocol error-severity: error error-info: : session ID of session holding the requested lock, or zero to indicate a non-NETCONF entity holds the lock Description: Access to the requested lock is denied because the lock is currently held by another entity. Reference: RFC 6241 error-tag: resource-denied error-type: transport, rpc, protocol, application error-severity: error error-info: none Description: Request could not be completed because of insufficient resources. Reference: RFC 6241 error-tag: rollback-failed error-type: protocol, application error-severity: error error-info: none Description: Request to roll back some configuration change (via rollback-on-error or operations) was not completed for some reason. Reference: RFC 6241 error-tag: data-exists error-type: application error-severity: error error-info: none Description: Request could not be completed because the relevant data model content already exists. For example, a "create" operation was attempted on data that already exists. Reference: RFC 6241 error-tag: data-missing error-type: application error-severity: error error-info: none Description: Request could not be completed because the relevant Andersson & Valaphil Expires 3 May 2027 [Page 5] Internet-Draft YANG Procotol Error Registries October 2026 data model content does not exist. For example, a "delete" operation was attempted on data that does not exist. Reference: RFC 6241 error-tag: operation-not-supported error-type: protocol, application error-severity: error error-info: none Description: Request could not be completed because the requested operation is not supported by this implementation. Reference: RFC 6241 error-tag: partial-operation error-type: application error-severity: error error-info: : identifies an element in the data model for which the requested operation has been completed for that node and all its child nodes. This element can appear zero or more times in the container. : identifies an element in the data model for which the requested operation has failed for that node and all its child nodes. This element can appear zero or more times in the container. : identifies an element in the data model for which the requested operation was not attempted for that node and all its child nodes. This element can appear zero or more times in the container. Reference: RFC 6241 Description: This error-tag is obsolete, and SHOULD NOT be sent by servers conforming to this document. Some part of the requested operation failed or was not attempted for some reason. Full cleanup has not been performed (e.g., rollback not supported) by the server. The error-info container is used to identify which portions of the application data model content for which the requested operation has succeeded (), failed (), or not been attempted (). Reference: RFC 6241 Andersson & Valaphil Expires 3 May 2027 [Page 6] Internet-Draft YANG Procotol Error Registries October 2026 error-tag: malformed-message error-type: rpc error-severity: error error-info: none Description: A message could not be handled because it failed to be parsed correctly. For example, the message is not well-formed XML or it uses an invalid character set. This error-tag is new in :base:1.1 and MUST NOT be sent to old clients. Reference: RFC 6241 error-tag: operation-failed error-app-tag: loop-detected error-type: transport, application error-info: : A copy of the Via header field when the loop was detected. Description: An infinite loop has been detected when forwarding a requests via a proxy. Reference: RFC 8783 3.2. YANG Protocol Error Identities Registry This document defines a registry for YANG Protocol Error Identities. The name of the registry is "YANG Protocol Error Identities". The review policy for this registry is "IETF Review" [RFC8126]. The registry shall record the following for each entry: * Identity name. * Base identity, if applicable. * Additional information. * The reference for the document registering the value. The initial contents of the registry is defined in [RFC8639] and [RFC8641] and inlined below: Andersson & Valaphil Expires 3 May 2027 [Page 7] Internet-Draft YANG Procotol Error Registries October 2026 dscp-unavailable encoding-unsupported filter-unsupported insufficient-resources replay-unsupported filter-unsupported insufficient-resources no-such-subscription no-such-subscription datastore-not-subscribable unchanging-selection period-unsupported update-too-big synchronization-size 4. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard, E., and A. Tripathy, "Subscription to YANG Notifications", RFC 8639, DOI 10.17487/RFC8639, September 2019, . Andersson & Valaphil Expires 3 May 2027 [Page 8] Internet-Draft YANG Procotol Error Registries October 2026 [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641, September 2019, . [RFC8783] Boucadair, M., Ed. and T. Reddy.K, Ed., "Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification", RFC 8783, DOI 10.17487/RFC8783, May 2020, . Acknowledgments TODO acknowledge. Authors' Addresses Per Andersson Ionio Systems Email: per.ietf@ionio.se Mithun Thai Valaphil Equinix Email: mithun.ietf@gmail.com Andersson & Valaphil Expires 3 May 2027 [Page 9]