Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-acme-authority-token-tnauthlist-13> for your review

[Alanna Paloma <[e-mail]>]

All,

Jon’s approval has been noted. With this, we have now received all necessary approvals and consider AUTH48 complete:
https://www.rfc-editor.org/auth48/rfc9448

As this document is part of Cluster C474, you may track the progress of all documents in this cluster through AUTH48 at:
https://www.rfc-editor.org/auth48/C474

We will move this document forward in the publication process once RFC-to-be 9447 has completed AUTH48 as well.

Please let us know if you have any questions.

RFC Editor/ap


> On Aug 25, 2023, at 5:05 AM, Peterson, Jon <[e-mail]> wrote:
> 
>  
> This looks good thanks,
>  
> - J
>  
> From: Alanna Paloma <[e-mail]>
> Date: Thursday, August 17, 2023 at 1:28 PM
> To: [e-mail] <[e-mail]>
> Cc: RFC Errata System <[e-mail]>, David Hancock <[e-mail]>, Chris Wendt <[e-mail]>, Mary Barnes <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, Roman Danyliw <[e-mail]>, auth48archive <[e-mail]>
> Subject: Re: AUTH48: RFC-to-be 9448 <draft-ietf-acme-authority-token-tnauthlist-13> for your review
> 
> Hi Jon,
> 
> This is a friendly reminder that we await your review and approval prior to moving this document forward in the publication process.
> 
> The files have been posted here (please refresh):
> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.xml__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_jqoP8xA$ 
> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.txt__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_WykQUCA$ 
> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_ivljbNM$ 
> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.pdf__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_jtavncE$ 
> 
> The relevant diff files have been posted here:
> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-diff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_P2V11hg$  (comprehensive diff)
> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-auth48diff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_30vTUhY$  (AUTH48 changes)
> 
> For the AUTH48 status of this document, please see:
> https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9448__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_UkUDdOw$ 
> 
> Thank you,
> RFC Editor/ap
> 
> > On Aug 10, 2023, at 10:52 AM, Alanna Paloma <[e-mail]> wrote:
> > 
> > Hi David,
> > 
> > We have noted your approval on the AUTH48 status page:
> > https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9448__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_UkUDdOw$ 
> > 
> > Thank you,
> > RFC Editor/ap
> > 
> >> On Aug 9, 2023, at 11:17 PM, David Hancock <[e-mail]> wrote:
> >> 
> >> Hi Alanna,
> >> 
> >> Thanks for the updates -- I now approve this RFC for publication.
> >> 
> >> David
> >> 
> >> On Wed, Aug 9, 2023 at 2:59 PM Alanna Paloma <[e-mail]> wrote:
> >> Hi David,
> >> 
> >> Thank you for your reply. Your affiliation has been updated.
> >> 
> >> The files have been posted here (please refresh):
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.xml__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_jqoP8xA$ 
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.txt__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_WykQUCA$ 
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_ivljbNM$ 
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.pdf__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_jtavncE$ 
> >> 
> >> The relevant diff files have been posted here:
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-diff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_P2V11hg$  (comprehensive diff)
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-auth48diff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_30vTUhY$  (AUTH48 changes)
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-lastdiff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_H8CWH0I$  (htmlwdiff diff between last version and this)
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-lastrfcdiff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_nI5EXzg$  (rfcdiff between last version and this)
> >> 
> >> For the AUTH48 status of this document, please see:
> >>  https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9448__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_UkUDdOw$ 
> >> 
> >> Thank you,
> >> RFC Editor/ap
> >> 
> >>> On Aug 9, 2023, at 10:16 AM, David Hancock <[e-mail]> wrote:
> >>> 
> >>> 
> >>> I would like to update my company name from Comcast to Somos Inc. in two places...
> >>> 
> >>> ---
> >>> On title page authors list:
> >>> 
> >>> OLD:
> >>> old text
> >>>  D. Hancock
> >>>  Comcast
> >>> 
> >>> NEW:
> >>> new text
> >>>  D. Hancock
> >>>  Somos Inc.
> >>> 
> >>> On the last page list of Authors' Addresses
> >>> OLD:
> >>> old text
> >>>   David Hancock
> >>>   Comcast
> >>>   United States of America
> >>>   Email: 
> >>> [e-mail]
> >>> NEW:
> >>> new text
> >>>   David Hancock
> >>>   Somos Inc.
> >>>   United States of America
> >>>   Email: 
> >>> [e-mail]
> >>> ---
> >>> 
> >>> Thanks
> >>> David
> >>> 
> >>> On Mon, Jul 24, 2023 at 11:56 PM <[e-mail]> wrote:
> >>> *****IMPORTANT*****
> >>> 
> >>> Updated 2023/07/24
> >>> 
> >>> 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/__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_nsxAXdE$ ).
> >>> 
> >>> 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/__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_Jx9mSQ4$ ).
> >>> 
> >>> *  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__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_PYSQ59Y$ >.
> >>> 
> >>> *  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__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_xyBUVTA$ 
> >>> 
> >>>     *  The archive itself:
> >>>        https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_zWiEKfE$ 
> >>> 
> >>>     *  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/rfc9448.xml__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_jqoP8xA$ 
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_ivljbNM$ 
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.pdf__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_jtavncE$ 
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.txt__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_WykQUCA$ 
> >>> 
> >>> Diff file of the text:
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-diff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_P2V11hg$ 
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-rfcdiff.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_Jy_9Yow$  (side by side)
> >>> 
> >>> Diff of the XML: 
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448-xmldiff1.html__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_e_zhK4c$ 
> >>> 
> >>> The following files are provided to facilitate creation of your own 
> >>> diff files of the XML.  
> >>> 
> >>> Initial XMLv3 created using XMLv2 as input:
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.original.v2v3.xml__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_19V_gwI$  
> >>> 
> >>> XMLv3 file that is a best effort to capture v3-related format updates 
> >>> only: 
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9448.form.xml__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_Ar8tQO4$ 
> >>> 
> >>> 
> >>> Tracking progress
> >>> -----------------
> >>> 
> >>> The details of the AUTH48 status of your document are here:
> >>>   https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9448__;!!N14HnBHF!6AJwRxqVx0zKo-vJ7Z6ZG8F3WVlYl8ccJKXxofR4Vf3MpU1CmeWYMOeoH-XsRUUx-iNvW82CzXI_UkUDdOw$ 
> >>> 
> >>> Please let us know if you have any questions.  
> >>> 
> >>> Thank you for your cooperation,
> >>> 
> >>> RFC Editor
> >>> 
> >>> --------------------------------------
> >>> RFC9448 (draft-ietf-acme-authority-token-tnauthlist-13)
> >>> 
> >>> Title            : TNAuthList profile of ACME Authority Token
> >>> Author(s)        : C. Wendt, D. Hancock, M. Barnes, J. Peterson
> >>> WG Chair(s)      : Deb Cooley, Deb Cooley, Yoav Nir
> >>> Area Director(s) : Roman Danyliw, Paul Wouters
> >>> 
> >>> 
> >> 
> > 
>