IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Fri, 14 December 2018 02: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 75179130EE0 for <iasa20@ietfa.amsl.com>; Thu, 13 Dec 2018 18:58:43 -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 j_L22rtewe4W for <iasa20@ietfa.amsl.com>; Thu, 13 Dec 2018 18:58:41 -0800 (PST)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 45569127598 for <iasa20@ietf.org>; Thu, 13 Dec 2018 18:58:41 -0800 (PST)
Received: by mail-wr1-x42c.google.com with SMTP id u4so3011850wrp.3 for <iasa20@ietf.org>; Thu, 13 Dec 2018 18:58:41 -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=aN9UvHI6jZS6ZJQzARUM/S6Wo9ObuUKoiIEhtdYUPZo=; b=VLE5LKUH1dbt0GNpfHpnVR0PEVW9AXr/0zmjcQvHff+/tV8lnOCyrZ5/JUzF/8rzmb Z2jmV0xe3g0Ah+AlgOw1UD9bK4KSBCQ56NUDxezSQ9hx9UWwMGWc8UmYtwZ/ZM4UobRP +myn57EHGkVgt8RBwRtRjqjd3FevdtRovH9GO6YXe9GnRaGJ1m0Yr0TWw3wB6HQ/siuE 5Y2854vJR4OLZUZZa+pRfIt3EP2cuzmUnma20Ix+Zqim65SDFMYvhCtOuXEBa1dSvbMH eC69wcapbZRiyqRkzwE1Z7/UVrd2Hvfo7dZ6j5b9Vz5uWBK0nHz7+gYGVZ0ssdoH9QBm hgiQ==
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=aN9UvHI6jZS6ZJQzARUM/S6Wo9ObuUKoiIEhtdYUPZo=; b=jzkKzHR/v3z136aF89lXyFIPjf9bKBsmA8kKEWF0AIdgPt921VCuK9vyH2bROveZsQ ZBBogZtWDXG/YdwIpxFIkWq0OC5BmCOjaFXjjEXVonXHzedxjOFhOPcHu1PVe5dexiEy DG3TiA7QHXG8kapsi2zz2zcEuD6u3srbZOtXnLENZTBb09KdOTIzqdhBqHjAwWXIqmR2 pTyEJnMzMTf4KnHZV4lThfQDVEWDApsVwdWPwTl0+laAyU36+vA+yh3oWWhCnHAG1nqI fhlMOmRAMDvIR0w4H0shcTeEGrEBFdzFZI9e5LQNw3AmQWGCm4jXrTARo5B92lN01pEA w0Pg==
X-Gm-Message-State: AA+aEWZvQQuW7AzDP04aaF4bSE2wjeT1Snoc0spBON353YrfS49RJmQm nJY2XPk+gAM+kGP4C/fdVys=
X-Google-Smtp-Source: AFSGD/X9uWOZIE/Mz8Sm7gLRs5d6YIrqIdLnxoVaFehKU3Pqf9CqAHV74Q7deqkzkqL2EFFSPWZtYQ==
X-Received: by 2002:a5d:5409:: with SMTP id g9mr1071626wrv.88.1544756319770; Thu, 13 Dec 2018 18:58:39 -0800 (PST)
Received: from [10.0.0.50] (c-76-21-112-100.hsd1.ca.comcast.net. [76.21.112.100]) by smtp.gmail.com with ESMTPSA id h13sm2665658wrp.61.2018.12.13.18.58.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Dec 2018 18:58:38 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <B40D60AF-0D82-45F9-9C5B-74474C3DB1D9@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BAE54ACA-AA44-4EC5-B5E9-C8918C62672E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 13 Dec 2018 18:58:34 -0800
In-Reply-To: <49f06101-0611-cb3b-860e-ff2df59c6739@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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/jbzFDk0VH_5BIwWMFqyo7npxWac>
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 02:58:43 -0000

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?


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

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

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