Greetings,
We have updated the document as described below (and per subsequent mail).
Regarding the following:
>> Form B: See the "Name" registry at [URL]
>
> [Med] Please use Form B for consistency through the document. Thanks.
Please note that we have updated the text as “See the ‘Name” registry [URL]”
with the exception of the following (6x):
See the assigned transport protocol (e.g., UDP, TCP, SCTP, and
DCCP) port numbers [https://www.iana.org/assignments/service-
names-port-numbers].
Please let us know if you prefer this be updated as:
See the "Service Name and Transport Protocol Port Number Registry”
[https://www.iana.org/assignments/service-
names-port-numbers].
Regarding item 9, apologies for the confusion. Correct, we meant to note that
this sentence does not appear in the NEW text. Please disregard or let us know
if any changes are desired.
> "These types are registered in the [IANA IPFIX Information Element Units]
> subregistry."
>> 9) <!-- [rfced] Section 6.14.2 (NEW for informationElementUnits):
>> FYI, if you accept the suggested text in the previous question,
>> we will ask IANA to remove the following sentence from the
>> registry; it is not part of the proposed new text.
>>
>> Original:
>> These types can take the values in the [IANA IPFIX
>> Information Element Units]
>> subregistry.
>> -->
>
> [Med] Not sure about this one. Do you mean this text "These types are
> registered in the [IANA IPFIX Information Element Units] subregistry.",
> instead?
The current files are available here:
https://www.rfc-editor.org/authors/rfc9710.xml
https://www.rfc-editor.org/authors/rfc9710.txt
https://www.rfc-editor.org/authors/rfc9710.pdf
https://www.rfc-editor.org/authors/rfc9710.html
AUTH48 diffs:
https://www.rfc-editor.org/authors/rfc9710-auth48diff.html
https://www.rfc-editor.org/authors/rfc9710-auth48rfcdiff.html (side by side)
Comprehensive diffs:
https://www.rfc-editor.org/authors/rfc9710-diff.html
https://www.rfc-editor.org/authors/rfc9710-rfcdiff.html (side by side)
Please review and let us know if additional updates are needed or if you
approve the RFC for publication.
Thank you,
RFC Editor/sg
> On Jan 27, 2025, at 9:05 AM, mohamed.boucad...@orange.com wrote:
>
> Hi all,
>
> (adding Paul (DE), fwiw)
>
> Thank you for sharing the edited version.
>
> Please see inline. I let Benoît (and Paul) further comment as appropriate.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org>
>> Envoyé : vendredi 24 janvier 2025 20:28
>> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>;
>> benoit.cla...@huawei.com
>> Cc : i...@iana.org; rfc-edi...@rfc-editor.org; opsawg-
>> a...@ietf.org; opsawg-cha...@ietf.org; thomas.g...@swisscom.com;
>> mjethanand...@gmail.com; auth48archive@rfc-editor.org
>> Objet : Re: AUTH48: RFC-to-be 9710 <draft-ietf-opsawg-ipfix-
>> fixes-12> for your review
>>
>>
>> [resending with IANA CC'ed as intended.]
>>
>> Authors,
>>
>> While reviewing this document during AUTH48, please resolve (as
>> necessary) the following questions, which are also in the XML
>> file.
>>
>> 1) <!-- [rfced] Regarding the NEW text that appears throughout
>> this document, we have updated it to include the registry name
>> followed by the URL to the registry group. Based on discussion
>> with IANA, this was the preferred way to refer to these
>> registries in the RFC. Note that the extended URLs remain in the
>> OLD text, as it does not matter if these links cease to work in
>> the future (they are marked OLD).
>>
>> For example: Section 6.2.2
>>
>> Original:
>> Additional Information: See the Classification Engine IDs
>> registry
>>
>> ([https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F
>> %2Fwww.iana.org%2Fassignments%2Fipfix%2F&data=05%7C02%7Cmohamed.b
>> oucadair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a2
>> 0af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098216920%7CUnknown
>> %7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOi
>> JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=wq9
>> 9btmlG0W3ycYItq2iJe%2BdwNsgV9taHEVaehZZx5I%3D&reserved=0
>> ipfix.xhtml#classification-engine-ids]).
>>
>> Current:
>> Additional Information: See the "Classification Engine IDs
>> (Value
>> 101)" registry
>> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2Fipfix&data=05%7C02%7Cmohamed.bouca
>> dair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af3
>> 4b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098231699%7CUnknown%7CT
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW
>> 4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GmzQ%2B
>> t%2BJvct8Y9lKN%2F5WfQvzaMLKK9YoV5n%2ByF9vXck%3D&reserved=0].
>> -->
>>
>
> [Med] Works for me. Thanks.
>
>>
>> 2) <!--[rfced] FYI, similarly Table 1 has been updated to use the
>> registry name and the URL without the URI fragment, per IANA's
>> preference for RFCs.
>>
>> For example: "Additional Information" for 33 igmpType.
>>
>> Original I-D:
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.iana.org%2Fassignments%2F&data=05%7C02%7Cmohamed.boucadair%4
>> 0orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bf
>> bc48b9253b6f5d20%7C0%7C0%7C638733438098240525%7CUnknown%7CTWFpbGZ
>> sb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs
>> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xBp%2F3SChrFi
>> %2Bt6phY2PO40s5lrVrZequtIKJRnuDjJU%3D&reserved=0
>> igmp-type-numbers/igmp-type-
>> numbers.xhtml#igmp-type-numbers-1
>>
>> Current document:
>> See "IGMP Type Numbers" at
>>
>> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2F&data=05%7C02%7Cmohamed.boucadair%
>> 40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b40b
>> fbc48b9253b6f5d20%7C0%7C0%7C638733438098249743%7CUnknown%7CTWFpbG
>> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI
>> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=luCubW7cYwHT
>> O5gJYNNoBFIb9reoRV1rMGRDjALYXTI%3D&reserved=0
>> igmp-type-numbers]
>>
>> Current IANA registry (we will send a request to update to the
>> registry name):
>> See the assigned IGMP type numbers at
>>
>> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2Figmp-type-
>> numbers%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d7204
>> 46a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0
>> %7C0%7C638733438098258036%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk
>> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldU
>> IjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=NJJ0E3T2B1EwYApUawm9Y8%2F0rpiYJlM
>> pihl0vBD7JOI%3D&reserved=0
>> igmp-type-numbers.xhtml#igmp-type-numbers-1]
>>
>> Note: Table 1 currently uses Form A, but if you prefer Form B,
>> please let us know.
>>
>> Form A: See "Name" at [URL]
>> Form B: See the "Name" registry at [URL]
>
> [Med] Please use Form B for consistency through the document. Thanks.
>
>> -->
>>
>>
>> 3) <!-- [rfced] Section 6.1.2: To which registry does "IPFIX MPLS
>> label type registry" refer? We see the following registries at
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.iana.org%2Fassignments%2Fmpls-label-
>> values&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d720446a4
>> b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0
>> %7C638733438098265300%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR
>> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy
>> fQ%3D%3D%7C0%7C%7C%7C&sdata=EWnB8fcZSmxDFf3GfEjn7taSyCzNbWDnuNUU%
>> 2Fc4zJRQ%3D&reserved=0:
>>
>> "Base Special-Purpose MPLS Label Values"
>> or "Extended Special-Purpose MPLS Label Values"
>>
>> Original:
>> Additional Information: See the IPFIX MPLS label type
>> registry
>>
>> ([https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F
>> %2Fwww.iana.org%2Fassignments%2Fmpls-label-
>> values&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d720446a4
>> b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0
>> %7C638733438098272852%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR
>> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy
>> fQ%3D%3D%7C0%7C%7C%7C&sdata=31r%2B3w05U4eCf2QBdHa9KsHHN2EcUL1Wfeh
>> WALJQG10%3D&reserved=0]).
>> -->
>>
>
> [Med] The link should be
> https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-mpls-label-type.
>
>>
>> 4) <!-- [rfced] Because it seems the pointers to the relevant
>> registry were moved from the "Description" to "Additional
>> Information", do you still want to keep the sentence about where
>> the values are listed in the "Description"?
>> It seems redundant in some cases; please review.
>>
>> Examples of sentences that you may want to cut from NEW
>> Descriptions:
>>
>> S 6.2.2
>> Values for this field are listed in the Classification
>> Engine IDs registry.
>>
>> S 6.3.2
>> Values are listed in the flowEndReason registry.
>>
>> S 6.4.2
>> Values are listed in the natOriginatingAddressRealm
>> registry.
>>
>> S 6.5.2
>> Values for this Information Element are listed in the "NAT
>> Event
>> Type" registry.
>> -->
>
> [Med] I guess I prefer to keep those.
>
>>
>>
>> 5) <!-- [rfced] The following text was included as a note for
>> IANA. We have removed the text. Please let us know if this is
>> incorrect.
>>
>> <t>Note to IANA: This change also corrects errors
>> in the pointers provided for NAT46/NAT64.</t>
>> -->
>
> [Med] Thanks.
>
>>
>>
>> 6) <!-- [rfced] Section 6.12.2: We are unable to find an
>> informationElementDataType registry on iana.org. From discussion
>> with IANA, it seems "[informationElementDataType] subregistry"
>> was renamed "IPFIX Information Element Data Types" at some point.
>> Assuming this is true, please consider the following updates.
>>
>> Original:
>> 6.12.2. NEW
>>
>> Description: A description of the abstract data type of an
>> IPFIX
>> information element.These are taken from the abstract data
>> types
>> defined in Section 3.1 of the IPFIX Information Model
>> [RFC5102];
>> see that section for more information on the types
>> described in
>> the [informationElementDataType] subregistry. These types
>> are
>> registered in the IANA IPFIX Information Element Data Type
>> subregistry.
>>
>> The [informationElementDataType] subregistry is intended to
>> assign
>> numbers for type names, not to provide a mechanism for
>> adding data
>> types to the IPFIX Protocol, and as such requires a
>> Standards
>> Action [RFC8126] to modify.
>>
>> Additional Information: See the IPFIX Information Element
>> Data Types
>> registry
>> ([https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F
>> %2Fwww.iana.org%2Fassignments%2Fipfix%2F&data=05%7C02%7Cmohamed.b
>> oucadair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a2
>> 0af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098280659%7CUnknown
>> %7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOi
>> JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=fZT
>> qMgUWdeawVC97Zcs0W%2FAxUOKHXF72NDlig4H5Pts%3D&reserved=0
>> ipfix.xhtml#ipfix-information-element-data-types]).
>>
>>
>> Perhaps:
>> 6.12.2. NEW
>>
>> Description: A description of the abstract data type of an
>> IPFIX
>> information element.These are taken from the abstract data
>> types
>> defined in Section 3.1 of the IPFIX Information Model
>> [RFC5102];
>> see that section for more information on the types
>> described in
>> the "IPFIX Information Element Data Types" registry
>> (previously the
>> "informationElementDataType" subregistry). These types are
>> registered in the "IPFIX Information Element Data Types"
>> registry.
>>
>> The "IPFIX Information Element Data Types" registry is
>> intended to assign
>> numbers for type names, not to provide a mechanism for
>> adding data
>> types to the IPFIX Protocol; as such, modifications require
>> Standards
>> Action [RFC8126].
>>
>> Additional Information: See the "IPFIX Information Element
>> Data Types"
>> registry
>> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2Fipfix%2F&data=05%7C02%7Cmohamed.bo
>> ucadair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20
>> af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098288750%7CUnknown%
>> 7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ
>> XaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Vq8v
>> EFpo9%2BQOFPrtg0K5fWkYS9hAUUcQ6%2FvlWsjYm3Q%3D&reserved=0].
>> -->
>
> [Med] Looks good.
>
>>
>>
>> 7) <!-- [rfced] Section 6.13.2: We updated the registry title to
>> refer to the "IPFIX Information Element Semantics" registry,
>> instead of the name of the registry group ("IP Flow Information
>> Export (IPFIX) Entities" registry group). Please confirm this is
>> correct.
>>
>> Original:
>> Additional Information: See the IP Flow Information Export
>> (IPFIX)
>> Entities registry
>> ([https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F
>> %2Fwww.iana.org%2Fassignments%2Fipfix%2F&data=05%7C02%7Cmohamed.b
>> oucadair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a2
>> 0af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098296172%7CUnknown
>> %7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOi
>> JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RUx
>> IUNMNspxE61EY92cciHQ%2FAxRUSFqwFa9wb7bUimI%3D&reserved=0
>> ipfix.xhtml#ipfix-information-element-semantic]).
>>
>> Current:
>> Additional Information: See the "IPFIX Information Element
>> Semantics" registry
>> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2Fipfix&data=05%7C02%7Cmohamed.bouca
>> dair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af3
>> 4b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098303554%7CUnknown%7CT
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW
>> 4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=LK7xneV
>> fcy5iYFno4EspXKtrCqcB75%2FSP%2Fp0Kwp1XR4%3D&reserved=0].
>> -->
>
> [Med] ACK
>
>>
>>
>> 8) <!-- [rfced] Section 6.14.1: We are unable to find an
>> informationElementsUnits registry on iana.org. We believe the
>> informationElementsUnits subregistry was renamed as "IPFIX
>> Information Element Units" registry at some point. Please confirm
>> this is correct.
>
> [Med] ACK.
>
> Assuming this is true, please consider the
>> following updates.
>>
>> Original:
>> 6.14.2. NEW
>>
>> Description: A description of the units of an IPFIX
>> Information
>> Element. These correspond to the units implicitly defined
>> in the
>> Information Element definitions in Section 5 of the IPFIX
>> Information Model [RFC5102]; see that section for more
>> information
>> on the types described in the informationElementsUnits
>> subregistry. These types can take the values in the [IANA
>> IPFIX
>> Information Element Units] subregistry. The special value
>> 0x00
>> (none) is used to note that the field is unitless.
>>
>> Additional Information: See the IPFIX Information Element
>> Units
>> registry ([IANA IPFIX Information Element Units]).
>>
>>
>> Perhaps:
>> 6.14.2. NEW
>>
>> Description: A description of the units of an IPFIX
>> Information
>> Element. These correspond to the units implicitly defined
>> in the
>> Information Element definitions in Section 5 of the IPFIX
>> Information Model [RFC5102]; see that section for more
>> information
>> on the types described in the "IPFIX Information Element
>> Units" registry
>> (previously the informationElementsUnits subregistry).
>> These types
>> can take the values in the "IPFIX Information Element
>> Units" registry.
>> The special value 0x00 (none) is used to note that the
>> field is unitless.
>>
>> Additional Information: See the "IPFIX Information Element
>> Units"
>> registry
>> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2Fipfix&data=05%7C02%7Cmohamed.bouca
>> dair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af3
>> 4b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098311017%7CUnknown%7CT
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW
>> 4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=552TXTV
>> VATp51z68kz140N%2BRbJ2k2p6Eag1DzuqEyBI%3D&reserved=0].
>> -->
>
> [Med] ACK.
>
>>
>>
>> 9) <!-- [rfced] Section 6.14.2 (NEW for informationElementUnits):
>> FYI, if you accept the suggested text in the previous question,
>> we will ask IANA to remove the following sentence from the
>> registry; it is not part of the proposed new text.
>>
>> Original:
>> These types can take the values in the [IANA IPFIX
>> Information Element Units]
>> subregistry.
>> -->
>
> [Med] Not sure about this one. Do you mean this text "These types are
> registered in the [IANA IPFIX Information Element Units] subregistry.",
> instead?
>
>>
>>
>> 10) <!-- [rfced] Section 7.3: It is unclear why there are hyphens
>> after destination and source in the tables. We see the OLD text
>> appears in RFC 6235, and it does not include hyphens. The
>> hyphens also are not used in RFC 5103.
>>
>> For example:
>> destination- Information
>> (i.e., source- or destination-) Information Element
>> destination- element
>>
>> Should the hyphens be removed? For example:
>> destination Information
>> (i.e., source or destination) Information Element
>> destination element
>> -->
>>
>
> [Med] I also think so. OK to change this as well in the NEW. Thanks.
>
>>
>> 11) <!-- [rfced] We removed the reference to [Forwarding-Status]
>> because IANA updated their registry with the link. We updated
>> the text to include the registry title name and the URL to the
>> registry group, based on discussion with IANA. Currently,
>> [Forwarding-Status] only appears in the OLD text. Please review.
>>
>> [Forwarding-Status]
>> IANA, "Forwarding Status (Value 89)",
>>
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2Fipfix%2F&data=05%7C02%7Cmohamed.bo
>> ucadair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20
>> af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098318318%7CUnknown%
>> 7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ
>> XaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=UaYV
>> 5lhrR5Ddi7cBmhVnVRh37ptSNNejzjS9bcInD3U%3D&reserved=0
>> ipfix.xhtml#forwarding-status>.
>>
>> Section 4.3.2 original:
>> - Additional Information: See "NetFlow Version 9 Flow-Record
>> Format"
>> [CCO-NF9FMT]. See the Forwarding Status sub-
>> registries
>> at [Forwarding-Status].
>>
>> Current:
>> Additional Information: See "NetFlow Version 9 Flow-Record
>> Format"
>> [CCO-NF9FMT]. See the "Forwarding Status (Value 89)"
>> registry at
>>
>> [https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.iana.org%2Fassignments%2Fipfix&data=05%7C02%7Cmohamed.bouca
>> dair%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af3
>> 4b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098325669%7CUnknown%7CT
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW
>> 4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=N9TVtGq
>> hPGoMxyN5JXujrV4aJKgNTf1qPN4pqDfMV60%3D&reserved=0].
>> -->
>
> [Med] ACK
>
>>
>>
>> Thank you.
>>
>> RFC Editor
>>
>>
>> On Jan 24, 2025, rfc-edi...@rfc-editor.org wrote:
>>
>> *****IMPORTANT*****
>>
>> Updated 2025/01/24
>>
>> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fwww.rfc-
>> editor.org%2Ffaq%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com
>> %7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6
>> f5d20%7C0%7C0%7C638733438098332916%7CUnknown%7CTWFpbGZsb3d8eyJFbX
>> B0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWF
>> pbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=63evOdWdkBjJsng08zKfSv1X
>> RukO6RXHI9xy3R79R24%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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Ftrustee.ietf.org%2Flicense-
>> info&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d720446a4b2
>> 40ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7
>> C638733438098340318%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd
>> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ
>> %3D%3D%7C0%7C%7C%7C&sdata=xXvNIQIRB86P6xGnBsu3Q6qvrTGS0v6uGZ2ydAH
>> Gl7M%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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
>> 2Fauthors.ietf.org%2Frfcxml-
>> vocabulary&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d7204
>> 46a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0
>> %7C0%7C638733438098347372%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk
>> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldU
>> IjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=pv%2B%2BY%2FPpP1hlXvGo1uonaNXj3Me
>> Nj%2FNe4%2BrNY8JJUTs%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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fmailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-
>> 4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%
>> 7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f
>> 5d20%7C0%7C0%7C638733438098355083%7CUnknown%7CTWFpbGZsb3d8eyJFbXB
>> 0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFp
>> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=HycPZKNvK0DTPrJAf1loEFiz5
>> 0agXLW8eilfWEmRdGA%3D&reserved=0
>>
>> * The archive itself:
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%
>> 7C02%7Cmohamed.boucadair%40orange.com%7C7d720446a4b240ac3b6408dd3
>> cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098
>> 362462%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLj
>> AuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C
>> %7C%7C&sdata=BeFHgeIKja0%2F5UyCO2KiWexwnoBeBAnOTf75XemYc4E%3D&res
>> erved=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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-
>> editor.org%2Fauthors%2Frfc9710.xml&data=05%7C02%7Cmohamed.boucada
>> ir%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b
>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098369591%7CUnknown%7CTWF
>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z
>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PKy9epb1f
>> 1mrOJweMy7CO7LavXnYkgsgx2S4Oc6YZ8w%3D&reserved=0
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-
>> editor.org%2Fauthors%2Frfc9710.html&data=05%7C02%7Cmohamed.boucad
>> air%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34
>> b40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098376710%7CUnknown%7CTW
>> FpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4
>> zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mFxWs6Om
>> K%2BWfF4vr4USMx2Y1C%2BC5OuCHcImrq3put7g%3D&reserved=0
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-
>> editor.org%2Fauthors%2Frfc9710.pdf&data=05%7C02%7Cmohamed.boucada
>> ir%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b
>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098384059%7CUnknown%7CTWF
>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z
>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FHhYiCBmd
>> 9evKeiU8gsX309Nv%2FwVo5KuzAjKq7L8bXI%3D&reserved=0
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-
>> editor.org%2Fauthors%2Frfc9710.txt&data=05%7C02%7Cmohamed.boucada
>> ir%40orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b
>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638733438098391054%7CUnknown%7CTWF
>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z
>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=IByqV24NK
>> nFieSEfjVoNhD778RtXRwQ5nv19FRLXY6k%3D&reserved=0
>>
>> Diff file of the text:
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-editor.org%2Fauthors%2Frfc9710-
>> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d72044
>> 6a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%
>> 7C0%7C638733438098413300%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki
>> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI
>> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=LlDJvAnpyJOryU9%2BzK5b7mC%2FBqPFnQ
>> ljsSgr2df4AWQ%3D&reserved=0
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-editor.org%2Fauthors%2Frfc9710-
>> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d72
>> 0446a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%7
>> C0%7C0%7C638733438098422900%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc
>> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl
>> dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=IOs2ipD6gNda3cPc46gVjKcFMpFvgIB
>> DDzpFF5tGx9k%3D&reserved=0 (side by side)
>>
>> Diff of the XML:
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-editor.org%2Fauthors%2Frfc9710-
>> xmldiff1.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7d7
>> 20446a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfbc48b9253b6f5d20%
>> 7C0%7C0%7C638733438098430551%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h
>> cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsI
>> ldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FN%2Bhfw2PF6%2BcnotzkkBCFL71pk
>> lEIxBcZPgv2WdIn34%3D&reserved=0
>>
>>
>> Tracking progress
>> -----------------
>>
>> The details of the AUTH48 status of your document are here:
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>> Fwww.rfc-
>> editor.org%2Fauth48%2Frfc9710&data=05%7C02%7Cmohamed.boucadair%40
>> orange.com%7C7d720446a4b240ac3b6408dd3cad7839%7C90c7a20af34b40bfb
>> c48b9253b6f5d20%7C0%7C0%7C638733438098438132%7CUnknown%7CTWFpbGZs
>> b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsI
>> kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=E0x%2FHML4LJqg
>> 0bWNl67yXjQ2Y%2Fp2xWnW6iCqvlji%2Fl4%3D&reserved=0
>>
>> Please let us know if you have any questions.
>>
>> Thank you for your cooperation,
>>
>> RFC Editor
>>
>> --------------------------------------
>> RFC9710 (draft-ietf-opsawg-ipfix-fixes-12)
>>
>> Title : Simple Fixes to the IP Flow Information Export
>> (IPFIX) Entities IANA Registry
>> Author(s) : M. Boucadair, B. Claise
>> WG Chair(s) : Henk Birkholz, Joe Clarke
>> Area Director(s) : Warren Kumari, 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
