IETF Logo Mail Archive

Re: IAB report to the community

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 22 November 2019 00:06 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 187F2120219 for <ietf@ietfa.amsl.com>; Thu, 21 Nov 2019 16:06:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 qSBUZwyVnPtD for <ietf@ietfa.amsl.com>; Thu, 21 Nov 2019 16:06:41 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 8CE8F120091 for <ietf@ietf.org>; Thu, 21 Nov 2019 16:06:41 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id b1so2443419pgq.10 for <ietf@ietf.org>; Thu, 21 Nov 2019 16:06:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Xm0t8/9wVaOAhClBvVCxJq8W9ruDt9lspMBe7YgQaSg=; b=h42x+EY1F6uPH4hrOczSPIJT4A0eeDe5m58v2kbQSSfbT0VR0/HkgFERkXdWvhme0j 0XzyKOyPlPiG0rIKStRcbHY1V5cSkAnzHANfbEGkObjIy2wGXZD//QGhai+xT/sER0dE 55CJ9sjdGCpOBC+VyT8Wjg0d6ocT3uKa0Sil8M/BfaMPLMHT1gtgtnVuIKwh91rDB+Fq Cw1M543OhDHTYgsOtgimIglc38xmijya8h5QWoIy7LtQUFju6uOm89AQVg0P32roUsEa ytScUXGAXUe1mFM688TbprynZhSnbMoK25Vu4G9LSg/1Cs/LsPHzZGTyAafI0YBz4hpk Xtaw==
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:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Xm0t8/9wVaOAhClBvVCxJq8W9ruDt9lspMBe7YgQaSg=; b=FMaD+JW7vSTDcrJNgQkpOJy6yxDiFm8eT+tzEk/uHwUQJ2HFbdSdkR3PwROJDpVIcw CznF1wy2H86IaUXXXLpih17DIVHTlmMhbRWPzpDjqzHrR1ws2bcdn3dP4fm0KMZrwObT EAWwT+V9umu55tGEL62WMDwvQ9RDZOuazO+wNFpUMPtJrfLW4gOOmlzl49WDgn6VOrK3 KZJYOzsiUFQZxazsYXity120xwqI0O4PCJKT6ByGvaFTKZXQlH2h1AMGC/g0T127A7n6 M4JSEJQhot6jB9HvhdjDN2oJpqmJJbzHwu3GGMitmQf1CXW8PGh+VtrafGnkAAe95PXq pHQQ==
X-Gm-Message-State: APjAAAVhT7ML2U0Fh2RkSBJTSsgCVNg8xWq8Q0+FwgewZ6uX7ln4W8TW 6w9XoKa56GZnKfYxKTiFGs5rz3yr
X-Google-Smtp-Source: APXvYqzzBbRe2KXfEbacWQVUCq2yT52rpFSgAPj5XYHI6xFQl5E3A0H5ocqUFhpe4o2GgKYhAVE1Lw==
X-Received: by 2002:a63:1916:: with SMTP id z22mr6530741pgl.206.1574381201018; Thu, 21 Nov 2019 16:06:41 -0800 (PST)
Received: from [31.133.151.10] (dhcp-970a.meeting.ietf.org. [31.133.151.10]) by smtp.gmail.com with ESMTPSA id a16sm4129191pgb.7.2019.11.21.16.06.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Nov 2019 16:06:40 -0800 (PST)
Subject: Re: IAB report to the community
To: Ted Hardie <iab-chair@iab.org>, 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> <53ea834a-1b72-08d7-0c13-24e9d55efcf8@iab.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a97632e2-286d-1f61-80d3-20fbcef939ab@gmail.com>
Date: Fri, 22 Nov 2019 13:06:37 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <53ea834a-1b72-08d7-0c13-24e9d55efcf8@iab.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BVov91vtclhSQMJvdgsspptPlt4>
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: Fri, 22 Nov 2019 00:06:43 -0000

Hi Ted,

On 18-Nov-19 15:38, Ted Hardie wrote:
> 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.

I've mulled it over, and I think that wordsmithing this before the RSEME discussion has advanced somewhat would be rather pointless. I will file this away for now, but perhaps come back to it before IETF 107.

Regards
    Brian

> 
> 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
>>
>>

v2.23.0 | Report a Bug | By Email