IETF Logo Mail Archive

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

Peter Saint-Andre <stpeter@mozilla.com> Fri, 25 June 2021 19:38 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 292703A0AFD for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 12:38:05 -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 lYI0S-bT3ZWO for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 12:38:02 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 BC60B3A0AF7 for <rfced-future@iab.org>; Fri, 25 Jun 2021 12:38:02 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id k11so13849351ioa.5 for <rfced-future@iab.org>; Fri, 25 Jun 2021 12:38:02 -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=P6ssUX8kPmVfMVbUef0OKEXJrMb0pFiHhpM0raT0WGs=; b=JHbp/oz5H8BW+EGG2EH1N+FzYfUwmsyoraZmuYlxkde7HpOrR5eIgzU7+fmiNZxzzr cwOt5+/g8aem4rJjo0AeMYje/BjwVnWbNgXJW8xnqPp62DhygHM7ei2a4TN4zTjtAwo/ EofcylRabpzlsg+Xp4OH/sPsrYLIvIfRtIdMQ=
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=P6ssUX8kPmVfMVbUef0OKEXJrMb0pFiHhpM0raT0WGs=; b=eKj8a3MbWR6CI4khMOhCWZkN3pNFxxT43LmFkPH1Wabwg7dGJw0/2sg6XQF3OFZql4 0lkO/UTCHF9Qx0I73WhySvJhy4Cy3ZmIyVn4PvWFAYq3CUbh7O87h+0wvPQTAXa6pwxT U3cxs2ALjzAgSEwWbtTbrJOhEs27YJjPfI+U5s9ZEbe0O2616KIkwEMzSL/20pxLle9P 5C75a1jO1iZy6xvyxTNxaz7WAMGan3M2Q7H3GuFvmwLOl3dv3i5PdWegj6HzyuHxwbYz T1PPOyR/jfjgQ/mGgSl+ZON+JfZ5VWLNSzU0sE7/jfmW+ZgXxawTxNZXXlxT+flyrkan yOtg==
X-Gm-Message-State: AOAM5325vRcXmbMpQe5hI9VeNKuxMZr2hWUrCrs4m3RavZ84ry8oQ871 GL8p8UxQnMURSipg/TUM8iJblw==
X-Google-Smtp-Source: ABdhPJz4fh5LGBZrrSCJF/uC2mrYRBv3fg+p2fC9owmqgZI7mGakSqNAWtUIOj/kKZMhLDhw5yINrg==
X-Received: by 2002:a6b:c305:: with SMTP id t5mr10181367iof.202.1624649881194; Fri, 25 Jun 2021 12:38:01 -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 f7sm4008434ilk.50.2021.06.25.12.38.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Jun 2021 12:38:00 -0700 (PDT)
To: Eliot Lear <lear@lear.ch>, adrian@olddog.co.uk
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> <0b9a01d76816$25690dd0$703b2970$@olddog.co.uk> <b86198ce-ecd6-1452-88cc-4d2a7449e1d1@lear.ch>
From: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <5113d732-2791-686a-3a46-66f81d5ea2a9@mozilla.com>
Date: Fri, 25 Jun 2021 13:37:59 -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: <b86198ce-ecd6-1452-88cc-4d2a7449e1d1@lear.ch>
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/hPiO5bnuj4EKnvNeh6dJspIOVyk>
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 19:38:05 -0000

On 6/23/21 4:07 AM, Eliot Lear wrote:
> Hi Adrian,
> 
> On 23.06.21 11:57, Adrian Farrel wrote:
>> Suppose a new stream published something that impeded in some way IETF
>> work? I'm sure it is not our intent to open up a channel for end runs
>> or subversion
> 
> Assuming that the stream is exclusively for use for documents that are
> approved via the process we are now defining, then the ultimate step is
> for the RSAB to approve the document.  As part of that process, other
> stream manager representatives get a shot at raising CONCERNs.  In a
> sense, therefore, a check is built in. Indeed the document already says
> the following:
> 
>>    Notices will always be sent to the rfc-interest mailing list.  The
>>    RSAB and RSWG should also send notices to other communities that may
>>    be interested in or impacted by a proposal as they see fit, following
>>    policies for those fora as appropriate.
> 
> And so this allows each stream to apply whatever conflict resolution
> process they would choose in order to determine whether a CONCERN should
> be raised.

Good point. That seems to cover it.

Peter

v2.23.0 | Report a Bug | By Email