Re: [auth48] [E] Re: AUTH48: RFC-to-be 9538 <draft-ietf-cdni-delegation-acme-04> for your review
"Mishra, Sanjay" <sanjay.mishra@verizon.com> Wed, 07 February 2024 15:34 UTC
Return-Path: <sanjay.mishra@verizon.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 7D309C1519AF for <auth48archive@ietfa.amsl.com>; Wed, 7 Feb 2024 07:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=verizon.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 Vo2OUFYrfoqO for <auth48archive@ietfa.amsl.com>; Wed, 7 Feb 2024 07:33:56 -0800 (PST)
Received: from mx0b-0024a201.pphosted.com (mx0b-0024a201.pphosted.com [148.163.153.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67C7FC1516EB for <auth48archive@rfc-editor.org>; Wed, 7 Feb 2024 07:33:56 -0800 (PST)
Received: from pps.filterd (m0098281.ppops.net [127.0.0.1]) by mx0a-0024a201.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 417CEqg3000955 for <auth48archive@rfc-editor.org>; Wed, 7 Feb 2024 10:21:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon.com; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=prodmail; bh=um5BHo7WCvLoVS53XihePxc3xCykUIzdfvuS9CbSPEU=; b=4vyj3WAdGT08czNKK4X4VlSPMsQonpOs3m7o0frgLRPItrhkR8xft9K3fnlNzqr6oQ73 1Aw8zBUwRVQ00/mXcyitGK/rvf2WO+EedLQiOqtwtB6xe20brHCm6vqZRC9v92kmjzuH LPgiD//r3xNtFVwEvVM3qi5/CvlSMmkVuDRuUk7Gz8PwsP23ZLyptfETSNwgrQR7Ct/e b/cNS3v5Ms8o7fYOVqoy2dz9UiBhySqtUXu9+Px6c0AJ7k3S+1NdA5nur3eeYHriCNaZ E/ZrpqXFmXHuHV3LXmQLxrqZtNM8L4+rzE0qnhznEZ3DdOiQ/OeFHGk9nzCwqyNfjKEJ mg==
Received: from mail-yw1-f200.google.com (mail-yw1-f200.google.com [209.85.128.200]) by mx0a-0024a201.pphosted.com (PPS) with ESMTPS id 3w3vqqf43y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <auth48archive@rfc-editor.org>; Wed, 07 Feb 2024 10:21:28 -0500
Received: by mail-yw1-f200.google.com with SMTP id 00721157ae682-5ee22efe5eeso12990877b3.3 for <auth48archive@rfc-editor.org>; Wed, 07 Feb 2024 07:21:28 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707319288; x=1707924088; 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=um5BHo7WCvLoVS53XihePxc3xCykUIzdfvuS9CbSPEU=; b=tCYdEAQxLpSKZNF4atoxTKKI5rBC77RiXTdJPYBpUPQOuD+TGZaExjJaC84yt1ateZ 5G6WFl/W8r3TsBiH5IAC7TpFhxU9KS7ylCg+BKf7hJhffMTHi6Xa19iDySJliML7pL7O OEnVma9Meh63JKr5HfHp63r09h7deX7LYHgw1OehJO8Y/WeWyaJ7/GA55UPD/+oqUZF7 TpMWWk/zT+z+0uBF8TGX5mljLTJsWdyb4270saniVAtw3DsBDgV+E20jbI1AahpSFFU8 yIhKLCXn4oJ5deNksyguLBstMd8BV1JPM8vvZJ/GhXk9LOqva1+O8/TrDFJMF7QGUdfj lBGw==
X-Gm-Message-State: AOJu0YwPDrZCTjzp8VIoXpw0tfkYdMwlLk1Q5MVFQ1uTOvRVmqp5GuDF +t6mgSktkH4wr35goGnTupekE7ZOsoCXIdquiVTw6HT7YA1kEDeM0MvSp4aPEwjCDg9IQf5c58x M4uI2z5Z+CNX38T7eO2EYdj27QD0xfo7Oy0om7gxOa3nwp5sGqAzAPn/Sy15nNPObZkFrKld0T3 vTWQHzKmcqbS5BPe16SPElIVhBhchUcbrRHqA=
X-Received: by 2002:a81:b703:0:b0:603:f078:1960 with SMTP id v3-20020a81b703000000b00603f0781960mr5375358ywh.6.1707319288085; Wed, 07 Feb 2024 07:21:28 -0800 (PST)
X-Google-Smtp-Source: AGHT+IEsKLyyrlM06KA5qoGHUWy5bp/9JUhmPSaEB4ibmOA6NXK04iOTok0A00xxzogD7/ftCFeljCNA6GM9tTxjsBI=
X-Received: by 2002:a81:b703:0:b0:603:f078:1960 with SMTP id v3-20020a81b703000000b00603f0781960mr5375318ywh.6.1707319287487; Wed, 07 Feb 2024 07:21:27 -0800 (PST)
MIME-Version: 1.0
References: <20240123065751.D786E199610A@rfcpa.amsl.com> <7566767A-2661-462A-AE1B-2E225ACAA0D7@amsl.com>
In-Reply-To: <7566767A-2661-462A-AE1B-2E225ACAA0D7@amsl.com>
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
Date: Wed, 07 Feb 2024 10:21:15 -0500
Message-ID: <CA+EbDtCSsAe6M=jW5NfXwpWkBPO2CLBuVmxFwM2ZB5sF+jXSGg@mail.gmail.com>
To: Alice Russo <arusso@amsl.com>
Cc: frederic.fieau@orange.com, emile.stephan@orange.com, cdni-ads@ietf.org, cdni-chairs@ietf.org, kevin.j.ma.ietf@gmail.com, francesca.palombini@ericsson.com, rfc-editor@rfc-editor.org, auth48archive <auth48archive@rfc-editor.org>
Content-Type: multipart/alternative; boundary="000000000000a67edd0610cc3f94"
X-mailroute: internal
X-Proofpoint-ORIG-GUID: OW_JzwGR5YuzecMuCpZ7UByO4o_LKFk2
X-Proofpoint-GUID: OW_JzwGR5YuzecMuCpZ7UByO4o_LKFk2
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/NxfWt2MR_yHods459K7y-Kh87Uw>
Subject: Re: [auth48] [E] Re: AUTH48: RFC-to-be 9538 <draft-ietf-cdni-delegation-acme-04> 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, 07 Feb 2024 15:34:00 -0000
Hi Alice - My co-author Frederic Fieau responded approving this drafts, however, it is a different email thread addressed to cdni@ietf.org so I as confirmation, I'm responding to this thread, I as a co-author along with Emile Stephan and Frederic Fieau have reviewed all changes and approve publication of this document as RFC 9538. We are thankful to co-chair Kevin Ma for his guidance and the AD, Francesca Palombini and everyone that contributed and commented to this draft and of course a big thanks to the editorial team. Regards Sanjay Mishra snippet of email from Fred is below: > frederic.fieau@orange.com > 9:41 AM (37 minutes ago) > to cdni@ietf.org, me, STEPHAN > > Dear all, > > I have reviewed all changes in draft-ietf-cdni-delegation-acme and concur > with them. On behalf of the authors, I approve the document for publication > as RFC9538. > > I would like to thank the CDNI WG and all individuals who participated for > their valuable contributions throughout the process which has now reached > its conclusion for this draft. > > Regards, > Frederic > On Tue, Feb 6, 2024 at 6:12 PM Alice Russo <arusso@amsl.com> wrote: > Authors, > > This is a reminder that we await word from you regarding the questions > below and this document's readiness for publication as an RFC. The files > are here: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=5TzFzGWGUvYktrbM8hNWTP8hhGH7e5HbSUIxNf_TLA0&e= > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.pdf&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=-ES9wp1LnU6Q7BFV8U-fcv_gUpKgEg8ECmuutDUGb9w&e= > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.txt&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=6vBNFP8MiPXcTbSU4PnBrPvuXbyaL7ysXKxiedlaDGc&e= > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=QyfJ3JEyXCJaYC3zyThHRZBmzKiYNACxoJ4MArXCUK8&e= > (source) > > Diff files of all changes from the approved Internet-Draft: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=lHSovOjBUHrLUveLLyMBUoqm_IlAWXB37E8HMdIUZ68&e= > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538-2Drfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=MjAFFfiY9fQr9Bv5FYsBigSAzexwRe3sL6KOEbvy7PM&e= > (side by side) > > This page shows the AUTH48 status of your document: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_auth48_rfc9538&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=-577wxpatCuL4syt5zliTCPSry6dSb98RzaRlHqLg10&e= > > Thank you. > RFC Editor/ar > > > On Jan 22, 2024, at 10:57 PM, rfc-editor@rfc-editor.org wrote: > > > > Authors, > > > > While reviewing this document during AUTH48, please resolve (as > necessary) the > > following questions, which are also in the XML file. > > > > 1) <!--[rfced] May this be rephrased as follows for readability? > > > > Original: > > RFC9115 allows delegating entities to remain in > > full control of the delegation and be able to revoke it any time and > > this avoids the need to share private cryptographic key material > > between the involved entities. > > > > Perhaps: > > Per RFC 9115, delegating entities can remain in > > full control of the delegation and can revoke it at any time. > > This avoids the need to share private cryptographic key material > > between the involved entities. > > --> > > > > > > 2) <!--[rfced] FYI, in Section 1.1, we added mention of "STAR" so that it > > is expanded upon first use. Please let us know if you prefer otherwise. > > (In the original, the first use was in Section 3 - "ACME STAR delegation" > > was followed by explanation but was without a direct expansion.) > > > > Original: > > It also uses > > terminology from Section 1.2 of [RFC8739] and Section 1.1 of > > [RFC9115]. > > > > Current: > > It also uses > > terminology from Section 1.2 of [RFC8739] and Section 1.1 of > > [RFC9115], including Short-Term, Automatically Renewed (STAR), > > as applied to X.509 certificates. > > --> > > > > > > 3) <!--[rfced] How may this sentence be rephrased for clarity? In > particular, > > "allows to specify" is not clear. Also, Section 2.3.1.3 of RFC 9115 > > indicates that the CNAME mapping is optional; should this sentence be > > updated to reflect that? > > > > Original: > > | Note: The delegation object defined in Section 2.3.1.3 of > > | [RFC9115] only allows to specify DNS mappings using CNAME RRs. > > > > Perhaps: > > | Note: The delegation object defined in Section 2.3.1.3 of > > | [RFC9115] only allows DNS mappings to be specified using CNAME > RRs. > > > > Or: > > | Note: The delegation object defined in Section 2.3.1.3 of > > | [RFC9115] allows DNS mappings to be specified using only CNAME > RRs. > > --> > > > > > > 4) <!--[rfced] FYI, for readability and precision, we have made the > following > > updates: split this into two sentences, changed "criticality around" > > to "criticality of", and changed "which" to "this account". > > Please review and let us know if you prefer otherwise. > > > > Original: > > The reader is expected to understand the ACME delegation trust model > > (Section 7.1 of [RFC9115]) and security goal (Section 7.2 of > > [RFC9115]), in particular the criticality around the protection of > > the user account associated with the delegation, which authorizes all > > the security relevant operations between dCDN and uCDN over the ACME > > channel. > > > > Current: > > The reader is expected to understand the ACME delegation trust model > > (Section 7.1 of [RFC9115]) and security goal (Section 7.2 of > > [RFC9115]). In particular, the reader is expected to understand the > > criticality of the protection of the user account associated with the > > delegation; this account authorizes all the security-relevant > > operations between a dCDN and a uCDN over the ACME channel. > > --> > > > > > > Thank you. > > > > RFC Editor/ar > > > > > > On Jan 22, 2024, rfc-editor@rfc-editor.org wrote: > > > > *****IMPORTANT***** > > > > Updated 2024/01/22 > > > > 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.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_faq_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=R4hL9hqFpSZGgmXJvmdQdyeMBbHY7FCjh0GE8Gi0D1E&e= > ). > > > > 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.proofpoint.com/v2/url?u=https-3A__trustee.ietf.org_license-2Dinfo_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=EmW5gH3BJpXZXT-FekEpk9Zue49U4IDv-ra41tvH3HA&e= > ). > > > > * 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.proofpoint.com/v2/url?u=https-3A__authors.ietf.org_rfcxml-2Dvocabulary&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=CX_FOMxHB5eRPJFPqhWilV8ikeJ9hN31MtUmds9PmH8&e= > >. > > > > * 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://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_ietf-2Dannounce_yb6lpIGh-2D4Q9l2USxIAe6P8O4Zc&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=JRtKeOtmc0a9OKglX5dbdiV7jPuQY-d62xiDMqZsuqA&e= > > > > * The archive itself: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_browse_auth48archive_&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=R2GXreV6dODcQkh65iAGd574zalkql34kJYuX2IDieM&e= > > > > * 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.xml&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=QyfJ3JEyXCJaYC3zyThHRZBmzKiYNACxoJ4MArXCUK8&e= > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=5TzFzGWGUvYktrbM8hNWTP8hhGH7e5HbSUIxNf_TLA0&e= > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.pdf&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=-ES9wp1LnU6Q7BFV8U-fcv_gUpKgEg8ECmuutDUGb9w&e= > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538.txt&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=6vBNFP8MiPXcTbSU4PnBrPvuXbyaL7ysXKxiedlaDGc&e= > > > > Diff file of the text: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538-2Ddiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=lHSovOjBUHrLUveLLyMBUoqm_IlAWXB37E8HMdIUZ68&e= > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538-2Drfcdiff.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=MjAFFfiY9fQr9Bv5FYsBigSAzexwRe3sL6KOEbvy7PM&e= > (side by side) > > > > Diff of the XML: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_authors_rfc9538-2Dxmldiff1.html&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=gr5CbHiFHDAcsb-X3DNuur50zhzN2kMZqb_RfnAcXJc&e= > > > > > > Tracking progress > > ----------------- > > > > The details of the AUTH48 status of your document are here: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_auth48_rfc9538&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=_uLNEDcaPBsFXYMA8j5oRepqfLBtLE6RKluO5xkPC-kqNuhB9LwWEVarzV9IR2tN&s=-577wxpatCuL4syt5zliTCPSry6dSb98RzaRlHqLg10&e= > > > > Please let us know if you have any questions. > > > > Thank you for your cooperation, > > > > RFC Editor > > > > -------------------------------------- > > RFC9538 (draft-ietf-cdni-delegation-acme-04) > > > > Title : Content Delivery Network Interconnection (CDNI) > Delegation Using the Automated Certificate Management Environment > > Author(s) : F. Fieau, Ed., S. Emile, S. Mishra > > WG Chair(s) : Kevin J. Ma, Sanjay Mishra > > Area Director(s) : Murray Kucherawy, Francesca Palombini > > > >
- [auth48] AUTH48: RFC-to-be 9538 <draft-ietf-cdni-… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9538 <draft-ietf-c… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9538 <draft-ietf-c… Alice Russo
- Re: [auth48] [E] Re: AUTH48: RFC-to-be 9538 <draf… Mishra, Sanjay
- Re: [auth48] AUTH48: RFC-to-be 9538 <draft-ietf-c… Alice Russo
- Re: [auth48] [E] Re: AUTH48: RFC-to-be 9538 <draf… Mishra, Sanjay
- Re: [auth48] AUTH48: RFC-to-be 9538 <draft-ietf-c… Alice Russo
- Re: [auth48] [E] Re: AUTH48: RFC-to-be 9538 <draf… Mishra, Sanjay
- Re: [auth48] [E] Re: AUTH48: RFC-to-be 9538 <draf… emile.stephan
- [auth48] question - Re: AUTH48: RFC-to-be 9538 <d… Alice Russo
- Re: [auth48] question - Re: AUTH48: RFC-to-be 953… frederic.fieau
- Re: [auth48] question - Re: AUTH48: RFC-to-be 953… Alice Russo