Re: [auth48] AUTH48: RFC-to-be 9448 <draft-ietf-acme-authority-token-tnauthlist-13> for your review
David Hancock <davidhancock.ietf@gmail.com> Wed, 09 August 2023 17:16 UTC
Return-Path: <davidhancock.ietf@gmail.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 16CCFC151520; Wed, 9 Aug 2023 10:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XjB42uG45-il; Wed, 9 Aug 2023 10:16:52 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 61AA7C151980; Wed, 9 Aug 2023 10:16:47 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id ca18e2360f4ac-790a8c74383so296391639f.3; Wed, 09 Aug 2023 10:16:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691601406; x=1692206206; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uWTs3gy0VGI0pCfefhpzeNE2kw7zajfTrzxtoWPIWEg=; b=K28NbFWkESdgZqGFcu/pAAvFC4ceP5Pgi5OC5TEGj6dnBHPChAJzxkfGMez+dVHgpX /nmD9ThmREFBzdcYWjzsXIZKCOfoLbvrayhr5VJYNhOe70hXcw/KG5spp0GNUMlKTgUr 69raUeqLNC1UJCDLOP0vlepqzqS0kKiomI+5C+PHD+4eF109uYRu+bVkirslw7cPPhYV Hv5S6M/tjpAH01ByKrNy2TsUk6MhM0q1sQr3kNQ2FQSXObwexEo1aCHleFtJjsh/7EKD m7lxtJ9RIjRznwGrrq7Gm1TR6wnGUAWe8wdRuLf9R6ibq1PhU4VZKaAspeH32DKpmoe/ y40g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691601406; x=1692206206; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uWTs3gy0VGI0pCfefhpzeNE2kw7zajfTrzxtoWPIWEg=; b=iQQrqGJAfDzhaQnqQZB/UgVu30cj35NSbZkMY5i/Q63EtRKpzFQD6nOEF8NRmMeUlk fct81nsfwh/uyKyZBvOkiLcok2MoATivAGgVM9S8wYVpCfIdoFJfizkDSHQlRjV7yh46 pK0lIShpGWm4nBcop4MMXdAkfmO68voXiRoetYpkaJ8KbysdOA6/nh4CKe25JJbFyo1G izH5EBaV8nId0qvzaFsi7kDiRjTS0xwkn7X7Zdk4Ldom8yR9cXn4TLm5qs45Dk3fwlA0 mLOgjMGDR598PuUx+QHTOJnC+ru69rtut/utVwEGcygRbCDp4EBRZeGDr1QHLaJOvmxq 8RIQ==
X-Gm-Message-State: AOJu0Yx03r0BBcddkIgvbKMa0w8aF+0xeL4Yr740uo6xADNlxL1JHVgW Hb6oB9lG5XDmWsNDGi2hPtsRP2J733jsb30U3d9FYhAlBoI=
X-Google-Smtp-Source: AGHT+IH9Kmmfr5tBtNaKYKl9WECfb3jo4+9fcJGnKsQaKHdNRnx2kcGX+IrXL8JqcASrffCmnLtkD7jpHVOK67c0tD4=
X-Received: by 2002:a5e:9907:0:b0:791:6aa4:2d89 with SMTP id t7-20020a5e9907000000b007916aa42d89mr10089ioj.21.1691601405297; Wed, 09 Aug 2023 10:16:45 -0700 (PDT)
MIME-Version: 1.0
References: <20230725055638.DCF7D3E8AF@rfcpa.amsl.com>
In-Reply-To: <20230725055638.DCF7D3E8AF@rfcpa.amsl.com>
From: David Hancock <davidhancock.ietf@gmail.com>
Date: Wed, 09 Aug 2023 11:16:34 -0600
Message-ID: <CAM7yphYR6XEdAX+yemh+eAWPtb1cdWcxO2rRabviYMCBhZ88FA@mail.gmail.com>
To: rfc-editor@rfc-editor.org
Cc: 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-Type: multipart/alternative; boundary="000000000000dd492d060280a495"
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/cCteH3zkO0kuj_e6YHoKEGswrr4>
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: Wed, 09 Aug 2023 17:16:56 -0000
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