Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 25 June 2021 21:42 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 444843A0A4C for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 14:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 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.338, SPF_HELO_NONE=0.001, SPF_PASS=-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 XjjPrbm-3y2c for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 14:42:54 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 ECF4B3A0A20 for <rfced-future@iab.org>; Fri, 25 Jun 2021 14:42:53 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id s14so7222649pfg.0 for <rfced-future@iab.org>; Fri, 25 Jun 2021 14:42:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=R05TgeH9smraJuAd8zGdKL0QX6jgSY0DVTzMx8BrwqA=; b=sBKLQ9ySO5FDQXQRS0BFSP7N3WVWhR9g6qKHEZEQjNNyY3rebpAlaz+GUySKza4SOg rnD9r8ve0Px8HtG3UssJGwAH8QYCR6yZwYfCWI8+TeYTpYIKPkTEiJolJtUFed1j0ZI8 YJ4Pe9to/X4hPgmh2usUyV3ohP4xVHJNU4AN2rRVkfKRcMHNNA23o5PjYtEysShsOmrv 8ot3MHE2JG3+64ijCl19bxmfp8dG3EmTAfKAJSnYh55E3C3FfZBaNk0FA2XUaOX2JRQm gwA3bT3oBGZb6NIzJY/l8hcVs056UZsBpcU1mzvUMQyrWnDOyAQuRrTz8H9ZpgW4SyVa WGRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; 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=R05TgeH9smraJuAd8zGdKL0QX6jgSY0DVTzMx8BrwqA=; b=Y1LFODganNWKAEafpMcWQ7VE6FV9Yg1kXtIKbe0iVHCXgPesGN4MkpkQSKOouSjmNh WWgwB3B4D4UWzVX0EyWqBAmuXjpZpd0EPa3wphfizTj1muUapyEvCvQvEJstMbtrqB2F fkfvUCAoGAxC2urct1nXWxMgiziFn/yFpIZmNsz1pStxaFSTkQFHYwZIq6A+2fGIgpKd ki564K1L651mFc+2QtKfkO3bk4n7t7K/AYwVW9FTJmsT+7E4aTCGZSiKL0M+GzEeJUey F+xLj4XI/J1b9eF5uAqiwPKocKrg3vI1IAY66+nSl3D+B9ZUNzY3sDlc9tV5oRPTK7D8 RIYw==
X-Gm-Message-State: AOAM533W2/KgMtjhXBYcV4jD1w2TjHoAwIrnUZ8DmMg4IfLHujIv49vp wN15bma9bKJ9bCDFj4VF5361qOtIh62Keg==
X-Google-Smtp-Source: ABdhPJyJAc1oPfynUvcEeIopSN2zCdCjIqY716gMrwgMmcNrWAQeGTUclKOBKjSzyr0UZiD9DEkwFA==
X-Received: by 2002:a05:6a00:1742:b029:308:add4:e844 with SMTP id j2-20020a056a001742b0290308add4e844mr8509037pfc.18.1624657372578; Fri, 25 Jun 2021 14:42:52 -0700 (PDT)
Received: from ?IPv6:2406:e003:100d:901:db7:d041:a2d:ce65? ([2406:e003:100d:901:db7:d041:a2d:ce65]) by smtp.gmail.com with ESMTPSA id r134sm7135367pfc.68.2021.06.25.14.42.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Jun 2021 14:42:52 -0700 (PDT)
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>, Peter Saint-Andre <stpeter@mozilla.com>
Cc: rfced-future@iab.org
References: <3f4c264e-4639-4d6b-cf22-0a2be503decc@joelhalpern.com> <3D3EC062-7B1A-43C4-99D5-A204A4565ECE@ietf.org> <cf2921d8-fd1f-d9c9-da72-ff760eda347c@lear.ch> <3b4b6d91-64e3-d0d7-bcbc-284f29a46fb7@joelhalpern.com> <2d926822-5c68-2279-b197-836534f3c030@mozilla.com> <faf54e3b-5c3c-4a97-f364-47c14c251eed@joelhalpern.com> <55602726-93b9-d03c-447c-9d4b9ede5397@mozilla.com> <34f4e8eb-3c81-6cb0-5cf1-ee3ab3b6cc5f@gmail.com> <d9d7116f-1603-4c5c-116a-176659aa418f@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <708a0477-2df9-d36c-61ba-27c2e0d2f2b7@gmail.com>
Date: Sat, 26 Jun 2021 09:42:47 +1200
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: <d9d7116f-1603-4c5c-116a-176659aa418f@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/lCw72nphL9aB-PitMyV0FNgPkgM>
Subject: Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
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: Fri, 25 Jun 2021 21:42:56 -0000

Yes, you're correct; so the IESG and IRSG should each pick
a regular participant, but presumably a deputy could attend
if necessary. 

Regards
   Brian

On 26-Jun-21 09:29, Joel Halpern Direct wrote:
> If those are the stream managers, then we need a different description 
> for the makeup of the RSAB.  It would be rather odd if the IESG sent 
> different people at different times to the RSAB activities.  Presumably 

> we hope for some limited degree of continuity.
> 
> Yours,
> Joel
> 
> On 6/25/2021 5:26 PM, Brian E Carpenter wrote:
>> On 26-Jun-21 08:55, Peter Saint-Andre wrote:
>>> On 6/25/21 2:52 PM, Joel M. Halpern wrote:
>>>> Hmm.  That does not seem to match reality.
>>>
>>> Well, then we should align documentation with reality. ;-)
>>
>> How about
>>
>>    the IESG (represented by any AD) and the IRSG (normally represented 
by the IRTF Chair)
>>
>>       Brian
>>
>>>
>>>> The IESG and IRSG do not
>>>> attend the stream managers meetings.  From everything I have ever
>> been
>>>> told about, the IRTF chair and the IETF chair have historically attended
>>>> those meetings.  And made practical decisions.  (I am sure 
that for
>>>> major items the IETF Chair checks with the IESG.  The IRSG serves
>> at the
>>>> pleasure of the IRTF chair, so whether he (the IRTF Chair) checks with
>>>> them is presumably up to him.)
>>>
>>> Right.
>>>
>>> Peter
>>>
>>