Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster-rep-12> for your review
Gary Illyes <garyillyes@google.com> Fri, 26 August 2022 14:09 UTC
Return-Path: <illyes@google.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 D6139C14F74C for <auth48archive@ietfa.amsl.com>; Fri, 26 Aug 2022 07:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.106
X-Spam-Level:
X-Spam-Status: No, score=-17.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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_NONE=-0.0001, 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, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 kyY6fEMZx5in for <auth48archive@ietfa.amsl.com>; Fri, 26 Aug 2022 07:09:08 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 D7851C14F73A for <auth48archive@rfc-editor.org>; Fri, 26 Aug 2022 07:09:07 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id z16so1941916wrh.10 for <auth48archive@rfc-editor.org>; Fri, 26 Aug 2022 07:09:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=+/txYjyzHMl1uNEL09sZzMaOncj0zXkThSb4Rq4zrrI=; b=bhgQRoRUySTmsQ3XqU4qE2FuXY1l6sMLcwuJphFevtqw5Q9YhenYEYCBq77P7whRm1 WOi55giAyXIFQh4CxhQEK6oFV8VmMrmcDr9IbnapwNqEh0fFt9ykvVkgdErYVQjii5ka VHoFUMcy2Fk2xIid/OJFquDDhEhF3Io/WQIwR98mCIdg3x2C6Oses/B0AjHzL+AKuQeT TpB2YGAQEfIjncn4C4TqqbXksrFKVtxeVZh09ngVEvaWs2qdFBpnjF8U5ozbY0L+uWrr RwxXERTX3UQtD+dEDtL11jATJf9AxxXEShuj1rbZeJGJr2+zL6dcQGtbFgP2AsQpEkxu sbTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=+/txYjyzHMl1uNEL09sZzMaOncj0zXkThSb4Rq4zrrI=; b=7kBilXX1PsibfdjOSiUQMubX2zJPdtDDruEobGOaZiGZgEfadbu0fKJ3RpD8L3Ab/H WZYVp1FTE+yTcN+/Nb6d09FlF2WrHhZH07JeUJy/egZq2By+aW7BYroECOJv2AGl58fP 2gqAffDd8z+U1qfGZ8cGb1LFWYk1SW8JfjY8o6VMcvXkI96IkszZTLIDwtOew9EbspqG dFJbN3pyju9KJjztP2a1GLlRw/rFfz1t3pX2wKY0Gs2y6JlXX5vHmcjIouQwiq1HQ061 6koQ4wjYHarY4yxKM3i2apmutS4LDLd3jXxq2+6lK2BqDOn2Az3V+pJZCTGwNlWrje8t FiSQ==
X-Gm-Message-State: ACgBeo3SIlqG49EQy+cHI9e846sd8qntf5rF7xp8Kd1wsy6YiD8R7qNn NxUSD0W3mCNY21ZJ+hTVzt+dvJnp7SSv9nkbg2A/2g==
X-Google-Smtp-Source: AA6agR5RNHtvbOJJ3GJ5fuZTmZXEAtgjmZOV9kG84BygZb/TFe2xJBcjjQ26+UfZdn+MCrtGgG9FJFlTYAeALBgP1dc=
X-Received: by 2002:a5d:47a1:0:b0:225:6290:2533 with SMTP id 1-20020a5d47a1000000b0022562902533mr4752640wrb.545.1661522945886; Fri, 26 Aug 2022 07:09:05 -0700 (PDT)
MIME-Version: 1.0
References: <20220826062352.D7AF555D46@rfcpa.amsl.com>
In-Reply-To: <20220826062352.D7AF555D46@rfcpa.amsl.com>
From: Gary Illyes <garyillyes@google.com>
Date: Fri, 26 Aug 2022 16:08:54 +0200
Message-ID: <CADTQi=eJZ0wPeu7o5_FLmsG_Wmm0cJAYWHrsrL-mwzSw7rDFFw@mail.gmail.com>
To: rfc-editor@rfc-editor.org, m.koster@greenhills.co.uk, henner@google.com, lizzi@google.com
Cc: ted.ietf@gmail.com, superuser@gmail.com, auth48archive@rfc-editor.org
Content-Type: multipart/mixed; boundary="000000000000fb09e005e72574d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/oPB0nQBU_CPn-vMOKQFhllIAjpg>
Subject: Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster-rep-12> 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: Fri, 26 Aug 2022 14:09:13 -0000
Thank you for your edits and review. Lizzi and I addressed the comments received and attached the updated XML to this email (also at https://github.com/google/robotstxt/blob/master/protocol-draft/rfc9309.xml) The draft attached looks good to me and from my perspective approved for publication. Martijn, Lizzi, Henner, please review this draft and provide feedback (probably on GitHub) and/or approval for publication. On Fri, Aug 26, 2022 at 8:24 AM <rfc-editor@rfc-editor.org> wrote: > *****IMPORTANT***** > > Updated 2022/08/25 > > 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/rfc9309.xml > https://www.rfc-editor.org/authors/rfc9309.html > https://www.rfc-editor.org/authors/rfc9309.pdf > https://www.rfc-editor.org/authors/rfc9309.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9309-diff.html > https://www.rfc-editor.org/authors/rfc9309-rfcdiff.html (side by side) > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9309-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/rfc9309.original.v2v3.xml > > XMLv3 file that is a best effort to capture v3-related format updates > only: > https://www.rfc-editor.org/authors/rfc9309.form.xml > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9309 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9309 (draft-koster-rep-12) > > Title : Robots Exclusion Protocol > Author(s) : M. Koster, Ed., G. Illyes, Ed., H. Zeller, Ed., L. > Sassman, Ed. > WG Chair(s) : > Area Director(s) : > > >
- [auth48] AUTH48: RFC-to-be 9309 <draft-koster-rep… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Gary Illyes
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Lizzi Sassman
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Martijn Koster
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Gary Illyes
- [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <draft-… Lynne Bartholomew
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Gary Illyes
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Gary Illyes
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Murray S. Kucherawy
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Gary Illyes
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Gary Illyes
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Murray S. Kucherawy
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Gary Illyes
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Murray S. Kucherawy
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Gary Illyes
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Gary Illyes
- Re: [auth48] *[AD] Re: AUTH48: RFC-to-be 9309 <dr… Gary Illyes
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Gary Illyes
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Martijn Koster
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Gary Illyes
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Gary Illyes
- Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster… Lynne Bartholomew