Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01
Bob Hinden <bob.hinden@gmail.com> Sun, 10 February 2019 00:58 UTC
Return-Path: <bob.hinden@gmail.com>
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 6637E124BAA; Sat, 9 Feb 2019 16:58:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_PASS=-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 ACGml3_ZtXsU; Sat, 9 Feb 2019 16:58:00 -0800 (PST)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 315F9129A87; Sat, 9 Feb 2019 16:58:00 -0800 (PST)
Received: by mail-wm1-x333.google.com with SMTP id q21so10084882wmc.5; Sat, 09 Feb 2019 16:58:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Kuo+YDDnlkSQItNDwAO/PA3Z/hCkmF5b2ezk3KlabRk=; b=QBAa5fJBDuXEtWirmQdmxUTFQdQP8E+xtWpIwEVOTS+AtWVnqnWCx70Zq71+n+s+tR pWSV3WNT11d0DxdzRtjl0zKwFJWRCR8ETGZE6XEkjz4mYl9ROSYfB5F0foQxz5Ix4KGr FR4RwDA1GLpZfnHX0D8X668/E3aUarHl1INDsmx+nbazwY+tx7Bo36d9CAcnqAsWYNbk hvrDJAR7JyUu4pH2g0ysziSQDkXH1pzDvcagifTd7//GDUEii8cusujfxf+cZYiOfJDt +vjH5SaPmPcTB8NoPZN8/FPqxWWgNZgZCpIyIq0SOmYDqLdzZx9O4GGrywvK18UWV/Dk kw9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Kuo+YDDnlkSQItNDwAO/PA3Z/hCkmF5b2ezk3KlabRk=; b=WK0gECGy9pRxGlMrlUAsd1IUQMI9vD8XRK587EevbEgNIDH3Rh1xQNRXOkF1GwdYRe ml3xT4zGAGR8frCGMNlkmafm0KRwyt1DluEGzvXq8DIIJCm4t30JU2/WCMTYCheZ9/+E pcDYH5txOqptAGOCDfKE+shRFPMT4YuCpm+zjVEsPhTDZihvUYmqK5k77jnc9RcNlZGM 6OCAlRK54/kWfGFCWJ+ZZQZfAKyOGtGTdgAaTroxinfF7X8U0NqvFAPrcXavcGKZ/VEt hUC960MfXnN9qHG4GdyidfynjIMTk+SZ3icrGAyN0wZkSpOdMIzjQEkoFvlD8Ke7/ghx XqRg==
X-Gm-Message-State: AHQUAuZuOplf9UnDv2xSLtoej3DQCL1IVeq6ppcpxh2wJfNqFczP0TOn EuXUq8jX0GxbYMLsj86tC98=
X-Google-Smtp-Source: AHgI3IbmryEjr/IWx69YEmGBME2pt2WpjheWgLilpXgdSDLD0/daz/1Lj20cV5xrmrll/4uz7aw39w==
X-Received: by 2002:a7b:c8c9:: with SMTP id f9mr299474wml.85.1549760278422; Sat, 09 Feb 2019 16:57:58 -0800 (PST)
Received: from [10.20.1.235] ([199.72.76.18]) by smtp.gmail.com with ESMTPSA id a12sm11942303wro.18.2019.02.09.16.57.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Feb 2019 16:57:57 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <a0a2ef94-335f-5ab6-e49c-7b1c985af3fc@cs.tcd.ie>
Date: Sat, 09 Feb 2019 16:57:53 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, Richard Barnes <rlb@ipv.sx>, Russ Housley <housley@vigilsec.com>, draft-ietf-iasa2-rfc4844-bis@ietf.org, IASA 2 WG <iasa20@ietf.org>, Alissa Cooper <alissa@cooperw.in>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBDCD74C-2AE8-4A58-9551-5613CEC4EC44@gmail.com>
References: <32C06675-C60B-4D6A-979A-FC3653E56D42@cooperw.in> <23C614C4-5C79-4355-9D74-2ED7D0DE63B2@vigilsec.com> <CAL02cgTzEQPTXyPL-ermABDne2G8F8UjbPpYADkyxxWHnVVf4g@mail.gmail.com> <a0a2ef94-335f-5ab6-e49c-7b1c985af3fc@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/ayU73ZWP6sIL4FpNbAcUnlCftmA>
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: Discussions relating to reorganising the IETF administrative structures in the so called IASA 2.0 project. <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: Sun, 10 Feb 2019 00:58:03 -0000
Hi > On Feb 9, 2019, at 3:59 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > > > 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. +1 The relations between the IAB and the LLC is defined in RFC6635 and updated for IASA2.0 in draft-ietf-iasa2-rfc6635bis-03. Specifically Section 4. "Administrative Implementation". Bob > > 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 >> > <0x5AB2FAF17B172BEA.asc>_______________________________________________ > iasa20 mailing list > iasa20@ietf.org > https://www.ietf.org/mailman/listinfo/iasa20
- Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844… Joseph Lorenzo Hall
- [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis… Alissa Cooper
- 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