Thanks Med! Alice — closing loop on my previous comment, this sounds acceptable to me as well. I approve publication.
Thanks, Carlos. > On Jun 18, 2026, at 9:09 AM, [email protected] wrote: > > Hi Alice, all, > > I disapprove the changes of the normative language in Section 3.7. Please > revert these changes and add relevant boilerplate. > > Thank you. > > Cheers, > Med > >> -----Message d'origine----- >> De : Alice Russo <[email protected]> >> Envoyé : jeudi 18 juin 2026 00:18 >> À : Carlos Pignataro <[email protected]>; BOUCADAIR Mohamed >> INNOV/NET <[email protected]> >> Cc : Adrian Farrel <[email protected]>; >> [email protected]; [email protected]; >> [email protected]; [email protected]; Mahesh Jethanandani >> <[email protected]>; RFC Editor <[email protected]>; >> auth48archive <[email protected]> >> Objet : AD - Re: Final Review: RFC-to-be 10014 (draft-ietf-opsawg- >> oam-characterization) in XML >> >> >> Carlos, Med (as AD), >> >> * Med, re: the lowercasing of the two SHOULDs, we await your reply >> to this mail from Carlos (15 June): >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> mailarchive.ietf.org%2Farch%2Fmsg%2Fauth48archive%2F5OFvsUA8GkPDXC >> DGXC8LRyxWrjQ%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1 >> 018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20 >> %7C0%7C0%7C639173314907088795%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h >> cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl >> dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=CZi3Xp2Qkfd4KVIHOuRN0e6CH6zoapLW >> 2IqR7Xrc7Co%3D&reserved=0 >> >> >> Thank you for your reply, Carlos. Please see the follow-ups below. >> The revised files are here (please refresh): >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc10014.html&data=05%7C02%7Cmohamed.boucad >> air%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b >> 40bfbc48b9253b6f5d20%7C0%7C0%7C639173314907104344%7CUnknown%7CTWFp >> bGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMi >> IsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=g9GSW2SLSsPp >> f%2BJo88DXTLC9k4G7pTsCBOIuYWYKv0s%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc10014.txt&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639173314907115270%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=b%2FpcqGO8yAc >> D%2FPsb%2FryIbEnepandZs%2FFQRgj5sSWuGI%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc10014.pdf&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639173314907127292%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=WbzZ14OICmPDg >> IMMPAY2jnIlpRiGJGRlZI4HvpPT5L8%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc10014.xml&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639173314907141910%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=9RDEbZqZ46VQP >> 2iwO98Xq%2BkbJmwDPFgA7otrwFG%2FqlE%3D&reserved=0 >> >> This diff file shows all changes from the approved I-D: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc10014- >> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1018bb28 >> d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C639173314907152678%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=M3yJDoRIZEadrtWxfzjsdgBM2otgBGObK1Kmlml >> EbmI%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc10014- >> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1018b >> b28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 >> %7C0%7C639173314907162895%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj >> oyfQ%3D%3D%7C0%7C%7C%7C&sdata=uEPR%2Baxs3XIFJNUzKLRMuJYRRTbExvhuQf >> NrbVeYc2A%3D&reserved=0 (side by side) >> >> This diff file shows the changes made during Final Review thus >> far: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc10014- >> auth48diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C10 >> 18bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20% >> 7C0%7C0%7C639173314907173477%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3int1X1bvoxcQk3IHYOWxmx%2FnBtGcQC >> 3BPSxc%2FZnVwo%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc10014- >> auth48rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 >> C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d >> 20%7C0%7C0%7C639173314907183896%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ssOBT96joBTZmJCUoFd5V7FEtLNHmo >> CJHgAHoJpv55A%3D&reserved=0 (side by side) >> >> >> Re: #8, we added the sentence in Section 3.4. Please review. >> Current: >> >> An example of "Equal-Forwarding-Treatment OAM" is presented in >> [RFC9551] in the context of Deterministic Networking (DetNet) >> OAM: >> "it traverses the same set of links and interfaces receiving >> the same >> QoS and Packet Replication, Elimination, and Ordering Functions >> (PREOF) treatment as the monitored DetNet flow". (The property >> of >> "Equal-Forwarding-Treatment" is referred to in [RFC9551] as >> "In-band >> OAM".) >> >> Re: #15 (Acknowledgements), removed duplicate as requested. FYI, >> we added a hyphen in "Huang-Feng" because of Alex's recent reply >> on this topic >> (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fmailarchive.ietf.org%2Farch%2Fmsg%2Fauth48archive%2FcNQMWS7FtV75D >> RiiExd5Idx3m4E%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C >> 1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d2 >> 0%7C0%7C0%7C639173314907193853%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1 >> hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsI >> ldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=4TAO8ZFSS3aHpICLwfO3GnBPFojdQ3U >> OEioUaZdK0zQ%3D&reserved=0). >> >> You wrote: >>> After implementing these updates on this email thread, please >> mark my Approval on this document. >>> Approved. >> >> Your approval has been recorded. >> >> This page shows the Final Review status of your document: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> queue.rfc-editor.org%2Ffinal- >> review%2Frfc10014&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C >> 1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d2 >> 0%7C0%7C0%7C639173314907204229%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1 >> hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsI >> ldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ulvn9Y8KOQhkGlIlbfdfJG6AawSEW4s >> oR7myAgVbjt8%3D&reserved=0 >> >> Thank you. >> >> Alice Russo >> RFC Production Center >> >>> On Jun 13, 2026, at 4:12 AM, Carlos Pignataro >> <[email protected]> wrote: >>> >>> Hi, Alice, >>> >>> Many thanks for this work, edits, and questions! >>> >>> Please find some responses inline. >>> >>> Additionally, I’d like to request these updates: >>> >>> 14. Grammo >>> OLD: >>> While this document introduces new terminology, it is does >> not update >>> or change the meaning of terminology found in existing RFCs. >>> >>> NEW: >>> While this document introduces new terminology, it does not >> update >>> or change the meaning of terminology found in existing RFCs. >>> >>> 15. Duplicate >>> OLD: >>> The authors wish to thank, chronologically, Hesham Elbakoury, >> Michael >>> Richardson, Stewart Bryant, Greg Mirsky, Med Boucadair, Loa >>> Andersson, Thomas Graf, Alex Huang Feng, Xiao Min, Dhruv >> Dhody, Henk >>> Birkholz, Alex Huang Feng, Tom Petch, Roni Even, Tim Chown, >> Marcus >>> Ihlar, Med Boucadair, Benoit Claise, Chongfeng Xie, Robert >> Sparks, >>> Kyle Rose, Mach Chen, Roman Danyliw, Gorry Fairhurst, Éric >> Vyncke, >>> Andy Newton, Deb Cooley, Ketan Talaulikar, and Gunter Van de >> Velde >>> for their thorough review and useful feedback comments that >> greatly >>> improved this document. >>> >>> NEW: >>> The authors wish to thank, chronologically, Hesham Elbakoury, >> Michael >>> Richardson, Stewart Bryant, Greg Mirsky, Med Boucadair, Loa >>> Andersson, Thomas Graf, Alex Huang Feng, Xiao Min, Dhruv >> Dhody, Henk >>> Birkholz, Tom Petch, Roni Even, Tim Chown, Marcus >>> Ihlar, Med Boucadair, Benoit Claise, Chongfeng Xie, Robert >> Sparks, >>> Kyle Rose, Mach Chen, Roman Danyliw, Gorry Fairhurst, Éric >> Vyncke, >>> Andy Newton, Deb Cooley, Ketan Talaulikar, and Gunter Van de >> Velde >>> for their thorough review and useful feedback comments that >> greatly >>> improved this document. >>> >>> 16: Carlos’ email contact >>> OLD: >>> Carlos Pignataro >>> Blue Fern Consulting >>> United States of America >>> Email: [email protected], [email protected] >>> >>> NEW: >>> Carlos Pignataro >>> Blue Fern Consulting >>> United States of America >>> Email: [email protected] >>> >>> More inline >>> >>>> On Jun 12, 2026, at 11:35 PM, [email protected] wrote: >>>> >>>> Authors, >>>> >>>> While reviewing this document during Final Review, please >> resolve (as >>>> necessary) the following questions, which are also in the >> source file. >>>> >>>> 1. This document will become part of BCP 161 because it updates >> RFC 6291. >>>> If this is not correct (i.e., it should be assigned a new BCP >>>> number), please let us know. >>>> >>>> See the complete list of BCPs here: >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www >>>> .rfc-editor.org%2Fbcp%2Fbcp- >> index.txt&data=05%7C02%7Cmohamed.boucadai >>>> >> r%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40 >> bfb >>>> >> c48b9253b6f5d20%7C0%7C0%7C639173314907214139%7CUnknown%7CTWFpbGZsb >> 3d8 >>>> >> eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIj >> oiT >>>> >> WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=N7C%2Bk%2Fe6xm1bY2jqi%2 >> BCk >>>> l613ZSR1HMoeIIa%2Baeo0yYk%3D&reserved=0 >>>> >>> >>> Correct >>> >>>> >>>> 2. Please insert any keywords (beyond those that appear in the >> title) >>>> for use on >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fsearch&data=05%7C02%7Cmohamed.boucadair%40orange.com% >> 7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5 >> d20%7C0%7C0%7C639173314907224081%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e >> U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI >> sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XBVRVrR3m6eVJ%2F5CErnN58q0qBI >> D7YxM7n%2F63QyDBjI%3D&reserved=0. >>>> >>> >>> >>> Suggested keywords: OAM, in-band, out-of-band, path-congruent, >> active >>> OAM, passive OAM, hybrid OAM, in-data-packet, forwarding >> treatment >>> >>>> >>>> 3. We note that [RFC9341] uses "Alternate-Marking" rather than >>>> "Alternate Marking". Should the hyphen be added here? >>>> >>>> Current: >>>> Another example of "Hybrid Type I OAM" that is also "In-Data- >> Packet >>>> OAM" is Alternate Marking [RFC9341], when applied to data >> packets of >>>> a single stream. >>>> >>> >>> No. We use “Alternate Marking” as a noun, “Alternate-Marking” as >>> adjective. Same as RFC9341 ("Indeed, Alternate Marking can be)”, >> "that >>> Service Providers using Alternate Marking must do”, "Alternate- >> Marking >>> Method”, "Alternate-Marking technique”.) >>> >>> Please keep as is. >>> >>>> >>>> 4. For clarity, what does "allowing for packet loss >> computation" refer to? >>>> >>>> Original: >>>> Instead, OAM >>>> packets are used for carrying information about observed >> network >>>> characteristics, namely user packet counter values, allowing >> for >>>> packet loss computation. >>>> >>>> Option A (if characteristics allow for the computation): >>>> Instead, OAM >>>> packets are used for carrying information about observed >> network >>>> characteristics (namely, user packet counter values) allowing >> for >>>> packet loss computation. >>>> >>>> Option B (if values allow for the computation): >>>> Instead, OAM >>>> packets are used for carrying information about observed >> network >>>> characteristics - namely, user packet counter values that >> allow for >>>> packet loss computation. >>> >>> Option B >>> >>>> >>>> >>>> 5. For clarity, should "Path Followed OAM" be "Path-Followed >> OAM" >>>> or "Path-Following OAM"? This term has not appeared in any >> RFCs, and >>>> it appears only once in this document. >>>> >>> >>> Please rename section 3.3 to be consistent with 3.4 and others >>> >>> OLD: >>> 3.3. Path Followed OAM >>> >>> NEW: >>> 3.3. Path-Congruent OAM >>> >>> >>> >>>> >>>> 6. FYI, we added hyphens to the section title to make "3.4. >>>> Packet-Forwarding-Treatment OAM" >>>> similar to usage of "Equal-Forwarding-Treatment OAM" and >>>> "Different-Forwarding-Treatment OAM" in this document. >>>> Please let us know if you prefer otherwise. >>>> >>> >>> Accepted. >>> >>>> >>>> 7. For readability, may "forwarding (e.g., QoS) treatment" be >>>> changed to "forwarding treatment (e.g., QoS)"? There are 4 >> instances >>>> in this document. For example: >>>> >>>> Original: >>>> Equal-Forwarding-Treatment OAM: >>>> The OAM packets receive the same forwarding (e.g., QoS) >> treatment >>>> as user data packets. >>>> >>>> Perhaps: >>>> Equal-Forwarding-Treatment OAM: >>>> The OAM packets receive the same forwarding treatment (e.g., >> QoS) >>>> as user data packets. >>>> >>> >>> Yes, for all instances. >>> >>>> >>>> 8. Section 3.4: To make it clear to the reader why the >> definition of >>>> "In-band OAM" is being quoted here, would you like to add a >> sentence >>>> (similar to that in Appendix A) here as well? >>> >>> Yes, pelase. >>> >>>> >>>> In other words, the quote is from the definition for "In-band >> OAM" >>>> in Section 1.1 of [RFC9551], and the mapping is explained in >> Appendix A: >>>> The property of "Equal-Forwarding-Treatment" is referred to in >>>> [RFC9551] as "In-band OAM". >>>> >>>> Original: >>>> An example of "Equal-Forwarding-Treatment OAM" is presented in >>>> [RFC9551] in the context of Deterministic Networking (DetNet) >> OAM: >>>> "it traverses the same set of links and interfaces receiving >> the same >>>> QoS and Packet Replication, Elimination, and Ordering >> Functions >>>> (PREOF) treatment as the monitored DetNet flow". >>>> >>>> >>>> 9. For [P4-INT-2.1], may the provided URL be replaced? The URL >>>> provided >>>> >> (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fp4 >>>> .org%2Fp4- >> spec%2Fdocs%2FINT_v2_1.pdf&data=05%7C02%7Cmohamed.boucadair%40oran >> ge.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9 >> 253b6f5d20%7C0%7C0%7C639173314907233839%7CUnknown%7CTWFpbGZsb3d8ey >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi >> TWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cC8POrpyw1p4yM6HUX4Fto >> H%2FTtsOVI3%2BnrbzUnjFqnI%3D&reserved=0) is 404. We have found >> the following URL, which appears to match the information in the >> reference: >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> p4. >>>> org%2Fwp-content%2Fuploads%2Fsites%2F53%2Fp4- >> spec%2Fdocs%2FINT_v2_1.p >>>> >> df&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1018bb28d4054bd >> 53f >>>> >> 3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639173 >> 314 >>>> >> 907243533%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIw >> LjA >>>> >> uMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7 >> C%7 >>>> >> C&sdata=gOhIS9iSqJbU62YM%2F8zsY9wlSmvurm9s%2Bbsd2xKFGKc%3D&reserve >> d=0 >>>> Is this the correct updated URL? >>> >>> Correct. Please update the URL >>> >>>> >>>> >>>> 10. How may this be rephrased to avoid the repetition of >> "similar >>>> uses still use"? Does "documents" convey the intended meaning? >>>> >>>> Original: >>>> Other similar uses, including [P4-INT-2.1], still use >>>> variations of "in-band", "in band", or "inband". >>>> >>>> Perhaps: >>>> Other similar documents, including [P4-INT-2.1], still use >>>> variations of "in-band", "in band", or "inband". >>>> >>> >>> Yes. >>> >>>> >>>> 11. Does RFC 9912 (which was draft-ietf-raw-architecture) still >>>> contain similar text? If not, please provide updated text. >>>> (We were not able to identify the similar text.) >>> >>> Because of our review of the draft, that text was removed: >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> auth >>> or-tools.ietf.org%2Fiddiff%3Furl1%3Ddraft-ietf-raw-architecture- >> 26%26u >>> rl2%3Ddraft-ietf-raw-architecture-27%26difftype%3D-- >> html&data=05%7C02% >>> >> 7Cmohamed.boucadair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4de >> e%7C >>> >> 90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639173314907253774%7CUn >> know >>> >> n%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOi >> JXaW >>> >> 4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BOpMRn >> hc1A >>> iZu2vZD5zrBBuDs%2FIBoEf4rvoAAq0oszc%3D&reserved=0 >>> >>> Please remove the sentence "[RFC9912] uses similar text.” And >> associated reference. >>> >>>> >>>> Current: >>>> Similarly, the property of "Different- Forwarding-Treatment >> OAM" >>>> can be found in the following definition in >>>> [RFC9551]: "Out-of-band OAM: an active OAM method whose path >> through >>>> the DetNet domain may not be topologically identical to the >> path of >>>> the monitored DetNet flow, its test packets may receive >> different QoS >>>> and/or PREOF treatment, or both." [RFC9912] uses similar text. >>>> >>>> >>>> 12. Please review the "Inclusive Language" portion of the >> online >>>> Style Guide >>>> >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fww >>>> w.rfc- >> editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05 >>>> >> %7C02%7Cmohamed.boucadair%40orange.com%7C1018bb28d4054bd53f3e08dec >> cbe >>>> >> 4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6391733149072643 >> 72% >>>> >> 7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMC >> IsI >>>> >> lAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata >> =bn >>>> 33Sb%2Fg%2Fy3yk%2BMJ42fsOMb9XMCJSSSfXyBl2wHcmX4%3D&reserved=0> >>>> and let us know if any changes are needed. Updates of this >> nature >>>> typically result in more precise language, which is helpful for >> readers. >>> >>> No inclusive language concerns identified. >>> >>> Thanks! >>> >>> Carlos. >>> >>>> >>>> Note that our script did not flag any words in particular, but >> this >>>> should still be reviewed as a best practice. >>>> >>>> Thank you. >>>> >>>> Alice Russo >>>> RFC Production Center >>>> >>>> >>>> On Jun 12, 2026, [email protected] wrote: >>>> >>>> *****IMPORTANT***** >>>> >>>> RFC Author(s): >>>> -------------- >>>> >>>> Final Review for RFC-to-be 10014 >>>> <draft-ietf-opsawg-oam-characterization> >>>> >>>> Your document is now available for Final Review (previously >> 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; see >>>> the Unavailable Authors section >>>> >> (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fauthors.ietf.org%2Frfc-publication-process%23unavailable- >> authors&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1018bb28d4 >> 054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0% >> 7C639173314907275001%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd >> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ% >> 3D%3D%7C0%7C%7C%7C&sdata=ANAk0sDlQaSijD9K2RbdXQgI11YL8jS6uCxkP5VO% >> 2Fog%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%7C1018bb28d4054 >> bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 >> 39173314907286712%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs >> IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% >> 3D%7C0%7C%7C%7C&sdata=R%2Bdhml83e5MGE5Prqm37oYkkeoTz%2BziotUcSwKTO >> KFk%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%7C1018bb2 >> 8d4054bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 >> C0%7C639173314907309914%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn >> RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy >> fQ%3D%3D%7C0%7C%7C%7C&sdata=V%2F3A4KEsG%2FHGFNKXyz1JWcenSJPqasNI4d >> %2FgKjcGFBE%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 >>>> >>>> * [email protected] (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). >>>> >>>> * [email protected], which is an archival mailing >> list >>>> to preserve discussion about the document while in the RPC >> editorial >>>> queue; it is not an active discussion list: >>>> >>>> * More info: >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> mai >>>> larchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh- >> 4Q9l2USxIAe >>>> >> 6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1018bb28d4 >> 054 >>>> >> bd53f3e08deccbe4dee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 >> 391 >>>> >> 73314907324367%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlY >> iOi >>>> >> IwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0 >> %7C >>>> >> %7C%7C&sdata=ht0nkYQB%2BGCETYKX3pIGff0HYQ6p5zWTs3MYRR4veaI%3D&rese >> rve >>>> d=0 >>>> >>>> * The archive itself: >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> mai >>>> >> larchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C02% >> 7Cm >>>> >> ohamed.boucadair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7 >> C90 >>>> >> c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639173314907339135%7CUnkn >> own >>>> >> %7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ >> XaW >>>> >> 4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1OpDrFAh >> yHQ >>>> v%2BhTrzizOY%2Fz2nyq37IxXKDh%2Bzcl8LP4%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, >>>> [email protected] 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%2Frfc10014.xml&data=05%7C02%7Cmohamed.bouca >>>> >> dair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34 >> b40 >>>> >> bfbc48b9253b6f5d20%7C0%7C0%7C639173314907354223%7CUnknown%7CTWFpbG >> Zsb >>>> >> 3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkF >> OIj >>>> >> oiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FRjtkyl5leCxtN%2FD >> CRn >>>> Dowk9QPB5jYTmHB8xp0bM0W4%3D&reserved=0 >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www >>>> .rfc- >> editor.org%2Fauthors%2Frfc10014.html&data=05%7C02%7Cmohamed.bouc >>>> >> adair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af3 >> 4b4 >>>> >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639173314907367428%7CUnknown%7CTWFpb >> GZs >>>> >> b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIk >> FOI >>>> >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=f%2B6w65O79KH39LR0g >> chf >>>> dphe29pgkyRo4Octq%2FoJV7U%3D&reserved=0 >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www >>>> .rfc- >> editor.org%2Fauthors%2Frfc10014.pdf&data=05%7C02%7Cmohamed.bouca >>>> >> dair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34 >> b40 >>>> >> bfbc48b9253b6f5d20%7C0%7C0%7C639173314907378166%7CUnknown%7CTWFpbG >> Zsb >>>> >> 3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkF >> OIj >>>> >> oiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=pTcMt3N09y8YIJ3dNGz9 >> yLJ >>>> wdiA2wSUh%2Bl6Wu9O5YZg%3D&reserved=0 >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www >>>> .rfc- >> editor.org%2Fauthors%2Frfc10014.txt&data=05%7C02%7Cmohamed.bouca >>>> >> dair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a20af34 >> b40 >>>> >> bfbc48b9253b6f5d20%7C0%7C0%7C639173314907388305%7CUnknown%7CTWFpbG >> Zsb >>>> >> 3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkF >> OIj >>>> >> oiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cszjRmfAfeBtFp3IX1%2 >> BhN >>>> MALESfT3lOxRlK7YOqAn18%3D&reserved=0 >>>> >>>> Diff file of the text: >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www >>>> .rfc-editor.org%2Fauthors%2Frfc10014- >> diff.html&data=05%7C02%7Cmohamed >>>> >> .boucadair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a >> 20a >>>> >> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C639173314907398641%7CUnknown%7C >> TWF >>>> >> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM >> iIs >>>> >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Iv4jo5%2F7tUCA >> nTY >>>> lQJIHUaq8zXrsLJtuoQhMQS9j9ek%3D&reserved=0 >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www >>>> .rfc-editor.org%2Fauthors%2Frfc10014- >> rfcdiff.html&data=05%7C02%7Cmoha >>>> >> med.boucadair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90 >> c7a >>>> >> 20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639173314907408790%7CUnknown >> %7C >>>> >> TWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW >> 4zM >>>> >> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MrLItgFLH7m >> 5%2 >>>> FaD8mu0UUa9kU7X87tF4MSuVgtvjwzs%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%2Frfc10014- >> xmldiff1.html&data=05%7C02%7Cmoh >>>> >> amed.boucadair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C9 >> 0c7 >>>> >> a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639173314907418905%7CUnknow >> n%7 >>>> >> CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa >> W4z >>>> >> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=G%2Bmy%2FB >> Hot >>>> MDgEuJaYhw6UFr8EbG70ijPknhcCf1F6d8%3D&reserved=0 >>>> >>>> >>>> Tracking progress >>>> ----------------- >>>> >>>> Details on the status of your Final Review are here: >>>> >>>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> que >>>> ue.rfc-editor.org%2Ffinal- >> review%2Frfc10014%2F&data=05%7C02%7Cmohamed >>>> >> .boucadair%40orange.com%7C1018bb28d4054bd53f3e08deccbe4dee%7C90c7a >> 20a >>>> >> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C639173314907428552%7CUnknown%7C >> TWF >>>> >> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM >> iIs >>>> >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=k%2Fhhxmz01B0A >> 7lq >>>> Jz1ljUyeyqCvex0Tnrhmx3gMPGi0%3D&reserved=0 >>>> >>>> Please let us know if you have any questions. >>>> >>>> Thank you for your cooperation, >>>> >>>> RFC Editor >>>> >>>> -------------------------------------- >>>> RFC 10014 (draft-ietf-opsawg-oam-characterization) >>>> >>>> Title : Guidelines for Characterizing the Term "OAM" >>>> Author(s) : C. Pignataro, >>>> A. Farrel, >>>> T. Mizrahi >>>> 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 -- [email protected] To unsubscribe send an email to [email protected]
