Re: [auth48] AUTH48: RFC-to-be 9309 <draft-koster-rep-12> for your review
Lizzi Sassman <lizzi@google.com> Fri, 26 August 2022 19:58 UTC
Return-Path: <lizzi@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 ABAFBC14F73D for <auth48archive@ietfa.amsl.com>; Fri, 26 Aug 2022 12:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.605
X-Spam-Level:
X-Spam-Status: No, score=-17.605 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, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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, 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 fcnv9UmnRAEZ for <auth48archive@ietfa.amsl.com>; Fri, 26 Aug 2022 12:58:52 -0700 (PDT)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (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 EFA7FC14EB1E for <auth48archive@rfc-editor.org>; Fri, 26 Aug 2022 12:58:51 -0700 (PDT)
Received: by mail-vs1-xe2d.google.com with SMTP id q67so2654456vsa.1 for <auth48archive@rfc-editor.org>; Fri, 26 Aug 2022 12:58:51 -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=MBGH46Jr4wvrVpgPQJ0FMEXWJ0trnmysWdYdMG67Ie4=; b=ie4ExR/wv0icRhKg5PBtD3g/Miyn5he/sqQ5WCmAHpPK9ygHbk7ouvmaOtErsemOiu 1xeV2nAqVBfdWxEStZ9xnniOhaFCNraQ+R0AHhvypZ0UiiODyWEAvbHJ0VzeV7chDW+8 I7Y4hcd75+ZkGjw8VWioRMyh7vnkN5Ue6hhaIWjJC/pFpfjd76psOqu/SPWU6YPnMMHF /alCEQgn2zLdmIhIGXIbVNqd1SzkDEj0ywqGhD5RobCYCPKeumSknjXsO4rQ/2tWS3zN 8PVn/Viwu99XGpznTAUu0Hby/wo+s3CH5Dw+PA5trBlkI7YI7JAA4iyD+ZdFRCE22npU bd6g==
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=MBGH46Jr4wvrVpgPQJ0FMEXWJ0trnmysWdYdMG67Ie4=; b=NuRKf642BWMRRk9CiLaxMnfxTRYiAWzd7rBEMdh+oPfbUHlt2R+Nua+0Ca83PyIscX 0rUaBnfWskRkobq3GKH5PaI0IavqC1AZhRO8Xemia4MO0CCZUNq8crP5dwNDS5Bgd0Dr SVPp8g1INa2ZlFvCyrt8FdWUS9KExgvMVOnnAEoKTWt3QFmmrkjefh5S5/4GgWtsdmRO n/ojrh8XrE7ZHhm+XMcZEkYfO3adEbyJ3ZIGoqIW2sYGrPKhX5Gtidl+5itdNpIABsg4 aCzQzZgp1URmRfQo+cJRawIiMxkA3YR+Gykp8lqSOog0UTNqydh9MK3u2t1qBGTLIU16 DRZw==
X-Gm-Message-State: ACgBeo1PapNgzR/9VBqcmv1z/KfDEm/8JNrj58mJJa84oWjWHEmE0jKV QdwtSYD+gdbneA8/WrEFOQLkiG0MCA1Wp/xwi4ZnvA==
X-Google-Smtp-Source: AA6agR6kwYq5VPNW/sLF0FRe7CKOvzhdNSU4wjiPXTY7SnW4vQFNh64iMW5yHXmmJQCePwlObsO2L23bnQa7f7tggmM=
X-Received: by 2002:a67:c205:0:b0:38f:3eb7:5429 with SMTP id i5-20020a67c205000000b0038f3eb75429mr422845vsj.52.1661543930974; Fri, 26 Aug 2022 12:58:50 -0700 (PDT)
MIME-Version: 1.0
References: <20220826062352.D7AF555D46@rfcpa.amsl.com> <CADTQi=eJZ0wPeu7o5_FLmsG_Wmm0cJAYWHrsrL-mwzSw7rDFFw@mail.gmail.com>
In-Reply-To: <CADTQi=eJZ0wPeu7o5_FLmsG_Wmm0cJAYWHrsrL-mwzSw7rDFFw@mail.gmail.com>
From: Lizzi Sassman <lizzi@google.com>
Date: Fri, 26 Aug 2022 21:58:13 +0200
Message-ID: <CAEZSzfhzh8jCHL8Tqon4-Hwjnato24ndwzr83GTWRabHFpedWA@mail.gmail.com>
To: Gary Illyes <garyillyes@google.com>
Cc: rfc-editor@rfc-editor.org, Martijn Koster <m.koster@greenhills.co.uk>, Henner Zeller <henner@google.com>, Ted Hardie <ted.ietf@gmail.com>, superuser@gmail.com, auth48archive@rfc-editor.org
Content-Type: multipart/alternative; boundary="000000000000c94b2005e72a57b9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/Ar2F1jMWoGAc6f7JTgS_gCCoN8I>
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 19:58:55 -0000
The draft LGTM. Thanks, Lizzi On Fri, Aug 26, 2022 at 4:09 PM Gary Illyes <garyillyes@google.com> wrote: > 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