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

[Yeshwant Muthusamy <[e-mail]>]

Claudio,



I was reacting specifically to the following line in your original email (the underlining of the word 'co-authoring' is mine):



>>I'd like to have a revision (or even co-authoring) at leaset from Apple, Google and others.



I will leave it at that.



Regards,

Yeshwant



Yeshwant Muthusamy, Ph.D. | Senior Director, Standards



[e-mail] | [phone]



-----Original Message-----
From: Claudio Allocchio <[e-mail]>
Sent: Monday, May 3, 2021 2:33 PM
To: Ned Freed <[e-mail]>
Cc: Yeshwant Muthusamy <[e-mail]>; Ted Hardie <[e-mail]>; Dispatch WG <[e-mail]>; [e-mail]; Applications and Real-Time Area Discussion <[e-mail]>; ART ADs <[e-mail]>; Claudio Allocchio <[e-mail]>; Francesca Palombini <francesca.palombini=[e-mail]>; [e-mail]
Subject: Re: [dispatch] [art] Status of Haptics I-D in DISPATCH?





>> Setting aside the implications (inadvertent or otherwise) of

>> Claudio's comment that Apple or Google need to be on the authors list

>> for IETF to even consider an ID  (or work on it expeditiously),



you totally misread what I stated, sorry. I said that at least those companies who are implementing the "new stuff" should be involved into the discussion of the specificaions, oitherwise the specification will be just ignored or result inaccurate compared to reality. And Apple and Google are just 2 examples. The way you read my sentence it totaly against what IETF is how it works etc. When I (and Ned and John, and many of the people who made suggestions in tis thread) started in the IETF, Apple, Google, and 80% of current companies weer "just not yet stablished", so please do not misread examples. :-) Specifications are done and are successful when all people who need them work to write them, and when people who will implement them work on them, too.



apart frm this, +1 to Ned's last email.

>

> I could even begin to count the number of times I've been told that

> this or that is critical because of the actions of some other

> standards group, and for that reason the IETF needs to engage post

> haste. IME a common result of such pleas is to slow the work down, as

> people begin to argue about how the IETF should handle its

> interactions with other standards bodies, rather than focusing on the technical issues at hand.



yes!



>

>                                                             Ned

>



------------------------------------------------------------------------------

Claudio Allocchio             G   A   R   R          [e-mail]<mailto:[e-mail]>

                         Senior Technical Officer

tel: [phone]      Italian Academic and       G=Claudio; S=Allocchio;

fax: [phone]        Research Network         P=garr; A=garr; C=it;



      PGP Key: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fwww.cert.garr.it%252fservizi%252finformazioni-su-pgp-keys%26c%3DE%2C1%2C-GTUZFGQdXv1p694QMmj1sboEwalq1CLyrRlB-PM9e7iQ5szrRm6OpyckAhxnSk2d8ObumtibdgcLcJfnSN_TW--yHCwqIEObJRv3_zTuuOk%26typo%3D1&amp;data=04%7C01%7C%7C6115199e24f6457dcad108d90e6a4141%7C4f05e41a59b8413aae19d5df3dfd0fb5%7C0%7C0%7C637556671794269703%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=OkQt7jhvQQ4g8gjGnRXiz0Px0Idrtj1hZuQsQOxtcAU%3D&amp;reserved=0