Re: [auth48] AUTH48: RFC-to-be 9473 <draft-irtf-panrg-path-properties-08> for your review

Sarah Tarrant <starrant@amsl.com> Thu, 07 September 2023 21:06 UTC

Return-Path: <starrant@amsl.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3BBDC151719; Thu, 7 Sep 2023 14:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.807
X-Spam-Level:
X-Spam-Status: No, score=-1.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTTP_ESCAPED_HOST=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXi6AZgd5oHK; Thu, 7 Sep 2023 14:06:43 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DBA4C151547; Thu, 7 Sep 2023 14:06:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id EBB8E424B434; Thu, 7 Sep 2023 14:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QzRLxJNp-753; Thu, 7 Sep 2023 14:06:42 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2600:1700:8f1d:4000:4091:7632:4822:5545]) by c8a.amsl.com (Postfix) with ESMTPSA id 70779424B42D; Thu, 7 Sep 2023 14:06:42 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: Sarah Tarrant <starrant@amsl.com>
In-Reply-To: <14acc9fe9a3a43d49d9f02a59dda8e45@inf.ethz.ch>
Date: Thu, 07 Sep 2023 16:06:31 -0500
Cc: RFC Editor <rfc-editor@rfc-editor.org>, "ietf@tenghardt.net" <ietf@tenghardt.net>, "irsg@irtf.org" <irsg@irtf.org>, "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <48885534-1CDD-4756-B16B-1C93D239B8C8@amsl.com>
References: <20230906202603.21090CD7E7@rfcpa.amsl.com> <AS8PR02MB10146C1BAAD31D1B244420D4588EEA@AS8PR02MB10146.eurprd02.prod.outlook.com> <14acc9fe9a3a43d49d9f02a59dda8e45@inf.ethz.ch>
To: Krähenbühl Cyrill <cyrill.kraehenbuehl@inf.ethz.ch>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/M5sK6oRX8nkHOR01zQhH4jHUzl0>
Subject: Re: [auth48] AUTH48: RFC-to-be 9473 <draft-irtf-panrg-path-properties-08> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2023 21:06:48 -0000

Hello Cyrill and Med,

Thank you for your replies. We have updated the document accordingly. All of our questions have been addressed.

Please review the document carefully to ensure satisfaction as we do not make changes once it has been published as an RFC. Contact us with any further updates or with your approval of the document in its current form. 

Updated XML file:
http://www.rfc-editor.org/authors/rfc9473.xml

Updated output files:
https://www.rfc-editor.org/authors/rfc9473.html
https://www.rfc-editor.org/authors/rfc9473.txt
https://www.rfc-editor.org/authors/rfc9473.pdf

Diff file showing all changes made during AUTH48:
https://www.rfc-editor.org/authors/rfc9473-auth48diff.html

Diff files showing all changes:
https://www.rfc-editor.org/authors/rfc9473-diff.html
https://www.rfc-editor.org/authors/rfc9473-rfcdiff.html (side-by-side diff)

Note that it may be necessary for you to refresh your browser to view the most recent version. 

For the AUTH48 status of this document, please see:
https://www.rfc-editor.org/auth48/rfc9473

Thank you,

RFC Editor/st

