Re: [auth48] AUTH48: RFC-to-be 9492 <draft-ietf-lsr-rfc8920bis-06> for your review

[John E Drake <[e-mail]>]

I approve publication.

Yours Irrespectively,

John


Juniper Business Use Only
> -----Original Message-----
> From: [e-mail] <[e-mail]>
> Sent: Monday, September 18, 2023 8:50 PM
> To: [e-mail]; [e-mail]; [e-mail];
> [e-mail]; John E Drake <[e-mail]>
> Cc: [e-mail]; [e-mail]; [e-mail];
> [e-mail]; John Scudder <[e-mail]>; auth48archive@rfc-
> editor.org
> Subject: AUTH48: RFC-to-be 9492 <draft-ietf-lsr-rfc8920bis-06> for your review
>
> [External Email. Be cautious of content]
>
>
> *****IMPORTANT*****
>
> Updated 2023/09/18
>
> 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://urldefense.com/v3/__https://www.rfc-
> editor.org/faq/__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdlwt8hCF$ ).
>
> 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://urldefense.com/v3/__https://trustee.ietf.org/license-
> info/__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdt_cD9Bh$ ).
>
> *  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://urldefense.com/v3/__https://authors.ietf.org/rfcxml-
> vocabulary__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdk7qA2ka$ >.
>
> *  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
>
>    *  [e-mail] (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).
>
>    *  [e-mail], which is a new archival mailing list
>       to preserve AUTH48 conversations; it is not an active discussion
>       list:
>
>      *  More info:
>         https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf-
> announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdto18wU3$
>
>      *  The archive itself:
>
> https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48ar
> chive/__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdtIMSDXd$
>
>      *  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,
>         [e-mail] 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://urldefense.com/v3/__https://www.rfc-
> editor.org/authors/rfc9492.xml__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdlwA4QM_$
>    https://urldefense.com/v3/__https://www.rfc-
> editor.org/authors/rfc9492.html__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdsqxunm0$
>    https://urldefense.com/v3/__https://www.rfc-
> editor.org/authors/rfc9492.pdf__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kds2agqtO$
>    https://urldefense.com/v3/__https://www.rfc-
> editor.org/authors/rfc9492.txt__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdtPRDfQx$
>
> Diff file of the text:
>    https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9492-
> diff.html__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdqMaUyFb$
>    https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9492-
> rfcdiff.html__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdvTLCs8W$  (side by side)
>
> Diff of the XML:
>    https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9492-
> xmldiff1.html__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdpTHijLk$
>
>
> Tracking progress
> -----------------
>
> The details of the AUTH48 status of your document are here:
>    https://urldefense.com/v3/__https://www.rfc-
> editor.org/auth48/rfc9492__;!!NEt6yMaO-
> gk!C9Pu17KolcOCrLbw59zXFB72X3va1iu8n3snXa4YxlKHKWCDa1DVmQR2cJvf5vA
> OBIjkotQrl-lDRv-kdhaEQ6YR$
>
> Please let us know if you have any questions.
>
> Thank you for your cooperation,
>
> RFC Editor
>
> --------------------------------------
> RFC9492 (draft-ietf-lsr-rfc8920bis-06)
>
> Title            : OSPF Application-Specific Link Attributes
> Author(s)        : P. Psenak, Ed., L. Ginsberg, W. Henderickx, J. Tantsura, J. Drake
> WG Chair(s)      : Acee Lindem, Christian Hopps
> Area Director(s) : Alvaro Retana, John Scudder, Andrew Alston
>