Re: [media-types] [art] [dispatch] Status of Haptics I-D in DISPATCH?
"Murray S. Kucherawy" <superuser@gmail.com> Thu, 06 May 2021 19:34 UTC
Return-Path: <superuser@gmail.com>
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 A51F03A2DEF; Thu, 6 May 2021 12:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JldgK-5_Yb4f; Thu, 6 May 2021 12:34:18 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C8EB3A2DED; Thu, 6 May 2021 12:34:17 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id t6so1044670vsp.13; Thu, 06 May 2021 12:34:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ajpmPiDPvxbovwewJp/2yAZ+itLXo0sNab8A+PvMRTg=; b=OU2cWAQaaXVXcMWDNkKtSXxvG++qXgzcgNrRSnxG9wBIF59fQhz+kQfyqTJovAFxPb U4HfiZRwePuIN8hU2vVxFzsVRwD5m2Mc6ek5U4HKPvIA22EqLDJWJ8IhsyYFXpUBhosV EmMSliigubb7l7sX/IigrgIf9zRY1n+Zi5yPrTAQgWwbgVnEeW+CrW3gvrIqS1j5fcCB 0ziwU/yid5be93Dt/yexNun8CBgwx02ZUtBacYZ+fyzSIyWz8JsMyCNgFklMunGZ8NN2 03lwu+LRXDh8bFJ4GlhRDTO8zk3gTsOUpYrHF9KHc+qTVObcyeEvT+mqEFUF0/Jy5STP kGtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ajpmPiDPvxbovwewJp/2yAZ+itLXo0sNab8A+PvMRTg=; b=QII4ghjasnwWYcUwrJNOqMzWNES5xjMx+Wcseuk8mMZonZ/LVxy8RvZZWRzhSjSmlW xjvTPKc2zSm03FT+giyO1pT/nci/229CqyN81m8NImgXIMB1DAi+J3poBzJRm0pMWOp+ Rvuc3z9wvEY9qh/Li0dcQoQL+uzZ7N+qsobG8se+oE7vov0AJnfwauYGW8sBk1TFutld 72rKa1D5JhVK+2P2DZf3o3UVE6lJel8c8UDk2pCYH04IY9/GlHwayJp6JD3Qstyd44/z 4iPSLrlTOA5tAZR/Hjf150KMAa72JnQQQt2c24aJZ0cmrPTfBAtNKeA+LA0Tbbj+ihpG IlUw==
X-Gm-Message-State: AOAM5318/tNYoUn/9ZSlkYwqMXMSjyQmAHRtCWxvPm69C0xVfTWGvhc8 CjIJcesg5W/8jzeAFotozNj6a3hOzTk3pcshVo0=
X-Google-Smtp-Source: ABdhPJw+MMRn0V8GRoJW8WO0AsdgkZ3VlYyhy9SdA/FE4C9UeJuBy0FNteXN1fDYncUOoKkAz6dSjwRv0QMI0m5fBL8=
X-Received: by 2002:a67:f754:: with SMTP id w20mr2019528vso.54.1620329654718; Thu, 06 May 2021 12:34:14 -0700 (PDT)
MIME-Version: 1.0
References: <C1D837ED-4EB1-4C69-BA7F-7269B111A002@ericsson.com> <FB16C435B6EFF84534985905@JcK-HP5> <alpine.OSX.2.20.2105031645070.824@mac-allocchio3.garrtest.units.it> <01RYLBC0JRNS00AUHD@mauve.mrochek.com> <CA+9kkMC7OaQ_KP=SQSfrA6uQAt_MmY9hR3_kkhBHp==uvoXvRw@mail.gmail.com> <2FD10F8AE6D1B9C7D6545340@PSB> <MW3PR16MB3914440DE7F74C93CCD7D408DE5A9@MW3PR16MB3914.namprd16.prod.outlook.com> <ADF08E6531ABEAFAE9B64ADD@PSB> <DM6PR16MB39126AF1F75D8C33F95E3809DE5A9@DM6PR16MB3912.namprd16.prod.outlook.com> <AAC0BC03399D18D48DA6A26A@PSB>
In-Reply-To: <AAC0BC03399D18D48DA6A26A@PSB>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 06 May 2021 12:34:03 -0700
Message-ID: <CAL0qLwZyy1zWwjGUxLthiF_cLU=W4QhpBdB8s4vVcnKdFHUEDA@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Yeshwant Muthusamy <ymuthusamy@immersion.com>, Ted Hardie <ted.ietf@gmail.com>, Dispatch WG <dispatch@ietf.org>, dispatch chairs <dispatch-chairs@ietf.org>, Applications and Real-Time Area Discussion <art@ietf.org>, ART ADs <art-ads@ietf.org>, draft-muthusamy-dispatch-haptics@ietf.org, media-types@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007d134f05c1ae65f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/mF-lnweZOXKYQC5Q4J5PwqMkTT4>
Subject: Re: [media-types] [art] [dispatch] Status of Haptics I-D in DISPATCH?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 May 2021 19:34:24 -0000
Hi all, Thanks for this discussion. At a minimum, it reaffirms my decision not to sponsor this myself. :-) Francesca and I talked about it this morning after the IESG call, and decided that I'll take up the pen to write a draft charter based on this thread and circulate it for comments. Stay tuned. -MSK On Tue, May 4, 2021 at 6:16 PM John C Klensin <john-ietf@jck.com> wrote: > Yeshwant, > > Thanks. And thanks for confirming. I think I've said as much > as I can usefully say on the subject. > > best wishes, > john > > > --On Tuesday, May 4, 2021 22:44 +0000 Yeshwant Muthusamy > <ymuthusamy@immersion.com> wrote: > > > John, > > > > > > > > Thanks for the note. Taking each one of your two questions in > > order: > > > > > > > >>> * Does the ISO FDIS mention "haptics/" as top-level media > >>> type? > > > >>> If it does, that is a major IETF (and probably IAB) strategy > >>> question, not really a media registration one. > > > >>> And that question includes my concern about precedents of > >>> other SDOs squatting on names without including us actively > >>> in the development process. > > > > > > > > No. The ISOBMFF FDIS does not mention 'haptics/' as top-level > > media type. That said, it treats haptics in exactly the same > > way that it treats other top-level media types in Chapter 12 > > (audio, video, text, font, etc.) that have been recognized as > > top-level media types by IETF. To be more specific, our > > haptics proposal to ISOBMFF follows the same box hierarchy as > > the other top-level types: > > > > * Media handler is 'hapt' > > * Haptic Media Header is the NullMediaHeaderBox > > * Sample entry is the HapticSampleEntry > > > > > > > > So, there is no issue of ISO squatting on the 'haptics/' name > > or shutting IETF out from the development process. Our > > objective was to first introduce haptics as a top-level media > > type in ISOBMFF and then approach IETF with the proposal that > > we have in our I-D. For obvious reasons, I am unable to share > > the DAMD or FDIS documents on this mailing list, but I suspect > > those who are also members of MPEG can get access to it easily. > > > > > > > >>> * If the answer to that is "no", are there objections to > >>> more or less the WG approach Ned suggested that do not rely > >>> on the "influence the work of other SDOs" argument? > > > > > > > > Like I've said before, I am open to whatever mechanism the > > IETF decides to use to move the I-D forward. Given the work > > that has already been done in MPEG and the fact that we are > > approaching the FDIS ballot completion stage, I would assume > > that the IETF would take that into account *in some form* as > > it discusses the technical merits of the I-D. > > > > > > > > Thanks, > > > > Yeshwant > > > > > > > > Yeshwant Muthusamy, Ph.D. | Senior Director, Standards > > > > > > > > ymuthusamy@immersion.com | +1 469-583-2171 > > > > > > > > -----Original Message----- > > From: John C Klensin <john-ietf@jck.com> > > Sent: Tuesday, May 4, 2021 2:12 PM > > To: Yeshwant Muthusamy <ymuthusamy@immersion.com>; Ted Hardie > > <ted.ietf@gmail.com> Cc: Dispatch WG <dispatch@ietf.org>; > > dispatch-chairs@ietf.org; Applications and Real-Time Area > > Discussion <art@ietf.org>; ART ADs <art-ads@ietf.org>; > > draft-muthusamy-dispatch-haptics@ietf.org; media-types@ietf.org > > Subject: RE: [art] [dispatch] Status of Haptics I-D in > > DISPATCH? > > > > > > > > Yeshwant, > > > > > > > > Thanks. I did see your response to Ned, but only after > > sending my note. > > > > > > > > In what is perhaps an odd way, from my point of view, this is > > a good news. If the document is in FDIS ballot, all of the > > suggestions on the this list about how the IETF needs to be > > involved, and involved, with some accelerated procedure in > > order to influence the substantive decisions of other > > standards bodies are moot: as I am sure you know, just about > > the one way to make a substantive change in an ISO FDIS > > document is a "no" vote from a national member body, > > presumably after either objecting all along (which I presume > > didn't happen) or discovering some catastrophic substantive > > problem. No room for a "we think it would be better to do > > this than that" intervention from the IETF. > > > > > > > > So the only issues relevant to other SDOs now, AFAICT, is > > what, if anything, those documents (which, sadly, I don't have > > time to read and study today or even this week) have to say > > about media type names. If the answer is that they don't say > > anything, then the IETF should move with appropriate > > diligence, but should not put "get it done quickly" ahead of > > "do it right and get it right". If they say "the media type > > is 'haptics/', then the IETF is essentially dealing, not with > > your I-D/ proposal but with an accomplished fact. That would > > present us with a very different, and unpleasant, situation > > although, using an extension of Ted's argument, I think some > > of us would argue for registering it and trying to figure out > > how to avoid that happening again. If it references the I-D, > > I suspect we could get a note to the editorial team at ISO /CS > > and/or to the relevant Committee Manager and secretariat about > > getting that fixed even after FDIS balloting was completed > > (and might get our > > > > way) but whether that would be of substantive importance given > > that there is no chance of giving them a stable RFC number as > > a reference is, well, questionable. > > > > > > > > So now, with the "need to do this quickly to influence the > > substantive decisions of other SDOs" and the "the IETF needs > > to be influential about this in order to remain an actor in > > the multimedia game" aside because, whatever the IETF decides > > to do about those issues neither they, nor your I-D, have > > much, if anything, to do with them, it seems to me there are > > only two questions for the near term: > > > > > > > > * Does the ISO FDIS mention "haptics/" as top-level media type? > > > > If it does, that is a major IETF (and probably IAB) strategy > > question, not really a media registration one. And that > > question includes my concern about precedents of other SDOs > > squatting on names without including us actively in the > > development process. > > > > > > > > * If the answer to that is "no", are there objections to more > > or less the WG approach Ned suggested that do not rely on the > > "influence the work of other SDOs" argument? > > > > > > > > thanks, > > > > john > > > > > > > > --On Tuesday, May 4, 2021 17:37 +0000 Yeshwant Muthusamy > > <ymuthusamy@immersion.com<mailto:ymuthusamy@immersion.com>> > > wrote: > > > > > > > >> John, > > > >> > > > >> > > > >> > > > >> Regarding your comment: > > > >> > > > >> > > > >> > > > >>>> One reason is that I think it would be really unfortunate to > > > >>>> establish a precedent that the way to get a top-level media > >>>> type is > > > >>>> to invoke work going on at > > > >> > > > >>>> what I understand to be essentially the WG level in another > >>>> SDO and > > > >>>> then plead urgency. > > > >> > > > >>>> I would feel somewhat differently about an established, > >>>> recognized, > > > >>>> deployed international standard, but, as I understand > >>>> "active work > > > >>>> in .. > > > >> > > > >>>> MPEG Systems File Format sub-group", this is fairly far > >>>> from that. > > > >> > > > >> > > > >> > > > >> I would just reiterate/summarize what I wrote in my response > >> to Ned's > > > >> comment that you might have missed: the haptics proposal in > >> MPEG is no > > > >> longer at the "WG level" in the MPEG Systems File Format > >> sub-group. It > > > >> just progressed to FDIS ballot at MPEG134, which should > >> complete by > > > >> July 2021, at which point progression to IS (International > >> Standard) > > > >> is just a matter of procedure. More to the point, it has > >> passed two > > > >> rounds (CDAM and DAMD) of international balloting, with over > > > >> 20 ISO National Bodies casting their ballots in each round. No > > > >> objections to the haptics proposal were received in either > >> round. The > > > >> proposal left the "WG level" after MPEG131 in July > > > >> 2020 (for the CDAM/CD ballot) and moved to DAMD/DIS ballot > >> after > > > >> MPEG132 in October 2020 - a fact that was indeed mentioned in > >> v01 of > > > >> the I-D. > > > >> > > > >> > > > >> > > > >> The ISO link to the DAMD is here: > > > >> https://nam10.safelinks.protection.outlook.com/?url=https%3A% > >> 2F%2Flink > > > >> protect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fwww.iso.o > >> rg%252fst > > > >> andard%252f81604.html%26c%3DE%2C1%2CUgSwpQgu6oGkeYZ_zgagOzAfs > >> KcfbpK8nr > > > >> TJxn5cKPD91dPB2D-9v9C2UvBhUd72m1ZTUXkAaAt3-r9nTGAUhqz5d0N-gfp > >> REaQwDMRV > > > >> d7M%2C%26typo%3D1&data=04%7C01%7C%7C98c8e2a934bf4973859d0 > >> 8d90f309c > > > >> 50%7C4f05e41a59b8413aae19d5df3dfd0fb5%7C0%7C1%7C6375575237331 > >> 34949%7CU > > > >> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB > >> TiI6Ik1ha > > > >> WwiLCJXVCI6Mn0%3D%7C2000&sdata=%2BufQx8YrBdXpXyihiMQXkoVk > >> uVKQ6A5E3 > > > >> Qz3BQ97HVs%3D&reserved=0<https://nam10.safelinks.protecti > >> on.outloo > > > >> k.com/?url=https%3A%2F%2Fnam10.safelink%2F&data=04%7C01%7 > >> C%7C98c8e > > > >> 2a934bf4973859d08d90f309c50%7C4f05e41a59b8413aae19d5df3dfd0fb > >> 5%7C0%7C1 > > > >> %7C637557523733134949%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA > >> wMDAiLCJQ > > > >> IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=y > >> JoFSrPdS6 > > > >> 62usG5UdU7goWWsu%2BXvT7vKr0OxSXoTns%3D&reserved=0 > > > >> s.protection.outlook.com/?url=https%3A%2F%2Fwww.iso.org%2Fstan > > > >> dard%2F81604.html&data=04%7C01%7C%7Cb9be185f21b44df1b2f708d90e > > > >> 58c34b%7C4f05e41a59b8413aae19d5df3dfd0fb5%7C0%7C0%7C6375565966 > > > >> 69589491%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > > > >> 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwZKX%2B26U > > > >> WRq%2FPyzp19%2BGfS9J9qG8C6FvmLedDer5w0%3D&reserved=0>. > > > >> > > > >> > > > >> > > > >> To be clear, I have no issues with the other points you raise. > > > >> Just want to make sure that the discussion is based on current > > > >> reality. > > > > > > > > > > >
- Re: [media-types] [dispatch] [art] Status of Hapt… Francesca Palombini
- Re: [media-types] [dispatch] [art] Status of Hapt… John C Klensin
- Re: [media-types] [art] [dispatch] Status of Hapt… John C Klensin
- Re: [media-types] [art] [dispatch] Status of Hapt… Ted Hardie
- Re: [media-types] [art] [dispatch] Status of Hapt… John C Klensin
- Re: [media-types] [dispatch] [art] Status of Hapt… Ned Freed
- Re: [media-types] [art] [dispatch] Status of Hapt… John C Klensin
- Re: [media-types] [art] [dispatch] Status of Hapt… John C Klensin
- Re: [media-types] [dispatch] [art] Status of Hapt… Ted Hardie
- Re: [media-types] [dispatch] [art] Status of Hapt… Ned Freed
- Re: [media-types] [dispatch] [art] Status of Hapt… Ted Hardie
- Re: [media-types] [art] [dispatch] Status of Hapt… Yeshwant Muthusamy
- Re: [media-types] [art] [dispatch] Status of Hapt… Yeshwant Muthusamy
- Re: [media-types] [art] [dispatch] Status of Hapt… Ned Freed
- Re: [media-types] [art] [dispatch] Status of Hapt… Murray S. Kucherawy
- Re: [media-types] [art] [dispatch] Status of Hapt… Larry Masinter
- Re: [media-types] [art] [dispatch] Status of Hapt… Patrick McManus