IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Sat, 02 March 2019 16:26 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 EE355130E57 for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 08:26:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, HTML_MESSAGE=0.001, 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 Mue4cQ5iegNo for <iasa20@ietfa.amsl.com>; Sat, 2 Mar 2019 08:26:47 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6442E128CF3 for <iasa20@ietf.org>; Sat, 2 Mar 2019 08:26:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6712; q=dns/txt; s=iport; t=1551544006; x=1552753606; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=w66iyhLEHempm9jGUYqc4B1d/2RE8yBbPy7CW7CcsQw=; b=PqswvvPmJarZ6DupapWpGJT/5tDVS80Xr57nT+qCojvvKvirxfINj6mk CWvXGUYpgp/H7OlzCqn6jgYWkwyF364ualrEp5DkfhpbaA+2MGPFzQSd4 ibR3LWtP6kgz/NJLfTTmyGhBJFWkKrg0zDIQs/HtYKDeom7tOFOaPiyRA Q=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAAD0qHpc/xbLJq1kGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVAIBAQEBCwGBDYJtJ4QIiHmMd5Iuh24IAwEBhGwChEM3Bg0?= =?us-ascii?q?BAQMBAQMBAwJtKIVKAQEBAQIBI1YFCwsYKgICVwYTgyIBgW0IqUWBL4VEhFU?= =?us-ascii?q?PgS8BgUiJdoF/gTgfgkyICzGCJgKRMJJUCYRPjiUZiniIKpoagm0CBAYFAhS?= =?us-ascii?q?BXSKBVjMaCBsVZQGCQT6QDj4DMJFdAQE?=
X-IronPort-AV: E=Sophos;i="5.58,432,1544486400"; d="asc'?scan'208,217";a="10442878"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2019 16:26:43 +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 x22GQfHo014530 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 2 Mar 2019 16:26:42 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <2E93E49C-E201-4EDC-91A7-544AFD40FB62@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6CA45FF6-73A8-4C5D-9A23-03536B706A75"; 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 17:26:40 +0100
In-Reply-To: <43379A25-D14D-413C-B940-9D135B128724@cable.comcast.com>
Cc: John C Klensin <john-ietf@jck.com>, IASA 2 WG <iasa20@ietf.org>, Russ Housley <housley@vigilsec.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.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>
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/od_U3GBh39NRusw3_5XY4fRcl7c>
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 16:26:49 -0000


> On 2 Mar 2019, at 14:36, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> 
> FYI for the WG – we conferred again with the RFC Editor and this is a rather complicated and arcane situation. She recommended we do the following, which John will be doing in his next revision. That should close this issue and we can move forward.
> 
> 1 – The document should obsolete ***and*** move to historic RFC 3929 and RFC 4633.
> 2 – The document should include text that requests that the IAB move RFC 3716 to historic.

We have crossed streams before.  See RFC 7979 (Russ was a co-author of that document).  There was a note in that document that simply stated:

> 5.  IAB Note
> 
>    The IAB supports the response in this document.



I would propose that the IAB simply agree to a note as follows:


> IAB Note
> 
> With the publication of this document, RFC 3716 is designated as historic.


That way you know that you have the IAB’s support for such an action at the time the document is published, and that you cannot end up in a situation where this document is published and 3716 is not, for whatever reason, not made historic.

Eliot

v2.8.7 | Report a Bug | By Email