IETF Logo Mail Archive

Re: [Iasa20] draft-ietf-iasa2-consolidated-upd-06

Alissa Cooper <alissa@cooperw.in> Thu, 07 March 2019 17:12 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 5771C130EE3 for <iasa20@ietfa.amsl.com>; Thu, 7 Mar 2019 09:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=XxxcuLIS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=iUsHJEhb
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 5YaoVNbqaGWs for <iasa20@ietfa.amsl.com>; Thu, 7 Mar 2019 09:12:51 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 225D3131312 for <iasa20@ietf.org>; Thu, 7 Mar 2019 09:12:48 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 5D654375E; Thu, 7 Mar 2019 12:12:47 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 07 Mar 2019 12:12:47 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=4 Y3q9u4k4pKWdduxl8n6ELdETQhjrcGZHmBNsUplm44=; b=XxxcuLISbQ2VQAgLa vrQCXci0v3yyWomJmUJl95h1NkyJvfZbJrOwFc17lxn02rNy/KN1DcCvQcbdtt/w wUE4fcebn6AZiijzt+raez+lKRP75trY0xqV3Xvmfw+ys5TSJjPq0bMSfHmF8mF3 4NuZ+uZ0bSQlAM7SStSLEGNgslUJBmSfEpjoFO61kJjjlJCkeRnfjaH8WhY+DSMG 95HlKonW8KfN6j9yUTKCA/X+iRdR8MCj0dGyZUqRleTjUTW3q+HSP85+SkxALIl4 9mITAghwiRCQRLpJHsAsAQjdIn4dU04VzsKJKd5elWmJtMb8/mYLJp9LOIMMWpTU 2gbsw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=4Y3q9u4k4pKWdduxl8n6ELdETQhjrcGZHmBNsUplm 44=; b=iUsHJEhb4fUp9JJEjsNBzLvXg6bhDRh3SG8Bu/tbeZWhTb/rFNdxpYeIY r2uvp0M5rIaULsw//3u7Q50gtwiPhVTH+5hF7zST76UE2cse6bmKsJ7dI/oZjHe+ 3zCdXX1LjtVNjspVeKsg5umQvXyIZB7i3xb3sZiStXNm/SW35KpYFwpC/fmTaNU/ WPOG0jTawz1Q55uj9hWnZf/u8B8fnq4/D4Qv2MlOpdRD/wwPpvegw5WxuClRn5gh gj+eYTe6aBpz2l37yHwZ4BEFx4BUfh//GDJCj8Qc9yUFyuv2E3V/zqyrq9q/JVAI 9mBLFAozygVJxi8oP2uVZfLaPXOLg==
X-ME-Sender: <xms:DlGBXDlGp_TtOLsnSOzQnQHm4J3xf28J2_uiujvehU-T3vM5j1Tl3A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrfeekgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtdejnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceorghlihhsshgrsegt ohhophgvrhifrdhinheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepudejfe drfeekrdduudejrdejgeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegt ohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:DlGBXA06xRMyt-0xkZcYvrWXI3x1Y8ecasL4AB9f8nCvEpRCBbHS1w> <xmx:DlGBXAT0W49kLk9A3aVZpu6xcUudpnZm2rI26Zh3tMfyduLyx11AFA> <xmx:DlGBXJx7yvNMW5I7tK5ByPLusL43FRJJ1viG1CRmQvY9d0Yb2rZRcg> <xmx:D1GBXKipCUaze0WrOvONHs3SrjMOT4YPjyyRnWdXkaCErDAGoyiFjA>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.74]) by mail.messagingengine.com (Postfix) with ESMTPA id CB8F5E4360; Thu, 7 Mar 2019 12:12:45 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <A7B72177ABB2B2F0BEE7763B@PSB>
Date: Thu, 07 Mar 2019 12:12:42 -0500
Cc: iasa20@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <567462F2-46E3-445E-BDA3-493DA7AD31CC@cooperw.in>
References: <A7B72177ABB2B2F0BEE7763B@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/JTBca15HpM9LI8DgudWJdHBj3c8>
Subject: Re: [Iasa20] draft-ietf-iasa2-consolidated-upd-06
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2019 17:12:54 -0000

Thanks. I still don’t think this is quite right because there is no basis for this working group to obsolete or render historic RFC 3929 simply because it mentions the IETF Executive Director. It seems that RFC 3929 should be treated in Section 2 the same as the other documents in that section.

Alissa

> On Mar 7, 2019, at 1:52 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
> Hi.
> 
> draft-ietf-iasa2-consolidated-upd-06 should be posted in a few
> minutes.  I hope this version reflects changes requested since
> -05 was posted at the end of January.  In particular, it
> reflects the suggestions from the RFC Editor and the  separate
> status of the RFC 3716 as an IAB document and the text supplied
> by Alissa in her note yesterday.
> 
> The bad news is that when I read Section 4 after patching those
> changes in, it was just too convoluted and I had to restructure
> and rewrite it.  I hope the changes are at least tolerable to
> everyone and that I didn't make mistakes that would require
> another iteration.  Of course, if I did and problems are
> spotted, I'll be happy to that.  
> 
> On the other hand, if the language reflects the WG's intent
> sufficiently well but some of my phrasing doesn't line up with
> the needs of the IAB or RFC Editor, I recommend that we attach
> appropriate notes and let them sort it out with each
> other and the IESG if needed on AUTH48 rather than trying to
> make small editorial changes by committee nit-picking.   Just my
> preference, of course, YMMD.
> 
>    john
> 
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20

v2.23.0 | Report a Bug | By Email