Re: New Version Notification for draft-resnick-variance-00.txt
Pete Resnick <resnick@episteme.net> Fri, 27 March 2020 22:38 UTC
Return-Path: <resnick@episteme.net>
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 1746C3A0C40 for <ietf@ietfa.amsl.com>; Fri, 27 Mar 2020 15:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 0ruizQdDJDPP for <ietf@ietfa.amsl.com>; Fri, 27 Mar 2020 15:38:01 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 729513A09AA for <ietf@ietf.org>; Fri, 27 Mar 2020 15:38:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 61CC1A571D9D; Fri, 27 Mar 2020 17:37:56 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P3n3YFX3o5hS; Fri, 27 Mar 2020 17:37:56 -0500 (CDT)
Received: from [172.16.1.18] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id E547FA571D96; Fri, 27 Mar 2020 17:37:55 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: Keith Moore <moore@network-heretics.com>
Cc: ietf@ietf.org
Subject: Re: New Version Notification for draft-resnick-variance-00.txt
Date: Fri, 27 Mar 2020 17:37:55 -0500
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <F4678926-10E3-46D8-B3AE-7A57400FF6F4@episteme.net>
In-Reply-To: <de98c36e-a0da-e480-6238-82c7f1e18c42@network-heretics.com>
References: <158533925458.17797.13806166303625482245@ietfa.amsl.com> <AE66200A-E718-4BF6-BA87-EE427A0BF971@episteme.net> <de98c36e-a0da-e480-6238-82c7f1e18c42@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"; markup="markdown"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1uCVUEVLWYAE2kT2fZE7M-ZXGMQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 27 Mar 2020 22:38:04 -0000
On 27 Mar 2020, at 17:22, Keith Moore wrote: > I think it's perfectly reasonable to publish a BCP for a one-time > variance. On the other hand I think it's a Very Bad Idea to invent a > lightweight variance procedure that allows for process exceptions that > aren't documented in the normal means, and which fragment the > historical record. Though I don't doubt anyone's intentions here, > a lightweight variance procedure will sooner or later inevitably be > misused. Also, it's never a great idea to hurriedly invent new > process when doing so can be avoided. If you read my draft, you'll notice that for all intents and purposes, all of the procedures of publishing a BCP are required anyway: It requires a written draft, a minimum 4-week last call, and a conclusion of consensus by the IESG. The only thing that is different is that it doesn't require publication as an RFC, addition to the BCP series, or an additional RFC or moving it to Historic when it no longer applies (because, as the draft says, it can't last longer than a year without actually publishing a BCP). So I don't see what the misuse vector you're seeing is. pr -- Pete Resnick https://www.episteme.net/ All connections to the world are tenuous at best
- Fwd: New Version Notification for draft-resnick-v… Pete Resnick
- Re: New Version Notification for draft-resnick-va… Spencer Dawkins at IETF
- Re: New Version Notification for draft-resnick-va… Spencer Dawkins at IETF
- Re: New Version Notification for draft-resnick-va… Pete Resnick
- Re: Fwd: New Version Notification for draft-resni… Keith Moore
- Re: New Version Notification for draft-resnick-va… Scott O. Bradner
- Re: New Version Notification for draft-resnick-va… Pete Resnick
- Re: New Version Notification for draft-resnick-va… Keith Moore
- Re: Fwd: New Version Notification for draft-resni… Adam Roach
- Re: New Version Notification for draft-resnick-va… Barry Leiba
- Re: New Version Notification for draft-resnick-va… Joel M. Halpern
- Re: New Version Notification for draft-resnick-va… Scott O. Bradner
- Re: New Version Notification for draft-resnick-va… Barry Leiba
- Re: Fwd: New Version Notification for draft-resni… Keith Moore
- Re: New Version Notification for draft-resnick-va… Pete Resnick
- Re: New Version Notification for draft-resnick-va… Keith Moore
- Re: Fwd: New Version Notification for draft-resni… Brian E Carpenter
- Re: New Version Notification for draft-resnick-va… Barry Leiba
- Re: New Version Notification for draft-resnick-va… Barry Leiba
- Re: New Version Notification for draft-resnick-va… Keith Moore
- Re: New Version Notification for draft-resnick-va… John C Klensin
- Re: New Version Notification for draft-resnick-va… S Moonesamy
- Re: New Version Notification for draft-resnick-va… John C Klensin
- Re: New Version Notification for draft-resnick-va… Brian E Carpenter
- Re: New Version Notification for draft-resnick-va… Keith Moore
- Re: New Version Notification for draft-resnick-va… Scott O. Bradner
- Re: New Version Notification for draft-resnick-va… Pete Resnick
- Re: New Version Notification for draft-resnick-va… Brian E Carpenter
- Re: New Version Notification for draft-resnick-va… S Moonesamy
- Re: New Version Notification for draft-resnick-va… Spencer Dawkins at IETF
- Re: New Version Notification for draft-resnick-va… Michael Richardson
- Re: New Version Notification for draft-resnick-va… Victor Kuarsingh
- Re: New Version Notification for draft-resnick-va… Brian E Carpenter
- Re: New Version Notification for draft-resnick-va… Keith Moore
- Re: New Version Notification for draft-resnick-va… Benjamin Kaduk
- Re: New Version Notification for draft-resnick-va… Spencer Dawkins at IETF