Re: [rfc-i] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 11 September 2019 02:04 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 42AB2120838 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 10 Sep 2019 19:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.996
X-Spam-Level:
X-Spam-Status: No, score=-4.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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=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 xZx_eerZQWhK for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 10 Sep 2019 19:04:55 -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 27309120088 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 10 Sep 2019 19:04:55 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 24598B80F77; Tue, 10 Sep 2019 19:04:52 -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 98436B80F77 for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 19:04:50 -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=gmail.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 WgHuE_b2JQdM for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 19:04:49 -0700 (PDT)
Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) by rfc-editor.org (Postfix) with ESMTPS id 1F7F0B80F6B for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 19:04:49 -0700 (PDT)
Received: by mail-pg1-x544.google.com with SMTP id n9so10703992pgc.1 for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 19:04:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=l00ETzA9TeQycUvFHX1UL7u6VIy6ZJkxCLHJhygPr8o=; b=E+V8poLMCY5q7kI8KqU9ZZHP25Z3MTdKgSRINJvhT0L0CBR8tUn8IxpIylke6yCXN0 piMZiNsriOhRuzrrA0vY/Vts1NKhUe8A5OMoAqDjRF6Jrp8NUHa2dTIF0RsL0PWatwfj TOP7CUdqND36wK+TqJnZ+cHa0mR7Yz+EWWExTTZeMqyD7YhI9F363SUF5PJdsd5T0gOb jASE5i4sbbogSzqsKr056uWqImcZ7u3TBHIHp+jcla7V29hvEVvCKF0mCVlwLyvCk96j X2QKD8mHt2oRBy/5UWvfftqt1keTAfF10GasHzbu4lh26rAOF7usF3pQru3tqqWJOwbC YPlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=l00ETzA9TeQycUvFHX1UL7u6VIy6ZJkxCLHJhygPr8o=; b=rUGUZPccVEpCI/6idM8ZHe8DyROBKtp0NmO2I+yUPfkVtyye8utlWdqykeR9h5+Wx5 GRWHmJ2pM+33O7N+spaO6AFhWOTMhd6doB17ngBMsrJrVBqnYq/dE44yZlr7RBHhoFrE Wp9QsZcXDucQZ1yeR5MukX9ehwxj3TgKxidRiL/yFUJx7kFyro+PEWoRaBT1ynTkapyh nPC9/JV/3s6m9rXzYCiqFtu3UNK9KFXtcZiDEF3J0zuywGQgFlffqqFXdayRNllYy8No HEp9bEwQgQHsnGG6JLgx2ouYXkXe8ELB1nuRDIS4j3rlbGFqp4du79Y7b5JkJVYh7Fpu nf7w==
X-Gm-Message-State: APjAAAVfpSUIi0LgGbb7Bp1BwRtf3qUsgMxaczJgJbbkC2Ssv9GwzLr5 0PbmZyZTf2ttLdXJqiRcPblIKs+z
X-Google-Smtp-Source: APXvYqxqliX+JsbZo+o5vMSOEuYydpAlWofczciKLkGMutr9Y1j96hYpRsNddGJ4OXPOEhINGfFxQw==
X-Received: by 2002:a17:90a:9749:: with SMTP id i9mr2843476pjw.42.1568167490839; Tue, 10 Sep 2019 19:04:50 -0700 (PDT)
Received: from [192.168.178.30] (82.206.69.111.dynamic.snap.net.nz. [111.69.206.82]) by smtp.gmail.com with ESMTPSA id l124sm18412928pgl.54.2019.09.10.19.04.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Sep 2019 19:04:50 -0700 (PDT)
To: architecture-discuss@ietf.org, iab@iab.org
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20e11a4f-26d6-24e3-f82e-b3a2bc8d1eec@gmail.com>
Date: Wed, 11 Sep 2019 14:04:46 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com>
Content-Language: en-US
Subject: Re: [rfc-i] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hi,

I believe this draft does represent the consensus of the IASA2 WG and cleans up some loose ends from the IAOC to IETF LLC transition. However, I believe that it should not be published as an RFC. The discussions that will soon start about the future of the RFC Editor model make that rather pointless.

Regards
   Brian Carpenter

On 05-Sep-19 08:59, IAB Executive Administrative Manager wrote:
> This is an announcement of an IETF-wide Call for Comment on 
> draft-ietf-iasa2-rfc6635bis-03.
> 
> The document is being considered for publication as an Informational RFC 
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
> 
> The Call for Comment will last until 2019-10-02. Please send comments to
> architecture-discuss@ietf.org and iab@iab.org.
> 
> Abstract
> 
>    The RFC Editor model described in this document divides the
>    responsibilities for the RFC Series into three functions: the RFC
>    Series Editor, the RFC Production Center, and the RFC Publisher.
>    Internet Architecture Board (IAB) oversight via the RFC Series
>    Oversight Committee (RSOC) is described, as is the relationship
>    between the IETF Administration Limited Liability Company and the
>    RSOC.  This document reflects the experience gained with "RFC Editor
>    Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 to
>    replace all references to the IASA and related structures with those
>    defined by the IASA 2.0 Model.
> 
>    [RFC Editor: Please remove the following paragraph prior to
>    publication.]
> 
>    The IASA2 WG requests that the IAB publish this replacement for RFC
>    6635.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest