IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 16 February 2018 19:22 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 4A981126CE8 for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 11:22:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 fgQQbyukT6n6 for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 11:22:17 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3CC71200C1 for <iasa20@ietf.org>; Fri, 16 Feb 2018 11:22:17 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ABD9B20090; Fri, 16 Feb 2018 14:29:22 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2CFF880B30; Fri, 16 Feb 2018 14:22:17 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Richard Barnes <rlb@ipv.sx>
cc: iasa20@ietf.org
In-Reply-To: <CAL02cgSDiUNJWnT28De1UbxjWTigyCztC1hQxb1bErhHrA4fLw@mail.gmail.com>
References: <CAL02cgSDiUNJWnT28De1UbxjWTigyCztC1hQxb1bErhHrA4fLw@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 16 Feb 2018 14:22:17 -0500
Message-ID: <9325.1518808937@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/xfLfhPaxJpklGL9ITiCp8V1LrEc>
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:22:20 -0000

Richard, that's AWESOME.
Thank you.  Can it go up during the plenary?

Richard Barnes <rlb@ipv.sx> wrote:
    > 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

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email