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

Cullen Jennings <fluffy@iii.ca> Tue, 27 October 2020 11:33 UTC

Return-Path: <fluffy@iii.ca>
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 217B13A005C for <dispatch@ietfa.amsl.com>; Tue, 27 Oct 2020 04:33:10 -0700 (PDT)
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 mvBmjTEi2ol5 for <dispatch@ietfa.amsl.com>; Tue, 27 Oct 2020 04:33:08 -0700 (PDT)
Received: from smtp127.ord1d.emailsrvr.com (smtp127.ord1d.emailsrvr.com [184.106.54.127]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81CBB3A0045 for <dispatch@ietf.org>; Tue, 27 Oct 2020 04:33:08 -0700 (PDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp8.relay.ord1d.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 29B9EC0229; Tue, 27 Oct 2020 07:33:07 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E6BCD14-ADE8-4358-ACA8-825C28F30D4A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <DM6PR16MB3912ECCB07E4E1875E20245EDE1C0@DM6PR16MB3912.namprd16.prod.outlook.com>
Date: Tue, 27 Oct 2020 05:33:06 -0600
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, Chris Ullrich <cullrich@immersion.com>
Message-Id: <8A14E9C6-2530-4E17-93DC-ECB943FAB94B@iii.ca>
References: <DM6PR16MB3912ECCB07E4E1875E20245EDE1C0@DM6PR16MB3912.namprd16.prod.outlook.com>
To: Yeshwant Muthusamy <ymuthusamy@immersion.com>
X-Mailer: Apple Mail (2.3445.104.17)
X-Classification-ID: c0282a2e-2eaf-497c-be40-b27f2afd4acc-1-1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/_BsQHC2MR_3a-fXRoz8U7py7oUI>
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: Tue, 27 Oct 2020 11:33:10 -0000

This is a very nicely written draft and I think the IETF is the best place to discuss this topic. I hope to see it get agenda time at and upcoming meeting. 

The biggest question I had while reading it was, what do we even do with top level media types at this point ?  What interoperability problem are we trying to solve? Should we deprecate top level media types ? How do we deal with that this media type is often embedded in a video stream?  Is this really different than game controller inputs and moves in real time settings? 

The need for things like the  hstr, hieee, henm, havc all make sense. But I wondering about what we really need the top level type for. Perhaps we should just have a top level type of “other”. I really have no idea of best answer to this but your draft did make me wonder. The flips side is that if top levels don’t mean much, there is no harm in defining a bunch of them. 



> On Oct 21, 2020, at 12:25 PM, Yeshwant Muthusamy <ymuthusamy@immersion.com> wrote:
> 
> Folks,
>  
> Re-posting with a more descriptive subjective line, since my previous post (see below) has not engendered any comments (yet).
>  
> https://datatracker.ietf.org/doc/draft-muthusamy-dispatch-haptics/ <https://datatracker.ietf.org/doc/draft-muthusamy-dispatch-haptics/>
>  
> Thanks,
> Yeshwant
>  
> Yeshwant Muthusamy, Ph.D. | Senior Director, Standards
> <image001.jpg>
> ymuthusamy@immersion.com <mailto:ymuthusamy@immersion.com> | +1 469-583-2171
>  
> From: Yeshwant Muthusamy 
> Sent: Tuesday, October 13, 2020 3:53 PM
> To: dispatch@ietf.org <mailto:dispatch@ietf.org>
> Cc: Chris Ullrich <cullrich@immersion.com <mailto:cullrich@immersion.com>>
> Subject: draft-muthusamy-dispatch-haptics-00.txt
>  
> I would like to initiate discussion on draft-muthusamy-dispatch-haptics:
>  
> https://datatracker.ietf.org/doc/draft-muthusamy-dispatch-haptics/ <https://datatracker.ietf.org/doc/draft-muthusamy-dispatch-haptics/>
>  
> An informal (and earlier) version of this document was discussed on the Media-Types mailing list (media-types@ietf.org <mailto:media-types@ietf.org>):
>  
> https://mailarchive.ietf.org/arch/msg/media-types/3cXb69ybEa65oCCIiHjl0MtGXVY/ <https://mailarchive.ietf.org/arch/msg/media-types/3cXb69ybEa65oCCIiHjl0MtGXVY/>
>  
> Look forward to your questions and comments.
>  
> Thanks,
> Yeshwant
>  
> Yeshwant Muthusamy, Ph.D. | Senior Director, Standards
> <image001.jpg>
> ymuthusamy@immersion.com <mailto:ymuthusamy@immersion.com> | +1 469-583-2171
>  
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org <mailto:dispatch@ietf.org>
> https://www.ietf.org/mailman/listinfo/dispatch <https://www.ietf.org/mailman/listinfo/dispatch>