Hi Alana, all,

Thank you for preparing this edited version. 

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org>
> Envoyé : lundi 15 septembre 2025 22:31
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>;
> kond...@gmail.com
> Cc : rfc-edi...@rfc-editor.org; opsawg-...@ietf.org; opsawg-
> cha...@ietf.org; thomas.g...@swisscom.com;
> mjethanand...@gmail.com; auth48archive@rfc-editor.org
> Objet : Re: AUTH48: RFC-to-be 9870 <draft-ietf-opsawg-tsvwg-udp-
> ipfix-14> for your review
> 
> Authors,
> 
> While reviewing this document during AUTH48, please resolve (as
> necessary) the following questions, which are also in the source
> file.
> 
> 1) <!--[rfced] Acronyms
> 
> a) FYI - We have added expansions for the following abbreviations
> per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review
> each expansion in the document carefully to ensure correctness.
> 
>  Datagram Congestion Control Protocol (DCCP)  Stream Control
> Transmission Protocol (SCTP)
> 

[Med] ACK.

> 
> b) FYI - We have updated the expansion of "APC" to reflect how the
> acronym is expanded in RFC 9868. Please let us know of any
> objections.
> 
> Original:
>    Alternate payload checksum (APC)
> 
> Current:
>    Additional Payload Checksum (APC)
> -->

[Med] Agree with the change to align with the latest use of APC in the UDP 
options spec. 

I see that it was changed in 
https://author-tools.ietf.org/iddiff?url1=draft-ietf-tsvwg-udp-options-32&url2=draft-ietf-tsvwg-udp-options-31&difftype=--html.
 

> 
> 
> 2) <!-- [rfced] Please review the "Inclusive Language" portion of
> the online  Style Guide
> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fwww.rfc-
> editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C
> 02%7Cmohamed.boucadair%40orange.com%7C3652b4017ff747b4ccb708ddf496
> d8b3%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6389356510391909
> 45%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA
> wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C
> &sdata=WMcc6HApPnUDtptad%2FuW0VEPM3OgOAAAnmb7iyiOS1g%3D&reserved=0
> >
> and let us know if any changes are needed.
> 
> Note that our script did not flag any words in particular, but
> this should still be reviewed as a best practice.
> -->
> 

[Med] Nothing flagged on my side as well. 

I also reviewed the full edited version and all looks good to me. I approve the 
publication of this version. Thanks.

