Re: [media-types] [Ext] Zaheduzzaman Sarker's No Objection on draft-ietf-mediaman-toplevel-03: (with COMMENT)

Amanda Baber <amanda.baber@iana.org> Wed, 20 September 2023 20:49 UTC

Return-Path: <amanda.baber@iana.org>
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 7B360C14CE24; Wed, 20 Sep 2023 13:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rTWA6gucaXsF; Wed, 20 Sep 2023 13:49:25 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) (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 45935C14F749; Wed, 20 Sep 2023 13:49:25 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa3.lax.icann.org (8.17.1.24/8.17.1.22) with ESMTPS id 38KKnKDT003110 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 20 Sep 2023 20:49:20 GMT
Received: from MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.37; Wed, 20 Sep 2023 13:49:18 -0700
Received: from MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) by MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) with mapi id 15.02.1118.037; Wed, 20 Sep 2023 13:49:18 -0700
From: Amanda Baber <amanda.baber@iana.org>
To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mediaman-toplevel@ietf.org" <draft-ietf-mediaman-toplevel@ietf.org>, "mediaman-chairs@ietf.org" <mediaman-chairs@ietf.org>, "media-types@ietf.org" <media-types@ietf.org>, "harald@alvestrand.no" <harald@alvestrand.no>
Thread-Topic: [Ext] Zaheduzzaman Sarker's No Objection on draft-ietf-mediaman-toplevel-03: (with COMMENT)
Thread-Index: AQHZ66D8u+Tpd8GvpEy6nMTyKfu9CbAkMJWA
Date: Wed, 20 Sep 2023 20:49:18 +0000
Message-ID: <4CCF58B6-8516-4140-AF90-AD4A64576D70@iana.org>
References: <169520045838.25485.17668016917538304821@ietfa.amsl.com>
In-Reply-To: <169520045838.25485.17668016917538304821@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.63.22070801
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha256"; boundary="B_3778062557_1349692441"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.601,FMLib:17.11.176.26 definitions=2023-09-20_11,2023-09-20_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/mCcCVm1Upv1nLFI72DJ7I96cFj4>
Subject: Re: [media-types] [Ext] Zaheduzzaman Sarker's No Objection on draft-ietf-mediaman-toplevel-03: (with COMMENT)
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
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, 20 Sep 2023 20:49:29 -0000

IANA also prefers that the registration procedure be repeated in the IANA Considerations section. Also, the RFC 8126 term "Standards Action" should be used.

Thanks,
Amanda

On 9/20/23, 2:01 AM, "iesg on behalf of Zaheduzzaman Sarker via Datatracker" <iesg-bounces@ietf.org on behalf of noreply@ietf.org> wrote:

    Zaheduzzaman Sarker has entered the following ballot position for
    draft-ietf-mediaman-toplevel-03: No Objection

    When responding, please keep the subject line intact and reply to all
    email addresses included in the To and CC lines. (Feel free to cut this
    introductory paragraph, however.)


    Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!PtGJab4!9_juBFGzoFD7ttUitU-KIzteMTFlnXdpQy43IewVscJISi9kaKYHatT31NRsb8iSXpcEJ0jjY0dpU7Fb3z94NVM$ [ietf[.]org] 
    for more information about how to handle DISCUSS and COMMENT positions.


    The document, along with other ballot positions, can be found here:
    https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-mediaman-toplevel/__;!!PtGJab4!9_juBFGzoFD7ttUitU-KIzteMTFlnXdpQy43IewVscJISi9kaKYHatT31NRsb8iSXpcEJ0jjY0dpU7FbM4P3ltM$ [datatracker[.]ietf[.]org]



    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------

    Thanks for working on this specification. I think the additional considerations
    will be useful.

    In my review I have no TSV related issues (obviously :-) ). However, I think
    the IANA consideration section should say the registry policy is "RFC required"
    with "standard track" specification and point to
    (https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc8126.html*section-4.7__;Iw!!PtGJab4!9_juBFGzoFD7ttUitU-KIzteMTFlnXdpQy43IewVscJISi9kaKYHatT31NRsb8iSXpcEJ0jjY0dpU7FbnP3eqL4$ [rfc-editor[.]org]). Even though it puts
    a requirement saying - "Every new top-level type MUST be defined in a Standards
    Track RFC", I don't think it hurts repeating it in IANA consideration.