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

[Alanna Paloma <[e-mail]>]

Hi David,

Thank you for your reply. Your affiliation has been updated.

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

The relevant diff files have been posted here:
  https://www.rfc-editor.org/authors/rfc9448-diff.html (comprehensive diff)
  https://www.rfc-editor.org/authors/rfc9448-auth48diff.html (AUTH48 changes)
  https://www.rfc-editor.org/authors/rfc9448-lastdiff.html (htmlwdiff diff between last version and this)
  https://www.rfc-editor.org/authors/rfc9448-lastrfcdiff.html (rfcdiff between last version and this)

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

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://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/rfc9448.xml
>    https://www.rfc-editor.org/authors/rfc9448.html
>    https://www.rfc-editor.org/authors/rfc9448.pdf
>    https://www.rfc-editor.org/authors/rfc9448.txt
> 
> Diff file of the text:
>    https://www.rfc-editor.org/authors/rfc9448-diff.html
>    https://www.rfc-editor.org/authors/rfc9448-rfcdiff.html (side by side)
> 
> Diff of the XML: 
>    https://www.rfc-editor.org/authors/rfc9448-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/rfc9448.original.v2v3.xml 
> 
> XMLv3 file that is a best effort to capture v3-related format updates 
> only: 
>    https://www.rfc-editor.org/authors/rfc9448.form.xml
> 
> 
> Tracking progress
> -----------------
> 
> The details of the AUTH48 status of your document are here:
>    https://www.rfc-editor.org/auth48/rfc9448
> 
> 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
> 
>