Re: [Iasa20] Memo exploring options for IASA 2.0 models

Eric Rescorla <ekr@rtfm.com> Fri, 16 February 2018 18:55 UTC

Return-Path: <ekr@rtfm.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 A1137126C2F for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 10:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 5Y7dGNnjezfo for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 10:55:39 -0800 (PST)
Received: from mail-yb0-x234.google.com (mail-yb0-x234.google.com [IPv6:2607:f8b0:4002:c09::234]) (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 8791F1242EA for <iasa20@ietf.org>; Fri, 16 Feb 2018 10:55:39 -0800 (PST)
Received: by mail-yb0-x234.google.com with SMTP id e135-v6so915429ybb.3 for <iasa20@ietf.org>; Fri, 16 Feb 2018 10:55:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FrbE3fVVPg9VptUFT0h8+V41hqypuca7Dl1usQ8HxqU=; b=ybrwVGl3yfbm6HkwkMDmJvPGlHucARe+TjBw/zK+ofIhqk5cTaUeCcsFHqjN4citeL TwJXbNCJYUkZECQjR89BgJ+c7MDxcDmsqHz/M2BWqqa6DPvxRGJwDgymnJFr6PagJL6S J3C7PWpeTPOlDnT2nhh4sUtfnwEuN/jTSGfraHGzONr/KvHKZ76jn4xVbfk9ABhRzeN+ xRQKcpXhjrG9ZcsyEUxfMhqxxRVtgbWLvxWqxNo/Cs74e7J6wzNDMNGHFj7bX5SQ8mOX +y5qoBebIf5WRitOwsGHyhfTgAE970j+0V4WPm9iGL5q0D1tLqlhb72HsiNnjFC/G/9U iPgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FrbE3fVVPg9VptUFT0h8+V41hqypuca7Dl1usQ8HxqU=; b=nW0MqoO/QOGIQPIkx/h5sJqWmmFoXoE624WUpQhe00qhuPxjvkXdtGpUsafokgnbVv lq5kLhEwvFu460GI4PmOF0fnFZ3ZeUrVHoUX+9ny+EA0qbOZBZ/3gyfpUFKrhpnPxeWA YpmWbblLvFKFbx7WBCNQse2KROU9UP4QouSF95BdppDtRKN6OI801k6qYkLR70yco8Iv 6zUpUp8IPP8UUwciMq7jyvowTie+c/Fpybu4KAcBf+mdfNwCxa2PbGhlVU1ykAzeWor0 9HVUmVbFNp+pUh4Cow8QjGPJQvYubAqy/+4xF4TC7aqzSmAZbnVcI/DzKi4Ya4Ky++Vn LKVQ==
X-Gm-Message-State: APf1xPAvScDqaR+VDsdWyFsDZ2/gKHypihfWPV0/R4aCvDsLJUQovQvT EznVzT53TcdEGl/DwUu3hQaxP0mawBxascpVm8XOGg==
X-Google-Smtp-Source: AH8x227BLq7ipCLKX8Ta3n1f8A1vojmMXeJqaRtP5X5Adf0MgiM/AD5UDhH99qZTS/LS/fIJwHY4bCXPeJnYgDm2wtQ=
X-Received: by 10.37.228.134 with SMTP id b128mr5436260ybh.474.1518807338589; Fri, 16 Feb 2018 10:55:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.114.10 with HTTP; Fri, 16 Feb 2018 10:54:58 -0800 (PST)
In-Reply-To: <be961111-9bed-086e-a0ab-b220125a438d@cs.auckland.ac.nz>
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <20182.1518727709@obiwan.sandelman.ca> <C77B41DA-268D-4F0E-8AC8-F2E292E38B14@cooperw.in> <9631.1518800971@obiwan.sandelman.ca> <be961111-9bed-086e-a0ab-b220125a438d@cs.auckland.ac.nz>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 16 Feb 2018 10:54:58 -0800
Message-ID: <CABcZeBNBXW1SVDDmaLg+-ZX_3WhaWtwEYFiXC8KBUpCXFVjB6g@mail.gmail.com>
To: Brian Carpenter <brian@cs.auckland.ac.nz>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, iasa20@ietf.org
Content-Type: multipart/alternative; boundary="001a114bb0ace63fed056558e325"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/M0a8_XjayHnRukQYR9WWZH82a7E>
Subject: Re: [Iasa20] Memo exploring options for IASA 2.0 models
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Feb 2018 18:55:41 -0000

On Fri, Feb 16, 2018 at 10:50 AM, Brian Carpenter <brian@cs.auckland.ac.nz>
wrote:

> On 17/02/2018 06:09, Michael Richardson wrote:
> ...
> > 1. I think that we want our own bank account.
>
> I have seen no consenus call to that effect. Personally, I think
> that we have no need of a bank account. It appears that we are in
> need of a primer for potential sponsors explaining how moneys sent
> to ISOC are applied to IETF needs.
> ...
>
> >
> > 3. I think that under Option III, that we would very CLEARLY be able to
> sign
> >    our own contracts.  Be they Executive Director, Secretariat,
> RFC-editor,
> >    or tools development.  I don't know that the community thinks this is
> >    high priority, but I think that it does matter.
>
> Why? When did the IETF ever suffer as a result of its contracts being
> signed by ISOC?
>

See, for instance:
https://tools.ietf.org/html/draft-haberman-iasa20dt-recs-01#section-3.1.3

"

 For example, due to IETF's lack of legal status, contractual
   agreements must be signed by ISOC on behalf of the IETF.  There are
   occasions when a decision that is right for the IETF and desired by
   IETF leadership cannot be executed due to constraints posed by what
   ISOC can and cannot agree to itself.  For example, when IETF sought
   to acquire a recent piece of software for business purposes, ISOC
   would initially not agree to entering into an agreement with the
   software provider.  Ideally, IETF could make decisions free from
   operational and other constraints imposed by its relationship with
   ISOC."

-Ekr



Regards
>    Brian Carpenter
>    Department of Computer Science
>    The University of Auckland
>    http://www.cs.auckland.ac.nz/~brian/
>
> (I am currently sending all mail from this address
> due to a Gmail bug. I can still receive via Gmail.)
>
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>