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

Eric Rescorla <ekr@rtfm.com> Wed, 30 October 2019 18:42 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 4851D12088F for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 30 Oct 2019 11:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level:
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=rtfm-com.20150623.gappssmtp.com
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 5Enag3CFlJU5 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 30 Oct 2019 11:42: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 015D5120124 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 30 Oct 2019 11:42:35 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AB479F40714; Wed, 30 Oct 2019 11:42:26 -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 0C00AF4071C for <rfc-interest@rfc-editor.org>; Wed, 30 Oct 2019 11:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 EvXW-voNw7sb for <rfc-interest@rfc-editor.org>; Wed, 30 Oct 2019 11:42:24 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) by rfc-editor.org (Postfix) with ESMTPS id 11191F40710 for <rfc-interest@rfc-editor.org>; Wed, 30 Oct 2019 11:42:24 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id y6so2391988lfj.2 for <rfc-interest@rfc-editor.org>; Wed, 30 Oct 2019 11:42:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NT0RpDnCPpnbAu5HRvwRFBEXffWzLz9w0DBXz5YuuU0=; b=SOpfUbnHgnbl961WTCUhbuyCf9i1P2870hcmFZm/0dqV1QFl+Q+F6m60dwUNLthLXi Sdr+MX1SGw0pTIs8tgLRjPshFWuokbgMtJ14EFNQsjUv3FvL0M2PAv3qPMjVcEpxR+j6 swXVDpDZiLmk1kMxhWX4Ft57Xw3se0dgLEUCTdxDJhuIqtEFNTvU2e8utCFRem0n1y8n RgsGVLVN4/b9Y0HOjqo77d+1679MzCDGH9SqZjPhvYkpPfHWoHwHwGdBmPI3On3exZ+c v8W7RRq/TM8+0/DHTvC1bqy8JyJ2NgemCOChMX8cPpKIO3PgaTF88YK5gFbDbRdKajcV Ra2w==
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=NT0RpDnCPpnbAu5HRvwRFBEXffWzLz9w0DBXz5YuuU0=; b=mmdazpRYkvVcVNZnBlsBfHqHfpMaJFAgUcb7lGvnD05OmtMlW8msJSCAhNZFeJZWPd c0yPV4CUQ0KpwD2dRwXq/IflGVGicp0bZX6+WYzcsNxepU8w3OeAnHloO0sU8/wuQREL JSODpBPoP+y4tM3+XXOL0WOF8qbvC358/4N9ElnoRkwO+4nAco8WeN9LtbLB1rMSE/jE m/sfQCwzWynQEn9YylgLQlfEgWawLbnicdiNLpFN/cIgF9IS76OLJi1bkJnJ+MowqCYl STWncistObGDIS+eJnslAFMuKJZ1N2hh17neO+zUTFYExAbdwBEXW2ltGIWW40HkQuaJ CjpA==
X-Gm-Message-State: APjAAAWM0AvyWqh3Gc3y9N/fikddYtKxXjyb7ohqbI8/ZeDO3JFiPUPQ eN3RwwRJJ+Y6kQW3ZpGHQXaGec//5+uRGBuIk0FJrw==
X-Google-Smtp-Source: APXvYqx1KLEKPuRQNfwSXve0M9pvYc1fOiOAXh91aRFuLPHKM9W8Kxd/BNGHxGarEev3rL4CENhwy9VPdWBn8gZQyHM=
X-Received: by 2002:a05:6512:75:: with SMTP id i21mr386819lfo.180.1572460950101; Wed, 30 Oct 2019 11:42:30 -0700 (PDT)
MIME-Version: 1.0
References: <157195362260.11387.2707786903653263155.idtracker@ietfa.amsl.com> <E9E92899-87E7-4036-8182-3330622DE71C@rfc-editor.org> <1B95F2FE-AEBF-4B65-8828-9B64831CB1FC@cooperw.in> <a17b3f28-8450-5208-1fe8-112ec8e5b599@huitema.net>
In-Reply-To: <a17b3f28-8450-5208-1fe8-112ec8e5b599@huitema.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 30 Oct 2019 11:41:53 -0700
Message-ID: <CABcZeBOOexdFbVSHgZrjc8nNEX3DEq_n120B_va=jOf_7_m=+A@mail.gmail.com>
To: Christian Huitema <huitema@huitema.net>
Subject: Re: [rfc-i] [Rsoc] 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>, RFC Interest <rfc-interest@rfc-editor.org>, Heather Flanagan <rse@rfc-editor.org>, Internet Architecture Board <iab@iab.org>
Content-Type: multipart/mixed; boundary="===============4598592627681260536=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

I also agree with this, and would also like to note that for *chair* of the
program we actually want someone who is good at making sure multiple
perspectives are heard and helps bring things to consensus more than
someone with a lot of institutional knowledge. Some of those people are
certainly former I* Chairs, but a number of people who we often call on for
this kind of duty are notand some of them are comparatively recent IETF
participants.

-Ekr


On Wed, Oct 30, 2019 at 11:29 AM Christian Huitema <huitema@huitema.net>
wrote:

>
> On 10/30/2019 5:39 AM, Alissa Cooper wrote:
> > Hi Heather, IAB,
> >
> > I realize I missed the window to comment on this before the -01 was
> > published, so feel free to disregard what I say below.
> >
> > I think the line "Past IAB or IETF chairs would likely be good
> > choices,” describing candidates to chair the program, is ill-advised.
> > It reinforces what I think is a perilous notion that old-timers are
> > best suited to do tasks in the community because they have been doing
> > similar tasks for a long time. I realize there are caveats in the
> > sentence, but to the extent that having it in there then creates some
> > onus on the IAB to explain itself if it does not choose past chairs to
> > chair this program, I think it would be better to leave this out. It
> > is already mentioned elsewhere in the document that one participant
> > suggested that past chairs be central to this process, which seems
> > sufficient to document the fact that someone thought this was a good
> idea.
>
>
> I agree with Alissa there. I notice that someone proposed that in the
> minutes of the 3rd conference call. Minuting that proposal is fine, but
> endorsing it is something entirely different.
>
> -- Christian Huitema
>
> _______________________________________________
> 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