Re: [Iasa20] Comments on <draft-ietf-iasa2-rfc4071bis-00>

Bob Hinden <bob.hinden@gmail.com> Fri, 14 December 2018 17:18 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 6B0081310F1 for <iasa20@ietfa.amsl.com>; Fri, 14 Dec 2018 09:18:19 -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 9BWYSZm5Pgbl for <iasa20@ietfa.amsl.com>; Fri, 14 Dec 2018 09:18:17 -0800 (PST)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 361AC130DE8 for <iasa20@ietf.org>; Fri, 14 Dec 2018 09:18:17 -0800 (PST)
Received: by mail-wm1-x32b.google.com with SMTP id y1so6370142wmi.3 for <iasa20@ietf.org>; Fri, 14 Dec 2018 09:18:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=6PieGFR1vRPHZqwywzr40bW1pbPv9xMoBDBqAN5OEAU=; b=t4ZmL06UnwC8ZfG8iidByn0PxbyaTj6jIObmU4+jq2MN00u7kzha3Ma1tk0NRBGsg+ QYQUdvGMk0hmExVEIVRivgJUkpgX+NN9iOMz58F1zENCFPcAy3wHL2VFB9G6BhYf0m8s HfyTA6akjK6im4R4o9rO8cTvmtKftRyhGHdNJ725y4BXNqh8mZoeYprf++Zmyw0aoWmZ GlrvTuLOTwEvtAcJRwXGTf8m1178Lg6D7Uq4JhO2MdgsG5z9IjGWvK03HRX19TPxssnL 41Pbug+48Z08hCA90t/NdW7b8kH8P/Li3KnZKMiBZrrhkUKpKdS7VO8ccHUL/mbMomZl 28lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=6PieGFR1vRPHZqwywzr40bW1pbPv9xMoBDBqAN5OEAU=; b=njJvlNK5Ycj1B5GoqzrLKytogh9fYY29gmEmwv9v7tQXIqfxnidkAYlB/NQF4oUIEn LvZpydjOQLKhBmDurJ1Wj3gyUcSHNv8m/FBjsiWeUFd+4dgY/Zmn95zRPjw1x6UW1bSb L+5IxUIdO28+Ro/PmxVeynzJ+N5CqZJDTCPQG0pIcgRSqB39hJ14SFbYUl2S0I18RrL5 p5CVhnzROPQDN2IWy7aY75JOrPEuIOThGH4vrbT3VaIGsocZibSc9cMu5Dw/sFlC6HVx CQSzRkUUfel4TXQZ5Q3r6SVc2Na+L+GA3bMiCu6mFNz4IekhUmH+oRib6Ppt+DpiK/r2 AX1Q==
X-Gm-Message-State: AA+aEWYzR/ymj9YoB1VS2FOr+U2JizSwenxj+W2j+coSskbfDUVBTJq1 pi2kkmqpqWYdgidLWF4IzDo=
X-Google-Smtp-Source: AFSGD/VlydHaWM10/oHa3S75tUBk/R0HHDUI1/8+rhGVtkgSg9R7hZikSMa5MRoU+TnsiKe/N9dH8w==
X-Received: by 2002:a1c:c2d5:: with SMTP id s204mr4245007wmf.144.1544807895582; Fri, 14 Dec 2018 09:18:15 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:f3a:f8ba:7d6f:30e8:acd3? ([2601:647:4d01:f3a:f8ba:7d6f:30e8:acd3]) by smtp.gmail.com with ESMTPSA id l20sm12320944wrb.93.2018.12.14.09.18.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Dec 2018 09:18:14 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <EEBFD606-B962-4968-9560-6509463EA280@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_9AD78918-4C46-48FA-88EA-C0E1D9DF0400"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 14 Dec 2018 09:18:10 -0800
In-Reply-To: <CANMZLAbCv3tEhPs9-HSFRQWUzufLhaFmWVnsw5sG3nGWrn46rw@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IASA 2 WG <iasa20@ietf.org>, Brian Haberman <brian@innovationslab.net>, Jason Livingood <jason_livingood@comcast.com>, Joseph Lorenzo Hall <joe@cdt.org>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
References: <D837EF96-8896-460E-BE07-EC53BC783FCC@gmail.com> <49f06101-0611-cb3b-860e-ff2df59c6739@gmail.com> <B40D60AF-0D82-45F9-9C5B-74474C3DB1D9@gmail.com> <CANMZLAbCv3tEhPs9-HSFRQWUzufLhaFmWVnsw5sG3nGWrn46rw@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/jTlkYfl08au2drL96l1PglqR9vU>
Subject: Re: [Iasa20] Comments on <draft-ietf-iasa2-rfc4071bis-00>
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: Fri, 14 Dec 2018 17:18:19 -0000

Hi Brian,

> On Dec 13, 2018, at 7:42 PM, Brian Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 
> 
> Regards
>  Bob,
> 
> On Fri, 14 Dec 2018, 15:58 Bob Hinden <bob.hinden@gmail.com wrote:
> Brian,
> 
> > On Dec 13, 2018, at 6:44 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> >
> > Bob,
> > On 2018-12-14 13:34, Bob Hinden wrote:
> > ...
> >>>   This document obsoletes [RFC4071], which specified the original IASA,
> >>>   [RFC4333], which specified the selection guidelines and process for
> >>>   IAOC members and [RFC7691], which specified terms for IAOC members.
> >>
> >> Does this doucment also update BCP101?   I think so, if it does, it should be
> >> mentioned here.
> >
> > That's automatic. This is a BCP that obsoletes RFC4071, which is the base
> > document of BCP101.
> 
> But shouldn’t we be redefining BCP101 to point the the RFC that <draft-ietf-iasa2-rfc4071bis-00> will become?
> 
> I'm sure the RFC Editor does that automatically.

Not sure, but I think it would better to say it explicitly here.


> 
> 
> > ...
> >>>   o  Unification: The IETF LLC is reponsible for providing unified
> >>>      legal, financial, and administrative support for operation of the
> >>>      IETF, IAB, IESG, IRTF, and RFC Editor.
> >>>
> >>
> >> I think it is correct that the IETF Trust is not included here.  Might be good to call that out.  That said, where does the IETF Trust get it’s funding?
> >
> > I think that for this document, it's simply part of the IETF. No need
> > to mention it separately.
> 
> Is it part of the IETF?  I thought the IETF Trust was a separate legal entity (otherwise it couldn’t hold IPR) and had it’s own bank account.  Seems separate to me.
> 
> Yes, of course, but "the IETF" is a pretty vague concept so it seems like a detail here, given that we have a dedicated draft for the Trust anyway.

Yes, “the IETF” is still a vague concept :-)

However, as I note below, we should know how the Trust is funded.

> 
> Also, how is the IETF Trust funded in the IASA 2.0 model?
> 
> I've been assuming via the LLC.

Can someone answer the question who knows and/or point to a document that says it?   If it’s the LLC, then I think this document should say it.

Thanks,
Bob


> 
> Regards
>     Brian
>     (via tiny screen & keyboard)
> 
> 
> >
> > For the 3rd time: this is yet another reason why we need to bring trust-update back to the WG to make it consistent with rfc4071bis.
> 
> I agree.
> 
> Bob
> 
>