IETF Logo Mail Archive

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

Brian Carpenter <brian.e.carpenter@gmail.com> Fri, 14 December 2018 03:42 UTC

Return-Path: <brian.e.carpenter@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 99FAD130ED1 for <iasa20@ietfa.amsl.com>; Thu, 13 Dec 2018 19:42:32 -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 sa0feJ8d9dpb for <iasa20@ietfa.amsl.com>; Thu, 13 Dec 2018 19:42:29 -0800 (PST)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450: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 65A8F130FEE for <iasa20@ietf.org>; Thu, 13 Dec 2018 19:42:29 -0800 (PST)
Received: by mail-ed1-x533.google.com with SMTP id p6so3850671eds.0 for <iasa20@ietf.org>; Thu, 13 Dec 2018 19:42:29 -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=PhPh8MlTNoIyuglRQwt59gFWr6irwOllFLKykMQVl4A=; b=LawYlX5qixLDOiOs2XfdA98J08iBt9O1d9HRFJR6QDqPQ+cjcEoSPNHoBsQPY+D2OB 46DI6T3wuCqGUhcCYRPo6T9vX1jv8SUt14iqKJJtBS7Y/2c0Jl0cK6HVOMVQbZ/6aBWn B1F55tx0e6tv8b71OWlHKC6h8TVq+NyUnt/vv0Ikx8XnO4lNZQEDn1Nr43JUD3nAo0mz iG/v10mxVEoaS8KkdpEYvdv1il9BF+dMS7HpL7orpWTjIe7LR0NZfpM9ihnHUwyfCYEt j9jFjrkEchP+Qs/whNHpRDq9HpXcL/hPGAoq5B7ppArcUePKVkSOuqxb1588ki3fkqLn ErEg==
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=PhPh8MlTNoIyuglRQwt59gFWr6irwOllFLKykMQVl4A=; b=tQFBakcZ6vOUZH1/g34WXYzS6BjL8n0W1apHb1AU7lOYpKAa7wFuwhr/SIbeu4B5DV PF3keQmeWVCLAsWumRX4+evld/uBhJQKcR0sUJSnRnfy1gtoBLNjQyEccFOKDZNX4pgZ 2ZQMcuYNLLj7SKvEYNWB5qlg69oeKClGUHaAaljTxCA4TJr96XIkbaiGCWMGe3NCG2qc nwatc3l11IfLb7BKqRqw3qHgM1qWCSW9XY+9/9aN+vpp/fOjRcqpyqdtwoymSVjDqKce Xny+vaewkzMRF8takpWPo0K2RbTqAgC8GcATPjqYG5QfNp+SZc18Gh2HP1UbOjwUI/yf qX5Q==
X-Gm-Message-State: AA+aEWa+hroTzUnQsY2f45tIEznOxeIYCFvwKaUMngzFiNaJlbEeQZZJ 7LG9n5qXTcyABUSZaqIMo8HCks+iUSBxPr5Xt8g=
X-Google-Smtp-Source: AFSGD/VHHmfpk1vkYFZl2DTFKhmw2/diQEQ7N2bwz6NxmXZEDlTj09HLFoxEzbcA0ecPUW4oBQud+ExcgxC0mq3HeVE=
X-Received: by 2002:a50:9315:: with SMTP id m21mr1525916eda.58.1544758947922; Thu, 13 Dec 2018 19:42:27 -0800 (PST)
MIME-Version: 1.0
References: <D837EF96-8896-460E-BE07-EC53BC783FCC@gmail.com> <49f06101-0611-cb3b-860e-ff2df59c6739@gmail.com> <B40D60AF-0D82-45F9-9C5B-74474C3DB1D9@gmail.com>
In-Reply-To: <B40D60AF-0D82-45F9-9C5B-74474C3DB1D9@gmail.com>
From: Brian Carpenter <brian.e.carpenter@gmail.com>
Date: Fri, 14 Dec 2018 16:42:15 +1300
Message-ID: <CANMZLAbCv3tEhPs9-HSFRQWUzufLhaFmWVnsw5sG3nGWrn46rw@mail.gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: IASA 2 WG <iasa20@ietf.org>, Brian Haberman <brian@innovationslab.net>, Jason Livingood <jason_livingood@comcast.com>, Joseph Lorenzo Hall <joe@cdt.org>
Content-Type: multipart/alternative; boundary="0000000000005ac701057cf338a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/S0ja5-Keduar3O5w6D1md78Hc14>
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 03:42:33 -0000

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.


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

>
Also, how is the IETF Trust funded in the IASA 2.0 model?
>

I've been assuming via the LLC.

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

v2.23.0 | Report a Bug | By Email