IETF Logo Mail Archive

Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05

Alissa Cooper <alissa@cooperw.in> Mon, 04 March 2019 20:38 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 8C9B813104A for <iasa20@ietfa.amsl.com>; Mon, 4 Mar 2019 12:38: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=FlOcTTEG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=BqBwwKJK
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 bcwVrri9_5J3 for <iasa20@ietfa.amsl.com>; Mon, 4 Mar 2019 12:38:51 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E58213103C for <iasa20@ietf.org>; Mon, 4 Mar 2019 12:38:51 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 757892682D; Mon, 4 Mar 2019 15:38:50 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 04 Mar 2019 15:38:50 -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=x 1X6C23TbjN/DCe4RXjqALTyF/cTJurqg7EGG1v6q3g=; b=FlOcTTEGzU+aIQ8j2 r9m5I/q31m/YUWhPbbwtL8ZapXf0oWPM2/zdV1scgilanXedULu0ko5nlgdW40YL u2/HuOiU9qSR9ilwRdTkl+wdY04soZJ1nXEBefDv+IYlhc1BcjJQLTFGBxb1GcKT 9uYp0QOAW0ydSImUb9IY9ggJFpSeniuRQ7ZqSiD7vLyKHgE6ajGAnHWY4HJ9WYKE xg8KQkau/GlaPhqEaoRKEgxkNw12SepCsjvK4ypR9ic0nsOZs4f1KKofhS9e5A/C Rgai5RTkIA7KCu6eK96S3jqj2zDp9VWflocM0MjbN0VlELs1mVO7eEsKcE86jNOH aPGxg==
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=x1X6C23TbjN/DCe4RXjqALTyF/cTJurqg7EGG1v6q 3g=; b=BqBwwKJKUrfn2h+WhsZkLkTyou45byLWgOyc23Pw32atp8vrjd6deWc5p KbHue0KJWq4X16qQ3DMdndWn/12vRZFV6MO6DQjO3Bp/TnLxFdf0dg96h2oYYWW4 lbEWzH8mDmsDZIGZLtn+dUL777ZyBXnlCaO41c0gQIO5Dd61mguSTEq5BzCa9et0 E7TY2a67JDeu7meftKamwRmfg142srDVfdL9z9/9sTKMwarTBU516qXrEniHU8h+ IwxNMECm871YaTueJrcl20lqOohpMvrRTyPj7UuxHLpMtqwIdf/4W3+T01WeQ9Kp rYmd7Pg15wPm9rw96XVHhi+TpveYA==
X-ME-Sender: <xms:2Yx9XAHI4PQ88hW86FY2VfN_nDRTkJudsfSs2V69h5DKsmFNKBoP_Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrfedugddufeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrkedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd
X-ME-Proxy: <xmx:2ox9XA9qLOppK5kbE4mBO9InDMZXsUYxTFrYR3M8_ROpUapIDzSvxw> <xmx:2ox9XHydb_KmTy4-hASYK_qEYXkww1OUtNvDHmX8H409XrnMQ0dsJQ> <xmx:2ox9XMMz4Mr1QDIAM2rZ_KTFJGpb_hw0XodlFV-4ymggrZ-x0QMuWA> <xmx:2ox9XHL-2kkydWHjr4XIq02xsQQOISleafopEgtymDUQXO1n4MYo7A>
Received: from dhcp-10-150-9-156.cisco.com (unknown [173.38.117.80]) by mail.messagingengine.com (Postfix) with ESMTPA id 9FE7B1033A; Mon, 4 Mar 2019 15:38:49 -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: <9A20C483-AE4D-45FB-89D3-C331329AE689@cisco.com>
Date: Mon, 4 Mar 2019 15:38:48 -0500
Cc: John C Klensin <john-ietf@jck.com>, "Livingood, Jason" <Jason_Livingood@comcast.com>, Russ Housley <housley@vigilsec.com>, IASA 2 WG <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F62E491-CE40-4819-923F-72B7F3DA0C41@cooperw.in>
References: <1b58312a-ab8e-ccba-2f9b-884091e1c603@nostrum.com> <27724fb0-25ee-0226-b2ee-2b861a34cbf2@gmail.com> <CFBA6F06-E1A6-4974-9BA0-5DCC1CCCA7AE@vigilsec.com> <AF40B5B2002AE7A55B489999@PSB> <051B5D57-4B47-4D29-83CB-9AA3B3E3A6DE@vigilsec.com> <96A8294B81742974985BE7C8@PSB> <17AB2523-CEB6-4464-8BED-E6B99AFE39A5@rfc-editor.org> <43379A25-D14D-413C-B940-9D135B128724@cable.comcast.com> <2E93E49C-E201-4EDC-91A7-544AFD40FB62@cisco.com> <D110E3546D6957A6CAB14502@PSB> <9A20C483-AE4D-45FB-89D3-C331329AE689@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/wOF8UeCUQatULsHCpOqj28j1kXM>
Subject: Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <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: Mon, 04 Mar 2019 20:38:53 -0000

I have asked to add this to the agenda for the IAB call on Wednesday, March 6.

Alissa

> On Mar 2, 2019, at 1:39 PM, Eliot Lear <lear@cisco.com> wrote:
> 
> 
> 
>> On 2 Mar 2019, at 18:22, John C Klensin <john-ietf@jck.com> wrote:
>> 
>> Eliot and IAB members who are following this,
>> 
>> If the IAB is willing to commit to that RSN, I'll fix the
>> document accordingly.
> 
> I think this way is simpler and cleaner.
> 
>> I'd prefer to not hold up IESG review on
>> this matter or to find time to generate extra drafts so, if a
>> quick IAB commitment is not possible, I suggest I fix the
>> document as Heather and Jason have suggested but encourage the
>> RFC Editor to treat the comment about IAB action as if it were a
>> normative reference, i.e., assuming the IESG actually approves
>> this I-D for publication, they don't actually publish until the
>> IAB's preferences are clear and then, if necessary, we do a
>> touch-up on the document during AUTH48 with confidence that the
>> WG's intent is perfectly clear.
> 
> Yeah, if the RFC Editor doesn’t mind, you can put text in like, [Note to RFC Editor: IAB to fill in their statement here.]
> 
> I also realize that I shouldn’t have proposed specific text. That was a bit forward of me.  The IAB should just consider that a sample that could get the job done.
> 
>> 
>> Does that work for everyone?
> 
> WFM, noting above.
> 
> Eliot
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20

v2.8.7 | Report a Bug | By Email