Re: [Ianaplan] CWG draft and its impact on the IETF

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 19 May 2015 11:07 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C53B1A888A for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 04:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.298
X-Spam-Level:
X-Spam-Status: No, score=0.298 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 Zq7Y9SOrGu0u for <ianaplan@ietfa.amsl.com>; Tue, 19 May 2015 04:07:36 -0700 (PDT)
Received: from APAC01-HK1-obe.outbound.protection.outlook.com (mail-hk1on0135.outbound.protection.outlook.com [134.170.140.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27BD41A88B4 for <ianaplan@ietf.org>; Tue, 19 May 2015 04:07:33 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
Received: from [133.2.210.64] (133.2.210.64) by TY1PR01MB0143.jpnprd01.prod.outlook.com (25.161.134.147) with Microsoft SMTP Server (TLS) id 15.1.166.22; Tue, 19 May 2015 11:07:25 +0000
Message-ID: <555B1969.9010302@it.aoyama.ac.jp>
Date: Tue, 19 May 2015 20:07:21 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Alissa Cooper <alissa@cooperw.in>, Milton L Mueller <mueller@syr.edu>
References: <5550F809.80200@cisco.com> <A78B554A-48C1-44FC-96B8-792EAB5C5DEB@cooperw.in> <6349b1ec0f3c4a14983ba41ca0c778b3@EX13-MBX-13.ad.syr.edu> <261D25FC-9376-4A1E-8D44-54D27B3B874D@cooperw.in>
In-Reply-To: <261D25FC-9376-4A1E-8D44-54D27B3B874D@cooperw.in>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [133.2.210.64]
X-ClientProxiedBy: KAWPR01CA0026.jpnprd01.prod.outlook.com (25.165.48.136) To TY1PR01MB0143.jpnprd01.prod.outlook.com (25.161.134.147)
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR01MB0143;
X-Microsoft-Antispam-PRVS: <TY1PR01MB014376C02AD93706E83D0346CAC30@TY1PR01MB0143.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(5005006)(3002001); SRVR:TY1PR01MB0143; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB0143;
X-Forefront-PRVS: 0581B5AB35
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(6049001)(24454002)(199003)(479174004)(189002)(68736005)(33656002)(40100003)(122386002)(23676002)(59896002)(65806001)(92566002)(64706001)(2950100001)(66066001)(47776003)(65956001)(65816999)(50986999)(76176999)(87266999)(42186005)(54356999)(86362001)(105586002)(81156007)(4001350100001)(5001830100001)(87976001)(74482002)(5001770100001)(106356001)(85202003)(46102003)(5001860100001)(2171001)(101416001)(62966003)(77156002)(64126003)(50466002)(85182001)(97736004)(93886004)(5001960100002)(80316001)(83506001)(4001540100001)(189998001)(7059030)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB0143; H:[133.2.210.64]; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
Received-SPF: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 May 2015 11:07:25.4734 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0143
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Yos-aDWdrpFE8kp61pzO77iQU8U>
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Eliot Lear <lear@cisco.com>
Subject: Re: [Ianaplan] CWG draft and its impact on the IETF
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2015 11:07:38 -0000

On 2015/05/19 02:59, Alissa Cooper wrote:

> Again, the IETF consensus is that we are satisfied with current arrangements.

That's definitely true. But my understanding would be that this is the 
position of the IETF starting from only the status quo before the whole 
process, i.e. without information about what the other bodies/functions 
want/need/desire/prefer.

It would have been a big waste of time for the IETF to 
discuss/describe/list, purely theoretically, other arrangements that 
might also satisfy us, also because the IETF was the first of the three 
bodies to express its consensus.

However, as far as I understand, that doesn't, at least not in theory, 
exclude that the IETF could be satisfied with other arrangements (e.g. 
in the way/extent that Russ has expressed it). There has been no 
consensus call on that, and so we simply don't know.


> Reading this, it seems like there are too many missing details about the board at this point to really be able to provide an opinion.

That's of course very much true. My guess is that one reason the 
information we received got sent our way at this stage is to test the 
waters.


Regards,   Martin.