[media-types] Roman Danyliw's No Objection on draft-ietf-mediaman-haptics-05: (with COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Mon, 18 September 2023 21:47 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 43A00C15108D; Mon, 18 Sep 2023 14:47:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mediaman-haptics@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: Roman Danyliw <rdd@cert.org>
Message-ID: <169507366026.50974.17839752784896297020@ietfa.amsl.com>
Date: Mon, 18 Sep 2023 14:47:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/JjwTOKTn_SsEHRSZ-4cfbt1QLn8>
Subject: [media-types] Roman Danyliw's No Objection on draft-ietf-mediaman-haptics-05: (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: Mon, 18 Sep 2023 21:47:40 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-mediaman-haptics-05: 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-haptics/



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

Thank you to Derrell Piper for the SECDIR review.

** Section 2.  Editorial. Is it worth mentioning that haptic signals are used
to make certain interfaces more accessible for visually or hearing impaired? 
Only entertainment seems to be highlighted in the current text.

** Section 2.4 and 2.5.  Editorial. This section makes references to numerous
industry stats.  Since that isn’t original analysis by the WG, consider
providing citations.

** Section 2.4.  Editorial.  This section seems to be trying to establish
market adoption.  The case is strongly made by all items in in the bulleted
list except the reference to W3C.  How does the definition of a standard
demonstrate haptics being a standard feature of adoption in consumer
electronics devices without explained the uptake of this work in W3C.

** Section 2.5
   While these subtypes have *not* been registered with IANA or
   standardized (yet), the prevalence of these haptic data formats in a
   large number of devices around the world, pre-dating the
   standardization of haptic tracks in ISOBMFF, provides a compelling
   argument for 'haptics' to be designated as a top-level media type:

Isn’t “ivs” being registered in Section 4.3.1

** Section 2.5.  Editorial. Consider providing a citation for ogg (just like
the other formats in the section).

** Section 2.5.
      -  In mobile haptic advertising (for W3C devices)

What are “W3C devices”?

** Section 2.6.
   These
   codes are not registered yet, but the plan is indeed to standardize
   these haptic coding formats in the near future.  Once standardized,
   these types should also be registered as subtypes of the 'haptics'
   top-level media type:

Isn’t “hmpg” and hjif” registered in Section 4.3.3 and 4.3.2 respectively? 
What is the standardization being waited for?