IETF Logo Mail Archive

Re: [arch-d] [Int-area] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)

Joseph Touch <touch@strayalpha.com> Fri, 28 February 2020 05:00 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 B5FF83A0F9A for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 21:00:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 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, HTML_MESSAGE=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 lOIdUNH9dWM2 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 21:00:45 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 E143B3A0F97 for <ietf@ietf.org>; Thu, 27 Feb 2020 21:00:44 -0800 (PST)
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=ryHPrxX4yaYVsUMqty3Pwp4djc/BpWMqW7sGkzkpUQ4=; b=IN+0f01EsND2LR83+CBtyJACu cfMOWsR2Y9z0V0gojnM33lZDIZvKmTPqb4JmcbQaOkpBERj05F0FIpZttDDNnq/GquKaHaQH/x+LX liR1H9Cu/hfmEjKqcXVdp1gPRKk1zZNs7ZPxgzlGajyNr8dTJK9QODAbShu9sh3yBwx7apj02JFWL bF85Q9TEqVDcFpE6VcVyGL2SLEu8tSWWPNCg45vh4MxWn/IQy9sSaMYFDsjULFZ1POHCHtQqX7EDM R+jf3un2OcL8LLBIThTFF/Lmt9iZ3N7i3J6D/8PoJSal5iQ/fo+DFtXptIdloZ44KOMjyVPQgMaYF F5MUkw0dg==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:58481 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1j7XlN-0038sp-H6; Fri, 28 Feb 2020 00:00:41 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_629030D3-F615-47EB-B305-E8E6D15101D3"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [arch-d] [Int-area] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <CAMm+Lwj20ZPQzCgOGDVV6mssAb+d4x3HS9S85fLs2TakwJSDuA@mail.gmail.com>
Date: Thu, 27 Feb 2020 21:00:36 -0800
Cc: Keith Moore <moore@network-heretics.com>, IETF Discussion Mailing List <ietf@ietf.org>
Message-Id: <FE5BA819-E1D7-4985-A324-8313F3FCC8EC@strayalpha.com>
References: <876c9105-3da4-e614-2db0-bea025b54663@si6networks.com> <7749f91f-03f1-cc14-bae8-5fe68c88879f@si6networks.com> <CALx6S36wN7VEi_rxLC1ETcTvkGaPhs20KhQrGWAGGTrCL5OT+g@mail.gmail.com> <CAMm+Lwg+4xMv=EKLfvmZMCgrQz31+38Fv0bYKeJ0fTB5vbXiaw@mail.gmail.com> <8d3e7b714666db00e0c05a2e06959da6@strayalpha.com> <CAMm+LwjYeSTro_TJujtRPDfVKtVMg7JbDL6A5V3Tj447c2E7nA@mail.gmail.com> <2e5b51a3-a81b-4e01-03f0-415c92ae5341@network-heretics.com> <CAMm+Lwj20ZPQzCgOGDVV6mssAb+d4x3HS9S85fLs2TakwJSDuA@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
X-Mailer: Apple Mail (2.3445.9.1)
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/E1HuF7_WqvGQoCSdu5JlyhjSxpk>
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: Fri, 28 Feb 2020 05:00:47 -0000


> On Feb 27, 2020, at 5:46 PM, Phillip Hallam-Baker <phill@hallambaker.com> wrote:
> 
> That IPSEC is a failure as a VPN standard is not an opinion, it is a fact. Every VPN vendor developed their own work-around for the AH debacle and as a result, the built in clients in Windows and Mac are rarely able to connect to an IPSEC VPN.

I’ll have to stop using them then. Pity.

> Meanwhile, SSH just works.


See RFC4953, Section 5.3.

Application layer security is not enough.

Joe

v2.23.0 | Report a Bug | By Email