Re: [Netconf] review request for media type application/yang-patch+json
Sean Leonard <dev+ietf@seantek.com> Tue, 19 July 2016 11:02 UTC
Return-Path: <dev+ietf@seantek.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34ADB12D179 for <netconf@ietfa.amsl.com>; Tue, 19 Jul 2016 04:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham 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 M3NaCpS2zjYu for <netconf@ietfa.amsl.com>; Tue, 19 Jul 2016 04:02:11 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D110412D12E for <netconf@ietf.org>; Tue, 19 Jul 2016 04:02:10 -0700 (PDT)
Received: from [192.168.123.151] (unknown [75.83.2.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 86DC050AC8; Tue, 19 Jul 2016 07:02:09 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <CABCOCHRLoEr8FTBV8KzTXHjZj7MPULyMCXuXmxH8NqxCM0w_Tw@mail.gmail.com>
Date: Tue, 19 Jul 2016 04:02:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0ACD5A6-846C-4A6E-8386-525A1291447E@seantek.com>
References: <CABCOCHRLoEr8FTBV8KzTXHjZj7MPULyMCXuXmxH8NqxCM0w_Tw@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/VXoegX_fOjc_Gy2RgtUiUR9Usnc>
Cc: Netconf <netconf@ietf.org>, media-types@iana.org
Subject: Re: [Netconf] review request for media type application/yang-patch+json
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2016 11:02:14 -0000
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
- [Netconf] review request for media type applicatiā¦ Andy Bierman
- Re: [Netconf] review request for media type appliā¦ Sean Leonard