Re: [media-types] [Netconf] review request for media type application/yang-patch+json

application/yang-patch+json and application/yang-data+json look fine to me. Carry on.

Sean

> On Jul 8, 2016, at 4:10 PM, Andy Bierman <andy@yumaworks.com> wrote:
> 
> Hi,
> 
> Here is the revised application/yang-patch+json media type registration request
> 
> 
>            Type name: application
>       Subtype name: yang-patch+json
> 
>       Required parameters: None
> 
>       Optional parameters: None
> 
>      // RFC Ed.: replace draft-ietf-netmod-yang-json with
>      // the actual RFC reference for JSON Encoding of YANG Data,
>      //  and remove this note.
> 
>      // RFC Ed.: replace draft-ietf-netmod-yang-metadata with
>      // the actual RFC reference for JSON Encoding of YANG Data,
>      //  and remove this note.
> 
>      // RFC Ed.: replace 'XXXX' with the real RFC number,
>      // and remove this note
> 
>       Encoding considerations: 8-bit
>          Each conceptual YANG data node is encoded according to
>          [draft-ietf-netmod-yang-json]. A data annotation is
>          encoded according to [draft-ietf-netmod-yang-metadata]
>          In addition, the "yang-patch" YANG data template found
>          in [RFCXXXX] defines the structure of a YANG Patch request.
> 
>      // RFC Ed.: replace 'NN' in Section NN of [RFCXXXX] with the
>      // section number for Security Considerations
>      // Replace 'XXXX' in Section NN of [RFCXXXX] with the actual
>      // RFC number, and remove this note.
> 
>       Security considerations: Security considerations related
>          to the generation and consumption of RESTCONF messages
>          are discussed in Section NN of [RFCXXXX].
>          Additional security considerations are specific to the
>          semantics of particular YANG data models. Each YANG module
>          is expected to specify security considerations for the
>          YANG data defined in that module.
> 
>      // RFC Ed.: replace XXXX with actual RFC number and remove this
>      // note.
> 
>       Interoperability considerations: [RFCXXXX] specifies the format
>          of conforming messages and the interpretation thereof.
> 
>      // RFC Ed.: replace XXXX with actual RFC number and remove this
>      // note.
> 
>       Published specification: RFC XXXX
> 
>       Applications that use this media type: Instance document
>         data parsers used within a protocol or automation tool
>         that utilize the YANG Patch data structure.
> 
>       Fragment identifier considerations: The syntax and semantics
>          of fragment identifiers are the same as specified for the
>         "application/json" media type.
> 
>       Additional information:
> 
>         Deprecated alias names for this type: N/A
>         Magic number(s): N/A
>         File extension(s): .json
>         Macintosh file type code(s): "TEXT"
> 
>      // RFC Ed.: replace XXXX with actual RFC number and remove this
>      // note.
> 
>       Person & email address to contact for further information: See
>          Authors' Addresses section of [RFCXXXX].
> 
>       Intended usage: COMMON
> 
>       Restrictions on usage: N/A
> 
>      // RFC Ed.: replace XXXX with actual RFC number and remove this
>      // note.
> 
>       Author: See Authors' Addresses section of [RFCXXXX].
> 
>       Change controller: Internet Engineering Task Force
>          (mailto:
> iesg&ietf.org
> ).
> 
>       Provisional registration? (standards tree only): no
> 
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf