IETF Logo Mail Archive

Re: Doc shepherd writeup Q

Benjamin Kaduk <kaduk@mit.edu> Tue, 27 February 2024 21:50 UTC

Return-Path: <kaduk@mit.edu>
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 E43FEC15108F for <wgchairs@ietfa.amsl.com>; Tue, 27 Feb 2024 13:50:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, RCVD_IN_DNSWL_HI=-5, 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=mit.edu
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 t8jIUh60dBvo for <wgchairs@ietfa.amsl.com>; Tue, 27 Feb 2024 13:50:29 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E991AC15107C for <wgchairs@ietf.org>; Tue, 27 Feb 2024 13:50:28 -0800 (PST)
Received: from kduck.mit.edu (c-73-235-241-23.hsd1.ca.comcast.net [73.235.241.23]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 41RLoMUQ015944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 27 Feb 2024 16:50:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1709070625; bh=0+R3ecuUvOZw3eTxv5dq55oIpNIDSk5AtlZVBmknaB4=; h=Date:From:Subject:Message-ID:MIME-Version:Content-Type; b=LwPWJhxzUxu/0VdObKOgG0uvmkaAd+kvhNXtjQ/hPfBKWoh23poIjhj9NHBro3lq9 MzBjfJ99+TH2GEpzR3W6N8jxh1Y1M3XIeVSZv2RDeYZ9zdJWQ6EewD7XGXXbHmDhHz uW6Kk1Rt3vMPegzBMtaG751SOk0OaH+EosfqKpinmADH6axbvqYyhbixhLksfimIVV wNdarPv+/+1UtEnkB4YiYI4I3nXPHzMq7d/R6LUw+VBKfV/lxG3k/QpyyOw204VfOy crGpgvM5EKIuIWjojY3t5dcIDLbXIRWsKxmEIgZlBl/KpIEuKuPiTiJB7+s1WNXcPr jw8eAO+3tOBYw==
Date: Tue, 27 Feb 2024 13:50:21 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: "sbanks@encrypted.net" <sbanks@encrypted.net>
Cc: WG Chairs <wgchairs@ietf.org>
Subject: Re: Doc shepherd writeup Q
Message-ID: <Zd5ZHUTjNm8WMQPA@kduck.mit.edu>
References: <FE1B8D7D-5412-4F4D-B0FF-88B34705F911@encrypted.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <FE1B8D7D-5412-4F4D-B0FF-88B34705F911@encrypted.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/HL4NwGJxqeWM1hVqetXnnKb2qBw>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 27 Feb 2024 21:50:33 -0000

On Tue, Feb 27, 2024 at 01:36:20PM -0800, sbanks@encrypted.net wrote:
> Hi,
> 	I’m in the process of writing up a doc shep review, and question 10 notes:
> 
> 10. Several IETF Areas have assembled [lists of common issues that their
>     reviewers encounter][6]. For which areas have such issues been identified
>     and addressed? For which does this still need to happen in subsequent
>     reviews?
> 
> 	Can someone point me to where this/these lists are posted? 

I think this refers to https://wiki.ietf.org/group/iesg/ExpertTopics
(and pages linked therefrom).

-Ben

v2.23.0 | Report a Bug | By Email