Re: IAB report to the community

Ted Hardie <iab-chair@iab.org> Mon, 18 November 2019 02:39 UTC

Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E6C1208FB; Sun, 17 Nov 2019 18:39:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
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 GrHGM0Nsxt-h; Sun, 17 Nov 2019 18:38:58 -0800 (PST)
Received: from hardie-macbookpro.roam.corp.google.com (dhcp-824e.meeting.ietf.org [31.133.130.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 787FC1208CB; Sun, 17 Nov 2019 18:38:57 -0800 (PST)
Subject: Re: IAB report to the community
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, iab@iab.org, ietf@ietf.org, "execd@iab.org" <execd@iab.org>
References: <7f516417-415b-367c-f8c5-a508942c034b@iab.org> <d180f25a-ad72-83b8-0f1e-cb4dc54d4a6b@gmail.com>
From: Ted Hardie <iab-chair@iab.org>
Message-ID: <53ea834a-1b72-08d7-0c13-24e9d55efcf8@iab.org>
Date: Mon, 18 Nov 2019 10:38:55 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <d180f25a-ad72-83b8-0f1e-cb4dc54d4a6b@gmail.com>
Content-Type: multipart/alternative; boundary="------------D3AE26D6C9CA377DDAA8F412"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OWz4TAiNOe7YeY30_3rumLmzCJU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 02:39:02 -0000

Hi Brian,

Thanks for the review.

On 11/18/19 9:01 AM, Brian E Carpenter wrote:
> Thanks for the report, Ted. However I do want to raise one issue. You say:...
>> The IAB has a few chartered roles. It ... appoints the RFC series editor and oversight committee,...
> Actually the charter (RFC850, BCP39) does not say that. What it says is:
>
> "The IAB must approve the appointment of an organization to
> act as RFC Editor and the general policy followed by the RFC Editor."

I'm happy to take a PR for future iterations of the report.  RFC 2850 is 
the charter and has the text you cite.  At the moment, the mechanisms by 
which it is carried out is in RFC 6635, Section 2.1, which says:

    The RSE is appointed by the IAB, but formally hired by the IAOC.  The
    IAB delegates the direct oversight over the RSE to the RSOC, which it
    appoints.

The reference to the IAOC is changed in 
https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/, which is 
currently in the RFC Editor's queue.

All of this may change as the result of the ongoing community 
discussions, but if you have a pithy way of summarizing all of that that 
we can use until it does change, as I said, I'd be happy to have it to hand.

regards,

Ted Hardie

> I think that at the moment it's important to distinguish what is formally
> chartered by BCP from what is current practice.
>
> Regards
>     Brian Carpenter
>
>