Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-acme-authority-token-tnauthlist-13> for your review
Alanna Paloma <apaloma@amsl.com> Thu, 10 August 2023 17:52 UTC
Return-Path: <apaloma@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 DBDF2C16B5A3; Thu, 10 Aug 2023 10:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 w_hjTy1CVHQi; Thu, 10 Aug 2023 10:52:46 -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 B8B3FC16B5A0; Thu, 10 Aug 2023 10:52:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 92E68424B42D; Thu, 10 Aug 2023 10:52:46 -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 Y4HFDLcwBGdn; Thu, 10 Aug 2023 10:52:46 -0700 (PDT)
Received: from [IPv6:2600:1700:bac0:1070:915e:ced7:2112:c3d3] (unknown [IPv6:2600:1700:bac0:1070:915e:ced7:2112:c3d3]) by c8a.amsl.com (Postfix) with ESMTPSA id 28D70424B426; Thu, 10 Aug 2023 10:52:46 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Alanna Paloma <apaloma@amsl.com>
In-Reply-To: <CAM7yphZ6Rytd1HOZbBgvCF+kBrd-n+GU_9UUsdFWEkxFVe5NGA@mail.gmail.com>
Date: Thu, 10 Aug 2023 10:52:45 -0700
Cc: rfc-editor@rfc-editor.org, chris-ietf@chriswendt.net, mary.ietf.barnes@gmail.com, jon.peterson@neustar.biz, acme-ads@ietf.org, acme-chairs@ietf.org, rsalz@akamai.com, rdd@cert.org, auth48archive@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AF4BE7B-1FF5-4D27-8429-37D6B67042BB@amsl.com>
References: <20230725055638.DCF7D3E8AF@rfcpa.amsl.com> <CAM7yphYR6XEdAX+yemh+eAWPtb1cdWcxO2rRabviYMCBhZ88FA@mail.gmail.com> <5FEA6AD0-3599-4C24-8317-776DA3CD05E3@amsl.com> <CAM7yphZ6Rytd1HOZbBgvCF+kBrd-n+GU_9UUsdFWEkxFVe5NGA@mail.gmail.com>
To: David Hancock <davidhancock.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/5FsmRuJwPN348uFDHxE7ThFxEFo>
Subject: Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-acme-authority-token-tnauthlist-13> 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, 10 Aug 2023 17:52:50 -0000
Hi David, We have noted your approval on the AUTH48 status page: https://www.rfc-editor.org/auth48/rfc9448 Thank you, RFC Editor/ap > On Aug 9, 2023, at 11:17 PM, David Hancock <davidhancock.ietf@gmail.com> 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 <apaloma@amsl.com> wrote: > 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 <davidhancock.ietf@gmail.com> 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: > > davidhancock.ietf@gmail.com > > NEW: > > new text > > David Hancock > > Somos Inc. > > United States of America > > Email: > > davidhancock.ietf@gmail.com > > --- > > > > Thanks > > David > > > > On Mon, Jul 24, 2023 at 11:56 PM <rfc-editor@rfc-editor.org> 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 > > > > * 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://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, > > 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://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 > > > > >
- [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-acme-… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Chris Wendt
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Chris Wendt
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Mary Barnes
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… David Hancock
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… David Hancock
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Peterson, Jon
- Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-a… Alanna Paloma