Re: [media-types] [Netconf] request review of media type application/yang-data+xml

Sean Leonard <dev+ietf@seantek.com> Wed, 29 June 2016 03:23 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 AAC1912D9E7 for <media-types@ietfa.amsl.com>; Tue, 28 Jun 2016 20:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ruwlChTr0scF for <media-types@ietfa.amsl.com>; Tue, 28 Jun 2016 20:23:46 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C63312D9E4 for <media-types@ietf.org>; Tue, 28 Jun 2016 20:23:46 -0700 (PDT)
Received: from fallback-in2.mxes.net (fallback-out2.mxes.net [216.86.168.191]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id u5T3NPIl007601 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <media-types@iana.org>; Wed, 29 Jun 2016 03:23:46 GMT
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in2.mxes.net (Postfix) with ESMTP id 5439C2FDD3B for <media-types@iana.org>; Tue, 28 Jun 2016 23:07:27 -0400 (EDT)
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 3C212509B6; Tue, 28 Jun 2016 23:06:44 -0400 (EDT)
To: Andy Bierman <andy@yumaworks.com>, media-types@iana.org
References: <CABCOCHQJXtyhpfAgUn94FJ0WWyLvvKjC9inHpVY7-34GMJd=Bw@mail.gmail.com>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <d99b9905-6dcf-3f8c-1490-d3e6cd2e93df@seantek.com>
Date: Tue, 28 Jun 2016 20:06:27 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CABCOCHQJXtyhpfAgUn94FJ0WWyLvvKjC9inHpVY7-34GMJd=Bw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Delayed for 00:15:59 by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Wed, 29 Jun 2016 03:23:46 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/1kjBgFtPiPDUuZWRI3az7zjghss>
Cc: Netconf <netconf@ietf.org>
Subject: Re: [media-types] [Netconf] request review of media type application/yang-data+xml
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, 29 Jun 2016 03:23:49 -0000

It is considered customary to copy and paste *just* the registration 
text in this mailing list.
Here you go:

    Type name: application

    Subtype name: yang-data+xml

    Required parameters: none

    Optional parameters: none

   // RFC Ed.: replace draft-ietf-netmod-rfc6020bis with
   // the actual RFC reference for YANG 1.1, and remove this note.

    Encoding considerations: 8-bit
       Each conceptual YANG data node is encoded according to
       XML Encoding Rules and Canonical Format for the specific
       YANG data node type defined in [draft-ietf-netmod-rfc6020bis].

   // 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 YANG defined data structures.

    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): .xml
      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

On 6/28/2016 7:24 PM, Andy Bierman wrote:
> Hi,
>
> Please review and provide feedback on the revised media type registration
> for the RESTCONF protocol.
>
> https://tools.ietf.org/html/draft-ietf-netconf-restconf-14#section-11.3.1
>