Re: New Version Notification for draft-resnick-variance-00.txt
Barry Leiba <barryleiba@computer.org> Fri, 27 March 2020 22:53 UTC
Return-Path: <barryleiba.mailing.lists@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 65B2D3A0B9B for <ietf@ietfa.amsl.com>; Fri, 27 Mar 2020 15:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 x8pyqYHjdGiv for <ietf@ietfa.amsl.com>; Fri, 27 Mar 2020 15:52:59 -0700 (PDT)
Received: from mail-ot1-f50.google.com (mail-ot1-f50.google.com [209.85.210.50]) (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 660C73A0A43 for <ietf@ietf.org>; Fri, 27 Mar 2020 15:52:59 -0700 (PDT)
Received: by mail-ot1-f50.google.com with SMTP id f52so11528313otf.8 for <ietf@ietf.org>; Fri, 27 Mar 2020 15:52:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=X+pL/P4lqy4tV5le5cYIqmRYNVGcog39qq5mQ4VmsA8=; b=fDXCN2MXE9JwS0ihHsKjlE3DBSbbtUpAvlh97yPkgyB+yhpS/Fc0x7ob6VjJkre5Eb vLo2tnV2I3LiH1TN/o1J6Ty2zUgbS4GTiqJE5M8C/JRhxnhWcNHClvrxQMyDqQL/dXB2 MCRGksgQIjis+5gGfertzs+d8CC0p6/O8w6TOvu5se22uRHaKTEvPIV8xXmYJVXkYfg7 Q/Q2rqMwlLpAa4Wg/09oYzN2Y1dtplBp7lseZV2Flh8t7kOmTUQjIgRdl7M4v4R2NgY5 elPBSqLAMZpXKyB5PxHYimumCe1TxrlRot1vBIf3g+KC4nwH2g+hbfY1/e0EDBe4MKNE rZNw==
X-Gm-Message-State: ANhLgQ1VybB+RjJFkX79QJZ3j+xMy5UXEZhPhVG/RaHwrAO8e817ZOps KdRnHHv4IDrD6MkzdPQjwo9E7gf32zMupVsVy/I=
X-Google-Smtp-Source: ADFU+vtxuQ4lj48FP+wsWrHcIULs1lnbuVJ7NQVowuTQHD3eqC3hMlNGBw+6gS/2/q/O0Bw4fPMnIbQikFllTLxExGc=
X-Received: by 2002:a4a:b91a:: with SMTP id x26mr1514823ooo.2.1585349578607; Fri, 27 Mar 2020 15:52:58 -0700 (PDT)
MIME-Version: 1.0
References: <158533925458.17797.13806166303625482245@ietfa.amsl.com> <AE66200A-E718-4BF6-BA87-EE427A0BF971@episteme.net> <de98c36e-a0da-e480-6238-82c7f1e18c42@network-heretics.com> <F4678926-10E3-46D8-B3AE-7A57400FF6F4@episteme.net> <bbaaa92b-22cc-4c09-cdf2-4e403ce5d8c5@network-heretics.com>
In-Reply-To: <bbaaa92b-22cc-4c09-cdf2-4e403ce5d8c5@network-heretics.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 27 Mar 2020 18:52:47 -0400
Message-ID: <CAC4RtVAd61Uz5i685DiGGeqoJ=czoNdF7YqxnsCJLYuxHog8Zg@mail.gmail.com>
Subject: Re: New Version Notification for draft-resnick-variance-00.txt
To: Keith Moore <moore@network-heretics.com>
Cc: Pete Resnick <resnick@episteme.net>, IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AScgWQ5v1iQVSElRoydiAGuti04>
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:53:00 -0000
> The problem I have is with not publishing as an RFC. I don't think > people should have to dig through email archives (which are not as > reliably archived as the RFC series) to find out what the whole IETF > process is, or even the evolution history of the IETF process. I think > even brief deviations from the process should be archived the same as > any other changes to the process. There's not a lot of "digging through" when we're posting it to ietf-announce (fairly low-volume, and where things such as NomCom announcements and other appointments, RFP decisions, and other Very Important IETF-related decisions are posted). I think, personally, that the kinds of exceptions we're talking about here are pretty much equally important to, say, the announcement of the NomCom chair, the NomCom's decisions about whom to appoint to the IESG and IAB and LLC Board, the IAB's appointment of ISOC BoT directors, and the like. The ietf-announce list is, in fact, where we archive all of that stuff. None of it goes into RFCs. > But I'll flip this on its head: why did we suddenly become so concerned > about the overhead of publishing a single RFC, when as far as I can tell > we've had a pretty low bar for RFC publication all along? Because (1) there is significant overhead, and publishing them does get in the way of publishing other RFCs (including clearing out Cluster 238), and (2) the RFCs are an archival document series, which we would LIKE to keep to things of actual, long-term importance. Historical information is (and should be) available elsewhere. Barry
- 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