Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrell-tenyearsafter-05> for your review
"Independent Submissions Editor (Eliot Lear)" <rfc-ise@rfc-editor.org> Wed, 12 July 2023 14:01 UTC
Return-Path: <rfc-ise@rfc-editor.org>
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 0BAB2C151B15; Wed, 12 Jul 2023 07:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=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 oubwTudl72ql; Wed, 12 Jul 2023 07:01:25 -0700 (PDT)
Received: from smtpclient.apple (unknown [41.86.46.73]) by ietfa.amsl.com (Postfix) with ESMTPA id B7867C151B0C; Wed, 12 Jul 2023 07:01:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Independent Submissions Editor (Eliot Lear)" <rfc-ise@rfc-editor.org>
Mime-Version: 1.0 (1.0)
Date: Wed, 12 Jul 2023 18:01:06 +0400
Message-Id: <59F40349-505A-45C7-BC1F-F7C0A7BD4D68@rfc-editor.org>
References: <20230711225516.03FB1EDFA0@rfcpa.amsl.com>
Cc: stephen.farrell@cs.tcd.ie, farzaneh.badii@gmail.com, schneier@schneier.com, smb@cs.columbia.edu, auth48archive@rfc-editor.org
In-Reply-To: <20230711225516.03FB1EDFA0@rfcpa.amsl.com>
To: rfc-editor@rfc-editor.org
X-Mailer: iPad Mail (20F75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/DDiMh82YY0Oc3CLmxo4PgBf1GgI>
Subject: Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrell-tenyearsafter-05> 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, 12 Jul 2023 14:01:29 -0000
Thank you, RFC Editor Team, for your thorough and timely editing! My suggestion is that you NOT revise the draft RFC until all authors have had a chance to comment. AUTHORS: please review ALL versions of the draft RFC before you approve. I have already noted at least one edit that will need to be reverted, but you will find that the overwhelming majority of the changes made are appropriate, so give a good look. As for timing, Stephen will be back over the weekend. No prize for fastest here. Just be sure you like what you read. Eliot > On 12 Jul 2023, at 02:55, rfc-editor@rfc-editor.org wrote: > > *****IMPORTANT***** > > Updated 2023/07/11 > > 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/rfc9446.xml > https://www.rfc-editor.org/authors/rfc9446.html > https://www.rfc-editor.org/authors/rfc9446.pdf > https://www.rfc-editor.org/authors/rfc9446.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9446-diff.html > https://www.rfc-editor.org/authors/rfc9446-rfcdiff.html (side by side) > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9446-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/rfc9446.original.v2v3.xml > > XMLv3 file that is a best effort to capture v3-related format updates > only: > https://www.rfc-editor.org/authors/rfc9446.form.xml > > For your convenience, we have also created an alt-diff file that will > allow you to more easily view changes where text has been deleted or > moved: > https://www.rfc-editor.org/authors/rfc9446-alt-diff.html > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9446 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9446 (draft-farrell-tenyearsafter-05) > > Title : Reflections on Ten Years Past The Snowden Revelations > Author(s) : S. Farrell, F. Badii, B. Schneier, S. Bellovin > WG Chair(s) : > Area Director(s) : > >
- [auth48] AUTH48: RFC-to-be 9446 <draft-farrell-te… rfc-editor
- [auth48] [ISE] Re: AUTH48: RFC-to-be 9446 <draft-… rfc-editor
- Re: [auth48] [ISE] Re: AUTH48: RFC-to-be 9446 <dr… Stephen Farrell
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Independent Submissions Editor (Eliot Lear)
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Jean Mahoney
- Re: [auth48] [ISE] Re: AUTH48: RFC-to-be 9446 <dr… farzaneh badii
- Re: [auth48] [ISE] Re: AUTH48: RFC-to-be 9446 <dr… Bruce Schneier
- Re: [auth48] [ISE] Re: AUTH48: RFC-to-be 9446 <dr… Independent Submissions Editor (Eliot Lear)
- Re: [auth48] [ISE] Re: AUTH48: RFC-to-be 9446 <dr… Stephen Farrell
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Steven M. Bellovin
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Bruce Schneier
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Stephen Farrell
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Bruce Schneier
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Independent Submissions Editor (Eliot Lear)
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Stephen Farrell
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Independent Submissions Editor (Eliot Lear)
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… farzaneh badii
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Stephen Farrell
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Steven M. Bellovin
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Independent Submissions Editor (Eliot Lear)
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Bruce Schneier
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Independent Submissions Editor (Eliot Lear)
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Bruce Schneier
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… farzaneh badii
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Independent Submissions Editor (Eliot Lear)
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Steven M. Bellovin
- Re: [auth48] AUTH48: RFC-to-be 9446 <draft-farrel… Jean Mahoney