Re: [media-types] [Netconf] request review of media type application/yang-patch+json
Sean Leonard <dev+ietf@seantek.com> Wed, 06 July 2016 18:55 UTC
Return-Path: <dev+ietf@seantek.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7BFB12D5AD for <media-types@ietfa.amsl.com>; Wed, 6 Jul 2016 11:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqEyi3fa8VDh for <media-types@ietfa.amsl.com>; Wed, 6 Jul 2016 11:55:34 -0700 (PDT)
Received: from pechora3.lax.icann.org (pechora3.icann.org [IPv6:2620:0:2d0:201::1:73]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 304B912D5AA for <media-types@ietf.org>; Wed, 6 Jul 2016 11:55:32 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id u66ItBIt008392 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <media-types@iana.org>; Wed, 6 Jul 2016 18:55:31 GMT
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A83E2509B5; Wed, 6 Jul 2016 14:55:10 -0400 (EDT)
To: Andy Bierman <andy@yumaworks.com>, media-types@iana.org
References: <CABCOCHR9AiQtiWO0gRzhDGe-XwnNdKQKm3+gdvsOBG1XYfi5Tg@mail.gmail.com>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <9137e33c-0b42-92f8-d55d-461617edc98a@seantek.com>
Date: Wed, 06 Jul 2016 11:54:37 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CABCOCHR9AiQtiWO0gRzhDGe-XwnNdKQKm3+gdvsOBG1XYfi5Tg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F7B927A0AABDB91957280512"
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Wed, 06 Jul 2016 18:55:32 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/clHRUbkEGecrMt5YEuonn78YiWg>
Cc: Netconf <netconf@ietf.org>
Subject: Re: [media-types] [Netconf] request review of media type application/yang-patch+json
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2016 18:55:36 -0000
Sorry I did not respond to this before. Looks good. Same comments as application/yang-data+json. The template is copied and pasted below for mailing list reference. Sean On 6/28/2016 7:32 PM, Andy Bierman wrote: > Hi, > > Please review and provide feedback on the media type registration > for the YANG Patch media type for the PATCH method. This is used by > the RESTCONF protocol. > > > https://tools.ietf.org/html/draft-ietf-netconf-yang-patch-09#section-4.2.2 > Type name: application Subtype name: yang-patch+json Required parameters: none Optional parameters: none // RFC Ed.: replacedraft-ietf-netmod-yang-json <https://tools.ietf.org/html/draft-ietf-netmod-yang-json> with // the actual RFC reference for JSON Encoding of YANG Data, // and remove this note. // RFC Ed.: replacedraft-ietf-netmod-yang-metadata <https://tools.ietf.org/html/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 <https://tools.ietf.org/html/draft-ietf-netmod-yang-json>]. A data annotation is encoded according to [draft-ietf-netmod-yang-metadata <https://tools.ietf.org/html/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 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 utilizes the YANG Patch data structure. Fragment identifier considerations: The fragment field in the request URI has no defined purpose. 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 (One of COMMON, LIMITED USE, or OBSOLETE.) 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
- [media-types] request review of media type applic… Andy Bierman
- Re: [media-types] [Netconf] request review of med… Sean Leonard