Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01

Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 10 February 2019 12:52 UTC

Return-Path: <abdussalambaryun@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 51CB1129BBF; Sun, 10 Feb 2019 04:52:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 n_2QnX1qk6la; Sun, 10 Feb 2019 04:52:51 -0800 (PST)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 681F5128D52; Sun, 10 Feb 2019 04:52:51 -0800 (PST)
Received: by mail-ot1-x330.google.com with SMTP id w25so13155289otm.13; Sun, 10 Feb 2019 04:52:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jB3LijzMLbBuqFCCzWViMi+/Wtn61LSCBjdkQuLfxNw=; b=bh5ePfX6CqlG58FjYfqBwF9OQuK2nkDVWxuAyktodx1VMc7J4vqjhDDyFRRQJzgOs7 Tc0o9wRlK+J8mQSMagKqR/BSZnrFSV5qZa+fDWPo6ICJl/l8HMVt2wdj/f+afI8UEBWR TUq+A9T+aAgJ0zhHoAX8YLxej/aEeHLxv89benpEAFI45Rogkey1QLAwhp1STdivbUuX u615dHZkZw/OPTttaSe/faazWEt+y/stnd69pDzcvmxvmK/ZnjnUVRoK3T5GxbSAVzu/ DJWYDX1HPXZ2iyaaRQ46Rfg6gMVDmdysJ/l1fn4OSQNLs3rI7GduOKncMt+OSyv2LeJe thOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jB3LijzMLbBuqFCCzWViMi+/Wtn61LSCBjdkQuLfxNw=; b=YfXVdHdLFLIe2+4/sj4PjKMYYo255hTjmFewWszon1asZZCDvRE3pJtoXQl2v/zJf8 zC7QzvcD6EmGtq7nhOShXWSTGCvXcggtZG80FvLlnvTmBvO8AS4Zp00oJTqr6qw6DGW/ cllJZPLpYXVfL+6LkBQwGaYvHBH8DdjKrgJ8hnVnkuJyywQbeYTA2WUPc6050xwI4/RF 894FZwLSfVmalD+UMvgUh6ln605MDVl0QqOD7CVgrNz/VpITh/ijRtMbUO6SSfeSVGcW cMCXTFu1SLTRoLnREuirvr/yignVkfCRsnjUfmFf9FnNhAzUKBw6j9++e9J1sbY4GsSX 1oZQ==
X-Gm-Message-State: AHQUAub9+JAhfdROTXwlp5J8oEoSKUWCfYXB7NnWAiiXf/fKSMCnwxMt EvZfK8jgvme5jfQUEXmskgMiTntCaNjytwscmu0=
X-Google-Smtp-Source: AHgI3IbXp7ZjCMPrRW3MvENgWrnB3ZznNnJEw4PQlCC5pPXMwJ2YIo6QrguvnFRa2krPg04ExTGPhVyyOek0jzjfzzM=
X-Received: by 2002:a9d:3782:: with SMTP id x2mr21799855otb.13.1549803170589; Sun, 10 Feb 2019 04:52:50 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <a0a2ef94-335f-5ab6-e49c-7b1c985af3fc@cs.tcd.ie>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Sun, 10 Feb 2019 14:52:34 +0200
Message-ID: <CADnDZ88+QE4SnB7js-zWc_Xh-yDDQH6O+Ete+1E8A6RPx=AovA@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: 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-Type: multipart/alternative; boundary="0000000000007470a3058189abb4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/WqqE1Y19WMaNtc-kFb6LhVWxcOs>
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: Sun, 10 Feb 2019 12:52:55 -0000

+1
AB

On Sun, Feb 10, 2019 at 1:59 AM 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.
>
> 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 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>