Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01
Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 09 February 2019 23:59 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id CC55E130FD6;
Sat, 9 Feb 2019 15:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.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=pass (1024-bit key)
header.d=cs.tcd.ie
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 C0y1UmKXGtgS; Sat, 9 Feb 2019 15:59:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 15A83130FCF;
Sat, 9 Feb 2019 15:59:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
by mercury.scss.tcd.ie (Postfix) with ESMTP id 44AFBBE38;
Sat, 9 Feb 2019 23:59:06 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1])
by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id nuTfH5wECcfW; Sat, 9 Feb 2019 23:59:04 +0000 (GMT)
Received: from [10.244.2.138]
(95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252])
by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0F93FBE2E;
Sat, 9 Feb 2019 23:59:04 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail;
t=1549756744; bh=CsD9JHb8uR11K2PTmgNyZhBM1k9ouqXJ2+qVScMuCro=;
h=Subject:To:Cc:References:From:Date:In-Reply-To:From;
b=mbzR66owOifNsqGBhQllD2bo1qziNtTSXS4YeYS01GgHJy2GzhE64K9DAa1LX512Y
pktQnA74cp6g7aTDwD/ApN4DZUeI5pClIfwTfoOMe/ZSNy3jScT6VzDuB7pHDLCZJi
z8lV58F2SkZQTRl3AradB9U+KeoF1Vl766uAAMC0=
To: Richard Barnes <rlb@ipv.sx>, Russ Housley <housley@vigilsec.com>
Cc: draft-ietf-iasa2-rfc4844-bis@ietf.org, IASA 2 WG <iasa20@ietf.org>,
Alissa Cooper <alissa@cooperw.in>
References: <32C06675-C60B-4D6A-979A-FC3653E56D42@cooperw.in>
<23C614C4-5C79-4355-9D74-2ED7D0DE63B2@vigilsec.com>
<CAL02cgTzEQPTXyPL-ermABDne2G8F8UjbPpYADkyxxWHnVVf4g@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=5BB5A6EA5765D2C5863CAE275AB2FAF17B172BEA; url=
Autocrypt: addr=stephen.farrell@cs.tcd.ie; prefer-encrypt=mutual; keydata=
mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh
5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+
QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKr
EMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZU
bUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqO
Vz+7L+WiVfxLbeVqBwV+4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJg
b097ZaNyuY1ETghVB5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k
4LyM2lp5FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK
7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5Xi
HzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQABtDJTdGVwaGVuIEZh
cnJlbGwgKDIwMTcpIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPokCQAQTAQgAKgIbAwUJ
CZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUCWj6jdwIZAQAKCRBasvrxexcr6o7QD/9m
x9DPJetmW794RXmNTrbTJ44zc/tJbcLdRBh0KBn9OW/EaAqjDmgNJeCMyJTKr1ywaps8HGUN
hLEVkc14NUpgi4/Zkrbi3DmTp25OHj6wXBS5qVMyVynTMEIjOfeFFyxG+48od+Xn7qg6LT7G
rHeNf+z/r0v9+8eZ1Ip63kshQDGhhpmRMKu4Ws9ZvTW2ACXkkTFaSGYJj3yIP4R6IgwBYGMz
DXFX6nS4LA1s3pcPNxOgrvCyb60AiJZTLcOk/rRrpZtXB1XQc23ZZmrlTkl2HaThL6w3YKdi
Ti1NbuMeOxZqtXcUshII45sANm4HuWNTiRh93Bn5bN6ddjgsaXEZBKUBuUaPBl7gQiQJcAlS
3MmGgVS4ZoX8+VaPGpXdQVFyBMRFlOKOC5XJESt7wY0RE2C8PFm+5eywSO/P1fkl9whkMgml
3OEuIQiP2ehRt/HVLMHkoM9CPQ7t6UwdrXrvX+vBZykav8x9U9M6KTgfsXytxUl6Vx5lPMLi
2/Jrsz6Mzh/IVZa3xjhq1OLFSI/tT2ji4FkJDQbO+yYUDhcuqfakDmtWLMxecZsY6O58A/95
8Qni6Xeq+Nh7zJ7wNcQOMoDGj+24di2TX1cKLzdDMWFaWzlNP5dB5VMwS9Wqj1Z6TzKjGjru
q8soqohwb2CK9B3wzFg0Bs1iBI+2RuFnxLkCDQRaPVAyARAA+g3R0HzGr/Dl34Y07XqGqzq5
SU0nXIu9u8Ynsxj7gR5qb3HgUWYEWrHW2jHOByXnvkffucf5yzwrsvw8Q8iI8CFHiTYHPpey
4yPVn6R0w/FOMcY70eTIu/k6EEFDlDbs09DtKcrsT9bmN0XoRxITlXwWTufYqUnmS+YkAuk+
TLCtUin7OdaS2uU6Ata3PLQSeM2ZsUQMmYmHPwB9rmf+q2I005AJ9Q1SPQ2KNg/8xOGxo13S
VuaSqYRQdpV93RuCOzg4vuXtR+gP0KQrus/P2ZCEPvU9cXF/2MIhXgOz207lv3iE2zGyNXld
/n8spvWk+0bH5Zqd9Wcba/rGcBhmX9NKKDARZqjkv/zVEP1X97w1HsNYeUFNcg2lk9zQKb4v
l1jx/Uz8ukzH2QNhU4R39dbF/4AwWuSVkGW6bTxHJqGs6YimbfdQqxTzmqFwz3JP0OtXX5q/
6D4pHwcmJwEiDNzsBLl6skPSQ0Xyq3pua/qAP8MVm+YxCxJQITqZ8qjDLzoe7s9X6FLLC/DA
L9kxl5saVSfDbuI3usH/emdtn0NA9/M7nfgih92zD92sl1yQXHT6BDa8xW1j+RU4P+E0wyd7
zgB2UeYgrp2IIcfG+xX2uFG5MJQ/nYfBoiALb0+dQHNHDtFnNGY3Oe8z1M9c5aDG3/s29QbJ
+w7hEKKo9YMAEQEAAYkCJQQYAQgADwUCWj1QMgIbDAUJCZQmAAAKCRBasvrxexcr6qwvD/9b
Rek3kfN8Q+jGrKl8qwY8HC5s4mhdDJZI/JP2FImf5J2+d5/e8UJ4fcsT79E0/FqX3Z9wZr6h
sofPqLh1/YzDsYkZDHTYSGrlWGP/I5kXwUmFnBZHzM3WGrL3S7ZmCYMdudhykxXXjq7M6Do1
oxM8JofrXGtwBTLv5wfvvygJouVCVe87Ge7mCeY5vey1eUi4zSSF1zPpR6gg64w2g4TXM5qt
SwkZVOv1g475LsGlYWRuJV8TA67yp1zJI7HkNqCo8KyHX0DPOh9c+Sd9ZX4aqKfqH9HIpnCL
AYEgj7vofeix7gM3kQQmwynqq32bQGQBrKJEYp2vfeO30VsVx4dzuuiC5lyjUccVmw5D72J0
FlGrfEm0kw6D1qwyBg0SAMqamKN6XDdjhNAtXIaoA2UMZK/vZGGUKbqTgDdk0fnzOyb2zvXK
CiPFKqIPAqKaDHg0JHdGI3KpQdRNLLzgx083EqEc6IAwWA6jSz+6lZDV6XDgF0lYqAYIkg3+
6OUXUv6plMlwSHquiOc/MQXHfgUP5//Ra5JuiuyCj954FD+MBKIj8eWROfnzyEnBplVHGSDI
ZLzL3pvV14dcsoajdeIH45i8DxnVm64BvEFHtLNlnliMrLOrk4shfmWyUqNlzilXN2BTFVFH
4MrnagFdcFnWYp1JPh96ZKjiqBwMv/H0kw==
Message-ID: <a0a2ef94-335f-5ab6-e49c-7b1c985af3fc@cs.tcd.ie>
Date: Sat, 9 Feb 2019 23:59:03 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <CAL02cgTzEQPTXyPL-ermABDne2G8F8UjbPpYADkyxxWHnVVf4g@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature";
boundary="8qL0iLdjOm9SbQnvafHHGIfn5jlRLjfpI"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/IpaRobwSVyxfl3hH8fjH-fYDmkE>
Subject: Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?=
<iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>,
<mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>,
<mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2019 23:59:14 -0000
On 09/02/2019 23:48, Richard Barnes wrote: > On Sat, Feb 9, 2019 at 1:44 PM Russ Housley <housley@vigilsec.com> wrote: > >> Alissa: >> >> I think we want the hiring/firing of the RFC Series Editor to stay with >> the IAB, but the funding to stay with IASA. >> > > This is not a reasonable thing to ask. I'm way behind in being up to speed on this wg's stuff, so I may be off base here, but I reckon I strongly agree with Russ. The IAB are picked by the community and ought be the ones to hire a new RSE if one is needed. With no disrespect meant to trades-persons, I'd be fine with the hiring of electricians being handled internal to IASA; but not an RSE - the context here means those are utterly different. Cheers, S. PS: I'd have said the above even were I not an incoming IAB member and hope not to be involved in picking a new RSE whilst on the IAB:-) > One of the key driving factors for > this whole endeavor it makes no legal sense for an organization to delegate > its hiring / firing / contracting decisions to people external to that > organization. > > By all means, the IASA should work with the IAB on the RSE, but since the > IASA is ultimately the responsible party, it can't totally cede > responsibility. The "operational oversight" text that's in there now seems > like it captures this accurately. > > > >> The decision whether the ED serves on the ROC should not be determined by >> this document. If the IAB wants the ED to be part of RSOC, they can make >> that appointment. >> >> Perhaps it would be best to make this change: >> >> OLD: >> >> The IASA is tasked with providing the funding for and operational >> oversight of the RFC Editor. >> >> NEW: >> >> The IASA is tasked with providing the funding for the RFC Editor. >> The IETF Executive Director is tasked with overnight of contracts >> and operational agreements related to the RFC Editor. >> > > I don't see how this accomplishes what you claim above. The IETF ED is > part of the IASA. And especially given that, the second sentence here is > really just micromanagement of the LLC. > > --Richard > > > >> >> Russ >> >> On Feb 8, 2019, at 8:11 PM, Alissa Cooper <alissa@cooperw.in> wrote: >> >> Earlier this week the IAB discussed whether to >> put draft-ietf-iasa2-rfc4844-bis-01 out for community review. In reviewing >> it I felt there were some clarifications needed before it would be ready >> and the IAB thought the most appropriate path would be to bring those to >> the WG for resolution first. >> >> I haven’t started my AD review of 4071bis yet (hope to next week), but I >> think 4071bis has a problem in that the definition of “IASA” in that >> document is broken (it refers to the definition in 4071, which it itself is >> obsoleting). And until it is clear how we are defining “IASA,” I have >> trouble with statements such as the following from Section 3.3 in 4844bis: >> >> "The IASA is tasked with providing the funding for and operational oversight >> of the RFC Editor.” >> >> Is the RSOC part of IASA? It’s pretty hard to tell without a good >> definition of IASA, which we do not currently have IMO. (I think there is a >> further problem with the sentence above, which is that the funding comes >> from the LLC, and it would be better to be that specific.) >> >> While looking at Section 3.3, I don’t think this text belongs there since >> this document is about the RFC series and editor, not IASA generally: >> >> "The IETF LLC Board provides oversight of the IASA, and the IETF Executive >> Director is the chief actor for the IASA.” >> >> I also find lack of clarity between 4844bis Section 3 and 6635bis Section >> 3. For example, 4844bis says: >> >> "The IETF Executive Director works with the IAB to identify suitable persons >> or entities to fulfill the mandate of the RFC Editor.” >> >> While 6635bis says: >> >> "For all decisions that affect the RSE individually (e.g., hiring and firing), >> the RSOC prepares recommendations for the IAB, but the final decision is >> the responsibility of the IAB.” >> >> But under the current model (which I presume we plan to keep), the ED is a >> member of the RSOC. So does the ED work directly with the IAB? Or >> indirectly with the IAB through the RSOC? Or both? >> >> 4844bis also says: >> >> "The IETF Executive Director may define additional operational >> requirements and policies for management purposes to meet the >> requirements defined by the various communities.” >> >> I wonder if this is really consistent with what is envisioned in 6635bis. >> >> I also find it odd that the budget for an RSE search is discussed in >> 6635bis, while the budget for the RFC Editor function overall is discussed >> in 4844bis — is the separation meaningful? Since the LLC Board approves the >> whole IETF budget, presumably what 4844bis says about the RFC Editor budget >> applies to the search budget mentioned in 6635bis as well, but since it’s >> not explicit it isn’t totally clear. >> >> Thanks, >> Alissa >> >> >> >> _______________________________________________ >> iasa20 mailing list >> iasa20@ietf.org >> https://www.ietf.org/mailman/listinfo/iasa20 >> > > > _______________________________________________ > iasa20 mailing list > iasa20@ietf.org > https://www.ietf.org/mailman/listinfo/iasa20 >
- [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis… Alissa Cooper
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Joseph Lorenzo Hall
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Joel M. Halpern
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Russ Housley
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Richard Barnes
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Stephen Farrell
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Richard Barnes
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Bob Hinden
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Joel M. Halpern
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Adrian Farrel
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Richard Barnes
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Joel M. Halpern
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Richard Barnes
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Stephen Farrell
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Brian E Carpenter
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Bob Hinden
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Eliot Lear
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Abdussalam Baryun
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Michael Richardson
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Richard Barnes
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Joel M. Halpern
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Brian E Carpenter
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Eliot Lear
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Alissa Cooper
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Joel M. Halpern
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Leslie Daigle
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Robert Sparks
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Alissa Cooper
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Leslie Daigle
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… John C Klensin
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… John Levine
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Richard Barnes
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Alissa Cooper
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Leslie Daigle
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Russ Housley