IETF Logo Mail Archive

Re: rfc791 coming up to 40 years ... what to do (remember, celebrate, ...?)

Joseph Touch <touch@strayalpha.com> Thu, 25 March 2021 17:28 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A2063A283F for <ietf@ietfa.amsl.com>; Thu, 25 Mar 2021 10:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.2
X-Spam-Level: *
X-Spam-Status: No, score=1.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HAS_X_OUTGOING_SPAM_STAT=2.517, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 SoC6vdFuFa0r for <ietf@ietfa.amsl.com>; Thu, 25 Mar 2021 10:28:22 -0700 (PDT)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (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 1F5813A29EB for <ietf@ietf.org>; Thu, 25 Mar 2021 10:27:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ZId0spvPbnyofUSK0Gs7fI8NDttZhsCt5ZEdc+Xy0sk=; b=E9tqpkBPVzJ2OkEfQ7si1JgB4 v8TMQEyuOObWdxWwJ/1K2XScdaqrcMJhIK/zzXTsMMyVOz5cxFcZfLMp3lxUzYRfFiAaZu1xBuBmA XZloOJ7niQbK/YPEB13fJriuYCY4Nl3Pa0EXYa6EzwQmo8OQHeZmioXrhS+xYvd5Co2omOKij4pTK rHxGvhbT1/qXH1IlnRAuKtzhfT0Z83jfkTQWNFlXxUr12QWU8i7xeTjt9BVaZpU8gqMD8RWloJXlU 7duFffbEwBw6yDQy00fxut7NQvk5YGus3Pfb24Us9DkcoZhRCdEY44JYf3EoC3O2+Ej3hOVrex0G2 ltJEcEnXQ==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:53012 helo=[192.168.1.14]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from <touch@strayalpha.com>) id 1lPTlr-002w2O-4O; Thu, 25 Mar 2021 13:27:51 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_0B12E027-F852-4D1A-B6CC-26B8F2F72A75"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Subject: Re: rfc791 coming up to 40 years ... what to do (remember, celebrate, ...?)
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <fb74de0d-78dc-c304-b6ee-97bd947b58b1@mtcc.com>
Date: Thu, 25 Mar 2021 10:27:45 -0700
Cc: ietf@ietf.org
Message-Id: <868F6240-A0DB-4791-9885-864F82B33DE5@strayalpha.com>
References: <4c4460b9-5074-a320-6ebb-8b537f4c22a2@network-heretics.com> <A5F380FA-FB87-46CB-9D77-1FDB4453E8BD@strayalpha.com> <CAC8QAcfLqmf8Hq22fr6SQQxGj7i9p4n0i=WG1fUBX9hnHwT55Q@mail.gmail.com> <CAMm+LwjunKat1rp9QgkmZEKrp0zUAzPDL8Mp35f6saX5dyzu7g@mail.gmail.com> <35816c08-3375-94a4-33d3-f0b2e3eca895@mtcc.com> <2119081b-c04e-2ff8-0530-11c96cc1c74f@network-heretics.com> <baa0a47f-d7b1-85f9-30a5-5eebf9becb4e@mtcc.com> <F1A84553-90BA-4E7F-9B89-7FBA9762C30F@strayalpha.com> <fb74de0d-78dc-c304-b6ee-97bd947b58b1@mtcc.com>
To: Michael Thomas <mike@mtcc.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/94EX7qovE8BMTFJ7KJHWmYlbf7U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2021 17:28:27 -0000


> On Mar 25, 2021, at 9:44 AM, Michael Thomas <mike@mtcc.com> wrote:
> 
>> IMO, what IPsec got wrong was tunnel mode; it should have just been transport mode and IP-IP tunneling (RFC 3884 explains why).
>> 
> From a separation of concerns, I would agree. It's really a shame that IPSec turned into a VPN tunneling solution. Didn't GRE and all of that exist back then?

GRE docs in the IETF go back to RFC1701 in Oct 1994, originating as drafts in Sep 1993.

IPsec docs in the IETF go back to RFC1825 in Apr 1995, originating as drafts in Feb 1995.

So strictly, IPsec seems to have followed GRE. But GRE isn’t a replacement for IPsec; it’s a shim tunnel layer that is more comparable to IP-IP tunneling, e.g., RFC2003 in Oct 1996, which dates back to July 1995 - but even that is just a variant of RFC1853 in Oct 1995 (whose draft origins are not available AFAICT).

So IP encapsulation predates IPsec; merging it inside IPsec is the problem; combining the two is fine.

Joe

v2.23.0 | Report a Bug | By Email