IETF Logo Mail Archive

Re: [media-types] DNS over HTTPS forthcoming Media Type Registration Notice

Sean Leonard <dev+ietf@seantek.com> Wed, 18 July 2018 20:51 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 D0C91130EA7 for <media-types@ietfa.amsl.com>; Wed, 18 Jul 2018 13:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 w5Zcm_aL5yKj for <media-types@ietfa.amsl.com>; Wed, 18 Jul 2018 13:51:19 -0700 (PDT)
Received: from pechora6.dc.icann.org (pechora6.icann.org [IPv6:2620:0:2830:201::1:72]) (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 70B681271FF for <media-types@ietf.org>; Wed, 18 Jul 2018 13:51:19 -0700 (PDT)
Received: from smtp-out-2.mxes.net (smtp-out-2.mxes.net [67.222.241.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora6.dc.icann.org (Postfix) with ESMTPS id C8F281E00FB for <media-types@iana.org>; Wed, 18 Jul 2018 20:51:18 +0000 (UTC)
Received: from Customer-MUA (mua.mxes.net [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A69992753F; Wed, 18 Jul 2018 16:50:55 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <CAHbrMsBMG_+X6s4G3O9ABh-Ehy+xoi-AenhpmRjhmwwaDU-33A@mail.gmail.com>
Date: Wed, 18 Jul 2018 16:50:54 -0400
Cc: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, Patrick McManus <mcmanus@ducksong.com>, Paul Hoffman <paul.hoffman@icann.org>, Adam Roach <adam@nostrum.com>, media-types@iana.org, David Lawrence <tale@dd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <991912F7-5CA4-4466-9FCB-BBA46E2F6F9E@seantek.com>
References: <CAHbrMsCupObmz5Ye7fdKSt3YOpUsPiH3ReV0UV0g3WuOQH0Zqg@mail.gmail.com> <63a538a6-d761-1372-ebd2-1a5d4a85d743@it.aoyama.ac.jp> <CAHbrMsBMG_+X6s4G3O9ABh-Ehy+xoi-AenhpmRjhmwwaDU-33A@mail.gmail.com>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
X-Sent-To: <bWVkaWEtdHlwZXNAaWFuYS5vcmc=>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/7lPKP07cSyJ01J1Q2ZSXKTKdSfo>
Subject: Re: [media-types] DNS over HTTPS forthcoming Media Type Registration Notice
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.27
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, 18 Jul 2018 20:51:22 -0000

Looks okay to me. Be sure that the published specification is replaced with RFC XXXX (this should be obvious, but usually it is denoted as [[RFCXXXX]] or [[NOTE to Editor, etc. etc.]]).

Sean

> On Jul 3, 2018, at 10:27 AM, Ben Schwartz <bemasc=40google.com@dmarc.ietf.org> wrote:
> 
> Here are the contents of Section 8.1, which matches the template form:
> 
>    MIME media type name: application
> 
>    MIME subtype name: dns-message
> 
>    Required parameters: n/a
> 
>    Optional parameters: n/a
> 
>    Encoding considerations: This is a binary format. The contents are a
>    DNS message as defined in RFC 1035. The format used here is for DNS
>    over UDP, which is the format defined in the diagrams in RFC 1035.
> 
>    Security considerations:  The security considerations for carrying
>    this data are the same for carrying DNS without encryption.
> 
>    Interoperability considerations:  None.
> 
>    Published specification:  This document.
> 
>    Applications that use this media type:
>      Systems that want to exchange full DNS messages.
> 
>    Additional information:
> 
>    Magic number(s):  n/a
> 
>    File extension(s):  n/a
> 
>    Macintosh file type code(s):  n/a
> 
>    Person & email address to contact for further information:
>       Paul Hoffman, paul.hoffman@icann.org
> 
>    Intended usage:  COMMON
> 
>    Restrictions on usage:  n/a
> 
>    Author:  Paul Hoffman, paul.hoffman@icann.org
> 
>    Change controller:  IESG
> 
> On Tue, Jul 3, 2018 at 5:51 AM Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
> Hello Ben,
> 
> If at all possible, please submit the registration templates here. That 
> greatly increases the chance to get (potentially valuable) comments.
> 
> Regards,   Martin.
> 
> On 2018/06/28 00:45, Ben Schwartz wrote:
> > Hello Media Type Experts,
> > 
> > In accordance with RFC 6838 Section 5.1, I would like to notify you that
> > the forthcoming draft "DNS over HTTPS" will request a new media type,
> > "application/dns-message".  See
> > https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-11#section-8.1.
> > 
> > I hope we're following this process correctly.
> > 
> > --Ben Schwartz, for the DOH Chairs
> 
> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types

v2.23.0 | Report a Bug | By Email