Re: [Rfcplusplus] Sunk cost + not about us

Alissa Cooper <alissa@cooperw.in> Wed, 11 July 2018 13:58 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: rfcplusplus@ietfa.amsl.com
Delivered-To: rfcplusplus@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D08128CF3 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 06:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=0pR4/2N3; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JQIur5Rt
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 SR1uh8-6jmz3 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 06:58:58 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DE891277BB for <rfcplusplus@ietf.org>; Wed, 11 Jul 2018 06:58:58 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6B38E21C48; Wed, 11 Jul 2018 09:58:57 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 11 Jul 2018 09:58:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=iGSv1yf0pKtTYcMNdKTmKTrWtoL6E QURSIRJ3xCogtg=; b=0pR4/2N3DIJV6NdI4SwNaFtLx29Iz0+Cyx6uXrKuQhoit 6SRXUJVngWlH6Hss4eTURi89yvXF5wT9jKMUy5mc3r/P+faYFhXhsjhybWiwjvrS 6jVr25Yv6tket39LBFys/M0iF8szFUU4TzFAWywcPvcNttz/0+PLphZnIgxDdqQE pkB+Ah5swTsrYgYR8EK4TxuTt17tAsgq+nCXOmyT/W6rchsCxpZZ5BmCMitIew+z ipOJCqEGL0ofmXHVNuykOv5mNOp9zYsYkfJSrr0OQM6+OK+MmkX2U7WlOYg61NpU /shcntoWserguH8175Z0EeUnQ2FfYMfgvvypXjSXw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=iGSv1y f0pKtTYcMNdKTmKTrWtoL6EQURSIRJ3xCogtg=; b=JQIur5Rt4vooKDa8ZNFt3r NwCQyDs0VfWyKQskkkL9ZnoOz2pUBQzzin0tIDhx8IVLNtjBFNFr4ge6F2UJEi98 Y76ApsNI6VcZKVznZOzvsZSDTBeIB0VrFaFSESbfXWks8OJPFfH/126wu7HpsB/L CJnDPzp3huaCImMqHon/TgwGjNpmDoIoZiee5p380RWL/Vzu/7UrEUpmI2N3XYex pl/bjjNfWGTZHI20K2oAiiulHfCABFyhiCzuZR4gOsdtjVmi/eha5D+PG9acp2pL adm6Ka6DMXlIFibKlQH0grwqpCiqS5/91t0x5qoFMuvk1Q5CTDIpITM+1oVLyEPA ==
X-ME-Proxy: <xmx:IQ1GW31sIoH6Ju7wTVIguU2JJH_iLsAGI9xrRsOb0Y9WX8cpcr0giQ> <xmx:IQ1GWwiN9RvE6z8KIXp1NbQGrtPMe2dZYH1-209GThEMoMDnmvXleQ> <xmx:IQ1GW_a6DMovRLPVF-RzvqjugLUySeCsrEFJNGwJOOre7dR1LP7IgQ> <xmx:IQ1GW0XAHKOY4c8VNJo_8Y2B0vFVaQbmWOCbKOU5w-J8aQzUa43Mmg> <xmx:IQ1GW_F6BcMFjxy0IjeJra_teW5oPTOJxneU-0z2jSn9d8YZik9Etg> <xmx:IQ1GW4dBVzS0Lq4QIG--g1JMrycllM4R2HN9XLeE29bN1_UeMO6TaA>
X-ME-Sender: <xms:IQ1GW6TzI0wnCkf3hRrYxC0ASxEN7xM3WM07LbV2l4AIjUkUcb1Z4Q>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.82]) by mail.messagingengine.com (Postfix) with ESMTPA id E161510273; Wed, 11 Jul 2018 09:58:56 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <53A44968B8377095ABB61DEC@PSB>
Date: Wed, 11 Jul 2018 09:58:55 -0400
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfcplusplus@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A472A36-1719-4D38-B2C5-DB5FAC37AC64@cooperw.in>
References: <CAL02cgQbT8s0493SdbM7Gbw2ZiSV1kMHk+6=Z4BdC2Ky664CNg@mail.gmail.com> <d159dd1f-de0b-d6c5-6430-cd5577e266fd@joelhalpern.com> <20180710144525.GE20282@mx4.yitter.info> <e0cfcb0c-7b23-9903-cf71-0f4d736bb80b@gmail.com> <53A44968B8377095ABB61DEC@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/lnZwZX3N3Th3oJyBragC4kfycVU>
Subject: Re: [Rfcplusplus] Sunk cost + not about us
X-BeenThere: rfcplusplus@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: For discussion of the RFC++ BoF proposal and related ideas <rfcplusplus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfcplusplus/>
List-Post: <mailto:rfcplusplus@ietf.org>
List-Help: <mailto:rfcplusplus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 13:59:00 -0000

Hi John,

> On Jul 11, 2018, at 9:49 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
> 
> 
> --On Wednesday, July 11, 2018 14:47 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> ...
>> However, what I'm getting clearly from the last
>> 24 hours' email is that since we don't yet understand the
>> problem, it's way too soon to seriously design an
>> (experimental) solution.
> 
> Normally, I'd say that was true.
> 
> But the situation is not normal.  We are in a situation in which
> it seems clear that the thinking that went into
> draft-thomson-rfcplusplus-label-00 was key to the BOF proposal
> and that both it and the BOF proposal posit a very specific
> solution.  While I accept Martin's explanation and hence have no
> reason to believe the posting of that draft at the last minute
> was intended to disadvantage any other proposed solutions, it
> does have that effect, an effect that is aggravated by there
> still being no posted agenda for a BOF that occurs on the first
> day of the meeting.  That leaves us without knowing whether the
> intention is to discuss the problem or to assume, as the BOF
> proposal does, that there is a problem that is in need of
> solutions and that we are discussing solutions (or one specific
> solution).  Perhaps the plan is "both", but, especially with
> only one possible solution available in I-D form before Monday
> morning and the amount of discussion about a variety of topics
> on the list, 90 minutes seems very compressed.
> 
> Alissa, given that state of affairs and assuming that possible
> solutions are not going to be ruled out of order in Monday's
> discussion, can we get blanket permission for late-posting
> (before Monday) of any draft related to this BOF?  

As has been my practice pretty much since I joined the IESG, I’m fine with doing manual postings of late-arriving drafts between now and when the submissions window opens, if people send them to me. And of course there is nothing stopping people from sending pointers to documents they’ve written that haven’t yet been posted to the I-D repo, as has become more common in some WGs lately.

Alissa

> I think it is
> generally accepted that discussing I-Ds, even hastily prepared
> ones, is usually more productive than discussing partial
> proposals that go by on mailing lists.   And, while the posting
> cutoff was intended, in part, to allow people adequate time to
> read and study documents before IETF begins, it seems to me that
> giving people the weekend (and possibly even part of tomorrow
> and Friday) is preferable to either giving them zero time
> (solutions introduced at the BOF itself) or well under 24 hours
> between whenever I-D postings are allowed again on Monday (the
> "important dates" page appears to no longer show whether that
> is, e.g., 00:01 UTC or the starting time of the meeting).
> 
> best,
>   john
> 
> 
> 
> 
>