Re: [Gendispatch] A gendispatch session at IETF 118?
Eric Rescorla <ekr@rtfm.com> Mon, 04 September 2023 13:14 UTC
Return-Path: <ekr@rtfm.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D0F6C1519B1 for <gendispatch@ietfa.amsl.com>; Mon, 4 Sep 2023 06:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20230601.gappssmtp.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 Ztp5T4fu-vod for <gendispatch@ietfa.amsl.com>; Mon, 4 Sep 2023 06:14:19 -0700 (PDT)
Received: from mail-oa1-x33.google.com (mail-oa1-x33.google.com [IPv6:2001:4860:4864:20::33]) (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 A00E1C1519B0 for <gendispatch@ietf.org>; Mon, 4 Sep 2023 06:14:19 -0700 (PDT)
Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-1ba5cda3530so1181938fac.3 for <gendispatch@ietf.org>; Mon, 04 Sep 2023 06:14:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20230601.gappssmtp.com; s=20230601; t=1693833258; x=1694438058; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wyR+wa3rXWfsKAzi4bvBNQrR7fH07eZmmiDcCZmbDRc=; b=q2yjKSHhFasUeHQI0L+N1KoFIR1+Y3BEK46c92G5MtYdwq3yk3PjIAClKtzHv8pMIk 41zz34LD6gW5nSeDys0Oph/kR54fKMn0bMd7hFMJnUSCqzCqlxz6kfkbuQ9El/Ro2ena s9C/VZRwxZLokYFUar80hMg020rOMo/adn8ER1n/8qcgIPVauGxU0p/zKCtWHgpGlllo ZUMOxFHg27faEI4yqjg7BzsW+IpE996mzMNgxNvu9+cn3Q6A8Fzj43WytFYyISG3l2In s0/ubcWH9bueNAEpTd26IxHwRqTDj3PtDAVbUXLsrGjkh3cnNuuftA85fsxwzBFhx3B4 Gapw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693833258; x=1694438058; 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=wyR+wa3rXWfsKAzi4bvBNQrR7fH07eZmmiDcCZmbDRc=; b=h8FhRTkZh78INNmMMg7tftgc0LP78IATowxILqND+t+NLNgSjSgg7CW1+Qp1SzhF7M ZB4XGaFeCFL0C/L4RgpX+32Np0kStiOjvKBEz7Ktjppkn9I3ISYH/IgsQ854rmJQXjw7 lxMzomskum7cawBFxABOfR5Wf7QpYHHZyljIQcUQoHP+mtKWaY9O702ZvFjVy+Tn4OFO /VM/tvy74PAyKK+8nqdtmt80BH7uJbTzVlTgpvXAabviGdkIBhWWh3aGQew4UIyYxqzf E8E+cxptnD3jg43tb4NG+5yA0XATLqOEU2/p+Y6Gx6nCfyAj9Rmy9hn0jCQTHKCneB9m 4BPA==
X-Gm-Message-State: AOJu0YyrVZxxHWX5nWX62NiMvIjZgHzwiiHhZcT0TuCwuswy9DOxfs1M XaL1lql4HbloNQSp1v2/6e9DeEx5VoZUhUF4yGRvKQ==
X-Google-Smtp-Source: AGHT+IGIhYORxWlZN6Hyqc1VumcAKn6nLv/kB9FFBVRuzgIFxYY4ZoKFIdCyKEF0lbHQ0yyOQy3Kt67qwVinCc9HiFM=
X-Received: by 2002:a05:6358:c11:b0:13a:d25a:ed7b with SMTP id f17-20020a0563580c1100b0013ad25aed7bmr11272639rwj.10.1693833257886; Mon, 04 Sep 2023 06:14:17 -0700 (PDT)
MIME-Version: 1.0
References: <6036cbfa3f204dcebdd2a2393a6101ab@huawei.com> <9b9a6c68-877b-42c5-9231-e95f0df4e190@betaapp.fastmail.com> <4cb7e10e-673d-27cf-1115-d721c5aa1a1e@cs.tcd.ie> <ed7b3d50-25d2-d82d-3514-3d5282f18c56@joelhalpern.com> <90816281-ce30-2112-4ea5-355e14105e06@gmail.com> <4935A0FA-F4B2-4ABE-8825-11485B30230B@akamai.com>
In-Reply-To: <4935A0FA-F4B2-4ABE-8825-11485B30230B@akamai.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 04 Sep 2023 06:13:41 -0700
Message-ID: <CABcZeBMqV33ks+J+k1cCRAh2iaxxHdEE7SLn3UiY_=hBxbCBQQ@mail.gmail.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "gendispatch@ietf.org" <gendispatch@ietf.org>, GENDISPATCH Chairs <gendispatch-chairs@ietf.org>, Paul Hoffman <paul.hoffman@icann.org>
Content-Type: multipart/alternative; boundary="000000000000a53ddd060488494e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/S7aWeJbBsDaV8-TwcfipCmzqv8A>
Subject: Re: [Gendispatch] A gendispatch session at IETF 118?
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2023 13:14:20 -0000
On Mon, Sep 4, 2023 at 6:04 AM Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote: > > My suggestion (just sent) is simply to make drafts >1 year old invisible > in the default search. > > I doubt that will be very useful. Most people who would be misled by > outdated drafts probably do not use Datatracker document search, but rather > one of the big web search engines. > We're way past the gendispatch question, but I actually find the datatracker's refusal to show expired drafts very confusing, especially when said drafts have been adopted or become an RFC and wish it would do so, at least by pointing me to the descendent documents. Rather than omitting documents, I would prefer that the datatracker by default attempted to sort by relevance, rather than just deciding I didn't want to see things. -Ekr > > > -- > Gendispatch mailing list > Gendispatch@ietf.org > https://www.ietf.org/mailman/listinfo/gendispatch >
- [Gendispatch] A gendispatch session at IETF 118? Pengshuping (Peng Shuping)
- Re: [Gendispatch] A gendispatch session at IETF 1… Martin Thomson
- Re: [Gendispatch] A gendispatch session at IETF 1… Stephen Farrell
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Brian E Carpenter
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Martin Thomson
- Re: [Gendispatch] A gendispatch session at IETF 1… Eliot Lear
- Re: [Gendispatch] A gendispatch session at IETF 1… Martin Thomson
- Re: [Gendispatch] A gendispatch session at IETF 1… Salz, Rich
- Re: [Gendispatch] A gendispatch session at IETF 1… Stephen Farrell
- Re: [Gendispatch] A gendispatch session at IETF 1… Eric Rescorla
- Re: [Gendispatch] A gendispatch session at IETF 1… Joel Halpern
- Re: [Gendispatch] A gendispatch session at IETF 1… Paul Hoffman
- Re: [Gendispatch] A gendispatch session at IETF 1… Brian E Carpenter
- Re: [Gendispatch] A gendispatch session at IETF 1… Geoff Huston
- Re: [Gendispatch] A gendispatch session at IETF 1… Robert Sparks
- Re: [Gendispatch] A gendispatch session at IETF 1… Rob Sayre
- Re: [Gendispatch] A gendispatch session at IETF 1… Eliot Lear
- Re: [Gendispatch] A gendispatch session at IETF 1… Jim Reid
- Re: [Gendispatch] A gendispatch session at IETF 1… Rob Sayre
- Re: [Gendispatch] A gendispatch session at IETF 1… Salz, Rich