[media-types] Application/alto-* Media Types Registration Request for second document draft-ietf-alto-unified-props-new

Qin Wu <bill.wu@huawei.com> Fri, 03 December 2021 11:33 UTC

Return-Path: <bill.wu@huawei.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 570D33A0831; Fri, 3 Dec 2021 03:33:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 q38aZ53pazHH; Fri, 3 Dec 2021 03:33:17 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB73C3A0830; Fri, 3 Dec 2021 03:33:16 -0800 (PST)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4J59dV5tdKz67YJk; Fri, 3 Dec 2021 19:31:42 +0800 (CST)
Received: from canpemm100005.china.huawei.com (7.192.105.21) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Fri, 3 Dec 2021 12:33:13 +0100
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm100005.china.huawei.com (7.192.105.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Fri, 3 Dec 2021 19:33:11 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2308.020; Fri, 3 Dec 2021 19:33:11 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "media-types@ietf.org" <media-types@ietf.org>
CC: "draft-ietf-alto-unified-props-new.all@ietf.org" <draft-ietf-alto-unified-props-new.all@ietf.org>, "alto@ietf.org" <alto@ietf.org>, Francesca Palombini <francesca.palombini@ericsson.com>
Thread-Topic: Application/alto-* Media Types Registration Request for second document draft-ietf-alto-unified-props-new
Thread-Index: AdfoOWvdfjwhHIyZQLWzrB+M8TBmuw==
Date: Fri, 03 Dec 2021 11:33:11 +0000
Message-ID: <af98bfef00d446efb81c39c767b1cd1f@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.16]
Content-Type: multipart/alternative; boundary="_000_af98bfef00d446efb81c39c767b1cd1fhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/1hOBaaTVCfl-M3uHmu2a7Q5Ogzk>
Subject: [media-types] Application/alto-* Media Types Registration Request for second document draft-ietf-alto-unified-props-new
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 03 Dec 2021 11:33:22 -0000

Hello,
Here is the registration request of application/alto-* Media Types defined in section 12.1 of draft-ietf-alto-unified-props-new:
https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/
https://www.ietf.org/archive/id/draft-ietf-alto-unified-props-new-21.txt

I've included the details below.

Note that this document has already entered into IESG review phase. Francesca Palombini kindly reminds us and the authors of this draft to
send the media type registrations to the media-type mailing list for review before the document moves forward. Thanks Francesca.

-Qin (on behalf of chairs)
12.1.  application/alto-* Media Types

   This document updates the IANA Media Types Registry by registering
   two additional ALTO media types, listed in Table 1.

         +=============+=========================+===============+
         | Type        | Subtype                 | Specification |
         +=============+=========================+===============+
         | application | alto-propmap+json       | Section 7.1   |
         +-------------+-------------------------+---------------+
         | application | alto-propmapparams+json | Section 8.3   |
         +-------------+-------------------------+---------------+

                   Table 1: Additional ALTO Media Types.

   Type name:
      application

   Subtype name:
      This document registers multiple subtypes, as listed in Table 1.

   Required parameters:
      n/a

   Optional parameters:
      n/a

   Encoding considerations:
      Encoding considerations are identical to those specified for the
      "application/json" media type.  See [RFC8259].

   Security considerations:
      Security considerations related to the generation and consumption
      of ALTO Protocol messages are discussed in Section 15 of
      [RFC7285].

   Interoperability considerations:
      This document specifies formats of conforming messages and the
      interpretation thereof.

   Published specification:
      This document is the specification for these media types; see
      Table 1 for the section documenting each media type.

   Applications that use this media type:
      ALTO servers and ALTO clients either stand alone or are embedded
      within other applications.

   Additional information:
      Magic number(s):  n/a

      File extension(s):  This document uses the mime type to refer to
         protocol messages and thus does not require a file extension.

      Macintosh file type code(s):  n/a

   Person & email address to contact for further information:
      See Authors' Addresses section.

   Intended usage:
      COMMON

   Restrictions on usage:
      n/a

   Author:
      See Authors' Addresses section.

   Change controller:
      Internet Engineering Task Force (mailto:iesg@ietf.org).