Re: Request for feedback - IESG thoughts about new work proposals

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 16 October 2017 19:35 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97779134564 for <ietf@ietfa.amsl.com>; Mon, 16 Oct 2017 12:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 qWjZ5DqlZPqN for <ietf@ietfa.amsl.com>; Mon, 16 Oct 2017 12:35:57 -0700 (PDT)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (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 A331F134555 for <ietf@ietf.org>; Mon, 16 Oct 2017 12:35:57 -0700 (PDT)
Received: by mail-pg0-x235.google.com with SMTP id y7so7612453pgb.7 for <ietf@ietf.org>; Mon, 16 Oct 2017 12:35:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=upa/e5UYMbZ5uZSUzzfCOhbZ8qebgNMMFe7qCjoLjoc=; b=lN0mNmhER4z6FN//nxhUxrRb1zfJlNfeaBx2OAEPFg+szXJqc8rv4s/8l9tZmYVKQt ZjBGv5L5Luul5F7Fd9AiOC75naF9HZFtUqcemekI6xamQEspAb9y+G7AdeYIid1Ye2jt LDLM2zV/9liCNd+u54NNsHUpcUlfHjPG9AOAPNf6V7aJBlhoVneN53sqoQP8s38amUuN D7RGEY1QcEKOr3ZyQZ0hGPwZspsKNMY+ot/hNQM/Hby6LXn66anyvfIZwhUOzhx5FLRz CYYQjANR1FHD53+TgmAMmSvnNi5aHu2BwBCOL1LwVyyD22q78BAKEUQ0szxqzVognOAD KcWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=upa/e5UYMbZ5uZSUzzfCOhbZ8qebgNMMFe7qCjoLjoc=; b=M5kCpHxTrFb6DVACXl3rwyfDMPGSl9kTTPKKYVzAjAp71pAtpG6w3VzfIIvw4bLRU0 5ipGixrEIVVJxbUhe3dovcOY9Qii2Zn3WmeoXUTQ9mZDoj6vHPji+0QKnjkWBMbRAnRb 3L+PaYMeqEvBI1b48E/xmfzrpHDmDioxNFGQkoQ0xj/mTMn+PIeTAQR2bHJFaiYCZiJG 9bKZixQJkWYvZIdqQOGu5XK8Hq2I8qnRtYyZww1D7lvSdoTX3WH76Aux6qavedE50IrW O79hBbQ0r/f+rYkWRWlxh/rAl6Zs1HyNV/UybMAXYI8MQviShrZ8L1EKRtVI6Op173Ux 6NDw==
X-Gm-Message-State: AMCzsaXSdQ+q/IeF0q3AShfJzjApSE/zsDSXk/sBEJz7YEdAyVY9zAU5 iIZqGSOWE5l9bgb/C+Kf+0C41w==
X-Google-Smtp-Source: AOwi7QBKVFMV/oHbdI5oikCcQv/DpoFBFDhGpMh5xictNWWQFga7OhWEyb8fDEg/rd4+VlVm/lhoog==
X-Received: by 10.98.202.131 with SMTP id y3mr9749589pfk.199.1508182556970; Mon, 16 Oct 2017 12:35:56 -0700 (PDT)
Received: from ?IPv6:2406:e007:6d3c:1:28cc:dc4c:9703:6781? ([2406:e007:6d3c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id x4sm14140176pge.23.2017.10.16.12.35.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Oct 2017 12:35:56 -0700 (PDT)
Subject: Re: Request for feedback - IESG thoughts about new work proposals
To: Eliot Lear <lear@cisco.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org" <ietf@ietf.org>
References: <CAKKJt-fAaNPeeuSfS0Dv6vTAOXR=OS2XSKqPVMyxxr1O1tLwBg@mail.gmail.com> <7d45859d-6efc-5576-e413-8c9162c42776@gmail.com> <CAKKJt-ergSJvmzzOCaNP-iEk1i80UCpst-oaHpVoZg8PxFZRTw@mail.gmail.com> <16416.1507915421@obiwan.sandelman.ca> <aab5c229-4ab7-5105-2056-85231b48a828@cisco.com> <CAKKJt-dmb5sMEjaJktSm7QBtFXmpO5rhW4k_kWRp1kYf1Yr1og@mail.gmail.com> <9a7abb82-856a-c881-b46d-13dbf212fd4a@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <587af5a8-c128-d747-e9fb-1b36f708bec3@gmail.com>
Date: Tue, 17 Oct 2017 08:35:53 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <9a7abb82-856a-c881-b46d-13dbf212fd4a@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/imfn17YChmxhxP4MtAtRnQEXlRw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Oct 2017 19:35:59 -0000

On 17/10/2017 03:18, Eliot Lear wrote:
> Hi Spencer,
> 
> On 10/16/17 3:51 PM, Spencer Dawkins at IETF wrote:
>>
>>     Except that you have to start somewhere.  And our documentation
>>     isn't up
>>     to date.
>>
>>
>> Could you say more about that? It sounds like something needs to be fixed.
> 
> Yes, the Tao needs a dust off.[1]  See Section 2.2.2 of that document. 
> There are probably other areas that need work.  Similarly, "Bringing New
> Work into the IETF"[2] needs a dust off* (see slides 6 and 7).   I will
> also add that these documents are not exactly prominent, either on our
> current web site or on beta.ietf.org.  Might I suggest that "Getting
> Involved" be just a bit more prominently featured?

There are also a number of fixes pending in [3]. I sort of went on strike
about maintaining it when we were promised that the new web site was almost
ready, so it hasn't been updated since 2015-08-25. Just to give an idea
of the rate of churn in process-related documents, here's the list of
pending updates since then:

      RFC 7649, The Jabber Scribe Role at IETF Meetings
      BCP 25, RFC 7776, IETF Anti-Harassment Procedures
      BCP 101, RFC 7691, Updating the Term Dates of IETF Administrative Oversight Committee (IAOC) Members
      BCP 205, RFC 7942 on Improving Awareness of Running Code: The Implementation Status Section
      BCP 97, RFC 8067 on Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level
      BCP 14, RFC 8174 on RFC 2119 Key Words: Clarifying the Use of Capitalization
      BCP 79, RFC 8179 on Intellectual Property Rights in IETF Technology
      BCP 26, RFC 8126 on Guidelines for Writing an IANA Considerations Section in RFCs

Brian

[3] https://www.ietf.org/about/process-docs.html

> Eliot
> [1] https://www.ietf.org/tao.html
> [2] https://www.ietf.org/edu/documents/81IETF-New-Work.pdf
> * (Both of these works were fine documents and remain mostly fine, and
> it was awfully generous of those who put them together to have done so).
> 
>