Re: [Gendispatch] draft-kucherawy-bcp97bis

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 08 August 2022 20:56 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D14B2C157B32 for <gendispatch@ietfa.amsl.com>; Mon, 8 Aug 2022 13:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=gmail.com
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 Q08VVFpP95HV for <gendispatch@ietfa.amsl.com>; Mon, 8 Aug 2022 13:56:21 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E25C14F738 for <gendispatch@ietf.org>; Mon, 8 Aug 2022 13:56:21 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id q7-20020a17090a7a8700b001f300db8677so10268363pjf.5 for <gendispatch@ietf.org>; Mon, 08 Aug 2022 13:56:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=6IRdcuymAAPI61vsyB1OYlm2SnQPkNSmb1LKt2byh/w=; b=qNFFNQ3W8HHU3iXgAs+pAvF57omBAyIPL56sGtWCS0fMRJ0lxXk0klkxsq4EGi0FhB dv7buTjR110ZqgQlBhGNRjEYXDaHU4UcGV6ERo0gTxmGqAUNapXeACf4T6E78g+ptmCD HOmdUAToN0Glpq1erLtaQ/y212LrNO3VM/w4HC/6ZboJvLjNmiBJ06SPMJ8qaGB+od4/ LbAP3sgin1zrMl8X3KhZizcKQ7w6PyPbvFsYvxqkSAanO42O+Dx1iiAL9K5g0fskitmR Y3O2rKc/8rrF9u/hVwT72OCKZkIU82StQ0qLtwGzylL9W/C6ezFoRvK6YZrp6PtcXjlH oZ3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=6IRdcuymAAPI61vsyB1OYlm2SnQPkNSmb1LKt2byh/w=; b=3kWH3koEwMCzISG+Gs5JUV/yC/eb3kxrLv2NsSiV7h55Kg3PtxkrOXVrjrwDZujJAf tLsUHCwTALaE+zrYyCBfvXWRrOfJg84+wHrR3fXXKVZPc7uQ70MDuqNQV5ip3EHRKy/f QAj4p6P4looJiUZqs7JbXpSmbDkEyA2/iHGu0EhMbmkyRjF14O9s45R/tjRJtM+XBDaD cqYmkXbhWuoXwpRPUWGGDsmlRZEv+oOP/KJgFFKCOpZvevEHodvlH9MkG+XU/w3dR+3f OxLWz18Jhy2kXT6DiRAL3NAE+/V8exCGkBUf8xHogh9d3ypNGAWtXttshVDsVAgjjKCs PgiA==
X-Gm-Message-State: ACgBeo1aW9ZOsySlLJkePegd6LyZ1buAd5V9X7E8IB+VjHr1I2vUDgta mMSQzLlZQczL21DsAKh/kbA=
X-Google-Smtp-Source: AA6agR7B4eZTHJC5I8GvdMXcAzAGD0NX9PxPC/0OkSlY0O+jnWcERUiI0mEBoMaav4QtSDoS4/X+JA==
X-Received: by 2002:a17:90b:4f8d:b0:1f5:835:1b19 with SMTP id qe13-20020a17090b4f8d00b001f508351b19mr30372692pjb.63.1659992180246; Mon, 08 Aug 2022 13:56:20 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id d2-20020a170902f14200b00170a8973137sm3037920plb.17.2022.08.08.13.56.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Aug 2022 13:56:19 -0700 (PDT)
Message-ID: <1501eb83-0260-4681-d1c9-6e2173b8f833@gmail.com>
Date: Tue, 09 Aug 2022 08:56:13 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: adrian@olddog.co.uk, "'Murray S. Kucherawy'" <superuser@gmail.com>, gendispatch@ietf.org
Cc: 'Erik Kline' <ek.ietf@gmail.com>
References: <CAL0qLwbpuvCLF68jdW-3ZDa4eACSSrVEyPDpyR9=GBoWFtT+1w@mail.gmail.com> <11f201d8ab0b$53fd5190$fbf7f4b0$@olddog.co.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <11f201d8ab0b$53fd5190$fbf7f4b0$@olddog.co.uk>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/piecfNjeroIafwvGXvlOFrHuL_8>
Subject: Re: [Gendispatch] draft-kucherawy-bcp97bis
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2022 20:56:24 -0000

1) I believe this draft is useful work and should be progressed. I doubt that it's controversial, so AD-sponsored would be an adequate process.

2) Re "stable", I think it's a reasonable choice of word and it's used three times in RFC 2026 (without definition). It is a judgment that the IESG is already allowed to make by RFC 2026, so why not here too?

Regards
    Brian Carpenter

On 08-Aug-22 21:43, Adrian Farrel wrote:
> Hi Murray,
> 
> A small point about your use of “stable”.
> 
> I think that the converse is largely subjective (I know unstable when I see it), and it doesn’t follow that that which I don’t think is unstable is actually stable.
> 
> It would be helpful, I think, if you were to replace the term “stable” (which you only use twice) with something that clearly expresses what you mean. At that point we can review and decide whether we agree with you.
> 
> Cheers,
> 
> Adrian
> 
> PS There is a Jim Morison joke in here somewhere, but I can’t be bothered to extract it.
> 
> *From:*Gendispatch <gendispatch-bounces@ietf.org> *On Behalf Of *Murray S. Kucherawy
> *Sent:* 08 August 2022 06:03
> *To:* gendispatch@ietf.org
> *Cc:* Erik Kline <ek.ietf@gmail.com>
> *Subject:* [Gendispatch] draft-kucherawy-bcp97bis
> 
> Colleagues,
> 
> A while ago I started an effort to revise BCP 97.  I announced it to GENDISPATCH early on but it hasn't gotten agenda time or direct discussion here to date.
> 
> It is currently an AD-sponsored document, which is a common pattern for IESG-initiated work.  There was some support for this path on the original thread where it was discussed, but Rich Salz suggested that it would be better if venue selection was done by one of the *DISPATCH groups.  I'm happy to divert it here if there's interest in calling the question the dispatch way before it goes any further.
> 
> The document can be found here:
> 
> https://datatracker.ietf.org/doc/draft-kucherawy-bcp97bis/ <https://datatracker.ietf.org/doc/draft-kucherawy-bcp97bis/>
> 
> ...and the original discussion thread:
> 
> https://mailarchive.ietf.org/arch/msg/ietf/tCQUsGFzyQ_I9qwabJdtVFF5XKI/ <https://mailarchive.ietf.org/arch/msg/ietf/tCQUsGFzyQ_I9qwabJdtVFF5XKI/>
> 
> Naturally I yield to the chair(s) to run the GENDISPATCH process in terms of venue selection.  Does this need agenda time, or is it possible to ask the question(s) on the list only?
> 
> -MSK, ART AD
> 
>