Re: [rfc-i] [IAB] Fwd: New Version Notification for draft-flanagan-rseme-00.txt

Heather Flanagan <rse@rfc-editor.org> Fri, 25 October 2019 14:26 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DB4120878 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 25 Oct 2019 07:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 CT_yv282g5Fa for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 25 Oct 2019 07:26:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61EDF12007C for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 25 Oct 2019 07:26:35 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 81636F406F0; Fri, 25 Oct 2019 07:26:34 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id A38EDF406F0 for <rfc-interest@rfc-editor.org>; Fri, 25 Oct 2019 07:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzdgAMnlBiI5 for <rfc-interest@rfc-editor.org>; Fri, 25 Oct 2019 07:26:31 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id ADC83F406D2 for <rfc-interest@rfc-editor.org>; Fri, 25 Oct 2019 07:26:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7F38A20366A; Fri, 25 Oct 2019 07:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gcelk5xYhzBm; Fri, 25 Oct 2019 07:26:29 -0700 (PDT)
Received: from [10.198.42.38] (c-71-231-216-10.hsd1.wa.comcast.net [71.231.216.10]) by c8a.amsl.com (Postfix) with ESMTPSA id 03DFE203667; Fri, 25 Oct 2019 07:26:28 -0700 (PDT)
From: Heather Flanagan <rse@rfc-editor.org>
Message-Id: <02514B7B-1546-420A-B3D0-7DD99DF6369C@rfc-editor.org>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 25 Oct 2019 07:26:30 -0700
In-Reply-To: <e0d446b2-3019-6350-4213-1126412fa228@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <157195362260.11387.2707786903653263155.idtracker@ietfa.amsl.com> <E9E92899-87E7-4036-8182-3330622DE71C@rfc-editor.org> <e0d446b2-3019-6350-4213-1126412fa228@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.104.11)
Subject: Re: [rfc-i] [IAB] Fwd: New Version Notification for draft-flanagan-rseme-00.txt
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, RSOC <rsoc@iab.org>, Internet Architecture Board <iab@iab.org>
Content-Type: multipart/mixed; boundary="===============1947224352891357661=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>


> On Oct 25, 2019, at 6:33 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hiya,
> 
> On 24/10/2019 22:48, Heather Flanagan wrote:
>> Hola a todos!
>> 
>> I’ve posted a -00 draft for the RSEME BoF (Tuesday, 19 November @
>> 08:45-09:30 Singapore Time). This is a proposal based on the
>> information I heard during the virtual meetings (and many thanks,
>> again, to those who participated). Discussion is welcome; if there is
>> enough constructive input that seems to have general agreement, I’ll
>> be happy to try and get in an -01 before the Nov 4 cut-off for I-Ds.
> 
> Good stuff. If we had consensus on something like that approach
> I think that'd be good.
> 
> While the text in the draft is fine as it says "may choose," I
> figure it could be a bad plan to try do any work via design teams
> in the short term.

That certainly wasn’t in my head - I just wanted to make sure that the option was out there, given there are likely to be several areas of that may well need focused attention. First, the whole group has to figure out the details (milestones, goals, requirements, etc) of what they’re going to tackle, and in what order. Then they can possibly use design teams to run some of those things in parallel. 

> 
> ISTM that at present the IETF has sets of participants with (at
> least) two general positions that seem fairly diametrically opposed.
> In that kind of situation my guess is there'd be a real fear of a
> design team being stacked (whether by accident or design) in one
> direction or another, and that fear might lead to lots of wrangling.

If it was an easy thing, we wouldn’t be here in the first place. :-)

> 
> I'm not sure if much can be done about that other than to depend
> on the wisdom of the chairs as to when to try use a design team,
> but I just wanted to check that the plan was not: "start work on
> Monday, name design teams on Tuesday, do nothing while awaiting
> design team output…"

I hope not!

-Heather

> 
> Cheers,
> S.
> 
> 
>> 
>> Thanks! Heather
>> 
>>> Begin forwarded message:
>>> 
>>> From: internet-drafts@ietf.org Subject: New Version Notification
>>> for draft-flanagan-rseme-00.txt Date: October 24, 2019 at 2:47:02
>>> PM PDT To: "Heather Flanagan" <rse@rfc-editor.org>
>>> 
>>> 
>>> A new version of I-D, draft-flanagan-rseme-00.txt has been
>>> successfully submitted by Heather Flanagan and posted to the IETF
>>> repository.
>>> 
>>> Name:		draft-flanagan-rseme Revision:	00 Title:		RFC Series Model
>>> Process Document date:	2019-10-24 Group:		Individual Submission 
>>> Pages:		6 URL:
>>> https://www.ietf.org/internet-drafts/draft-flanagan-rseme-00.txt 
>>> Status:
>>> https://datatracker.ietf.org/doc/draft-flanagan-rseme/ Htmlized:
>>> https://tools.ietf.org/html/draft-flanagan-rseme-00 Htmlized:
>>> https://datatracker.ietf.org/doc/html/draft-flanagan-rseme
>>> 
>>> 
>>> Abstract: This draft offers a proposal to form a new IAB program
>>> called the RFC Editor Future Development Program.  This proposal is
>>> based on the discussions held during three virtual meetings in
>>> September and October 2019, and requests a new program, open to
>>> all, that will drive consensus around any changes to the RFC Editor
>>> model through extensive community engagement and outreach to a
>>> broad set of stakeholder communities.
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of
>>> submission until the htmlized version and diff are available at
>>> tools.ietf.org.
>>> 
>>> The IETF Secretariat
>>> 
>> 
>> 
> <0x5AB2FAF17B172BEA.asc>

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest