Dear All,
I am happy to be an author. I did the changes about the references in my
working copy.
Diff here:
https://htmlpreview.github.io/?https://raw.githubusercontent.com/JeanQuilbeufHuawei/draft-collected-data-manifest/refs/heads/comments_08/docs/latest-diff.html
Best,
Jean
From: IGNACIO DOM
Dear Joe,
I’m also happy to be an author and I agree with making an informative reference.
Many thanks,
Nacho.
From: thomas.g...@swisscom.com
Date: Sunday, 29 June 2025 at 11:00
To: benoit.claise=40huawei@dmarc.ietf.org
, Diego R. Lopez
, jcla...@cisco.com ,
draft-ietf-opsawg-collected-d
Dear Joe,
I agreed to be listed as an author. Changing RFC 9232 to be informative makes
perfectly sense since the term "Network Telemetry" is used as overall context
so understand to which data the platform manifest is being used. Moreover
YANG-Push notifications, RFC 8639 and RFC 8641 are norm
Hi Joe,
I also agreed to be an author.
And yes informative is sufficient.
Thanks, Benoit
From:Diego R. Lopez
mailto:diego.r.lo...@telefonica.com>>
To:Joe Clarke (jclarke)
mailto:jcla...@cisco.com>>;draft-ietf-opsawg-collected-data-manifest
mailto:draft-ietf-opsawg-collected-data-manif...@
Hi Joe,
This is to confirm I am happy to be listed as author. And, regarding your
question, I believe an informative reference would suffice.
Be goode,
--
“Esta vez no fallaremos, Doctor Infierno”
Dr Diego R. Lopez
Telefonica
https://www.linkedin.com/in/dr2lopez/
e-mail: diego.r.lo...
On Apr 10, 2025, at 10:23 AM, Joe Clarke (jclarke)
wrote:
> In going through the shepherd write-up requirements, I note a few NITs in
> this document. The most correctable one is to remove the 2119 boilerplate
> and reference as this document doesn’t make use of any normative text.
That has
Thanks for the context, Med. I’ll note that in the review.
Other authors, please confirm you wish to be listed as such.
Joe
From: mohamed.boucad...@orange.com
Date: Saturday, March 8, 2025 at 04:39
To: Joe Clarke (jclarke) , Wubo (lana)
, Zitao Wang (wangzi...@huawei.com)
, Guangying Zheng
Re-,
Please see inline.
Cheers,
Med
De : Joe Clarke (jclarke)
Envoyé : vendredi 7 mars 2025 17:37
À : draft-ietf-opsawg-secure-tacacs-y...@ietf.org
Cc : opsawg@ietf.org
Objet : Shepherd procedural review
As I work through the shepherd write-up, I have questions:
* Has this module been im