One related comment triggered by "least-signification"/"most-signification" to 
"least signification"/"most signification" changes: I checked recent 
IPFIX-related RFCs to see if we are consistent, which is indeed the case for 
9740 in particular. However, I noted that the use in RFC9740 was not echoed in 
the IANA registry (https://www.iana.org/assignments/ipfix/ipfix.xhtml) for 
these IEs:

* ipv6ExtensionHeadersFull
* tcpOptionsFull

Can we please report that to IANA and update as appropriate? Thank you.

Cheers,
Med

> 
> Thank you.
> Alanna Paloma and Sandy Ginoza
> RFC Production Center
> 
> 
> On Sep 15, 2025, at 1:27 PM, rfc-edi...@rfc-editor.org wrote:
> 
> 
> *****IMPORTANT*****
> 
> Updated 2025/09/15
> 
> RFC Author(s):
> --------------
> 
> Instructions for Completing AUTH48
> 
> Your document has now entered AUTH48.  Once it has been reviewed
> and approved by you and all coauthors, it will be published as an
> RFC.
> If an author is no longer available, there are several remedies
> available as listed in the FAQ
> (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fwww.rfc-
> editor.org%2Ffaq%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%
> 7C3652b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc48b9253b6f5
> d20%7C0%7C0%7C638935651039222510%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e
> U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI
> sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=nlf%2BSNGTDcV3a1bJdqUluHA62rx
> vGbF5dm%2Bf9rAlFMQ%3D&reserved=0).
> 
> You and you coauthors are responsible for engaging other parties
> (e.g., Contributors or Working Group) as necessary before
> providing your approval.
> 
> Planning your review
> ---------------------
> 
> Please review the following aspects of your document:
> 
> *  RFC Editor questions
> 
>    Please review and resolve any questions raised by the RFC
> Editor
>    that have been included in the XML file as comments marked as
>    follows:
> 
>    <!-- [rfced] ... -->
> 
>    These questions will also be sent in a subsequent email.
> 
> *  Changes submitted by coauthors
> 
>    Please ensure that you review any changes submitted by your
>    coauthors.  We assume that if you do not speak up that you
>    agree to changes submitted by your coauthors.
> 
> *  Content
> 
>    Please review the full content of the document, as this cannot
>    change once the RFC is published.  Please pay particular
> attention to:
>    - IANA considerations updates (if applicable)
>    - contact information
>    - references
> 
> *  Copyright notices and legends
> 
>    Please review the copyright notice and legends as defined in
>    RFC 5378 and the Trust Legal Provisions
>    (TLP -
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> trustee.ietf.org%2Flicense-
> info&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C3652b4017ff74
> 7b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6
> 38935651039237298%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs
> IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%
> 3D%7C0%7C%7C%7C&sdata=yoMJIzGJNfmGQZyP%2B56EkpX5C5lYO0pmN53zTB6mEO
> w%3D&reserved=0).
> 
> *  Semantic markup
> 
>    Please review the markup in the XML file to ensure that
> elements of
>    content are correctly tagged.  For example, ensure that
> <sourcecode>
>    and <artwork> are set correctly.  See details at
> 
> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fauthors.ietf.org%2Frfcxml-
> vocabulary&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C3652b40
> 17ff747b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7
> C0%7C638935651039252102%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn
> RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy
> fQ%3D%3D%7C0%7C%7C%7C&sdata=0Msc2MHFE9HshA5mwdq4qQMTZoIf20%2BuXYKr
> alt9YS8%3D&reserved=0>.
> 
> *  Formatted output
> 
>    Please review the PDF, HTML, and TXT files to ensure that the
>    formatted output, as generated from the markup in the XML file,
> is
>    reasonable.  Please note that the TXT will have formatting
>    limitations compared to the PDF and HTML.
> 
> 
> Submitting changes
> ------------------
> 
> To submit changes, please reply to this email using 'REPLY ALL' as
> all the parties CCed on this message need to see your changes. The
> parties
> include:
> 
>    *  your coauthors
> 
>    *  rfc-edi...@rfc-editor.org (the RPC team)
> 
>    *  other document participants, depending on the stream (e.g.,
>       IETF Stream participants are your working group chairs, the
>       responsible ADs, and the document shepherd).
> 
>    *  auth48archive@rfc-editor.org, which is a new archival
> mailing list
>       to preserve AUTH48 conversations; it is not an active
> discussion
>       list:
> 
>      *  More info:
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> mailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-
> 4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7
> C3652b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc48b9253b6f5d
> 20%7C0%7C0%7C638935651039266250%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU
> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs
> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=7ndKEhYEhZz1YXVuUVEZ69Dp2JFl8Z
> 2nnZHwDzjROE0%3D&reserved=0
> 
>      *  The archive itself:
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> mailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C
> 02%7Cmohamed.boucadair%40orange.com%7C3652b4017ff747b4ccb708ddf496
> d8b3%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6389356510392800
> 53%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA
> wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C
> &sdata=RuyAiLfgaqZT0YPfTBXRrR1FuaDluTnyPg508%2BguA%2Bw%3D&reserved
> =0
> 
>      *  Note: If only absolutely necessary, you may temporarily
> opt out
>         of the archiving of messages (e.g., to discuss a sensitive
> matter).
>         If needed, please add a note at the top of the message
> that you
>         have dropped the address. When the discussion is
> concluded,
>         auth48archive@rfc-editor.org will be re-added to the CC
> list and
>         its addition will be noted at the top of the message.
> 
> You may submit your changes in one of two ways:
> 
> An update to the provided XML file
>  - OR -
> An explicit list of changes in this format
> 
> Section # (or indicate Global)
> 
> OLD:
> old text
> 
> NEW:
> new text
> 
> You do not need to reply with both an updated XML file and an
> explicit list of changes, as either form is sufficient.
> 
> We will ask a stream manager to review and approve any changes
> that seem beyond editorial in nature, e.g., addition of new text,
> deletion of text, and technical changes.  Information about stream
> managers can be found in the FAQ.  Editorial changes do not
> require approval from a stream manager.
> 
> 
> Approving for publication
> --------------------------
> 
> To approve your RFC for publication, please reply to this email
> stating that you approve this RFC for publication.  Please use
> 'REPLY ALL', as all the parties CCed on this message need to see
> your approval.
> 
> 
> Files
> -----
> 
> The files are available here:
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-
> editor.org%2Fauthors%2Frfc9870.xml&data=05%7C02%7Cmohamed.boucadai
> r%40orange.com%7C3652b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40
> bfbc48b9253b6f5d20%7C0%7C0%7C638935651039293891%7CUnknown%7CTWFpbG
> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs
> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=WvHMelNRQIxee9
> i9bTQGZPbckfBnvRQ7Ee5oCAQecao%3D&reserved=0
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-
> editor.org%2Fauthors%2Frfc9870.html&data=05%7C02%7Cmohamed.boucada
> ir%40orange.com%7C3652b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b4
> 0bfbc48b9253b6f5d20%7C0%7C0%7C638935651039307486%7CUnknown%7CTWFpb
> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI
> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=6keCGAFqE2R0v
> lPDfA1r6TTFnNdJIykAAdwCofBRNRk%3D&reserved=0
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-
> editor.org%2Fauthors%2Frfc9870.pdf&data=05%7C02%7Cmohamed.boucadai
> r%40orange.com%7C3652b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40
> bfbc48b9253b6f5d20%7C0%7C0%7C638935651039320875%7CUnknown%7CTWFpbG
> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs
> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=IX5pJb607%2BvN
> %2B84ohXd1jXwcUuIYscsSmgI3mHFqoWc%3D&reserved=0
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-
> editor.org%2Fauthors%2Frfc9870.txt&data=05%7C02%7Cmohamed.boucadai
> r%40orange.com%7C3652b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40
> bfbc48b9253b6f5d20%7C0%7C0%7C638935651039334119%7CUnknown%7CTWFpbG
> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs
> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FrJRCOqLrf%2
> F04nuVM7hYWhJ7D%2Fdw8JFwhIGrDbfVgPM%3D&reserved=0
> 
> Diff file of the text:
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-editor.org%2Fauthors%2Frfc9870-
> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C3652b401
> 7ff747b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> 0%7C638935651039347876%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR
> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf
> Q%3D%3D%7C0%7C%7C%7C&sdata=UXTnYXMR8Lem2igZgbvMk2GPkPmESqEziXpy35t
> raFU%3D&reserved=0
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-editor.org%2Fauthors%2Frfc9870-
> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C3652b
> 4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0
> %7C0%7C638935651039365493%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki
> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj
> oyfQ%3D%3D%7C0%7C%7C%7C&sdata=tAiGQ%2Fpj0rm3SmgpYzTYeZUtVpSz04TMV%
> 2FuP2OHIHYc%3D&reserved=0 (side by side)
> 
> Diff of the XML:
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-editor.org%2Fauthors%2Frfc9870-
> xmldiff1.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C3652
> b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc48b9253b6f5d20%7C
> 0%7C0%7C638935651039380507%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk
> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI
> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=vJX82ROvkGGcOQNE7Vc3jb5Ol38WjMWl1ek
> 7J4ed99g%3D&reserved=0
> 
> 
> Tracking progress
> -----------------
> 
> The details of the AUTH48 status of your document are here:
> 
> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.rfc-
> editor.org%2Fauth48%2Frfc9870&data=05%7C02%7Cmohamed.boucadair%40o
> range.com%7C3652b4017ff747b4ccb708ddf496d8b3%7C90c7a20af34b40bfbc4
> 8b9253b6f5d20%7C0%7C0%7C638935651039393761%7CUnknown%7CTWFpbGZsb3d
> 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI
> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=r%2B6IRRevcUXDpUxZm
> fcG5iFFpjGqm1SWozvChbPnZuk%3D&reserved=0
> 
> Please let us know if you have any questions.
> 
> Thank you for your cooperation,
> 
> RFC Editor
> 
> --------------------------------------
> RFC 9870 (draft-ietf-opsawg-tsvwg-udp-ipfix-14)
> 
> Title            : Export of UDP Options Information in IP Flow
> Information Export (IPFIX)
> Author(s)        : M. Boucadair, T. Reddy.K
> WG Chair(s)      : Joe Clarke, Benoît Claise
> 
> Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani
> 

____________________________________________________________________________________________________________
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.

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to