IETF Logo Mail Archive

Re: [rfc-i] [Rsoc] New proposal/New SOW comment period

Sarah Banks <sbanks@encrypted.net> Wed, 04 September 2019 03:48 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 09F32120072 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 3 Sep 2019 20:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.951
X-Spam-Level:
X-Spam-Status: No, score=-4.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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 fWu_hnpjr6rn for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 3 Sep 2019 20:48:21 -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 319AF12008F for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 3 Sep 2019 20:48:21 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1D1BCB8083E; Tue, 3 Sep 2019 20:48:00 -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 5E1DAB8083E for <rfc-interest@rfc-editor.org>; Tue, 3 Sep 2019 20:47:59 -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 OafAVw1dhPbL for <rfc-interest@rfc-editor.org>; Tue, 3 Sep 2019 20:47:55 -0700 (PDT)
Received: from aws.hosed.org (aws.hosed.org [50.16.104.137]) by rfc-editor.org (Postfix) with ESMTPS id 650DEB8083B for <rfc-interest@rfc-editor.org>; Tue, 3 Sep 2019 20:47:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id 7829780094; Tue, 3 Sep 2019 23:48:15 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at aws.hosed.org
Received: from aws.hosed.org ([127.0.0.1]) by localhost (aws.hosed.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5vN-wV_ER1C; Tue, 3 Sep 2019 23:48:15 -0400 (EDT)
Received: from [172.16.12.109] (c-73-71-250-98.hsd1.ca.comcast.net [73.71.250.98]) by aws.hosed.org (Postfix) with ESMTPSA id F1A4B8007D; Tue, 3 Sep 2019 23:48:14 -0400 (EDT)
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Sarah Banks <sbanks@encrypted.net>
In-Reply-To: <02e801d56023$a7de6730$f79b3590$@augustcellars.com>
Date: Tue, 03 Sep 2019 20:48:13 -0700
Message-Id: <1CDF0BEF-E0C7-4EB6-BAD8-045F9DD036C7@encrypted.net>
References: <4675DA5C-0CFE-4E02-980D-770B17907D35@encrypted.net> <6.2.5.6.2.20190830124138.08d4ab38@elandnews.com> <5dd85c7b-84d4-9192-db70-28e61ed3bf01@nostrum.com> <6.2.5.6.2.20190830214019.0ba94918@elandnews.com> <740F4638-B988-4FB3-97EE-8EAEF366D521@akamai.com> <6.2.5.6.2.20190831082218.0ba64748@elandnews.com> <FD1BA644-68A7-45E9-BAC7-16FB75F7D1FD@huitema.net> <02e801d56023$a7de6730$f79b3590$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.3445.104.11)
Subject: Re: [rfc-i] [Rsoc] New proposal/New SOW comment period
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-editor.org, rsoc@iab.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Speaking for myself, I'd say that anything that can wait should wait. Do we NEED to have change bars RIGHT NOW in order for documents to flow? I think the temp position shouldn't be forming policy unless we think it has to be done now. That starts with a discussion in the RSOC; I'd expect either the temp person to bring it to us (as Heather often does today) or for the RSOC to bring it to the temp person. 

If we agree on this rough idea, should we add it to the SOW to be clear, or simply have that discussion during the interview process, etc?

Thanks
Sarah


> On Aug 31, 2019, at 10:43 AM, Jim Schaad <ietf@augustcellars.com> wrote:
> 
> So the piece of mail from Russ makes for an interesting starting point for
> discussion of what you believe this new person should be doing.
> 
> He has asked for a new feature, change bars, to be added to the v3
> vocabulary and provided an example of when this has been done in the past.
> This means that the person in charge needs to look at this feature request
> and decide what to do with it.  Except for a decision to punt, this is a
> decision that has long term effects on the RFC series.  Should this be
> allowed?  If allowed how is it presented for the different document formats?
> What is the mechanism that this is done in the vocabulary?  Does this mean
> that we should have the full set of change bar features or not?  The current
> document just has bars down the side, but does not have any insert or delete
> markers.
> 
> Is this the type of decision that this new Temp RFC Series Manager supposed
> to be making?  
> 
> Jim
> 
> 
> _______________________________________________
> Rsoc mailing list
> Rsoc@iab.org
> https://www.iab.org/mailman/listinfo/rsoc

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

v2.23.0 | Report a Bug | By Email