IETF Logo Mail Archive

Re: [tcpm] RFC793bis draft 14 Reserved Bits

Joe Touch <touch@strayalpha.com> Thu, 12 December 2019 15:09 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 99F5812083C for <tcpm@ietfa.amsl.com>; Thu, 12 Dec 2019 07:09:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level:
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 w-_qCKjhKx4a for <tcpm@ietfa.amsl.com>; Thu, 12 Dec 2019 07:09:03 -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 D5F501201CE for <tcpm@ietf.org>; Thu, 12 Dec 2019 07:09:03 -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: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To: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=XwBaOMPALYo1eTlHBqf0RTvWNc4icD3LtJ4s36I2bJ8=; b=B3CkP8llZXlmaX9BjdbJtTWAS prqFvreENRczWHRTpbNbuduGBpDClzks8fzdYrsP1EQGMobHUPCHbsrAfBtxk8X/qj4rIXxUCtk3E 3UvQMaWWEuf0asg5EjPRJcaHmu4urq6tob6McptsY410xc98RgTHwGYnUGzG1VuVjcv9MHeT/tt03 ynazOEPPaDBpjrXC4+GN1++lmgGGslGh4SakqyBj0hIJUUIfxF6gIg04Um+6T4Hh1uwJf691EWgWg +1TFNcV7ak97m8E2ByoG2leGeLaa0OoQTUwjYqBDkvM09Xcspa2h0NZJi95xHfhRle8Mo4nvk8qvI 7QPQca9dA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:56767 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 1ifQ5K-002cNB-Rt; Thu, 12 Dec 2019 10:09:03 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <a85d6e4a-9a91-b287-a1e4-4288a51fe8a1@bobbriscoe.net>
Date: Thu, 12 Dec 2019 07:08:58 -0800
Cc: Wes Eddy <wes@mti-systems.com>, "tcpm@ietf.org" <tcpm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <35D83F55-0588-4EF7-AD7E-1E52742D93AC@strayalpha.com>
References: <201911280244.xAS2iX3T010083@gndrsh.dnsmgr.net> <991312DB-9503-4253-8C87-3CBCA6AB99F1@strayalpha.com> <77bade9d-f090-9ec7-cc7a-29e4118321ad@mti-systems.com> <a85d6e4a-9a91-b287-a1e4-4288a51fe8a1@bobbriscoe.net>
To: Bob Briscoe <in@bobbriscoe.net>
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/tcpm/be0A9U4movVmUssPH_s0yrX1CT4>
Subject: Re: [tcpm] RFC793bis draft 14 Reserved Bits
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: Thu, 12 Dec 2019 15:09:04 -0000


> On Dec 11, 2019, at 10:12 AM, Bob Briscoe <in@bobbriscoe.net> wrote:
> 
> Wes,
> 
> On 04/12/2019 14:59, Wesley Eddy wrote:
>>> Perhaps further explicitly: 
>>> 
>>> they MUST be ignored by the network and MUST traverse the network unchanged 
>> 
>> 
>> This clarification seems good to me, and it looks like everyone who's chimed in so far agrees, so I can put it into the upcoming revision. 
> 
> I think it's important to make this a requirement for middleboxes as well as just 'the network'. Where I would define middlebox as a function acting on L4 (TCP) fields without being a full implementation of TCP.

RFC1812. ;-)

> I know some middlebox developers will ignore it. But their customers (operators) cannot require middleboxes to comply with IETF spec's if we don't write what middleboxes should do in our specs.

That hasn’t helped in the past. Laws for the lawless aren’t productive.

Joe

v2.23.0 | Report a Bug | By Email