The links page [was: something else]
Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 01 October 2021 20:27 UTC
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1663E3A096F; Fri, 1 Oct 2021 13:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 z7CJvpTYuBpQ; Fri, 1 Oct 2021 13:27:34 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 2BC2A3A0977; Fri, 1 Oct 2021 13:27:34 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id r201so4526465pgr.4; Fri, 01 Oct 2021 13:27:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=4cWX6EvnXs7nJLjUEUdn/u3lpm/oua+FSsMllyFojj8=; b=VV8gq/Ftjz0XdZa1AsOr6yaiSGwsRMqs+tZ+7QJ0CghtupugxsDDOhyc1zjxfwZnvD aXAaTNRO+0qX1eSQ/gOCNRwkYBk64kjpi5olHF9dw+EhUjdDNMugeBRJ7PUMRxNvGnV5 lvqctKXbIifO822/kjtMJJX95+zHG+b+Lv01d42T37HPJCCThtD653DCY3dyOIdhnnpk KPZfWpnhtyJZbIFkbUF2AqsOtbanPNaW4gTCYj9UAFdzvCg9uOz3HsQo63XnH5DS18GQ QnmAB1Tc+9BfNX+ogB4yQStbIEgGmRH2nDNsrG9rJomqigjO/6e3Zg71j/Dv4S5Zchaj Yk5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4cWX6EvnXs7nJLjUEUdn/u3lpm/oua+FSsMllyFojj8=; b=GYNAXRtg3ZN63V8H7NGRPeXARNxFHjbEWqfLKf31/wfogNJTbyYC89i7cMQ2ntBvRg 5Cs3WlXjDJRBJc8N42dmM0zpnIH/em3bdh6aOlAaJjyEhql9qRWlsx/ovHY7PAODQ4iT akGj+yDrJ9T0tIYlBZk9KUStNSbK30IlrVHjNeq2c3Ve/3FsSX0mbWTt3sEm80R61uoi FsqaxmLMvM0RCRN9WV0wr8Qx6AXRyUieAmUbkoWQQWwL/JknnuKxc5+x9/RyxG+bWVON F79RNbgjWcV1uKHN0Cdz1qaFQMPQ/1Lk24OBMh1HoZZzYdz/cXf8eLxthbehbhzbOZyL KqMQ==
X-Gm-Message-State: AOAM531vp+HCJwPu0Nhv0P6MwFXLbg1/FQCgmQtteXt50z/3f3YWe8jZ 627JXcJt3StW9F7xUPeRnVe7q1RPzeputg==
X-Google-Smtp-Source: ABdhPJz9zVGjtH2pE3cKQyuFLWp6B87ysyPff2WHczPqMtxcmfot+KppgUzDl1qCVclVuwykYzVkmQ==
X-Received: by 2002:a62:8855:0:b0:44b:8cc3:8f6d with SMTP id l82-20020a628855000000b0044b8cc38f6dmr13052877pfd.44.1633120053246; Fri, 01 Oct 2021 13:27:33 -0700 (PDT)
Received: from ?IPv6:2406:e003:11aa:d701:80b2:5c79:2266:e431? ([2406:e003:11aa:d701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id s197sm5735286pfs.141.2021.10.01.13.27.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 01 Oct 2021 13:27:32 -0700 (PDT)
Subject: The links page [was: something else]
To: John C Klensin <john-ietf@jck.com>, Robert Sparks <rjsparks@nostrum.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Working Chairs <wgchairs@ietf.org>, tom petch <daedulus@btconnect.com>, IETF <ietf@ietf.org>
References: <f22d22ea-80da-e595-d91f-c577461766a3@huitema.net> <44B61547-1B28-4D1C-88C1-4AD7BA7F9639@lear.ch> <69E7C755-D09C-447B-B327-4F13C19A3EED@eggert.org> <475d7515-f71a-c3f0-e455-03336226cc47@lear.ch> <04F3603A-514B-49DF-81C5-36023CBBB69E@eggert.org> <CALaySJLseu4Ci_=-OZDN1NKLimnfLSjnPFyv2bwOnOxL6q4RGg@mail.gmail.com> <3627.1632928020@localhost> <6c6129eb-21b0-6bf1-86a8-f092fe78b3d4@gmail.com> <29954.1633025138@localhost> <b7101988-a26a-019a-bee8-7605b4a6d212@gmail.com> <6156C837.3020003@btconnect.com> <D9D2D7FF0974E6C3F00CCE65@PSB> <CAKKJt-dUNsnvVixd6ysaQ-s7feCgiA4sCm_52OV9xLj6YePX+A@mail.gmail.com> <ccb570db-3d68-87f2-1300-feb25093cd90@nostrum.com> <5C75B025FE3E8C26AE4EBD50@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <5e057baf-a1e4-e168-b780-6c67feec33ae@gmail.com>
Date: Sat, 02 Oct 2021 09:27:27 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <5C75B025FE3E8C26AE4EBD50@PSB>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/BRNTBSIWndFEYpJuUFDLNbdOBz4>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2021 20:27:39 -0000
On 02-Oct-21 07:01, John C Klensin wrote: > > > --On Friday, October 1, 2021 10:32 -0500 Robert Sparks > <rjsparks@nostrum.com> wrote: > >> Related but apart from discussion of what summaries might be >> sent by email - >> >> There is a feed for last call documents at >> https://datatracker.ietf.org/feed/last-call, and a page at >> https://datatracker.ietf.org/doc/in-last-call. >> >> There are several feeds, fwiw. At one point there was a menu >> for them, but pressure to declutter the menus some time back >> took that away. There should at least be a summary page >> somewhere. > > Robert, > > Thanks. > > Noting that a page the IETF participants don't know about or > don't know how to find is of limited utility, your paragraph > above exactly, if indirectly, summarizes part of the problem. > I've just looked at > https://www.ietf.org > https://www.ietf.org/standards/process/ > and even > https://www.ietf.org/links/ > (which only active participants who have been paying attention > know how to find). > > And, if any of them contain the links you provided or even hints > that they exist, I'm not looking hard enough. While, again, I > don't think that page is a substitute for well-considered Last > Call announcements (at least to the relevant WG, maybe Area, and > a weekly summary as others have discussed), it suggests that we > should be looking more broadly than tweaking or subdividing > mailing lists. > > Some particular suggestions that I assume should be > straightforward if others agree: > > (1) Add https://datatracker.ietf.org/doc/in-last-call to the > "links" page under "IESG", "Internet-Drafts" or both. > > (2) Add a line to the bottom of the template for Last Call > announcements that says something like "A listing of open IETF > Last Calls is available at > https://datatracker.ietf.org/doc/in-last-call > > Really a different topic, but I also think the "links" page > should be more obviously available from the www.ietf.org home > page and wonder whether the Last Calls should be identified > there too. However, I've lost track of who the audience for > that page is supposed to be and wonder if any evaluation is > underway for whether that redesign is serving its intended > purpose. I believe I am to blame for the existence of that page, which largely speaking does what the old IETF sidebar did. (For the nostalgic, see https://www6.ietf.org/) fwiw, I agree that it should be more obvious and cover more ground. Brian
- Proposal: an "important-news" IETF announcement l… IETF Chair
- Re: Proposal: an "important-news" IETF announceme… Melchior Aelmans
- IETF calendar (was: Re: Proposal: an "important-n… Toerless Eckert
- Re: Proposal: an "important-news" IETF announceme… Bob Hinden
- Re: Proposal: an "important-news" IETF announceme… Christian Huitema
- RE: Proposal: an "important-news" IETF announceme… Adrian Farrel
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Salz, Rich
- Re: Proposal: an "important-news" IETF announceme… David Noveck
- Re: Proposal: an "important-news" IETF announceme… Tim Wicinski
- Re: Proposal: an "important-news" IETF announceme… Lucas Pardue
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: [irsg] Proposal: an "important-news" IETF ann… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- Re: [irsg] Proposal: an "important-news" IETF ann… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Lars Eggert
- RE: Proposal: an "important-news" IETF announceme… MORTON JR., AL
- Re: Proposal: an "important-news" IETF announceme… Stephen Farrell
- RE: Proposal: an "important-news" IETF announceme… STARK, BARBARA H
- Re: Proposal: an "important-news" IETF announceme… Eliot Lear
- Re: Proposal: an "important-news" IETF announceme… Carsten Bormann
- Re: Proposal: an "important-news" IETF announceme… Marc Petit-Huguenin
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Alexey Melnikov
- RE: Proposal: an "important-news" IETF announceme… MORTON JR., AL
- Re: Proposal: an "important-news" IETF announceme… Robert Sparks
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- RE: Proposal: an "important-news" IETF announceme… STARK, BARBARA H
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- making upcoming calendar more useful Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Jay Daley
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… Jay Daley
- Re: Proposal: an "important-news" IETF announceme… Martin Thomson
- Why last calls matter more than ever [Re: Proposa… Brian E Carpenter
- Re: making upcoming calendar more useful John C Klensin
- Re: making upcoming calendar more useful Warren Kumari
- Re: making upcoming calendar more useful Barry Leiba
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Brian E Carpenter
- Re: Proposal: an "important-news" IETF announceme… tom petch
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- Re: Proposal: an "important-news" IETF announceme… Spencer Dawkins at IETF
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… Robert Sparks
- Re: Proposal: an "important-news" IETF announceme… Michael Richardson
- Re: Proposal: an "important-news" IETF announceme… John C Klensin
- The links page [was: something else] Brian E Carpenter