Hi Benoît, I was referring to updating the description **IEs defined in this document**. These IEs belong to a WG-adopted document and as such the WG has control over the content. Aligning what was pre-registered vs. the consensus of the WG is simple logistic and will follow usual involvement of DEs, etc.
If we can’t touch those, I don’t see the point in adopting this document at the first place. No? Cheers, Med De : Benoit Claise <benoit.cla...@huawei.com> Envoyé : mercredi 18 décembre 2024 11:27 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; Sriram Gopalakrishnan (sriragop) <sriragop=40cisco....@dmarc.ietf.org>; opsawg@ietf.org; Aitken, Paul <pait...@ciena.com> Cc : ops-ads <ops-...@ietf.org>; ie-doct...@ietf.org Objet : Re: [OPSAWG]Re: I-D Action: draft-ietf-opsawg-ipfix-gtpu-02.txt Hi Med, On 12/17/2024 1:40 PM, mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> wrote: Hi Sriram, I didn’t check this version against my comments, but I’m reacting to this part of your message: == Since the IEs mentioned in the draft (Sec-5) are already published by the IANA and is available in https://www.iana.org/assignments/ipfix/ipfix.xhtml, we did not change the description of these IEs. == That’s actually not a reason as the IEs are not frozen: scope/description can be changed as part of the WG process. IANA section can capture any deviation that may occur vs. existing entries. Do you have a document/IANA statement supporting this? This is new to me. RFC 7120 does not really apply here as https://www.iana.org/assignments/ipfix/ipfix.xhtml is "Expert Review" The following conditions must hold before a request for early allocation of code points will be considered by IANA: a. The code points must be from a space designated as "RFC Required", "IETF Review", or "Standards Action". Additionally, requests for early assignment of code points from a "Specification Required" registry are allowed if the specification will be published as an RFC. https://datatracker.ietf.org/doc/html/rfc8126#section-2.4 mentions "revising existing registries" but not really overwriting the Expert Reviews (https://datatracker.ietf.org/doc/html/rfc8126#section-4.5) The IE-doctors are copied here, for full transparency. Regards, Benoit (chair hat on) Cheers, Med De : Sriram Gopalakrishnan (sriragop) <sriragop=40cisco....@dmarc.ietf.org><mailto:sriragop=40cisco....@dmarc.ietf.org> Envoyé : mardi 17 décembre 2024 13:11 À : opsawg@ietf.org<mailto:opsawg@ietf.org> Objet : [OPSAWG]Re: I-D Action: draft-ietf-opsawg-ipfix-gtpu-02.txt Hi OPSAWG We updated the draft with the comments received from last two versions (sincere thanks to Med and Paul on that). Majorly we made some updates to Use case section (Sec-4) by giving additional references to slicing related info, some more notes added to Terminology (Sec-2) and few other minor updates overall – Acknowledgement section, grammatically better phrases. Since the IEs mentioned in the draft (Sec-5) are already published by the IANA and is available in https://www.iana.org/assignments/ipfix/ipfix.xhtml, we did not change the description of these IEs. Requesting the working group to take the next steps on this draft. Thanks --Sriram From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> Date: Tuesday, 17 December 2024 at 10:52 AM To: i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org> <i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org>> Cc: opsawg@ietf.org<mailto:opsawg@ietf.org> <opsawg@ietf.org<mailto:opsawg@ietf.org>> Subject: [OPSAWG]I-D Action: draft-ietf-opsawg-ipfix-gtpu-02.txt Internet-Draft draft-ietf-opsawg-ipfix-gtpu-02.txt is now available. It is a work item of the Operations and Management Area Working Group (OPSAWG) WG of the IETF. Title: Export of GTP-U Information in IP Flow Information Export (IPFIX) Authors: Daniel Voyer Sriram Gopalakrishnan Thomas Graf Benoit Claise Vyasraj Satyanarayana Name: draft-ietf-opsawg-ipfix-gtpu-02.txt Pages: 14 Dates: 2024-12-16 Abstract: This document introduces IP Flow Information Export (IPFIX) Information Elements to report information contained in the Generic Packet Radio Service Tunneling Protocol User Plane header such as Tunnel Endpoint Identifier, and data contained in its session container extension header. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-gtpu/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ipfix-gtpu-02 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-gtpu-02 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ OPSAWG mailing list -- opsawg@ietf.org<mailto:opsawg@ietf.org> To unsubscribe send an email to opsawg-le...@ietf.org<mailto:opsawg-le...@ietf.org> ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ OPSAWG mailing list -- opsawg@ietf.org<mailto:opsawg@ietf.org> To unsubscribe send an email to opsawg-le...@ietf.org<mailto:opsawg-le...@ietf.org> ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
