Re: [IPsec] graveyard: deprecate->historic

Benjamin Kaduk <kaduk@mit.edu> Mon, 13 January 2020 06:35 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B31AD120073 for <ipsec@ietfa.amsl.com>; Sun, 12 Jan 2020 22:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 MVNyR6I1Y5Kz for <ipsec@ietfa.amsl.com>; Sun, 12 Jan 2020 22:35:48 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7427B120088 for <ipsec@ietf.org>; Sun, 12 Jan 2020 22:35:47 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 00D6ZgdD018597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 13 Jan 2020 01:35:44 -0500
Date: Sun, 12 Jan 2020 22:35:41 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Dan Harkins <dharkins@lounge.org>
Cc: ipsec@ietf.org
Message-ID: <20200113063541.GB66991@kduck.mit.edu>
References: <A8FABB55-C89E-4DDE-88CA-9A5839E023B2@sn3rd.com> <20191223184651.GC35479@kduck.mit.edu> <a0ac2861-d106-a464-be49-53fcc3dc802a@lounge.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <a0ac2861-d106-a464-be49-53fcc3dc802a@lounge.org>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/hueDL_HfEdgnmZ1s3r7u0Y767yY>
Subject: Re: [IPsec] graveyard: deprecate->historic
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2020 06:35:50 -0000

On Fri, Jan 10, 2020 at 12:01:39AM -0800, Dan Harkins wrote:
> 
> 
> On 12/23/19 10:46 AM, Benjamin Kaduk wrote:
> > Since we're in pedantic process mode...
> [snip]
> > Perhaps something like "IKEv1 is no longer relevant for Internet
> > systems" would work, though I suspect we could even get away without such
> > an intro sentence and just dive in straight with "Systems running IKEv1
> > should be upgraded and reconfigured to run IKEv2.
> 
>    See that's the thing. There is nothing compelling to force the change 
> away
> from "no longer relevant" so people still use it. If there was something
> compelling to make people want to change we wouldn't be forced to do this,
> sigh, die die die nonsense. Perhaps, "we're the IETF and we are really
> serious now". That should dispel all doubt in whoever happens to read this
> RFC. That way we won't need a die die die die or a die die die die die die.

I'm only aboue 95% sure I'm parsing you properly -- you're saying that if
there was a clear reason to move from IKEv1 to IKEv2 the market would have
done it already and we wouldn't be bothering with a doc like this?  That
is, that what we're really doing is akin to "we're the IETF and we
pinky-swear that we're not going to touch this anymore" as opposed to "here
is a list of the ways that using IKEv1 is going to bite you"?

Thanks,

Ben