Re: [Extra] Fwd: Personnel change for extra WG

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Sun, 31 March 2019 07:58 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A0F1200B6 for <extra@ietfa.amsl.com>; Sun, 31 Mar 2019 00:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 ixNT1BBb8g-A for <extra@ietfa.amsl.com>; Sun, 31 Mar 2019 00:58:07 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6872F12008F for <extra@ietf.org>; Sun, 31 Mar 2019 00:58:07 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 588BEC04F5; Sun, 31 Mar 2019 09:00:10 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1554019210; bh=osyRw52LqX15gDxn/ZJhTshC+TsHFXYpKC6pbxpgZmk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=B192RkU2M3ogJ45U6ISl0CIEaxWo5HzKo0nava7dCThfrUdEabMRapWno9Cij+akR ezCj47Bat6646WBC8jw7BDnM8kGsPSuvtEe+2/T9ZoXZbMR7qa/qYqd/CGIFD1raus v/7qbsuG6QD+m1kBE91ls9+xWpcWIZRGMwaiTvj0=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1554019209-26265-2661/9/92; Sun, 31 Mar 2019 08:00:09 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: extra@ietf.org
Date: Sun, 31 Mar 2019 09:58:04 +0200
Mime-Version: 1.0
Message-Id: <efb751c5-6a1d-492e-bbf1-c621c112c38e@gulbrandsen.priv.no>
In-Reply-To: <f82d658e-7590-42a4-b38e-b38bff2541f3@www.fastmail.com>
References: <49b87029-7cc2-4324-9d97-f7fa2b8762ce@www.fastmail.com> <25ed8a44-6fce-4778-d9cd-d732b7cb91f6@linuxmagic.com> <533a9f07-80c6-4cbc-b7af-fe10ce62580c@www.fastmail.com> <17b8d4e0-0ce5-4768-891c-5a7c77f19289@gulbrandsen.priv.no> <f82d658e-7590-42a4-b38e-b38bff2541f3@www.fastmail.com>
User-Agent: Trojita/0.7; Qt/5.7.1; xcb; Linux; Devuan GNU/Linux 2.0 (ascii)
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/ImTcj7zNGrpoUXmOsbOpnZYalS4>
Subject: Re: [Extra] Fwd: Personnel change for extra WG
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Mar 2019 07:58:10 -0000

On Friday 29 March 2019 19:44:53 CET, Bron Gondwana wrote:
> In this particular case, there's a pretty good piece of prior 
> art for the name in RFC5232, plus multiple mentions online.

Oh, that was easy to misunderstand, wasn't it. Sorry. I didn't mean to say 
that this particular flag was a bad candidate for standardisation. Rather 
that we already have two many piecemeal standardisations. If there's 
another RFC, it should make some attempt to cover most of the flags that 
ought to be standardised at this point in time.

...

> That sounds reasonable.  I'd be happy to help with a document 
> like that, or find someone else at FastMail who might want their 
> name on an RFC in exchange for doing the work :)

I can edit, iff two big providers will produce flag lists. Alone or with a 
co-editor.

I like the way Neil has used github.

Arnt