IETF Logo Mail Archive

Re: [Iasa20] Diagrams of current vs. Option 2/3

Richard Barnes <rlb@ipv.sx> Fri, 16 February 2018 19:07 UTC

Return-Path: <rlb@ipv.sx>
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 2BA6C126CE8 for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 11:07:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 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_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.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 UMsplIgoNNe5 for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 11:07:04 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 23E7F1242EA for <iasa20@ietf.org>; Fri, 16 Feb 2018 11:07:04 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id x21so4859663wmh.0 for <iasa20@ietf.org>; Fri, 16 Feb 2018 11:07:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Udd5JgVoz0GtCO0BfIWGVCUWT8rgT6suxjfsrfTxk78=; b=aQ2hYG+gwAoBTsgDOX5zuc7vIDG+BnTSIxrGAN++K/1hRmdggtx3uFhtlXbS6hK6px fbc8BjSUG7mwikTokC3sn8ZZclTAxUEsyrGDT8tNRpNUQej6onEWPE88Sh2yAiEmKKuO 1/hfg0ELkWCN/VSew3Wqhqh2DzoueA14s9zn6rkvoiznABAWQfJP9UuzCB1pLwGt1boD Do+m6vwPMcMI+sEaaZLd1QeiS1pSIt0riE6cOYWLBB77BJU5AyDmjMH/1HZNdaevUqGh Rs5rEr9DhiEYCyGt/suVrOmDflV8+8ZTRsX7ehyUdoHuUC+lxF+uDOGTVy7WqAvWGkDs tLlA==
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=Udd5JgVoz0GtCO0BfIWGVCUWT8rgT6suxjfsrfTxk78=; b=sM3yAx0YbYFjhv36p9W24+KfTE1xHDhU+yDcN3AupweKiKrdPrFqACnyJ1VdM8vxri lQ+y5DeN+HOu+m1F1UpMM9JY9dscgLlTPc8bUUAhiKazC7jQ07JQuJpPyMFXbFrhEzHP 3H+/t8gzEvCo+3oKdPTnUnNOSo4oVyJRBIMTXiA/4dcOzRkPaB5JsuOgJOdImxlIZVkg fPFxg5BuzMAB8J0wY+I7ApweiZYSHo8gI2nZOU02lneCWSORItICHm8GVI+qyd1px2er 7OCcStCgM8YuKAlmiCVK6766esud0b1blXKL5pjXX9hqZb5p4rfWrcVPZRMwpTaUcniD NRgw==
X-Gm-Message-State: APf1xPCXaMbgYiUyVEOjyZWGvufgj8UI3RBHZh9K1bQB1YHnJEDAGDHh E1nLkitYxC6IVCOAE+SrfVTDzr9IrvRZTD/kXqqlKA==
X-Google-Smtp-Source: AH8x225O/lD5Jr0CxzOCKOoPDQ3MiqgarCWPom3j87CfHlLKuzccoBsxU85fmCKgt19jUVLGd9UftoKS1O5qt8JnbTY=
X-Received: by 10.28.47.80 with SMTP id v77mr5460420wmv.23.1518808022568; Fri, 16 Feb 2018 11:07:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.20.66 with HTTP; Fri, 16 Feb 2018 11:07:02 -0800 (PST)
In-Reply-To: <CA+9kkMCdr=FqAy6qxvKtsUq3B182Cyd0A+6GCTbaTaLZ3cp2YA@mail.gmail.com>
References: <CAL02cgSDiUNJWnT28De1UbxjWTigyCztC1hQxb1bErhHrA4fLw@mail.gmail.com> <CA+9kkMCdr=FqAy6qxvKtsUq3B182Cyd0A+6GCTbaTaLZ3cp2YA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Fri, 16 Feb 2018 14:07:02 -0500
Message-ID: <CAL02cgTZdkHGz3vSCshzxWuPMR-Xoi_kS8do+kcbmb2Jveid9w@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: iasa20@ietf.org
Content-Type: multipart/alternative; boundary="001a114242caaae4a30565590c64"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/g3ysF3GH1Iu4NXm6HrOjTdAFwe4>
Subject: Re: [Iasa20] Diagrams of current vs. Option 2/3
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 19:07:06 -0000

Thanks for the clarifications, Ted.  Revised diagram removing Trust and
adding IAD on IAOC:

https://ipv.sx/iasa2.0/IASA-Strawman-NoTrust.pdf



On Fri, Feb 16, 2018 at 1:46 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> Hi Richard,
>
> I note that your diagram includes the IETF Trust, which is not part of
> this discussion since it already had a separate legal existence.  I think
> it would be cleaner to remove it, especially since the relationship is not
> that the IAOC administers the IETF Trust, as this diagram describes it.
> The Trustees do; they simply are currently defined in terms of the trust.
> I agree that this would need adjustment if the IAOC disappeared, but that's
> really a very separate question than the core of the IASA 2.0 work.  On a
> related note, the IAD also serves as an ex-officio, non-voting member of
> the IAOC (that's why the IAD is a Trustee).
>
> Lastly, this is certainly one way to look at what might get created but it
> presumes some structures (like an advisory council and the IETF Admin Org
> board having some members selected by the board itself) which have not been
> in any of the proposals I've seen.  If the proposals out of the design team
> plan to include those, I think having them in drafts before London would be
> very useful.
>
> thanks,
>
> Ted
>
> On Fri, Feb 16, 2018 at 10:01 AM, Richard Barnes <rlb@ipv.sx> wrote:
>
>> Hey all,
>>
>> As we're considering the various options available, I thought I would
>> play cartoonist again (after contributing [1] earlier) and share some
>> diagrams of how processes might change if we go for one of the subsidiary
>> options (II or III in the memo from the lawyers).  Based on a whiteboard
>> that Alissa, Sean, and I sketched out one afternoon:
>>
>> https://ipv.sx/iasa2.0/IASA-Strawman.pdf
>>
>> Obviously, the details will need to change as a result of the legal
>> discussion, but I thought it would be useful to illustrate one possible
>> realization here.
>>
>> --Richard
>>
>> [1] https://ipv.sx/iasa2.0/IASA-org-charts.pdf
>>
>>
>> _______________________________________________
>> iasa20 mailing list
>> iasa20@ietf.org
>> https://www.ietf.org/mailman/listinfo/iasa20
>>
>>
>

v2.23.0 | Report a Bug | By Email