Re: [media-types] [art] [dispatch] Status of Haptics I-D in DISPATCH?

Yeshwant Muthusamy <ymuthusamy@immersion.com> Tue, 04 May 2021 17:37 UTC

Return-Path: <ymuthusamy@immersion.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 5B43E3A15B2; Tue, 4 May 2021 10:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level:
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=immr.onmicrosoft.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 dQNVCYiAXLIy; Tue, 4 May 2021 10:37:45 -0700 (PDT)
Received: from outbound-ip12a.ess.barracuda.com (outbound-ip12a.ess.barracuda.com [209.222.82.179]) (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 E419A3A15AC; Tue, 4 May 2021 10:37:34 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11lp2171.outbound.protection.outlook.com [104.47.58.171]) by mx-outbound11-68.us-east-2a.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 04 May 2021 17:37:15 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b20Kn4+N1hGBBp+zB2gygDH+s8/pWL4dMYxEtnm4VlyyMdUKAXOcniWkSLyRP6Ch7QjIchgDCmaTXP1csrJ9DebNbXB+v8QGjGoav3twY8BaDPDOviy2tVj6O3ZF15A6e7ynbW84Ebz/Sy1Z200mz7+3swZKB2yXT+XMWhgKV8heTff/3EzKHlSA91gYRF/ZUu3EbvoM5IB2RduO6pGM+GCEcf4aKGuOGHFdUNqy0wgZJjQRdSuD4pjjGPOaKA76tJiV0UK5CuVTdaciy9ZRas2xMgH+ke/iMOgz7+esGvGqj/UtMS9jj5NxWXoGpojL6P+O3Am1WcIIN0iru4O30A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DW6Et+8k5G9T8Mg5xAkmsFJwAgAHvxZ6r2kPvFUg5eI=; b=Mgj7m3cEPtXThMf+hzH9o3Al1L7s3XVdyUkFQ/ZhEo6kehALIxr7kbuqyAMjkODmwizLg6N9A1yU5UTnqwdzEyvdoOS+CyEvEWTmjVKA6I1RYpd6+ZHhDXgNExAtVYvdHim8xmYMm+aYVY0Lz8rngEz2EyaEhqaMsLceGW4y1u19kW6BUG368/K3V5ikomjJWqyAixfp9TOSbITM8ZAaPknI0fsBwgnZM8qSFhUF1rJY60mKvNg00nFO0tsYe52aeOZUxFp7TpqmDqP2H8m+Cdtk4wvuQgY5JG/938PY8dVXt+cJYtD0JaNTZG2VINPJvh99yGaRxzSYqeq9G+x1JA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=immersion.com; dmarc=pass action=none header.from=immersion.com; dkim=pass header.d=immersion.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=immr.onmicrosoft.com; s=selector2-immr-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DW6Et+8k5G9T8Mg5xAkmsFJwAgAHvxZ6r2kPvFUg5eI=; b=aRPaq7hgLuK/BHlVEz1zJObXeX1+is2a4MaHWnaCHGiE7KM3SVXwuHeD+AvMLhn48E5gQ99OIamOKh5j/jK7ZwYsfPkt1sZLByPim8PFP0fZg7sVJogEkFZsBfexNxXltr7M197qy6BINF+YJK36Bc5guhvm/lvkoMyCWQZ65t4=
Received: from MW3PR16MB3914.namprd16.prod.outlook.com (2603:10b6:303:4d::19) by MWHPR1601MB1183.namprd16.prod.outlook.com (2603:10b6:300:e3::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4087.25; Tue, 4 May 2021 17:37:12 +0000
Received: from MW3PR16MB3914.namprd16.prod.outlook.com ([fe80::3566:e24:c46d:1e4]) by MW3PR16MB3914.namprd16.prod.outlook.com ([fe80::3566:e24:c46d:1e4%8]) with mapi id 15.20.4108.024; Tue, 4 May 2021 17:37:11 +0000
From: Yeshwant Muthusamy <ymuthusamy@immersion.com>
To: John C Klensin <john-ietf@jck.com>, Ted Hardie <ted.ietf@gmail.com>
CC: Dispatch WG <dispatch@ietf.org>, "dispatch-chairs@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" <draft-muthusamy-dispatch-haptics@ietf.org>, "media-types@ietf.org" <media-types@ietf.org>
Thread-Topic: [art] [dispatch] Status of Haptics I-D in DISPATCH?
Thread-Index: AQHXQJhM4Zh3T3YG3E61gUYzSXJNSarTkCMQ
Date: Tue, 04 May 2021 17:37:11 +0000
Message-ID: <MW3PR16MB3914440DE7F74C93CCD7D408DE5A9@MW3PR16MB3914.namprd16.prod.outlook.com>
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>
In-Reply-To: <2FD10F8AE6D1B9C7D6545340@PSB>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: jck.com; dkim=none (message not signed) header.d=none;jck.com; dmarc=none action=none header.from=immersion.com;
x-originating-ip: [47.188.43.20]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 89cc91f2-cdd6-4459-193b-08d90f233fde
x-ms-traffictypediagnostic: MWHPR1601MB1183:
x-microsoft-antispam-prvs: <MWHPR1601MB118318A7E0534BB17B1B8780DE5A9@MWHPR1601MB1183.namprd16.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: KiveCH8lVbtFsMm7lx3NDlSs5fVPu6ACq3Gr3CIJOnD7IpFn5g3Pi7mNJxJ5Z7kH3MQtSZoUizN5J1qEvxtgACCMF66Of6j8EVO/QHMNb9BGoPsXH5ZDAalqVfZBLMPiSdGCSZWasWO6F4BBF3ygCQY2jQX1vM+A1bxf6VgoLMJvPyG0TcVq4zQglqJLxXyNSMehda8UvtvUQ111O1X5C+KagSxPplvjAPEW2Tv9eye3XZtv5jFXUWnMhwHY8dpfYazdiSVqlcMNOUzLLHOJEu1foD+VUCUrXPWPrugfPBhGD+szRMB7HJxsv4TTNRPOrtPaRMtZa6dGErYs7GRVSd+DO1ZYvYxMTwAvnJpfMjS/uXlpXtIXsejOY7aAU2UGEWj72V+/JyvTU6GzmLelBRXQl5RneOtPiNakrHB9rm3rN0TU8Q2plLg/IOFgHL+1NFJirAemvnTrFLIx+4m/HMuNPqnemAKcPDN+RiHlTbZbC8TszggFTnykLv+urK2FNuTFok0yBvY7FHUOdzfvA3VDD/iLszUfOtFaiUQQ/X/A6QHs8/jlz0MC4STlBXwsHBrCXUz/ivaqfqG3HGQbJFMZ8QupalJelcrxFqLDTXQGJToVVV9hxmadsRgCHKCrcgjoy4LKrQAw7X2XN9FkeZ4BUEf2IZK/VSSyswTvIk+X0bp7OJVyiwuh/mVlScpV
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW3PR16MB3914.namprd16.prod.outlook.com; PTR:; CAT:NONE; SFS:(376002)(346002)(396003)(39830400003)(366004)(136003)(66946007)(64756008)(66556008)(66476007)(66446008)(76116006)(8936002)(33656002)(316002)(8676002)(86362001)(166002)(54906003)(83380400001)(966005)(45080400002)(38100700002)(5660300002)(52536014)(71200400001)(55016002)(478600001)(9686003)(110136005)(4326008)(53546011)(6506007)(2906002)(7696005)(122000001)(186003)(26005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: SgzVGk89Fh50mPow152PPEPlNW05/oj+HY539vCp2XEW5qRhMh95dLkMo6NguoVXd8kCtT0B3yREYiAriVHpXrMcUn68DtUnOMsZ/3T62zRUK6XyNspf8NGE2zPUELTE7TpSsQtL9OlOL7WZSXNSIGtThe06bZ/9pEK0dDEYjCTp3Zrx01YMX0Hl0ia/fBthoBsEkShuTVHfr1Jd1zWiIV9snrTahxF2R6E5Ms2xwIgiWs6oLrhvg5ndMZHbne37mPoRASxi49Tg1jP/wu3I6PsVFHUu4nw7i2eJniVPyVB4BjkRc9//E3wc0LKTGcuuRJh7ZS4kHinjYdKxX9A4EjnokYtcF8GyIukAAxXxg2eEicKS/8u7b60XHUrOWO9gn3EskAKnTLq3MSNBVp4Z1RZG2ICh+N+vpEZyNGqE+/CKGBaPEPo8qgzlvQJi3oQbeXstMhH9Yqx+YiIy2M33911MBv6ztrSdVoEcIpD8kHD/zsUQYf/BZqADWrfTNqNXzOa/YquEFMgeDkgENv3GVY0nQOMM759R7cWTn2P1rFe1U1Jdu7RarX0JRQH8tYiYtxcutsu+eZaPytj+Gpi6hb7f9HcOUli3vs2omo0F8wMXlm3NPSqXe6lQWCw0d3DFOsMbF/1lFElf+C+tpOCYjzgNf+tkYbxCRHlvDs8jc8h93gcKuf/QP35gqsORJFG+ROomo7srCQmsImOo3kyTikvRzKMcyu9Ez+k/qmQ3q3L8pe4LwnRgcWXifaf67omHqw+bZbi5P5qykDtmsxHngSYmyZOGLgJmAqk+iHu7qBuW6a3t03GIVGgMqiJjwlDcfiBLCeMazq/zBEWEDtyWQvatzz6f5X5pBZhKi/Ja/hDC8ObMuFGwGcSTZQtDoYy8XazxIFMiaa6zzcUE1K3KFJiF26TIkvOCyal9vYpZm2rfdJA2r5xB41cP17jhRixev7pNAiBNj8xSpzEzIwGW7sQZ00eHB9cFW47jO8Ka/EJIITGi/7pCivlFSeAZW+ZaR+XOqnROQnAf3YVriMAc3N5dxwcRog22WkPYurTiI9NVgTZK/0Xc51FChvWhau0j6uz7/mQI5KWodz+BaNyN837QCxDEfUlWqkokHYJIbVY/5iMf7aOfJwkuCoN68sSdfFQbkBQl+tJlK4bWP8M16rpGeoLIE+FVPHAWDO1OTdAiqHBRFlwV1HFULBHIvlViMsW9AKpvG2Szow8wOOKERJKiRNlt2XcRy8GFRandqiKulLA9MPhyt9wIUWGI//ldVWiG4sIWnzXhCUVSLBWQeJH91LTOpnQ10Dlq28Ep/Kg=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR16MB3914440DE7F74C93CCD7D408DE5A9MW3PR16MB3914namp_"
MIME-Version: 1.0
X-OriginatorOrg: immersion.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR16MB3914.namprd16.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 89cc91f2-cdd6-4459-193b-08d90f233fde
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 May 2021 17:37:11.7690 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f05e41a-59b8-413a-ae19-d5df3dfd0fb5
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: yK8zpX83wpZZWegtx1Zl48d0M9sorkbrrkgRnpkdJdpzHPrRz/e77Tta1ZdOYSGBbWkZcp3rcjM7iGvxGGXozjz1E0ImzruirZ81/WfS97s=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1601MB1183
X-BESS-ID: 1620149835-102884-5394-29313-1
X-BESS-VER: 2019.1_20210504.1407
X-BESS-Apparent-Source-IP: 104.47.58.171
X-BESS-Outbound-Spam-Score: 0.00
X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.232003 [from cloudscan8-233.us-east-2a.ess.aws.cudaops.com] Rule breakdown below pts rule name description ---- ---------------------- -------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message 0.00 BSF_BESS_OUTBOUND META: BESS Outbound
X-BESS-Outbound-Spam-Status: SCORE=0.00 using account:ESS117783 scores of KILL_LEVEL=7.0 tests=HTML_MESSAGE, BSF_BESS_OUTBOUND
X-BESS-BRTS-Status: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/WdxjWzUh8n2sSe0qbrVq7mT5QUc>
X-Mailman-Approved-At: Wed, 05 May 2021 08:49:34 -0700
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: Tue, 04 May 2021 17:37:51 -0000

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://www.iso.org/standard/81604.html<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iso.org%2Fstandard%2F81604.html&data=04%7C01%7C%7Cb9be185f21b44df1b2f708d90e58c34b%7C4f05e41a59b8413aae19d5df3dfd0fb5%7C0%7C0%7C637556596669589491%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwZKX%2B26UWRq%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.



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: Monday, May 3, 2021 10:48 PM
To: 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?



(adding the media-types list and doing a bit of trimming)



--On Monday, May 3, 2021 17:29 +0100 Ted Hardie <ted.ietf@gmail.com<mailto:ted.ietf@gmail.com>> wrote:



> I think the set of work items Ned lays out might well be the basis for

> a working group.  I have concerns, however, with including the

> registration for a haptics top-level type in that work.

>

> As the draft points out, there is a good bit of active work going on

> related to haptics in other forums (e.g. the MPEG Systems File Format

> sub-group).  If the work on registering a top-level haptics type is

> interspersed with work on multiple media type suffixes and media types

> for programming languages, I have concerns about the speed with which

> it can complete.

> If we want to see haptic signals be treated appropriately as a media

> type, I suspect the time we have to do it is not unbounded.  My

> personal advice is thus to progress the haptics work separately.  If

> that means as an ad-sponsored draft, I'm personally okay with that,

> but I think the best other option is to do it as its own short-lived

> group.  The other work (and the relevant expertise) is pretty

> distinct.



Ted,



As you have probably figured out from my recent notes responding to Francesca and Claudio, I have a slightly different take on this, again somewhat different than Ned's comments.  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.



Analogies to other bodies treating I-Ds as if they are finished, consensus, IETF work product are probably useful here.



So, in the hope that the IETF is still an organization in which we can figure out what the right thing is to do and then make the procedures work with it, let me suggest something which may be a bit of a strawman:



(1) We get the WG that Ned proposed going, with adjustments as suggested.  Getting it going should not take long, e.g., no one

as proposed a BOF or two as prerequisites.   The first charge

for that WG should be to review prior work discuss criteria for new top-level media types.  I would hope that can be done fairly quickly.  If we cannot reach at least sufficient agreement to conclude that a Haptics top level type would be reasonable (independent of the details of how it is defined and who is defining it, much less candidate subtypes) then I suggest the proposal is dead in the water independent of what other bodies are or are not doing.



(2) Probably in parallel with the above, Francesca (or Murray) do a call for volunteers who are familiar with and involved in work on Haptics, in the MPEG group, in their "day job" settings, or elsewhere.  Where they are tapped as participants in a short-lived WG or as reviewers of a potential AD-sponsored document is probably unimportant, as long as they represent diverse perspectives.  The numbers, expertise, and industry coverage are important.  Based on the outcome of that poll, they reach a conclusion as to whether meaningful, informed, IETF consensus on the details of the proposal (presumably a revised

I-D) is plausible.



(3) If the outcome of (2) is that we have a sufficient number of such people, I don't have a strong preference between AD-sponsored and a short-lived WG.  However, the less clear the criteria are that emerge from (1) --or if the early result of that effort is general principles but not anything we would consider criteria-- the more I think a WG is needed.



(4) If the outcome of (1) is that a Haptics top-level type is plausible but that of (2) is that we don't have, in the judgment of the ADs,  the right combination of expertise, interest, and energy, then I suggest we cut a deal with the MPEG effort (close to one end of the pipeline) and/or the relevant ISO TC (the other end) in which we promise them that we will allocate the top-level media type and delegate responsibility for defining subtypes to them as soon as they tell us that a standard that described the properties and use of that type is finished (not being worked on, but finished).  Note that punts the question of how subtypes are evaluated and decided upon to another body.

Otherwise, that question is one of the harder issues facing the question of criteria for a new top-level type (and a subject on which I, personally, think the current I-D is fairly weak).



I don't know if it would be possible to complete the above before IETF 111, but, if not, we ought to be able to come fairly close.  And it is _really_ pragmatic.



  best,

   john













[1[

https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fmailarchive.ietf.org%252farch%252fmsg%252fdispatch%252fRRIs5MxWbQuF9kJJclJ-KsFQNIg%26c%3DE%2C1%2C6G6eDTk9mcWs8uM122hKaDB0VrG8GnkKRboPw6fB2_Uk0RCPxB0I4AJmz_kiaV6x6hH9YVFkCIjyUrDrCvar10bLNPZHxnhFl2vdY6YRZpbwR-x73Q%2C%2C%26typo%3D1&amp;data=04%7C01%7C%7C0c8685de1863484c353008d90eaf6c6a%7C4f05e41a59b8413aae19d5df3dfd0fb5%7C0%7C1%7C637556968891437551%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=2woxbmYzryVC8LwiaH3%2FQqX3MpKmy6swcrYTRJABu0A%3D&amp;reserved=0



[2]

https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fmailarchive.ietf.org%252farch%252fmsg%252fdispatch%252fzE9eMvNXpCXF1LWAMt3y-_2GjJ0%26c%3DE%2C1%2ChatQi5r0UG0Mih2C0qTKWqSwanmSjZB1qP6OUtqmoEv54rvdqzNMzyWS0pGKI22pTuojS3pMRy-JXiQ9VV5jflqvNUmH3UZysPJ6zpaBLbNBf3Z8L6oychaJolb2%26typo%3D1&amp;data=04%7C01%7C%7C0c8685de1863484c353008d90eaf6c6a%7C4f05e41a59b8413aae19d5df3dfd0fb5%7C0%7C1%7C637556968891437551%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=RdVZ172jKG0Z31HPBVVeuZgZ916IbaB36dFom6A9rXA%3D&amp;reserved=0