IETF Logo Mail Archive

Re: [tcpm] 793bis: what to say about source routing

"touch@strayalpha.com" <touch@strayalpha.com> Wed, 01 December 2021 04:44 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9313A0A79 for <tcpm@ietfa.amsl.com>; Tue, 30 Nov 2021 20:44:22 -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 o8zuEz14-MYn for <tcpm@ietfa.amsl.com>; Tue, 30 Nov 2021 20:44:18 -0800 (PST)
Received: from server217-1.web-hosting.com (server217-1.web-hosting.com [198.54.114.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 2EF793A0A62 for <tcpm@ietf.org>; Tue, 30 Nov 2021 20:44:18 -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=2H5WsseExJc55PaOglhcVxb9hIi0afywJy9ITIiNw6k=; b=6fyOn9Y5Ic/GVjkT1hjP64FKKF siWddDJ1Q4Z4Q9TjUbFwgecVkgUA4kgmJiu0MkCoMnLwLJp7y/LFIXKO7UM2WR1PrERQ/SbvpK7OF rOwdRsxDC34ejGWXg37p4wOKNrzEbXHEJyLTU52UbS92C29Mubpa3OKh5mZCrXzLy0Vi3kaEK6/pK FrM83yyB1DrGosLWWsSnIdQyDCl3U29zGbFJtwULDA71BOfsNEEovOgs9BmLXE6DXnGrZgP+EtSYP DaH2wxVzrdYFCJyEE+iT3t2YjgTywU606CN6tsCuKBwGEiiuvAoDrKmwEKoTRsjiRznjOv92b7cb/ Vxp4phrQ==;
Received: from cpe-172-114-237-88.socal.res.rr.com ([172.114.237.88]:59362 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <touch@strayalpha.com>) id 1msHTZ-0033uK-HS; Tue, 30 Nov 2021 23:44:17 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_1FA3E58A-6396-461D-8863-00AAD4235389"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <2095724f-5db8-bcd7-df4e-b655b92d5cf6@erg.abdn.ac.uk>
Date: Tue, 30 Nov 2021 20:44:11 -0800
Cc: Wes Eddy <wes@mti-systems.com>, tcpm IETF list <tcpm@ietf.org>
Message-Id: <6DDF9B1D-7EA4-4B3A-BF8F-7AD8F050E32A@strayalpha.com>
References: <242bd633-0a7b-51dd-9200-3e3360d75e83@mti-systems.com> <E5ACB10A-FB03-4A5C-9862-400E6FB8F4F1@strayalpha.com> <2095724f-5db8-bcd7-df4e-b655b92d5cf6@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
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/tcpm/3hffCN0Qn8CpL06IykAlZMxpLLs>
Subject: Re: [tcpm] 793bis: what to say about source routing
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2021 04:44:23 -0000

Hi, Gorry, 

To me, your final point is the most significant. 

Notably, putting the proposed note in TCP would suggest either that IP source routing is deprecated (it isn’t) or that TCP support for it should be considered optional (it should not) - regardless of whether is deprecated in the future or not.

Joe
 
—
Joe Touch, temporal epistemologist
www.strayalpha.com

> On Nov 30, 2021, at 1:17 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> 
> To me the security concerns are not relevant here - this is a transport spec., and the mechanisms below need to be designed correctly, and while an exmaple or two are good, it seems rather silly to state or enumerate the different sub-transport protocols or their individual concerns.
> 
>

v2.23.0 | Report a Bug | By Email