Re: [auth48] [C381] AUTH48: RFC-to-be 9306 <draft-ietf-lisp-vendor-lcaf-12> for your review

[Alanna Paloma <[e-mail]>]

Hi Dino, Alberto, and Anton,

Thank you for your replies. We have noted Alberto’s and Anton’s approvals on the AUTH48 status page:
 https://www.rfc-editor.org/auth48/rfc9306

Alberto - We have updated the dates for RFCs-to-be 9300 and 9301 to be "September 2022". 

The files have been posted here (please refresh):
 https://www.rfc-editor.org/authors/rfc9306.xml
 https://www.rfc-editor.org/authors/rfc9306.txt
 https://www.rfc-editor.org/authors/rfc9306.html
 https://www.rfc-editor.org/authors/rfc9306.pdf

The relevant diff files have been posted here:
 https://www.rfc-editor.org/authors/rfc9306-diff.html (comprehensive diff)
 https://www.rfc-editor.org/authors/rfc9306-auth48diff.html (AUTH48 changes)

We will await approvals from Dino, Vina, and Vrushali prior to moving this document forward in the publication process.

Thank you,
RFC Editor/ap

> On Sep 19, 2022, at 7:17 AM, Anton Smirnov (asmirnov) <asmirnov=[e-mail]> wrote:
> 
>    All,
>    editorial changes look good. Approved with no comments.
> 
> Anton Smirnov
> From: [e-mail] <[e-mail]>
> Sent: Friday, September 16, 2022 23:14
> To: Alberto Rodriguez-Natal (natal) <[e-mail]>; [e-mail] <[e-mail]>; Anton Smirnov (asmirnov) <[e-mail]>; Vrushali Ashtaputre (vrushali) <[e-mail]>; [e-mail] <[e-mail]>
> Cc: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
> Subject: Re: [C381] AUTH48: RFC-to-be 9306 <draft-ietf-lisp-vendor-lcaf-12> for your review
>  
> Authors,
> 
> While reviewing this document during AUTH48, please resolve (as necessary) the following ques
> tions, which are also in the XML file.
> 
> 1) <!--[rfced] FYI, we updated the short title as follows, which appears in 
> the running header of the PDF file. Please review and let us know if updates
> updates are needed.
> 
> Original:
> LISP-Vendor-LCAF
> 
> Current:
> Vendor-Specific LCAF
> -->
> 
> 
> 2) <!--[rfced] FYI, regarding the IANA-registered name "Vendor Specific", 
> within this document, we have updated to use the phrase with a hyphen
> when needed in context, even though it doesn't exactly match the name.
> For example, see the title of the RFC and "the Vendor-Specific LCAF"
> (15 instances total). Please let us know if you prefer otherwise.
> -->
> 
> 
> 3) <!-- [rfced] Please review the "Inclusive Language" portion of the online 
> Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> 
> and let us know if any changes are needed. Note that our script did not flag
> any words in particular, but this should still be reviewed as a best practice.
> -->
> 
> 
> Thank you.
> 
> RFC Editor/ap/ar
> 
> 
> On Sep 16, 2022, [e-mail] wrote:
> 
> *****IMPORTANT*****
> 
> Updated 2022/09/16
> 
> 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://www.rfc-editor.org/faq/).
> 
> 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://trustee.ietf.org/license-info/).
> 
> *  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://authors.ietf.org/rfcxml-vocabulary>.
> 
> *  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://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc
> 
>     *  The archive itself:
>        https://mailarchive.ietf.org/arch/browse/auth48archive/
> 
>     *  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://www.rfc-editor.org/authors/rfc9306.xml
>   https://www.rfc-editor.org/authors/rfc9306.html
>   https://www.rfc-editor.org/authors/rfc9306.pdf
>   https://www.rfc-editor.org/authors/rfc9306.txt
> 
> Diff file of the text:
>   https://www.rfc-editor.org/authors/rfc9306-diff.html
>   https://www.rfc-editor.org/authors/rfc9306-rfcdiff.html (side by side)
> 
> Diff of the XML: 
>   https://www.rfc-editor.org/authors/rfc9306-xmldiff1.html
> 
> The following files are provided to facilitate creation of your own 
> diff files of the XML.  
> 
> Initial XMLv3 created using XMLv2 as input:
>   https://www.rfc-editor.org/authors/rfc9306.original.v2v3.xml 
> 
> XMLv3 file that is a best effort to capture v3-related format updates 
> only: 
>   https://www.rfc-editor.org/authors/rfc9306.form.xml
> 
> 
> Tracking progress
> -----------------
> 
> The details of the AUTH48 status of your document are here:
>   https://www.rfc-editor.org/auth48/rfc9306
> 
> Please let us know if you have any questions.  
> 
> Thank you for your cooperation,
> 
> RFC Editor
> 
> --------------------------------------
> RFC9306 (draft-ietf-lisp-vendor-lcaf-12)
> 
> Title            : Vendor-Specific LISP Canonical Address Format (LCAF)
> Author(s)        : A. Rodriguez-Natal, V. Ermagan, A. Smirnov, V. Ashtaputre, D. Farinacci
> WG Chair(s)      : Joel M. Halpern, Luigi Iannone
> Area Director(s) : Alvaro Retana, John Scudder, Andrew Alston