Accepted, last comment. Balazs -----Original Message----- From: Benjamin Kaduk <[email protected]> Sent: 2021. október 7., csütörtök 23:45 To: Balázs Lengyel <[email protected]> Cc: The IESG <[email protected]>; Benoit Claise <[email protected]>; [email protected]; [email protected]; [email protected]; Kent Watsen <[email protected]> Subject: Re: Benjamin Kaduk's No Objection on draft-ietf-netmod-yang-instance-file-format-20: (with COMMENT)
Hi Balázs, Replies inline as well (where needed) On Thu, Oct 07, 2021 at 10:43:28AM +0000, Balázs Lengyel wrote: > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > Section 2 > > Two formats are specified based on the XML and JSON YANG encodings. > Later, as other YANG encodings (e.g., CBOR) are defined, further > instance data formats may be specified. > > I don't remember seeing a clear description of the specifics of these > two specified formats. (I assume it's just "use the XML/JSON encoding > for YANG structures", but I don't remember that stated anywhere.) > BALAZS: I added references to the relevant RFCs (7950, 7951, 8791) As the model starts with a YAN structure, I included YANG Data Structure Extensions RFC8791 too. I was hoping for a statement like "The file formats are achieved by applying the respective XML and JSON encoding rules for the YANG structure included in this document." BALAZS2: OK Thanks for all the replies and updates, Ben
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
