Re: [rfc-i] New Version Notification for draft-flanagan-rseme-00.txt
Heather Flanagan <rse@rfc-editor.org> Fri, 25 October 2019 13:14 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 28740120288 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 25 Oct 2019 06:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-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 DVQ7JeBOKL7u for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 25 Oct 2019 06:14:10 -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 E0658120877 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 25 Oct 2019 06:14:10 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1AFB6F40710; Fri, 25 Oct 2019 06:14:10 -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 7F6B5F4070B for <rfc-interest@rfc-editor.org>; Fri, 25 Oct 2019 06:14:08 -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 vJjvaQtwQhrq for <rfc-interest@rfc-editor.org>; Fri, 25 Oct 2019 06:14:05 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 92158F406F2 for <rfc-interest@rfc-editor.org>; Fri, 25 Oct 2019 06:14:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A0D582034AB; Fri, 25 Oct 2019 06:14:03 -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 BesmIgy4ia32; Fri, 25 Oct 2019 06:14:03 -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 49964203423; Fri, 25 Oct 2019 06:14:03 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Heather Flanagan <rse@rfc-editor.org>
In-Reply-To: <6878c026-f2a3-dbce-ce17-ff81489774d5@nomountain.net>
Date: Fri, 25 Oct 2019 06:14:03 -0700
Message-Id: <BBB9E661-D798-47D7-9D55-DFB668028F63@rfc-editor.org>
References: <157195362260.11387.2707786903653263155.idtracker@ietfa.amsl.com> <E9E92899-87E7-4036-8182-3330622DE71C@rfc-editor.org> <6878c026-f2a3-dbce-ce17-ff81489774d5@nomountain.net>
To: Melinda Shore <melinda.shore@nomountain.net>, RFC Interest <rfc-interest@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.104.11)
Subject: Re: [rfc-i] 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: RSOC <rsoc@iab.org>, Internet Architecture Board <iab@iab.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
> On Oct 24, 2019, at 9:11 PM, Melinda Shore <melinda.shore@nomountain.net> wrote: > > On 10/24/19 1:48 PM, Heather Flanagan wrote: >> 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. > > Thanks for getting this out so quickly, and for what > looks like a comprehensive and well-structured summary > of the discussion so far. > > I have to admit that it never occurred to me to do this > as an IAB program and I find it a really appealing idea, > with the caveat that some new processes are going to have > to be defined. For example, the proposal doesn't mention > how the program would reach decisions (by rough consensus, > I assume?) or how it would be handled if things went badly > (accountability, chair/editor replacement if necessary, etc.). > As things currently stand, IAB programs are chaired by > IAB members, but that's not defined anywhere so it's > an open question AFAIC. Similarly, to my knowledge we've > never had a completely open IAB program, either, as there's > been an expectation that it would be a small, focused (fsvo) > group with domain expertise. So, I think some process > questions would need to be settled in advance to protect > the group against process-based DoS attacks (not that that > would ever happen at the IETF), etc. > FWIW, not all IAB programs are chaired by IAB members. I point to the RSOC as the current example of that. As to the openness of IAB programs, I don’t think there’s anything that says they can’t be; I did not see any requirements about that one way or the other on https://www.iab.org/activities/programs/ or in RFC 2850. > I also think this is an opportunity to try some innovation > around longer-term efforts, so I'd be curious to hear additional > proposals. Suggestions are more than welcome! -Heather > > Melinda > > > -- > Melinda Shore > melinda.shore@nomountain.net > > Software longa, hardware brevis > > _______________________________________________ > rfc-interest mailing list > rfc-interest@rfc-editor.org > https://www.rfc-editor.org/mailman/listinfo/rfc-interest _______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Fwd: New Version Notification for draft-f… Heather Flanagan
- Re: [rfc-i] Fwd: New Version Notification for dra… Melinda Shore
- Re: [rfc-i] Fwd: New Version Notification for dra… Adrian Farrel
- Re: [rfc-i] New Version Notification for draft-fl… Heather Flanagan
- Re: [rfc-i] New Version Notification for draft-fl… Heather Flanagan
- Re: [rfc-i] [IAB] Fwd: New Version Notification f… Stephen Farrell
- Re: [rfc-i] [IAB] Fwd: New Version Notification f… Wes Hardaker
- Re: [rfc-i] [IAB] Fwd: New Version Notification f… Heather Flanagan
- Re: [rfc-i] New Version Notification for draft-fl… Alissa Cooper
- Re: [rfc-i] New Version Notification for draft-fl… Jari Arkko
- Re: [rfc-i] [Rsoc] New Version Notification for d… Christian Huitema
- Re: [rfc-i] [Rsoc] New Version Notification for d… Eric Rescorla
- Re: [rfc-i] New Version Notification for draft-fl… Jari Arkko
- Re: [rfc-i] New Version Notification for draft-fl… Brian E Carpenter