IETF Logo Mail Archive

Re: [media-types] OpenApi media type registration questions

Sean Leonard <dev+ietf@seantek.com> Thu, 10 March 2016 00:45 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 3793E12DBCC for <media-types@ietfa.amsl.com>; Wed, 9 Mar 2016 16:45:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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 oGetOsBwqPCY for <media-types@ietfa.amsl.com>; Wed, 9 Mar 2016 16:45:45 -0800 (PST)
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 8F4F812DC03 for <media-types@ietf.org>; Wed, 9 Mar 2016 16:45:41 -0800 (PST)
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 9D98850A84 for <media-types@ietf.org>; Wed, 9 Mar 2016 19:45:40 -0500 (EST)
To: media-types@ietf.org
References: <SNT405-EAS138D1B69D14EDBB70D8B858A3B20@phx.gbl> <56DE624C.6020700@seantek.com> <SNT405-EAS2340EEA914B00AA87537FD8A3B40@phx.gbl>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <56E0C35B.9@seantek.com>
Date: Wed, 09 Mar 2016 16:44:11 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <SNT405-EAS2340EEA914B00AA87537FD8A3B40@phx.gbl>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/TXhMhK2zsR0hO-rPmmBNt3l14qM>
Subject: Re: [media-types] OpenApi media type registration questions
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: Thu, 10 Mar 2016 00:45:47 -0000

On 3/9/2016 4:29 PM, Darrel Miller wrote:
> Thanks for your feedback Sean.
>
>> Regarding +yaml, adding a new structured syntax registration requires
> Expert
>> Review. This means that an RFC is not required. Just fill out the template
> and
>> get it reviewed and approved.
>>
> I'm not sure I follow.  Where would I find this template to fill out that
> allows me to register a new suffix?  I don't see any reference to this
> process in RFC 6839.

RFC 6838 Section 6
https://tools.ietf.org/html/rfc6838#section-6

RFC 6839 has examples of the template actually instantiated in the text.

> Thanks again for your assistance.

You are welcome!

Sean

v2.23.0 | Report a Bug | By Email