My idea is similar to section 4.2 of RFC8072, i.e., define subtype name,e.g.,
yang-instance+xml, yang-instance+json
-Qin
-邮件原件-
发件人: Balázs Lengyel [mailto:balazs.leng...@ericsson.com]
发送时间: 2018年11月30日 21:00
收件人: Qin Wu; Joe Clarke; netmod@ietf.org
主题: yang-instance-file-format - do we n
OK, so lets go with option 3.
balazs
On 2018. 11. 30. 16:17, Juergen Schoenwaelder wrote:
On Fri, Nov 30, 2018 at 12:48:48PM +, Balázs Lengyel wrote:
Hello, Joe, Jurgen,
RFC6020 doesn't really register� file extensions, but rather media types.
I don't feel we need a new mediaty
On Fri, Nov 30, 2018 at 12:48:48PM +, Balázs Lengyel wrote:
>Hello, Joe, Jurgen,
>
>RFC6020 doesn't really register� file extensions, but rather media types.
>I don't feel we need a new mediatype for this as we really use json and
>xml. However I see it useful to document in th
Hello Qin,
Do you have a better suggestion for the file extension?
regards Balazs
On 2018. 11. 29. 2:53, Qin Wu wrote:
The abbreviation of YANG instance data yid may confuse with YANG identitifer
short name
"
YANG Identifier: Numeric object identifier, which is a fixed-length
nume
Hello, Joe, Jurgen,
RFC6020 doesn't really register file extensions, but rather
media types. I don't feel we need a new mediatype for this as we
really use json and xml. However I see it useful to document in
the file extension that this is not just any plain old X
