Re: [dispatch] Proposal to add 'haptics' as a new top-level media type - Comments welcome [Was RE: draft-muthusamy-dispatch-haptics-00.txt]

worley@ariadne.com Thu, 22 October 2020 01:31 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFD5D3A0EF8 for <dispatch@ietfa.amsl.com>; Wed, 21 Oct 2020 18:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.984
X-Spam-Level:
X-Spam-Status: No, score=-0.984 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 k9RhzbawgCLX for <dispatch@ietfa.amsl.com>; Wed, 21 Oct 2020 18:31:04 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [69.252.207.38]) (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 E1EF03A0C31 for <dispatch@ietf.org>; Wed, 21 Oct 2020 18:31:03 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-06v.sys.comcast.net with ESMTP id VPFukz6SQjbDaVPQYkQ05P; Thu, 22 Oct 2020 01:30:02 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1603330202; bh=vk+RBNGxaIyhc9D5YjI9pdL4065pfdU2RxbKHBcTDAo=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=UZAadkgvMwnV6o7Q7tO3wFMo9qH2s76pzM852YqIxsNjNk6KTf2URK8Rz9VAAtMgw 2/dTF3qbIkYoZrJwTUqsur76Q90luriRenXmBzDaYLwtHjqGNGHQ9fDZhicOuVutFm HqTBBwCEdp5VpozR3cG91eOC7beujcEGgZNcURwctfRc38nx/UWgUaBLvfTKYCEnAH EIIdlYLp/nAV58f3JpO7rDF9Y95N6b2miF2ei9U285a1E7zssZXDjh2/fjjJMfDk/4 935s/CAg6O7Mk41xjwdE4pNnyx7kbUeP8TaM0DB6FmRfpIFqsHto1pnOV47JVeG7C4 +Ug+Xz+P0c6lA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-17v.sys.comcast.net with ESMTPA id VPQWk8Hxry9YdVPQXkRWFn; Thu, 22 Oct 2020 01:30:01 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 09M1TxGU014741; Wed, 21 Oct 2020 21:30:00 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 09M1Txxl014736; Wed, 21 Oct 2020 21:29:59 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Yeshwant Muthusamy <ymuthusamy@immersion.com>
Cc: dispatch@ietf.org, cullrich@immersion.com
In-Reply-To: <DM6PR16MB3912ECCB07E4E1875E20245EDE1C0@DM6PR16MB3912.namprd16.prod.outlook.com> (ymuthusamy@immersion.com)
Sender: worley@ariadne.com
Date: Wed, 21 Oct 2020 21:29:59 -0400
Message-ID: <87tuunavzc.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/ATu6ivQjpqTyz5I92fD9QoWGu1Y>
Subject: Re: [dispatch] Proposal to add 'haptics' as a new top-level media type - Comments welcome [Was RE: draft-muthusamy-dispatch-haptics-00.txt]
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 01:31:06 -0000

In general, this makes sense.  Reading your proposal quickly, I can see
two complications:

One is that in many current usages, haptic data is incorporated into the
same media stream as other media, making it questionable whether haptic
data would be in a stream that could be labeled as such.  I notice that
combined video/audio seems to be common, so this problem is probably
already being solved in that case.

Another is that it seems like few of these media formats are
non-secret.  There are registrations of media formats that are
patent-encumbered, but the specifics of those formats can be
documented.  What would really encourage support for a haptics data type
is one or more open standards.

I would probably be informative to prepare draft IANA registrations of
the haptics type and two or three subtypes and see how writing up the
registrations works out in practice.

Dale