Thank you, Rob. Best regards,
Alexei Sadovnikov Principal System Architect Business Solutions AT&T Business AT&T Services, Inc. 550 Cochituate Road, Framingham, MA 01701 m 781.249.1516 | o 781.249.1516 | as5...@att.com<mailto:as5...@att.com> This e-mail and any files transmitted with it are AT&T property, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. From: "Rob Wilton (rwilton)" <rwil...@cisco.com> Date: Tuesday, February 22, 2022 at 10:21 AM To: Kent Watsen <kent+i...@watsen.net>, as549r <as5...@att.com> Cc: RFC Errata System <rfc-edi...@rfc-editor.org>, "m...@tail-f.com" <m...@tail-f.com>, "war...@kumari.net" <war...@kumari.net>, Joel Jaeggli <joe...@bogus.com>, Lou Berger <lber...@labn.net>, Randy Presuhn <randy_pres...@alumni.stanford.edu>, "netmod@ietf.org" <netmod@ietf.org> Subject: RE: [netmod] [Technical Errata Reported] RFC7950 (6855) Hi, I basically agree with Kent, Randy, Andy. Alexi, Thanks for flagging this, and the subsequent discussion. I can see your point of view that MUST is used in other similar places, and I'm sure that in hindsight it would be nice if the language was used consistently in equivalent places. However, I don't think that the lack of a MUST statement makes the other text any less normative, or ambiguous. In particular, there is this paragraph of RFC 8174 that updates RFC 2119: o These words can be used as defined here, but using them is not required. Specifically, normative text does not require the use of these key words. They are used for clarity and consistency when that is what's wanted, but a lot of normative text does not use them and is still normative. Hence, I have rejected this errata. If you find the current text to be confusing and think that it would be helpful to clarify this is a future version of this specification, then I would suggest that you open an issue here (https://urldefense.com/v3/__https://github.com/netmod-wg/yang-next/issues__;!!BhdT!nBhCe6YCJpOtCnmFwZ1oBRjxufTDTet131D2wG3sxyq6mSUshsyDWQzcIrvGvVlRg4l8NnqjPk8x$<https://urldefense.com/v3/__https:/github.com/netmod-wg/yang-next/issues__;!!BhdT!nBhCe6YCJpOtCnmFwZ1oBRjxufTDTet131D2wG3sxyq6mSUshsyDWQzcIrvGvVlRg4l8NnqjPk8x$> ), and it will get evaluated when we get to revising YANG. Regards, Rob -----Original Message----- From: Kent Watsen <kent+i...@watsen.net<mailto:kent+i...@watsen.net>> Sent: 22 February 2022 15:05 To: Rob Wilton (rwilton) <rwil...@cisco.com<mailto:rwil...@cisco.com>> Cc: SADOVNIKOV, ALEXEI <as5...@att.com<mailto:as5...@att.com>>; RFC Errata System <rfc-edi...@rfc-editor.org<mailto:rfc-edi...@rfc-editor.org>>; m...@tail-f.com<mailto:m...@tail-f.com>; war...@kumari.net<mailto:war...@kumari.net>; Joel Jaeggli <joe...@bogus.com<mailto:joe...@bogus.com>>; Lou Berger <lber...@labn.net<mailto:lber...@labn.net>>; Randy Presuhn <randy_pres...@alumni.stanford.edu<mailto:randy_pres...@alumni.stanford.edu>>; netmod@ietf.org<mailto:netmod@ietf.org> Subject: Re: [netmod] [Technical Errata Reported] RFC7950 (6855) Move to close this Errata without accepting it. Kent // as co-chair On Feb 17, 2022, at 5:53 PM, Randy Presuhn <randy_pres...@alumni.stanford.edu<mailto:randy_pres...@alumni.stanford.edu>> wrote: Hi - On 2022-02-17 1:01 PM, SADOVNIKOV, ALEXEI wrote: Randy, I definitively see that point, and the line of sparing usage can be somewhat subjective. In this case, I think use of “MUST” is justified RFC 2119 “actually required for interoperation or to limit behavior which has potential for causing harm”. Missing “MUST” statement does leave it open for interpretation, and That is simply not true. The existing text, e.g. "If the container defines RPC or action input or output parameters, these subelements are encoded in the same order as they are defined within the 'container' statement" leaves no room whatsoever for interpretation. misinterpretation will result in harm – XML payload which encapsulated without following these ordering rule can be rejected during decapsulation which does follow the rule. The XML payload is exchanged between client and server, often different implementations, hence different interpretation by different developers will lead to communication failure. The existing text is unambiguous, and provides no options in ordering. As such, I do not see how proposed errata is at odds with sparing usage provision, when it meets the described reason for usage. In other sections of this RFC (7.7.8., 7.8.5. and 7.9.5) “MUST” already used for same purpose; it is difficult to see how it is any more important in where ‘MUST’ is used vs to where it is not. Having said all that, the suggested errata can be reduced to exclude section 7.5.7 and second paragraph of 7.8.5 – in both of this cases the exact meaning can be referred from section 7.14.4 (as long as “MUST” is present in there). Would that resolve your concern of sparing usage? Such text-diddling seems utterly pointless to me. Randy -------------------- Best regards, *Alexei Sadovnikov* Principal System Architect Business Solutions AT&T Business *AT&T Services, Inc.* 550 Cochituate Road, Framingham, MA 01701 m 781.249.1516 | o 781.249.1516 | _as5...@att.com<mailto:_as5...@att.com> <mailto:as5...@att.com>_<mailto:as5...@att.com%3e_> This e-mail and any files transmitted with it are AT&T property, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. *From: *Randy Presuhn <randy_pres...@alumni.stanford.edu<mailto:randy_pres...@alumni.stanford.edu>> *Date: *Thursday, February 17, 2022 at 2:55 PM *To: *RFC Errata System <rfc-edi...@rfc-editor.org<mailto:rfc-edi...@rfc-editor.org>>, "m...@tail-f.com<mailto:m...@tail-f.com>" <m...@tail-f.com<mailto:m...@tail-f.com>>, "war...@kumari.net<mailto:war...@kumari.net>" <war...@kumari.net<mailto:war...@kumari.net>>, "rwil...@cisco.com<mailto:rwil...@cisco.com>" <rwil...@cisco.com<mailto:rwil...@cisco.com>>, "joe...@bogus.com<mailto:joe...@bogus.com>" <joe...@bogus.com<mailto:joe...@bogus.com>>, "kent+i...@watsen.net<mailto:kent+i...@watsen.net>" <kent+i...@watsen.net<mailto:kent+i...@watsen.net>>, "lber...@labn.net<mailto:lber...@labn.net>" <lber...@labn.net<mailto:lber...@labn.net>> *Cc: *as549r <as5...@att.com<mailto:as5...@att.com>>, "netmod@ietf.org<mailto:netmod@ietf.org>" <netmod@ietf.org<mailto:netmod@ietf.org>> *Subject: *Re: [netmod] [Technical Errata Reported] RFC7950 (6855) Hi - This seems like a remarkably pointless change, and arguably at odds with section 6 of RFC 2119. ("Imperatives of the type defined in this memo must be used with care and sparingly.") Randy On 2022-02-17 10:50 AM, RFC Errata System wrote: > The following errata report has been submitted for RFC7950, > "The YANG 1.1 Data Modeling Language". > > -------------------------------------- > You may review the report below and at: > https://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid6855__;!!BhdT!gZbsQDBeTveBJPSYBpHQOJS8wjZSUsguzZ6KwXq4NAiJ1cAOZgcko9_3wb4pLOxeGCFKcQFoi9XajHOG-NeqWtpDMmnMUI4$<https://urldefense.com/v3/__https:/www.rfc-editor.org/errata/eid6855__;!!BhdT!gZbsQDBeTveBJPSYBpHQOJS8wjZSUsguzZ6KwXq4NAiJ1cAOZgcko9_3wb4pLOxeGCFKcQFoi9XajHOG-NeqWtpDMmnMUI4$> > > <https://urldefense.com/v3/__https:/www.rfc-editor.org/errata/eid6855__;!!BhdT!gZbsQDBeTveBJPSYBpHQOJS8wjZSUsguzZ6KwXq4NAiJ1cAOZgcko9_3wb4pLOxeGCFKcQFoi9XajHOG-NeqWtpDMmnMUI4$> > > > -------------------------------------- > Type: Technical > Reported by: Alexei Sadovnikov <as5...@att.com<mailto:as5...@att.com> > <mailto:as5...@att.com><mailto:as5...@att.com%3e>> > > Section: GLOBAL > > Original Text > ------------- > 7.5. The "container" Statement > 7.5.7. XML Encoding Rules > > A container node is encoded as an XML element. The element's local > name is the container's identifier, and its namespace is the module's > XML namespace (see Section 7.1.3). > > The container's child nodes are encoded as subelements to the > container element. If the container defines RPC or action input or > output parameters, these subelements are encoded in the same order as > they are defined within the "container" statement. Otherwise, the > subelements are encoded in any order. > > 7.8. The "list" Statement > 7.8.5. XML Encoding Rules > > The list's key nodes are encoded as subelements to the list's > identifier element, in the same order as they are defined within the > "key" statement. > > The rest of the list's child nodes are encoded as subelements to the > list element, after the keys. If the list defines RPC or action > input or output parameters, the subelements are encoded in the same > order as they are defined within the "list" statement. Otherwise, > the subelements are encoded in any order. > . . . . . > > 7.14. The "rpc" Statement > 7.14.4. NETCONF XML Encoding Rules > > . . . . . > > Input parameters are encoded as child XML elements to the rpc node's > XML element, in the same order as they are defined within the "input" > statement. > > If the RPC operation invocation succeeded and no output parameters > are returned, the <rpc-reply> contains a single <ok/> element defined > in [RFC6241]. If output parameters are returned, they are encoded as > child elements to the <rpc-reply> element defined in [RFC6241], in > the same order as they are defined within the "output" statement. > > > 7.15. The "action" Statement > 7.15.2. NETCONF XML Encoding Rules > > . . . . . > > The <action> element contains a hierarchy of nodes that identifies > the node in the datastore. It MUST contain all containers and list > nodes in the direct path from the top level down to the list or > container containing the action. For lists, all key leafs MUST also > be included. The innermost container or list contains an XML element > that carries the name of the defined action. Within this element, > the input parameters are encoded as child XML elements, in the same > order as they are defined within the "input" statement. > > . . . . . > > If the action operation invocation succeeded and no output parameters > are returned, the <rpc-reply> contains a single <ok/> element defined > in [RFC6241]. If output parameters are returned, they are encoded as > child elements to the <rpc-reply> element defined in [RFC6241], in > the same order as they are defined within the "output" statement. > > > Corrected Text > -------------- > 7.5. The "container" Statement > 7.5.7. XML Encoding Rules > > . . . . . > > The container's child nodes are encoded as subelements to the > container element. If the container defines RPC or action input or > output parameters, these subelements MUST be encoded in the same order as > they are defined within the "container" statement. Otherwise, the > subelements are encoded in any order. > > 7.8. The "list" Statement > 7.8.5. XML Encoding Rules > > The list's key nodes MUST be encoded as subelements to the list's > identifier element, in the same order as they are defined within the > "key" statement. > > The rest of the list's child nodes are encoded as subelements to the > list element, after the keys. If the list defines RPC or action > input or output parameters, the subelements MUST be encoded in the same > order as they are defined within the "list" statement. Otherwise, > the subelements are encoded in any order. > . . . . . > > 7.14. The "rpc" Statement > 7.14.4. NETCONF XML Encoding Rules > > . . . . . > > Input parameters MUST be encoded as child XML elements to the rpc node's > XML element, in the same order as they are defined within the "input" > statement. > > If the RPC operation invocation succeeded and no output parameters > are returned, the <rpc-reply> contains a single <ok/> element defined > in [RFC6241]. If output parameters are returned, they MUST be encoded as > child elements to the <rpc-reply> element defined in [RFC6241], in > the same order as they are defined within the "output" statement. > > > 7.15. The "action" Statement > 7.15.2. NETCONF XML Encoding Rules > > . . . . . > > The <action> element contains a hierarchy of nodes that identifies > the node in the datastore. It MUST contain all containers and list > nodes in the direct path from the top level down to the list or > container containing the action. For lists, all key leafs MUST also > be included. The innermost container or list contains an XML element > that carries the name of the defined action. Within this element, > the input parameters MUST be encoded as child XML elements, in the same > order as they are defined within the "input" statement. > > . . . . . > > If the action operation invocation succeeded and no output parameters > are returned, the <rpc-reply> contains a single <ok/> element defined > in [RFC6241]. If output parameters are returned, they MUST be encoded as > child elements to the <rpc-reply> element defined in [RFC6241], in > the same order as they are defined within the "output" statement. > > Notes > ----- > The RFC 2119 keywords are missing in description of ordering for XML encoding rules for RPC, actions and references thereto and in additional instance of list keys encoding. > > Although the text of RFC suggests reading this as if "MUST" was present, without keyword it is open to interpretation if the sentences actually mean "MUST" or "SHOULD" or may be even "MAY". > > In other places discussing ordering, for example 7.7.8., 7.8.5. and 7.9.5. the "MUST" is actually present, hence proposed errata would make ordering description usage of keywords consistent. > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC7950 (draft-ietf-netmod-rfc6020bis-14) > -------------------------------------- > Title : The YANG 1.1 Data Modeling Language > Publication Date : August 2016 > Author(s) : M. Bjorklund, Ed. > Category : PROPOSED STANDARD > Source : Network Modeling > Area : Operations and Management > Stream : IETF > Verifying Party : IESG > > _______________________________________________ > netmod mailing list > netmod@ietf.org<mailto:netmod@ietf.org> <mailto:netmod@ietf.org> > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/netmod__;!!BhdT!gZbsQDBeTveBJPSYBpHQOJS8wjZSUsguzZ6KwXq4NAiJ1cAOZgcko9_3wb4pLOxeGCFKcQFoi9XajHOG-NeqWtpD91awGhs$<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/netmod__;!!BhdT!gZbsQDBeTveBJPSYBpHQOJS8wjZSUsguzZ6KwXq4NAiJ1cAOZgcko9_3wb4pLOxeGCFKcQFoi9XajHOG-NeqWtpD91awGhs$> > > <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/netmod__;!!BhdT!gZbsQDBeTveBJPSYBpHQOJS8wjZSUsguzZ6KwXq4NAiJ1cAOZgcko9_3wb4pLOxeGCFKcQFoi9XajHOG-NeqWtpD91awGhs$>
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
