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

Peter Saint-Andre <stpeter@mozilla.com> Fri, 25 June 2021 20:55 UTC

Return-Path: <stpeter@mozilla.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 BDF593A03FB for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 13:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 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, 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 (1024-bit key) header.d=mozilla.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 Z_UnbGyfcjuy for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 13:55:11 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 CFE093A0400 for <rfced-future@iab.org>; Fri, 25 Jun 2021 13:55:11 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id h2so14062567iob.11 for <rfced-future@iab.org>; Fri, 25 Jun 2021 13:55:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=lC/WA7L5OXi9HarzqIGIY/mQZuMaOohcQ6jW9XOaGkY=; b=H0Dntzxm2ls0acqp0Lqvdl6jWnWiyNgGBJr0GXCRepIcjWSuYA3M0He4ueZXwjnHN2 5VnFAV0mOO8d5Nm0Pz+1+hcjtckuceX3va2dIOdTvuVEwCyavMjDZFu0OieHwIvtlZ1l gD7ZsYHXYJyQX/TDzH8nMBwe/MO80E3fDPbBk=
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=lC/WA7L5OXi9HarzqIGIY/mQZuMaOohcQ6jW9XOaGkY=; b=GcCRPZok7pDlRnDwfuMhem72gxk71ds/vXI2oOY0O3G+69g8OWN3srY+G0CqNzzR91 xyZ8WrVqX3N0qCVa5lsq/8kCv+kPK7WhgSqjuI/oAPAOhuA07Y7oyFMCPnj7WMqD4Hwx //wosKaOpeGg0Kr7wCZBrbDlF8kcN9veW/I5EOCerJ/TeuIlaMh2t1A4BF7NI+dvzjyr tLqTUDdWpLtuRyigUM0kc0NClSzHeknhLVlw7dW3MUXSRwVR0T5L64li+N0QVHsuTv6P gjResEMFa26js+F38n08sn9UMjXXJKZLJlpJvF4qBQtrfMP0r2joktTQqkYnW+1y2tzo UkDw==
X-Gm-Message-State: AOAM532hBhA+3goIsAcuzbfWJx097oQikmKHo34QkAhUwh78CtQXe59v ssKQhiZbdOzoE9ms0E4NlaFUvQ==
X-Google-Smtp-Source: ABdhPJwJTQcd17N6J+5CZldru4KM2x8FLtu8evnaoHSk0N3vRD7ThiB3O6oOdyZNIXsezNmJEbmoMg==
X-Received: by 2002:a05:6638:13c3:: with SMTP id i3mr11111873jaj.140.1624654508823; Fri, 25 Jun 2021 13:55:08 -0700 (PDT)
Received: from dragon.local (c-73-78-113-156.hsd1.co.comcast.net. [73.78.113.156]) by smtp.gmail.com with ESMTPSA id e2sm3934240iot.50.2021.06.25.13.55.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Jun 2021 13:55:08 -0700 (PDT)
To: "Joel M. Halpern" <jmh@joelhalpern.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>
From: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <55602726-93b9-d03c-447c-9d4b9ede5397@mozilla.com>
Date: Fri, 25 Jun 2021 14:55:07 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <faf54e3b-5c3c-4a97-f364-47c14c251eed@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/kw5oMifMsxAM-Oax73kQ1EBz4sw>
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 20:55:15 -0000

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. ;-)

> 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