Re: [tcpm] 793bis: what to say about source routing
"touch@strayalpha.com" <touch@strayalpha.com> Fri, 03 December 2021 15:38 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 0EE913A0B5B
for <tcpm@ietfa.amsl.com>; Fri, 3 Dec 2021 07:38:18 -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 xg6Ai7rr0s4v for <tcpm@ietfa.amsl.com>;
Fri, 3 Dec 2021 07:38:13 -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 8B3E03A0B51
for <tcpm@ietf.org>; Fri, 3 Dec 2021 07:38:13 -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=GL+3a8KiS5u+HyHNB5pNh6y1Cx+/JNgQA18hL+Kn3OU=; b=df+S2jlVrat73SUnuH3LetE2Xo
4ed8j3CVuC+jbsQWDUNTgYkP7dF6V/bh4JWxf1IFDrkOHDJj3v/LEMFyw0IQIrYzncvIVnm90r1UV
REzL1JaSUY7GQx1R5YnfiS3XrDWE2CxuiIAeQLHp30Rne+7qqB6gJ878obwr7pcmGEMWGkfdlxmwp
By9c/sFSuXd9hDxmALTQ2+KBRHRAWJWf/0INNHDGD8Xmr6BvEiJHFfK2jNAS6802CsW6HdOPL1Jb3
u9Iw/RZBF1zClUeeHnTvyoPKs9kxeTtADKxQSlFtTNInV4aJe723hCzZ5pl0lC2Jfc1JpnfjPO3xu
MY1bMMxw==;
Received: from cpe-172-114-237-88.socal.res.rr.com ([172.114.237.88]:51985
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 1mtAdT-00EsJv-Az; Fri, 03 Dec 2021 10:38:12 -0500
Content-Type: multipart/alternative;
boundary="Apple-Mail=_499B18CA-E2A4-43B1-8C0D-CFECA74885AA"
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: <a7e99870c6584f9daf38f9d6312e8c99@hs-esslingen.de>
Date: Fri, 3 Dec 2021 07:38:05 -0800
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>,
tcpm IETF list <tcpm@ietf.org>
Message-Id: <FE9149CC-79BA-4501-A074-981F58A20EB6@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>
<6DDF9B1D-7EA4-4B3A-BF8F-7AD8F050E32A@strayalpha.com>
<a7e99870c6584f9daf38f9d6312e8c99@hs-esslingen.de>
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
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/96arjPW7x9pf4fr3a6V46q5siCY>
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: Fri, 03 Dec 2021 15:38:18 -0000
Hi, Michael, Although *use* of source routing with TCP is optional, *support for* source routing is not. Source routing is not deprecated for IPv4 and we should not imply support for it in TCP is optional in any way. TCP isn’t deciding whether to use source routing, so this doc has no rationale for warning about whether source routing is enabled or not. Joe — Joe Touch, temporal epistemologist www.strayalpha.com > On Dec 3, 2021, at 2:51 AM, Scharf, Michael <Michael.Scharf@hs-esslingen.de> wrote: > > Hi all, > > The existing 793bis test already implies that use of source routing is optional, since it starts with an if-clause. > > For what it is worth, I think that we could add a comment along the lines of „source routing may be disabled or unsupported on some systems“ to make this more explicit. I don’t see much harm in such an informative statement. If we go down this route, IMHO the 793bis spec does not have to discuss why stacks implement or don’t implement features below TCP. > > Having said this, I don’t see a strong need for any additional wording. I just don’t object to a brief note. > > In any case, as long as there is no other PS or BCP guidance, the normative statements in 793bis should not change 1122. > Michael (with no hat whatsoever) > > > From: tcpm <tcpm-bounces@ietf.org <mailto:tcpm-bounces@ietf.org>> On Behalf Of touch@strayalpha.com <mailto:touch@strayalpha.com> > Sent: Wednesday, December 1, 2021 5:44 AM > To: Gorry Fairhurst <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> > Cc: tcpm IETF list <tcpm@ietf.org <mailto:tcpm@ietf.org>> > Subject: Re: [tcpm] 793bis: what to say about source routing > > 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 <http://www.strayalpha.com/> > > > On Nov 30, 2021, at 1:17 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk <mailto: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. > > > _______________________________________________ > tcpm mailing list > tcpm@ietf.org <mailto:tcpm@ietf.org> > https://www.ietf.org/mailman/listinfo/tcpm <https://www.ietf.org/mailman/listinfo/tcpm>
- [tcpm] 793bis: what to say about source routing Wesley Eddy
- Re: [tcpm] 793bis: what to say about source routi… touch@strayalpha.com
- Re: [tcpm] 793bis: what to say about source routi… Gorry Fairhurst
- Re: [tcpm] 793bis: what to say about source routi… Mirja Kuehlewind
- Re: [tcpm] 793bis: what to say about source routi… touch@strayalpha.com
- Re: [tcpm] 793bis: what to say about source routi… Scharf, Michael
- Re: [tcpm] 793bis: what to say about source routi… touch@strayalpha.com
- Re: [tcpm] 793bis: what to say about source routi… Scharf, Michael
- Re: [tcpm] 793bis: what to say about source routi… touch@strayalpha.com
- Re: [tcpm] 793bis: what to say about source routi… Scharf, Michael
- Re: [tcpm] 793bis: what to say about source routi… touch@strayalpha.com
- Re: [tcpm] 793bis: what to say about source routi… Rodney W. Grimes