Re: [Rfced-future] Issue 151: Consultation / Approval for RSCE Selection committee

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 11 January 2022 02:29 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B80A03A0EE2 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 18:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 v9x8Ibl9N5QO for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 18:29:28 -0800 (PST)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CD283A0EDB for <rfced-future@iab.org>; Mon, 10 Jan 2022 18:29:28 -0800 (PST)
Received: by mail-pj1-x102e.google.com with SMTP id rj2-20020a17090b3e8200b001b1944bad25so3189010pjb.5 for <rfced-future@iab.org>; Mon, 10 Jan 2022 18:29:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=/idwVkJ/aGOjxRh5LKFaMBbVHoTok5B1kGNcdP3IzgQ=; b=W1njqdsPhMrY/KgvTO2iyJTWVX3Rk+LZlfdJsGQnXhWCgy92V6DTvL9JKsfXS/nT0R ZX23lDBA31fi4R10GIFNeCOAxPEHtFQ/vd7Jahg2gulFH3LQcx9w6EUfjEuO7F525xlD bnuPlRMi1LSmUh4G5hHAjCnWtVhyANDaYDF3Nfu3a+HlVXfd9UdXXaWHLVKPKXzmyLTX GEiWbRqe9o2O6yc91RGFpgROTKQ2d1SLow+kJ0xtuNmXLdw5AKlioAC3YWokeFQNcR3B CimSORkGS9ZwndlHRjns6KXTxE81c1Ba3IlsDZFXw6xDmwOwxiGH3MbqjPRrdc6ItZZa mymA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/idwVkJ/aGOjxRh5LKFaMBbVHoTok5B1kGNcdP3IzgQ=; b=5mD1a41q1Zq35018D1zX7GwKAhVnpRLokCALuOQgoBpq2Kb3TSY0FUJ5BMBWDJicI8 TI1dInCoP8SuEvkuHSIdLeHwUH6qZly4Ice1c3w2qtUOsvvegNGvREzhiDDwndYYhpKL R6Ak//9SqVovJ0nUEDeulUMEllV2AOCLt0r3g9GA23yu0OOl3alQKm+uStdhaBq15P6j Qi3CPb3UywhmcnHJENvntrbN6Oy86Nq+0oeyvqxTB3QWgjjzlA9COKIsMvaqFy8Ojula 34INqZNuJlJ4YSNI3J5W0qyn1RN7Iwx0VTAlzxTeP7i0CFIzWu+ed8ELGEpk3JtrgoWC WEJw==
X-Gm-Message-State: AOAM533YPK5KKS8ZdRUTzAClvGMBrPxzgpukSsfbGB9rdUHt/44kmaG9 lKqgE0Q+C7p+g0GsI84xkpE=
X-Google-Smtp-Source: ABdhPJxVGhmTnSv9AGT0jFT26YNkp4C6FCSE+w/KtPfrv6C0E7A+OE1xLxjJs8HQ+AatkeljYVGAzw==
X-Received: by 2002:a17:902:d703:b0:149:db85:9b30 with SMTP id w3-20020a170902d70300b00149db859b30mr2231560ply.23.1641868166725; Mon, 10 Jan 2022 18:29:26 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:80b2:5c79:2266:e431? ([2406:e003:1071:1701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id d21sm8479216pfv.45.2022.01.10.18.29.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 Jan 2022 18:29:26 -0800 (PST)
To: Peter Saint-Andre <stpeter@stpeter.im>, Eric Rescorla <ekr@rtfm.com>, Eliot Lear <lear@lear.ch>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Russ Housley <housley@vigilsec.com>
References: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch> <C6C07861-A0EF-4C74-A5EC-A6D6ADD4F367@vigilsec.com> <4427b157-8ad9-9152-28ae-5db750932d66@lear.ch> <CABcZeBOXXVe8sMzUt8VtZBR2oOoSOdV--1J6_pvmdfGTt-j3RQ@mail.gmail.com> <1539b2df-ef80-ca11-fea8-e88cd60b142a@stpeter.im> <800bde92-f8ae-a622-c02a-8140d5b9a177@stpeter.im>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1b79ecb8-0fa7-a6e4-f0dd-0b4c1773edd8@gmail.com>
Date: Tue, 11 Jan 2022 15:29:22 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <800bde92-f8ae-a622-c02a-8140d5b9a177@stpeter.im>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/5rRkbZY7RkSe9OSgewIDEhKiwNI>
Subject: Re: [Rfced-future] Issue 151: Consultation / Approval for RSCE Selection committee
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2022 02:29:33 -0000

wfm, but I'd like to hear Jay's opinion.

Regards
    Brian

On 11-Jan-22 14:46, Peter Saint-Andre wrote:
> Proposed text for Section 5.1...
> 
> OLD
> 
>      The IETF LLC will form a selection committee, including members from
>      the community, that will be responsible for making a recommendation
>      to the IETF LLC for the RSCE role.  The selection committee will take
>      into account the definition of the role as well as any other
>      information that the committee deems necessary or helpful in making
>      its decision.  The IETF LLC is responsible for contracting or
>      employment of the RSCE.
> 
> NEW
> 
>      Responsibility for making a recommendation to the IETF LLC regarding
>      the RSCE role will lie with a selection committee.  The IETF LLC will
>      propose an initial slate of members for this committee, making sure
>      to include members from the community, and consult with the stream
>      representatives regarding the final membership of the committee.  In
>      making its recommendation for the role of RSCE, the selection
>      committee will take into account the definition of the role as well
>      as any other information that the committee deems necessary or
>      helpful in making its decision.  The IETF LLC is responsible for
>      contracting or employment of the RSCE.
> 
> On 1/10/22 6:36 PM, Peter Saint-Andre wrote:
>> +1
>>
>> On 1/10/22 1:26 PM, Eric Rescorla wrote:
>>> This seems fine to me.
>>>
>>> -Ekr
>>>
>>>
>>> On Mon, Jan 10, 2022 at 12:23 PM Eliot Lear <lear@lear.ch
>>> <mailto:lear@lear.ch>> wrote:
>>>
>>>      I'm beginning to see a rough consensus here.  
Are there other views?
>>>
>>>      Eliot
>>>
>>>      On 10.01.22 20:59, Russ Housley wrote:
>>>       > I agree with the suggest that Brian made about consulting with
>>>      the four stream managers.  It does not need to be a prolonged
>>>      consultation.
>>>       >
>>>       > Russ
>>>       >
>>>       >> On Jan 8, 2022, at 3:44 AM, Eliot Lear <lear@lear.ch
>>>      <mailto:lear@lear.ch>> wrote:
>>>       >>
>>>       >> Hi,
>>>       >>
>>>       >> I've opened a separate issue on the discussion that John Klensin
>>>      initiated regarding how the selection committee has formed.  At this
>>>      time, I would like to ask if others believe that there is a
>>>      concern.  If not, we will not make any changes.
>>>       >>
>>>       >> To review, John has proposed that the RSAB be consulted once the
>>>      ED has a proposed search committee.  I suggested that the
>>>      consultation could occur earlier.  Jay pointed out that any such
>>>      change would delay hiring of the RSCE and didn't think the change
>>>      was necessary, as he is consulting this group.
>>>       >>
>>>       >> One way forward might be that we put together a proposal in the
>>>      RSWG to address this point, so that we can get on 
with the hiring.
>>>      That would of course require rough consensus and approval.
>>>       >>
>>>       >> Another way forward might be that the text doesn't become
>>>      operative until after the RSWG and RSAB are formed.
>>>       >>
>>>       >> There may be other ways forward.  Please indicate your
>>> preference.
>>>       >>
>>>       >> Eliot
>>>       >>
>>>       >>
>>>       >>
>>>       >
>>>      --     Rfced-future mailing list
>>>      Rfced-future@iab.org <mailto:Rfced-future@iab.org>
>>>      https://www.iab.org/mailman/listinfo/rfced-future
>>>      <https://www.iab.org/mailman/listinfo/rfced-future>
>>>
>>>
>>
>