Re: [Iasa20] draft-haberman-iasa20dt-recs-00.txt

Jari Arkko <jari.arkko@piuha.net> Tue, 11 July 2017 18:56 UTC

Return-Path: <jari.arkko@piuha.net>
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 02B2713179F for <iasa20@ietfa.amsl.com>; Tue, 11 Jul 2017 11:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 IBlyOaUzhcsd for <iasa20@ietfa.amsl.com>; Tue, 11 Jul 2017 11:56:06 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 7956213179C for <iasa20@ietf.org>; Tue, 11 Jul 2017 11:56:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0EFDF2DB68; Tue, 11 Jul 2017 21:56:05 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XbP20EfgiUN1; Tue, 11 Jul 2017 21:56:04 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id 8073E2DB67; Tue, 11 Jul 2017 21:56:04 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_A18BC55F-7316-4002-B9C1-E455D16FE43F"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <4f2cced5-be6c-0a9d-9d72-e559dccdd90f@cs.tcd.ie>
Date: Tue, 11 Jul 2017 21:56:01 +0300
Cc: "iasa20@ietf.org" <iasa20@ietf.org>
Message-Id: <16F44533-E295-410D-A57A-D80D686CE339@piuha.net>
References: <CABtrr-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com> <4f2cced5-be6c-0a9d-9d72-e559dccdd90f@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/aMSHFOHlL2SEjxsq8Ra_X4jKuws>
Subject: Re: [Iasa20] draft-haberman-iasa20dt-recs-00.txt
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: Tue, 11 Jul 2017 18:56:09 -0000

Stephen,

> I guess I understand how the DT got there, but I'm a bit
> disappointed that so far, we only seem to have addressed
> the "should the IETF incorporate" aspect of the iasa2
> work.

That’s taken a fair amount of discussion, but in the
document Sections 5.2 and 5.3 are not about that.

I guess my question to you (and more generally all
of you) is whether we’ve missed options or aspects
that we should have explored. The idea with the
meeting next week is to talk more about potentially
missing options or what we should put into to the analysis
of those options, than what the “Right Answer” is
for the IETF yet.

So, do you have thoughts on what aspects we
are missing and which should be documented?
Or are you unhappy with the level of detail or
analysis of the current options?

> - I didn't find section 6 clear or convincing but
>  it's also hard to see how one might document
>  such an analysis at this point. Maybe when I
>  read it more closely or we see a presentation in
>  Prague, it'll be clearer, but as of now, the DT's
>  analysis isn't that clear to me. It could be that
>  I change my opinion about IASA++ if/when I do
>  understand the DT's analysis better, but I'd be
>  surprised if that were the case.

At this point, we’d love to hear your thoughts
on aspects that should be taken into account.
Lets worry about what the right conclusion is
later.

Jari