> On Sep 7, 2023, at 3:58 AM, Krähenbühl Cyrill <cyrill.kraehenbuehl@inf.ethz.ch> wrote:
> 
> Dear RFC Editor, all,
> 
> Here are my answers/comments regarding the 11 questions posed in the previous mail:
> 
> 1) I suggest the following additional keywords: PAN, path-aware network, path property, path selection
> 
> 2) this change looks good to me
> 
> 3) this change looks good to me
> 
> 4) I suggest to rephrase this sentence to: "Observed property: A property that is observed for a specific path element, subpath, or path. A property may be observed using measurements, for example the one-way delay of a specific packet transmitted from node to node."
> 
> 5) I suggest to rephrase this sentence to: "This may apply to security-related target properties (e.g., mandate that all enterprise traffic goes through a specific firewall) and path selection (e.g., enforce traffic policies by allowing or disallowing to send flows over paths that involve specific networks or nodes)."
> 
> 6) I suggest to replace RFC2616 with RFC9110.
> 
> 7) I suggest to rephrase this sentence to: "For example, if the packet's content is altered when forwarded over a Generic Routing Encapsulation (GRE) tunnel [RFC2784] [RFC7676], per this document the software instances that terminate the tunnel are considered nodes over which the actions are performed; thus, the transparency definition applies to these nodes."
> 
> 8) this change looks good to me
> 
> 9a) consistently using the lowercase forms works for me.
> 
> 9b) yes, that works for me as well
> 
> 9c) I suggest to use "AS path"
> 
> 9d) I suggest to only mention tcpcrypt with its respective RFC (similar as it is done in RFC8803 in the third paragraph of 1.1): "For example, a 0-RTT Transport Converter [RFC8803] will be involved in a path only when invoked by an endpoint; such invocation will lead to the use of Multipath TCP (MPTCP) [RFC8684] or tcpcrypt [RFC8548] capabilities, while such use is not supported via the default forwarding path."
> 
> 9e) I would suggest to use the all caps version since this is also used in the original draft: https://datatracker.ietf.org/doc/html/draft-schinazi-masque-02
> 
> 10) IMO, we followed the guidelines of Section 2.1 of RFC 5743.
> 
> 11) IMO, there are no changes needed for this document to adhere to the inclusive language portion of the style guide.
> 
> Best, Cyrill
> 
> 
> Von: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> Gesendet: Donnerstag, 7. September 2023 09:01
> An: rfc-editor@rfc-editor.org; ietf@tenghardt.net; Krähenbühl Cyrill
> Cc: irsg@irtf.org; auth48archive@rfc-editor.org
> Betreff: RE: AUTH48: RFC-to-be 9473 <draft-irtf-panrg-path-properties-08> for your review
>  Dear RFC Editor, all, 
> 
> Please find below two minor comments on the edited version:
> * Replace the occurrences of "IETF network slices" with "IETF Network Slices" to align with the usage in draft-ietf-teas-ietf-network-slices (in IESG review).
> * Section 4: Replace "802.11 WiFi" with "802.11 Wireless Local Area Network (WLAN)" (seehttps://www.ieee802.org/11/). 
> 
> Thank you.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>
> > Envoyé : mercredi 6 septembre 2023 22:26
> > À : ietf@tenghardt.net; cyrill.kraehenbuehl@inf.ethz.ch
> > Cc : rfc-editor@rfc-editor.org; irsg@irtf.org; BOUCADAIR Mohamed
> > INNOV/NET <mohamed.boucadair@orange.com>; auth48archive@rfc-
> > editor.org
> > Objet : AUTH48: RFC-to-be 9473 <draft-irtf-panrg-path-properties-
> > 08> for your review
> > 
> > *****IMPORTANT*****
> > 
> > Updated 2023/09/06
> > 
> > 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%2
> > Fwww.rfc-
> > editor.org%2Ffaq%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%
> > 7Cf96d14608e5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc48b9253b6f5
> > d20%7C0%7C0%7C638296288868914687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
> > C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7
> > C%7C%7C&sdata=Rm23OrKcJq65ILv7XZfe12DLRyko5SpiHrawGr%2FdRRg%3D&res
> > erved=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%2F
> > trustee.ietf.org%2Flicense-
> > info%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Cf96d14608e
> > 5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%
> > 7C638296288868914687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> > CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat
> > a=gkU2mxtqRC3plh2x8zo3jUKzc2E8P7Flrdc2Jfr%2Foig%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%2
> > Fauthors.ietf.org%2Frfcxml-
> > vocabulary&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Cf96d146
> > 08e5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7
> > C0%7C638296288868914687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&s
> > data=bEmKpInkQsKHYVcnfic9bTNO6nplDS05IVRNq8Kz%2BiU%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-editor@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%2F
> > mailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-
> > 4Q9l2USxIAe6P8O4Zc&data=05%7C01%7Cmohamed.boucadair%40orange.com%7
> > Cf96d14608e5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc48b9253b6f5d
> > 20%7C0%7C0%7C638296288868914687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC
> > 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C
> > %7C%7C&sdata=P2PUcy460P1pY98px7T0Nq5bPWGJkTRrTuhwOBDjX%2FQ%3D&rese
> > rved=0
> > 
> >      *  The archive itself:
> > 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > mailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C
> > 01%7Cmohamed.boucadair%40orange.com%7Cf96d14608e5d49d8bea408dbaf17
> > c655%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6382962888689146
> > 87%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ
> > BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AU5%2Ftt%2F7JAxc
> > gi9rS9JEA8QYuWAfVUzky6kri9VRoe8%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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > www.rfc-
> > editor.org%2Fauthors%2Frfc9473.xml&data=05%7C01%7Cmohamed.boucadai
> > r%40orange.com%7Cf96d14608e5d49d8bea408dbaf17c655%7C90c7a20af34b40
> > bfbc48b9253b6f5d20%7C0%7C0%7C638296288868914687%7CUnknown%7CTWFpbG
> > Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6
> > Mn0%3D%7C3000%7C%7C%7C&sdata=H5dKUlGgesxBo20%2BKzsvKYo0PiQ4MMpt5sm
> > XpYZ6wMA%3D&reserved=0
> > 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > www.rfc-
> > editor.org%2Fauthors%2Frfc9473.html&data=05%7C01%7Cmohamed.boucada
> > ir%40orange.com%7Cf96d14608e5d49d8bea408dbaf17c655%7C90c7a20af34b4
> > 0bfbc48b9253b6f5d20%7C0%7C0%7C638296288868914687%7CUnknown%7CTWFpb
> > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
> > 6Mn0%3D%7C3000%7C%7C%7C&sdata=R%2Fvmd4zVgTl%2FlPu4KZMKg4tH7lDgN80B
> > JiwFxgWpNqQ%3D&reserved=0
> > 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > www.rfc-
> > editor.org%2Fauthors%2Frfc9473.pdf&data=05%7C01%7Cmohamed.boucadai
> > r%40orange.com%7Cf96d14608e5d49d8bea408dbaf17c655%7C90c7a20af34b40
> > bfbc48b9253b6f5d20%7C0%7C0%7C638296288868914687%7CUnknown%7CTWFpbG
> > Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6
> > Mn0%3D%7C3000%7C%7C%7C&sdata=ZlWwu4SdLNe8C90KkeRBi8BRn7lwECwY7%2FD
> > geim7fqo%3D&reserved=0
> > 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > www.rfc-
> > editor.org%2Fauthors%2Frfc9473.txt&data=05%7C01%7Cmohamed.boucadai
> > r%40orange.com%7Cf96d14608e5d49d8bea408dbaf17c655%7C90c7a20af34b40
> > bfbc48b9253b6f5d20%7C0%7C0%7C638296288869070919%7CUnknown%7CTWFpbG
> > Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6
> > Mn0%3D%7C3000%7C%7C%7C&sdata=DRDYqIWQfDjAuHMDg%2FG%2FUV3XUnDJZdDTY
> > 2VRm6YfStE%3D&reserved=0
> > 
> > Diff file of the text:
> > 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > www.rfc-editor.org%2Fauthors%2Frfc9473-
> > diff.html&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Cf96d1460
> > 8e5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> > 0%7C638296288869070919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> > iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sd
> > ata=0hrf9NIXvHKFIPeiiJDRqH%2Fu9nLwJbvRDYkORLosVBo%3D&reserved=0
> > 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > www.rfc-editor.org%2Fauthors%2Frfc9473-
> > rfcdiff.html&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Cf96d1
> > 4608e5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0
> > %7C0%7C638296288869070919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw
> > MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C
> > &sdata=J1CADQuSRTuSojuwOaVsTlLw%2FfpyMEla%2BTqlvvhTziE%3D&reserved
> > =0 (side by side)
> > 
> > Diff of the XML:
> > 
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > www.rfc-editor.org%2Fauthors%2Frfc9473-
> > xmldiff1.html&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Cf96d
> > 14608e5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc48b9253b6f5d20%7C
> > 0%7C0%7C638296288869070919%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA
> > wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7
> > C&sdata=LDzpaVWvKqgj2ZU%2FlViOkPGap5NYAR5gRRi2znFG0GQ%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%2F
> > www.rfc-
> > editor.org%2Fauth48%2Frfc9473&data=05%7C01%7Cmohamed.boucadair%40o
> > range.com%7Cf96d14608e5d49d8bea408dbaf17c655%7C90c7a20af34b40bfbc4
> > 8b9253b6f5d20%7C0%7C0%7C638296288869070919%7CUnknown%7CTWFpbGZsb3d
> > 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> > D%7C3000%7C%7C%7C&sdata=T2Dwg5SOVolsuOfCJT1M%2FIHoCtdOrYJcgpqLTvRX
> > 2tI%3D&reserved=0
> > 
> > Please let us know if you have any questions.
> > 
> > Thank you for your cooperation,
> > 
> > RFC Editor
> > 
> > --------------------------------------
> > RFC 9473 (draft-irtf-panrg-path-properties-08)
> > 
> > Title            : A Vocabulary of Path Properties
> > Author(s)        : R. Enghardt, C. Krähenbühl
> > WG Chair(s)      :
> > Area Director(s) :
> > 
> 
> ____________________________________________________________________________________________________________
> 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.