[media-types] John Scudder's No Objection on draft-ietf-mediaman-toplevel-03: (with COMMENT)
John Scudder via Datatracker <noreply@ietf.org> Tue, 19 September 2023 00:09 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: media-types@ietf.org
Delivered-To: media-types@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F09DC151097; Mon, 18 Sep 2023 17:09:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mediaman-toplevel@ietf.org, mediaman-chairs@ietf.org, media-types@ietf.org, harald@alvestrand.no, harald@alvestrand.no
X-Test-IDTracker: no
X-IETF-IDTracker: 11.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <169508218418.33822.5404879303379696314@ietfa.amsl.com>
Date: Mon, 18 Sep 2023 17:09:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/fvr52Tg84RFQ6eJ5gwZDcqlOrnU>
Subject: [media-types] John Scudder's No Objection on draft-ietf-mediaman-toplevel-03: (with COMMENT)
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 19 Sep 2023 00:09:44 -0000
John Scudder 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://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-mediaman-toplevel/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for this document! I support Paul Wouters’ DISCUSS. Generally, the IANA Considerations section is a little less comprehensive than I’m used to seeing, but I guess the sponsoring AD and IANA will be able to work with the authors if they think changes are needed. Also, to elaborate on one of Paul’s points, it seems to me all the SHOULD in “The registration and actual use of a certain number of subtypes under the new top-level type SHOULD be expected. At a minimum, one actual subtype SHOULD exist. But the existence of a single subtype SHOULD not be enough; it SHOULD be clear that new similar types may appear in the future. Otherwise, the creation of a new top-level type is most probably not justified” are misplaced. They SHOULD be “should”. Finally, a nit: In Section 3, you don’t want “shortly describes” but “briefly describes”.
- [media-types] John Scudder's No Objection on draf… John Scudder via Datatracker
- Re: [media-types] John Scudder's No Objection on … Martin J. Dürst