Re: [Gendispatch] I-D Action: draft-nottingham-where-does-that-come-from-00.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 15 March 2021 13:48 UTC

Return-Path: <jmh@joelhalpern.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 2E9D83A1208 for <gendispatch@ietfa.amsl.com>; Mon, 15 Mar 2021 06:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 bpfi9XFdUswR for <gendispatch@ietfa.amsl.com>; Mon, 15 Mar 2021 06:48:48 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 1E5D43A121B for <gendispatch@ietf.org>; Mon, 15 Mar 2021 06:48:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4Dzd7401NQz6G9QK; Mon, 15 Mar 2021 06:48:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1615816128; bh=YXiRNKzztGgH2o6ocyWUT+9a15jXu6s8488+7SFhoPk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=cGNw+behaupbDmz0/aD3taPKraJqmW/g4DKiDoRivlHbE6ycMVwswu9kevUsF5Xld 8L8SFvFajV18swk0ppRNUAAJBU48vuI7xvwQZyqqxO8A0u7oLY9tZINCNu314kNEer dx1SYJ7nC0aNM65QTlEWt35kmjBsRQjhlSwO+02Y=
X-Quarantine-ID: <IXAtz7O8h7UI>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4Dzd732Nj2z6G7wM; Mon, 15 Mar 2021 06:48:47 -0700 (PDT)
To: "Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>
Cc: Mark Nottingham <mnot@mnot.net>, gendispatch@ietf.org
References: <202103151327.12FDR5oX003868@gndrsh.dnsmgr.net>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <0b169e33-a419-92ce-89fc-1df6d37dc2b1@joelhalpern.com>
Date: Mon, 15 Mar 2021 09:48:45 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <202103151327.12FDR5oX003868@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/iI6_Qsa_7tNBeISp-4rba_VXOPw>
Subject: Re: [Gendispatch] I-D Action: draft-nottingham-where-does-that-come-from-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Mar 2021 13:48:49 -0000

I am happy to discuss (somewhere?  by direct email?  on the IETF list? 
It is not the role of Gendispatch even if we are abusing it that way.) 
ideas for effective ways to keep internet drafts effective while better 
differentiating them.  I have no good ideas to offer, sorry.

Yours,
Joel

On 3/15/2021 9:27 AM, Rodney W. Grimes wrote:
> Gendisp, etc,
> 	Three comments inline marked [RWG].
> Regards,
> Rod
> 
 >> Joel Halpern wrote
...
>> Note that none of your changes would seem to help much with the most
>> common consufion, namely informational or experimental IETF RFCs being
>> treated as Standards Track RFCs by external promoters.  And no, I do not
>> think the right answer is to remove Informational or Experimental RFCs.
>>
>> And we already see folks (maybe deliberately, maybe accidentally)
>> confusing individual or WG Internet Drafts with RFCs.  Even though any
>> form of reference is completely different.
> 
> [RWG] I have actually seen a rather large open source project propose
> adopting an Individual Draft as a policy as if the IETF had
> published that work as an RFC.  This is a dangeriously bad state
> of affairs and is worth spending some time thinking about how
> the IETF can minimize such mistakes.
> 
...
> 
> [RWG]  Would it be worth creating a better document, or is this
> a solution in need of a problem?
>