IETF Logo Mail Archive

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

Alissa Cooper <alissa@cooperw.in> Thu, 15 February 2018 04:48 UTC

Return-Path: <alissa@cooperw.in>
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 3786D1270A3 for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 20:48:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level:
X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=ZQiy5FBm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=TPDHEwI4
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 5rohcDvvp7HF for <iasa20@ietfa.amsl.com>; Wed, 14 Feb 2018 20:48:43 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DCB712025C for <iasa20@ietf.org>; Wed, 14 Feb 2018 20:48:43 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 84D0B20D3C; Wed, 14 Feb 2018 23:48:42 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 14 Feb 2018 23:48:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=zsLE0SXZkW1i8+ED+iVt3vL22WHpJCVk1HwBNTd2bZU=; b=ZQiy5FBm 8ZkXc6PjbIMiSrjKN+MvtI2nxm/SHCdX/BHrY+vQ/yaRCTGFcQOSCvbrcFpbc3kh 83LB6LdG9qsNH+uRxWHYbpPNFJD8ech+65wCsBJZy9pgCnOg6iTxZOSk/thNFRhw g3afyvKR3I7wZlAtayLuwkSTC2Ih+//S0s7fJRRoECjgZeppoNf9oP1TQbryOrFe ISz/Gze9MjqJDDPNAvIzqGr9kNzTIkXWSO4hR59PbPpJ1crbjej6gVrQWkE2hqKe yelpQYiw0jEfEvWRDnnGKJYBEPT1UsDAQ2x8ZPtblhMV8AV4h5Yc5PgKf+421vQG q5Pljr4AG4mNpQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=zsLE0SXZkW1i8+ED+iVt3vL22WHpJ CVk1HwBNTd2bZU=; b=TPDHEwI4iLc5/Hy2lNSvTHt/8l/GfnR5C0hOMFxCvmGiv 7fv/hmz+zx37cbAJtQaQkwZrLNC36RtsQ7uTDH74mSeTAH4j+qETWZo6NucQX7Wd NiZ4CV08hBnMZ5n8m3ChyPH/GpGxQHqpt6iscjDD2PQ1CKmOADtDnzg4COh5JMpE tQn/K38XwX01d83+TGt5gK4dKF7l/mWMf75xHLvQnUZa7eMBlvNULQOpSrBFMgn7 oC94jNBJPVlP6733NwWdbVDn8lI37gfaBPRaFPjcOl35toIH5KYUA4aTJQT6aV9Y DESQeLy4nshJpz0NShSUy4aVREEXtR29R69LCPXow==
X-ME-Sender: <xms:KhGFWosAujfrQ89RKvQyDk02IB1aD9s6wyMQmOgYxkrhbOwn-ImVFw>
Received: from rtp-vpn6-391.cisco.com (unknown [173.38.117.66]) by mail.messagingengine.com (Postfix) with ESMTPA id BDFEF7E1DE; Wed, 14 Feb 2018 23:48:41 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0328BA3B-7241-427B-AD4E-3EA93AA54FC4"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <05DFEC48-5443-475C-BB98-5059FC51C654@akamai.com>
Date: Wed, 14 Feb 2018 20:48:45 -0800
Cc: Joseph Lorenzo Hall <joe@cdt.org>, "iasa20@ietf.org" <iasa20@ietf.org>
Message-Id: <8F5DBA58-FC19-43FF-A2D5-45A4CE5EA5DE@cooperw.in>
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <458C6912-4C20-4A5E-88A1-6397ABE3969A@akamai.com> <CABtrr-XXTvhhs0bFq=oYVJHpr2fnWEr8YLAwwKzaM5Pcq-UdJw@mail.gmail.com> <05DFEC48-5443-475C-BB98-5059FC51C654@akamai.com>
To: "Salz, Rich" <rsalz@akamai.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/UaKemEyAs8NRuvXp8lMp7_Oy9_U>
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: Thu, 15 Feb 2018 04:48:45 -0000

Hi Rich,

The nature of the options present in the memo has nothing to do with the nationalities of the people on the design team. It has to do with the fact that ISOC is a 501(c)3 not-for-profit organization incorporated in the US, and that the preferences expressed in the hums in Singapore were for options that maintain the IETF’s administrative activity under ISOC’s umbrella [1].

Alissa

[1] https://datatracker.ietf.org/meeting/100/materials/minutes-100-iasa20 <https://datatracker.ietf.org/meeting/100/materials/minutes-100-iasa20>



> On Feb 14, 2018, at 7:25 PM, Salz, Rich <rsalz@akamai.com> wrote:
> 
> So it’s the six authors of that document?
>  
> https://tools.ietf.org/html/draft-haberman-iasa20dt-recs-01 <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dhaberman-2Diasa20dt-2Drecs-2D01&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=UPuAyEtZNXSh2F99CSDW73yyDRgpv4yFvbUIeRJNGqc&s=5JhWA7LtzjfeRY1mz0XQ-YhGuuOwgnNwHexKq9IgK1w&e=> 
> On Wed, Feb 14, 2018 at 20:29 Salz, Rich <rsalz@akamai.com <mailto:rsalz@akamai.com>> wrote:
>> Stephen's question makes me ask: Who's on the design team?  Any non-US?
>> 
>> 
> 
>  
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org <mailto:iasa20@ietf.org>
> https://www.ietf.org/mailman/listinfo/iasa20 <https://www.ietf.org/mailman/listinfo/iasa20>

v2.23.0 | Report a Bug | By Email