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

Eliot Lear <lear@cisco.com> Sat, 02 March 2019 18:39 UTC

Return-Path: <lear@cisco.com>
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 5C72E130DC0 for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 10:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 X6WMxgotaX7z for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 10:39:57 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A97C130E2F for <iasa20@ietf.org>; Sat, 2 Mar 2019 10:39:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2219; q=dns/txt; s=iport; t=1551551996; x=1552761596; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=r3VURKYEJFC6u5qfa+261ZHZla5ZXW95GZMP1wFyMgA=; b=KzuYqxDIM8UR9QqoDl+yXiH/Li0++AlpdtuYcTN6kPiWj6RR+WBxLd43 A7CKkCJ9LCsYA/WPxRDhI5aZv8lUX7OZxX+ll97ZfEFts/5vpS22b5J5y 7GNF90SWeLGjr60PV5IUx/wnISQrieK/5+QWYzutYX7EPhrhIOUb4KCQj o=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AJAACTzHpc/xbLJq1kGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUwMBAQEBCwGDRyESJ4QIiHmMd5ghgXsIAwEBhGwChEM2Bw0?= =?us-ascii?q?BAQMBAQMBAwJtKIVKAQEBAwEjVgULCxgqAgJXBhODIgGBbQipOYEvhUSEUw+?= =?us-ascii?q?BLwGBSIl2gX+BEScfgkyICzGCJgKRMJJUCYRPjiUZiniIKpoagm0CBAYFAhS?= =?us-ascii?q?BTgsmgVYzGggbFWUBgkE+kA4+AzCRXAEB?=
X-IronPort-AV: E=Sophos;i="5.58,432,1544486400"; d="asc'?scan'208";a="10504925"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2019 18:39:54 +0000
Received: from [10.61.224.234] ([10.61.224.234]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x22Idrsr010301 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 2 Mar 2019 18:39:54 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <9A20C483-AE4D-45FB-89D3-C331329AE689@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5399ED8C-BFB8-496F-9038-4033F3410C35"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Sat, 2 Mar 2019 19:39:52 +0100
In-Reply-To: <D110E3546D6957A6CAB14502@PSB>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, IASA 2 WG <iasa20@ietf.org>, Russ Housley <housley@vigilsec.com>
To: John C Klensin <john-ietf@jck.com>
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>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.224.234, [10.61.224.234]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/n82s6QTw6S2UIrQKWNxLRj8GLDw>
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: Sat, 02 Mar 2019 18:40:00 -0000


> 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