IETF Logo Mail Archive

Re: Tricky cross-area topics

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 06 October 2019 10:43 UTC

Return-Path: <mcr@sandelman.ca>
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 D3366120073 for <wgchairs@ietfa.amsl.com>; Sun, 6 Oct 2019 03:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.435
X-Spam-Level: *
X-Spam-Status: No, score=1.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 phWgn_ndilFh for <wgchairs@ietfa.amsl.com>; Sun, 6 Oct 2019 03:43:05 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EDC312004E for <wgchairs@ietf.org>; Sun, 6 Oct 2019 03:43:04 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [82.117.217.154]) by relay.sandelman.ca (Postfix) with ESMTPS id BAC5D1F456; Sun, 6 Oct 2019 10:43:03 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 08D402070; Sun, 6 Oct 2019 12:43:51 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF WG Chairs <wgchairs@ietf.org>, Mark Nottingham <mnot@mnot.net>
Subject: Re: Tricky cross-area topics
In-reply-to: <6C35326B-7C1B-404F-AE1B-CFA9023CF82B@mnot.net>
References: <77b22339-6a8e-8eaa-a695-724deb963dec@nostrum.com> <B5171FA2-F2B8-4BD6-BE9C-F669FCD86373@gmail.com> <6C35326B-7C1B-404F-AE1B-CFA9023CF82B@mnot.net>
Comments: In-reply-to Mark Nottingham <mnot@mnot.net> message dated "Sun, 06 Oct 2019 11:12:03 +1100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 06 Oct 2019 12:43:51 +0200
Message-ID: <1123.1570358631@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/XZwQGCQdicqGmokAoW--kDi94ws>
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: Sun, 06 Oct 2019 10:43:07 -0000

Mark Nottingham <mnot@mnot.net> wrote:
    > Random thought -- we make WGs jump through a minor formal hoop -- the
    > shepherd writeup -- before going to IETF LC, to make sure they've done
    > everything the need to and save later work.

    > It might be good to start doing something similar when they *start* a
    > new document, to make sure they take things like this into
    > account. Otherwise, I suspect this wiki page is going to get... dusty.

The trend is supposed to now be that shepherds are assigned when the document
is adopted.  That is so that they can watch to how the consensus is formed.
That write-up can't be finished until the WGLC, but it should be started when
the document is adopted.

So I'm agreeing with you: we should go through this list earlier.  But I
think that it can be done as part of the shepherd process.  I suggest that
the write up template include the top-level overview (area list + links) from
this document.


-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email