Was that the
<BEGIN TEMPLATE TEXT>
OAM terms [INSERT TERMS] are to be interpreted as described in
[RFC10014].
<END TEMPLATE TEXT>
Or the SHOULDs?
Thanks,
Carlos.
> On Jun 15, 2026, at 7:33 AM, [email protected] wrote:
>
> Hi all,
>
> That wording/language (and all compliance text blob) was added to the draft
> to address a DISCUSS from Gunter.
>
> I suggest to keep it and add the typical keyword text.
>
> Thank you.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : Tal Mizrahi <[email protected]>
>> Envoyé : dimanche 14 juin 2026 09:20
>> À : Carlos Pignataro <[email protected]>; Alice Russo
>> <[email protected]>; RFC Editor <rfc-editor@rfc-
>> editor.org>
>> Cc : Adrian Farrel <[email protected]>; [email protected];
>> [email protected]; BOUCADAIR Mohamed INNOV/NET
>> <[email protected]>; [email protected]; Mahesh
>> Jethanandani <[email protected]>; auth48archive
>> <[email protected]>
>> Objet : Re: Final Review: RFC-to-be 10014 (draft-ietf-opsawg-oam-
>> characterization) in XML
>>
>>
>> Dear RFC Editor team,
>>
>> Thanks for your thorough work on this document!
>> I agree with Carlos' suggestions and comments (including the one
>> about changing the SHOULD to lowercase).
>> Assuming these suggestions are implemented, I approve.
>>
>> Thanks,
>> Tal.
>>
>> On Sat, Jun 13, 2026 at 2:15 PM Carlos Pignataro
>> <[email protected]> wrote:
>>>
>>> Hi, Alice,
>>>
>>> I tend to prefer removing those instances and use lowercase.
>>>
>>> But I leave this decision to Adrian and Tal.
>>>
>>>
>>> Alice,
>>>
>>> After implementing these updates on this email thread, please
>> mark my Approval on this document.
>>> Approved.
>>>
>>> Thanks,
>>>
>>> Carlos.
>>>
>>>> On Jun 13, 2026, at 12:23 AM, Alice Russo <[email protected]
>> editor.org> wrote:
>>>>
>>>> Authors,
>>>> An additional question.
>>>>
>>>> re:
>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> ww
>>>> w.rfc-editor.org%2Fauthors%2Frfc10014.html%23section-
>> 3.7&data=05%7C0
>>>>
>> 2%7Cmohamed.boucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55
>> 51
>>>>
>> 2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275809998%
>> 7C
>>>>
>> Unknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIs
>> Il
>>>>
>> AiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=
>> 58
>>>> xwP9nCHmhNMnfpgJVpt37BsAd0k2%2FXyuqoCHsOrAA%3D&reserved=0
>>>>
>>>> 13. 'SHOULD' is used twice in this document. Do you prefer to
>> add the typical keywords paragraph and the references to [RFC2119]
>> and [RFC8174], or remove the 2 instances?
>>>>
>>>> Thank you.
>>>>
>>>> Alice Russo
>>>> RFC Production Center
>>>>
>>>>> On Jun 12, 2026, at 2: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
>> w
>>>>> ww.rfc-editor.org%2Fbcp%2Fbcp-
>> index.txt&data=05%7C02%7Cmohamed.bouc
>>>>>
>> adair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%7C90c7a20af3
>> 4
>>>>>
>> b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275829045%7CUnknown%7CTWF
>> p
>>>>>
>> bGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMi
>> I
>>>>>
>> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MabvmpjoQc%2B
>> o
>>>>> lyjpnpdVCXEJQHt4eHV5s6zqnRq9QfQ%3D&reserved=0
>>>>>
>>>>>
>>>>> 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%
>> 7C56bb3b09ed264c5e87b008dec9e55512%7C90c7a20af34b40bfbc48b9253b6f5
>> d20%7C0%7C0%7C639170184275841405%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e
>> U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI
>> sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=qQ8GlnBBPtAagXsUHkvt6iTR4ipYL
>> DCEYHQuFZMnECQ%3D&reserved=0.
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> 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?
>>>>>
>>>>> 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
>> F
>>>>> p4.org%2Fp4-
>> spec%2Fdocs%2FINT_v2_1.pdf&data=05%7C02%7Cmohamed.boucadair%40oran
>> ge.com%7C56bb3b09ed264c5e87b008dec9e55512%7C90c7a20af34b40bfbc48b9
>> 253b6f5d20%7C0%7C0%7C639170184275852430%7CUnknown%7CTWFpbGZsb3d8ey
>> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi
>> TWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=TjhanD8W%2BlgzaZVaE1j7
>> 34gEv%2F%2FqF%2FtIMqbYmVwvgEQ%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
>> p
>>>>> 4.org%2Fwp-content%2Fuploads%2Fsites%2F53%2Fp4-
>> spec%2Fdocs%2FINT_v2
>>>>>
>> _1.pdf&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C56bb3b09ed2
>> 6
>>>>>
>> 4c5e87b008dec9e55512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C
>> 6
>>>>>
>> 39170184275863160%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs
>> I
>>>>>
>> lYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3
>> D
>>>>>
>> %7C0%7C%7C%7C&sdata=PQ8sI%2B%2BFgHIwkr8b7BZYXQPda9GvUQrgqqBUkU64Gv
>> o
>>>>> %3D&reserved=0
>>>>> Is this the correct updated 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".
>>>>>
>>>>>
>>>>> 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.)
>>>>>
>>>>> 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
>> F
>>>>> www.rfc-
>> editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&dat
>>>>>
>> a=05%7C02%7Cmohamed.boucadair%40orange.com%7C56bb3b09ed264c5e87b00
>> 8
>>>>>
>> dec9e55512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6391701842
>> 7
>>>>>
>> 5873769%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLj
>> A
>>>>>
>> uMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7
>> C
>>>>>
>> %7C&sdata=ywbCVuchZ7Zb3KrIV7fhK4ikW%2FAC1ziss7ZDnL3pblc%3D&reserve
>> d
>>>>> =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.
>>>>>
>>>>> 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%7C56bb3b09ed
>> 264c5e87b008dec9e55512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%
>> 7C639170184275883982%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd
>> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%
>> 3D%3D%7C0%7C%7C%7C&sdata=5adegApa%2BhIvz6%2FcsG7rZnMzyUC2AFYpVidy0
>> 7ObY64%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%7C56bb3b09ed264
>> c5e87b008dec9e55512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6
>> 39170184275894044%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs
>> IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%
>> 3D%7C0%7C%7C%7C&sdata=DWY7DExA21aUoKSyNn8joXU%2FbX6iS%2BdekwHzhCIh
>> qck%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%7C56bb3b0
>> 9ed264c5e87b008dec9e55512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7
>> C0%7C639170184275905239%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn
>> RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy
>> fQ%3D%3D%7C0%7C%7C%7C&sdata=s8hmGpCc1HE2AHcnASDk9YutdoXIkJSmTrTHGy
>> K%2FDkM%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
>> m
>>>>> ailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-
>> 4Q9l2US
>>>>>
>> xIAe6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C56bb3b
>> 0
>>>>>
>> 9ed264c5e87b008dec9e55512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7
>> C
>>>>>
>> 0%7C639170184275914882%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR
>> y
>>>>>
>> dWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ
>> %
>>>>>
>> 3D%3D%7C0%7C%7C%7C&sdata=fU0ATPDe6ZlRCbq6V13%2F0sfzugRWuKBM9ijbvSP
>> N
>>>>> mAI%3D&reserved=0
>>>>>
>>>>> * The archive itself:
>>>>>
>>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> m
>>>>>
>> ailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C0
>> 2
>>>>>
>> %7Cmohamed.boucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e555
>> 1
>>>>>
>> 2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275926654%
>> 7
>>>>>
>> CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCI
>> s
>>>>>
>> IlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdat
>> a
>>>>> =OwUvJYZ1cAZDbBV4%2BG1Nt69FNsgc0NvBRE3vgYBNwKc%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
>> w
>>>>> ww.rfc-
>> editor.org%2Fauthors%2Frfc10014.xml&data=05%7C02%7Cmohamed.b
>>>>>
>> oucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%7C90c7a20
>> a
>>>>>
>> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275937236%7CUnknown%7C
>> T
>>>>>
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4
>> z
>>>>>
>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MPalv6s22p
>> o
>>>>> Tj8oT%2BdAqomQxarl6fgMDJBHxHmywca4%3D&reserved=0
>>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> w
>>>>> ww.rfc-
>> editor.org%2Fauthors%2Frfc10014.html&data=05%7C02%7Cmohamed.
>>>>>
>> boucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%7C90c7a2
>> 0
>>>>>
>> af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275947027%7CUnknown%7
>> C
>>>>>
>> TWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW
>> 4
>>>>>
>> zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=rUVsK7PC8
>> N
>>>>> RDFgZclleeZX9UgCUk6VcpLEKAPCE2eig%3D&reserved=0
>>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> w
>>>>> ww.rfc-
>> editor.org%2Fauthors%2Frfc10014.pdf&data=05%7C02%7Cmohamed.b
>>>>>
>> oucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%7C90c7a20
>> a
>>>>>
>> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275956666%7CUnknown%7C
>> T
>>>>>
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4
>> z
>>>>>
>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Zl2GgGxQIZ
>> k
>>>>> 8%2BqvRiVV4Q3SELMw5CHmqB4pgF2mdFmU%3D&reserved=0
>>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> w
>>>>> ww.rfc-
>> editor.org%2Fauthors%2Frfc10014.txt&data=05%7C02%7Cmohamed.b
>>>>>
>> oucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%7C90c7a20
>> a
>>>>>
>> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275966653%7CUnknown%7C
>> T
>>>>>
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4
>> z
>>>>>
>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=srX%2FbSDV
>> 3
>>>>> YqUjE7eY%2BtMOABCq6fQZyv8d692VkGuscc%3D&reserved=0
>>>>>
>>>>> Diff file of the text:
>>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> w
>>>>> ww.rfc-editor.org%2Fauthors%2Frfc10014-
>> diff.html&data=05%7C02%7Cmoh
>>>>>
>> amed.boucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%7C9
>> 0
>>>>>
>> c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275976567%7CUnkn
>> o
>>>>>
>> wn%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiO
>> i
>>>>>
>> JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=c2cC
>> K
>>>>> ElkYn1E7KHoXJ7FxHqX4HZbsZoktj5KO1VzdAQ%3D&reserved=0
>>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> w
>>>>> ww.rfc-editor.org%2Fauthors%2Frfc10014-
>> rfcdiff.html&data=05%7C02%7C
>>>>>
>> mohamed.boucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%
>> 7
>>>>>
>> C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275986439%7CU
>> n
>>>>>
>> known%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIl
>> A
>>>>>
>> iOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=p
>> Z
>>>>> JmZZPCkmiVobTdlpHj4HrEnn%2BqAs9m0yxr21Yteyg%3D&reserved=0
>> (side by
>>>>> side)
>>>>>
>>>>> Diff of the XML:
>>>>>
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> w
>>>>> ww.rfc-editor.org%2Fauthors%2Frfc10014-
>> xmldiff1.html&data=05%7C02%7
>>>>>
>> Cmohamed.boucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512
>> %
>>>>>
>> 7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184275996335%7C
>> U
>>>>>
>> nknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsI
>> l
>>>>>
>> AiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=
>> D
>>>>> CteY%2BI6YrnWoV6o4PG6rNj%2BsCUHYq8o2YI6giScO6M%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
>> q
>>>>> ueue.rfc-editor.org%2Ffinal-
>> review%2Frfc10014%2F&data=05%7C02%7Cmoh
>>>>>
>> amed.boucadair%40orange.com%7C56bb3b09ed264c5e87b008dec9e55512%7C9
>> 0
>>>>>
>> c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639170184276006285%7CUnkn
>> o
>>>>>
>> wn%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiO
>> i
>>>>>
>> JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RWW0
>> 0
>>>>> NnfezBmPfSFjq%2BwUcJM6of%2FAth688bH86szSPQ%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
>>>>>
>>>>
>>>>
>>>>
>>>> Thank you.
>>>>
>>>> Alice Russo
>>>> RFC Production Center
>>>>
>>>>
>>>>
>>>>
>>>
> ____________________________________________________________________________________________________________
> 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]
