Type name: application Subtype name: yang-patch+json Required parameters: None Optional parameters: None Encoding considerations: 8-bit The "utf-8" charset is always used for this type. Each conceptual YANG data node is encoded according to [draft-ietf-netmod-yang-json]. A metadata annotation is encoded according to [draft-ietf-netmod-yang-metadata] In addition, the "yang-patch" YANG Patch template found in [RFC8072] defines the structure of a YANG Patch request. Security considerations: Security considerations related to the generation and consumption of RESTCONF messages are discussed in Section 5 of [RFC8072]. 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. Interoperability considerations: [RFC8072] specifies the format of conforming messages and the interpretation thereof. Published specification: RFC8072 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 the syntax and semantics 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): None Macintosh file type code(s): "TEXT" Person & email address to contact for further information: See the Authors' Addresses section of [RFC8072]. Intended usage: COMMON Restrictions on usage: N/A Author: See the Authors' Addresses section of [RFC8072]. Change controller: Internet Engineering Task Force (mailto:iesg&ietf.org). Provisional registration? (standards tree only): no