Re: [Last-Call] Last Call: <draft-koster-rep-06.txt> (Robots Exclusion Protocol) to Informational RFC

Gary Illyes <garyillyes@google.com> Fri, 18 March 2022 10:11 UTC

Return-Path: <illyes@google.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0459A3A08B1 for <last-call@ietfa.amsl.com>; Fri, 18 Mar 2022 03:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.108
X-Spam-Level:
X-Spam-Status: No, score=-17.108 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y3D6jt2J7Er8 for <last-call@ietfa.amsl.com>; Fri, 18 Mar 2022 03:11:37 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 373CF3A08A6 for <last-call@ietf.org>; Fri, 18 Mar 2022 03:11:37 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id m3so1342843lfj.11 for <last-call@ietf.org>; Fri, 18 Mar 2022 03:11:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9LuSzyOT1pdSI7w8TSx36FTd5VKea5NRfW/elhjHUoo=; b=Qwna1sDEA8nMbtEa8IgGlr7Oa+WpAOrKrafYDIarydieXvdq0WOqx0xqZf9bs1QCb1 u11OimOirw3ns1KdvKlmL7QDJy5l8WqmqDqF80eWhiylyB5s4WlIuQ9Vn18QjF5iI6f6 a5IbNSLnpU2XuXRC+xnV7w2xBXFhr2stE192JdV89NVvaxf5MZYORez6RWuxpSIDxTRC Bgmrcv3Txo1KBOlfT6sIe5b5lVLCvKQOf8gmqxwjww0Ry1JTADPU7hO07fZBg0naf5N1 LSL9ZU2bClSZ9Z8wJHh5cJ/Gczkfa2N4kmMHsjljVvb2zWN5aCDrzCkW0hN0vEPZ5Q1z fQjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9LuSzyOT1pdSI7w8TSx36FTd5VKea5NRfW/elhjHUoo=; b=FZ8VCeJNfpQcvGedhWm5vZsW+dUYZri1PWtC90B3M0rvqqLKt52CaFcK4ak35PG4ZM ZKTECaRjFv9t7ja97+M6qcujTlTmRb1XLHmeWzWuw3b20q+MZaF2zhtfz+SeegAiAOxo TQaMtndJYiX6lmgQ34a8y11NLS9hqsMq/EO3zma8Q2yk8deBj6eX4Fjbf66n1bBNsi0v DzXHjtjR2rcGGnL/5MkIn0jv2E64Ze+iqwZNJCJDnzmGBRcsO6wocKc68dOaV6YLB3Q+ wvFaQGee8uCrPcPDP17ljilEyRjW/u4Iu6NDTs1Z8FT+N3VrCV9iUrNCwYMizf9LtEx+ rrzA==
X-Gm-Message-State: AOAM533TwQxECBGSluxcOhjcsE0RqhVURP5S/ZVlyk7WWj/yajElfH/y thFYpP6R+5WN9YNrcX8Qk9v4bf3MoaFu7wat7Zim2w==
X-Google-Smtp-Source: ABdhPJwnrfE9yrY2T9ak8YNqlI5zIWUynKxukfW2KIyZ77yh8yL89UG0y3DvkbPYi3eLCzctBLkxrgpaDiBC4WD7QEU=
X-Received: by 2002:a19:505b:0:b0:448:1f71:5866 with SMTP id z27-20020a19505b000000b004481f715866mr5385742lfj.372.1647598294510; Fri, 18 Mar 2022 03:11:34 -0700 (PDT)
MIME-Version: 1.0
References: <20220228222932.825F33844270@ary.qy> <245C65D2-EC38-4C49-9CA0-3DD687CB37DA@mnot.net> <CA+9kkMAnmoJ0n3mPscZvc6kbyOZjQU78vb+iA0Pw5Qq=_kKZEw@mail.gmail.com> <ee8c0615-9207-cf7a-b1a0-905f33062e7a@taugh.com> <CA+9kkMBn-jJbwKjOdOpLL3PFS0REVUBUoSa+2MD0NxnvttHCcg@mail.gmail.com> <91329874-9301-40EC-8155-FBFE55DB89E4@akamai.com> <618c8f70-3d09-fe09-6088-597b2b63655e@it.aoyama.ac.jp> <3efab652-be64-e179-b387-0468a2da9f1c@taugh.com> <5DCC145C-D887-4184-B8F5-3C00563C620A@akamai.com> <7672C0CA-DED8-45A4-842A-BC5C159DD792@greenhills.co.uk> <CADTQi=ekZ-0ChcJ2F-WTxCRvGRSuPOyygbBuRkDpO39mq0Hykw@mail.gmail.com> <CAL0qLwa54t0P_ZniVHvMnee1j9g0Rb6j7Rj9LMCUPwPeOEVrcg@mail.gmail.com> <888588E5-D0F2-4BFE-9EBB-68E7C7FC4744@mnot.net>
In-Reply-To: <888588E5-D0F2-4BFE-9EBB-68E7C7FC4744@mnot.net>
From: Gary Illyes <garyillyes@google.com>
Date: Fri, 18 Mar 2022 11:11:22 +0100
Message-ID: <CADTQi=cW4=WbaP1QDSK_iWWkd_EnZQCPkwsGDg2mU2zkhMnXBA@mail.gmail.com>
To: Andrey Zosimov <zosimov@yandex-team.ru>, Fabrice Canel <Fabrice.Canel@microsoft.com>, Mark Nottingham <mnot@mnot.net>
Cc: Martijn Koster <m.koster@greenhills.co.uk>, "Murray S. Kucherawy" <superuser@gmail.com>, "Salz, Rich" <rsalz@akamai.com>, "henner@google.com" <henner@google.com>, "last-call@ietf.org" <last-call@ietf.org>, "lizzi@google.com" <lizzi@google.com>
Content-Type: multipart/alternative; boundary="0000000000001482ef05da7b5fec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/SdfcsCenTrvWDcmB_C-lp_8G7Sg>
Subject: Re: [Last-Call] Last Call: <draft-koster-rep-06.txt> (Robots Exclusion Protocol) to Informational RFC
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2022 10:11:42 -0000

Adding to this thread Andrey Zosimov (Yandex) and Fabrice Canel (Bing) to
confirm the draft is acceptable for their respective search engines.

https://datatracker.ietf.org/doc/html/draft-koster-rep-06

Based on the feedback we received so far, we're not going to  have more
changes to the draft other than the boilerplate change discussed in this
thread, and the example and language corrections in the ART review.

On Tue, 15 Mar 2022 at 22:24, Mark Nottingham <mnot@mnot.net> wrote:

>
>
> > On 16 Mar 2022, at 3:52 am, Murray S. Kucherawy <superuser@gmail.com>
> wrote:
> >
> > If the authors are prepared to make this change, I'd like to hear why
> "IETF Standards Track w/consensus" is (or should be) off the table,
> especially if other search engines are going to indicate support.
>
> That's reasonable, if support eventuates. If it doesn't, it would be
> pretty awkward -- I think we'd want at least some level of review or at
> least acknowledgement by other major implementers before declaring it
> Standards Track.
>
> AIUI a status change would necessitate another IETF LC, so that might be
> the best way to solicit that support. Make it a long one to give other
> implementations a meaningful way to respond -- say, four weeks.
>
> If the IESG doesn't hear from at least two or three other stakeholder
> implementations (in its estimation), it could still be published at
> Informational, and transitioned to Standards Track if/when that support
> eventuates.
>
> Make sense?
>
> Cheers,
>
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> --
Thanks,
Gary