IETF Logo Mail Archive

Re: [Spud] Connect and ACK Bits: Why?

Toerless Eckert <eckert@cisco.com> Mon, 13 July 2015 17:25 UTC

Return-Path: <eckert@cisco.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A670B1B2C9E for <spud@ietfa.amsl.com>; Mon, 13 Jul 2015 10:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 fWSTbX-Odp27 for <spud@ietfa.amsl.com>; Mon, 13 Jul 2015 10:25:40 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B1AF1B2C9D for <spud@ietf.org>; Mon, 13 Jul 2015 10:25:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1722; q=dns/txt; s=iport; t=1436808340; x=1438017940; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=a2qLEITmJGp3x188A27MYXsLTpRrnj7+NBIGhqGtVh0=; b=X6KGHVyrru8JC0wIOvMyoBcenRr7upUS3YOL+Kjl3ReQVM0tb66jkoPQ xZAam+uxu1KaJjjd5hO/SKMdt/QNcrB+12xlo1cxOevaJyUfln7QeaD1u h0eraFH3BcnbrGxdRKzv2q5+7KaWJ0oxwNLDxqHT2jbqMCTqgZfzAAXkF s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BfAwBP86NV/5JdJa1bgxNUabtDCYFqCoV3AoE8OBQBAQEBAQEBgQqEIwEBAQQBAQEvATsLDAQLFQMJDBIHDwUTHxcTiC4NywkBAQEBAQEBAQEBAQEBAQEBAQEBAQETBItMhQYHCoMNgRQFjRyHFYwDAZhrJmODOB4xgksBAQE
X-IronPort-AV: E=Sophos;i="5.15,464,1432598400"; d="scan'208";a="15004261"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-2.cisco.com with ESMTP; 13 Jul 2015 17:25:40 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t6DHPc3U018241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jul 2015 17:25:39 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t6DHPcm8013146; Mon, 13 Jul 2015 10:25:38 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t6DHPbLA013145; Mon, 13 Jul 2015 10:25:37 -0700
Date: Mon, 13 Jul 2015 10:25:37 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Christian Huitema <huitema@microsoft.com>
Message-ID: <20150713172537.GF23837@cisco.com>
References: <CANJ8QndAWK1ErRsUNAUHkA00aA5xzFsaQHiArCaN9jr64qCSnQ@mail.gmail.com> <FD304957-E34A-4CA5-B05A-3394D9062F1D@tik.ee.ethz.ch> <DM2PR0301MB06551595B03037418CD24D75A89C0@DM2PR0301MB0655.namprd03.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <DM2PR0301MB06551595B03037418CD24D75A89C0@DM2PR0301MB0655.namprd03.prod.outlook.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/_oiM-KhFwprQ00zv7HnJjx6M6xg>
Cc: Jacob Chappell <chappellind@gmail.com>, Mirja =?iso-8859-1?Q?K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "spud@ietf.org" <spud@ietf.org>
Subject: Re: [Spud] Connect and ACK Bits: Why?
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2015 17:25:41 -0000

Route changes:

the middleboxes of interest are setup so that route-changes don't
matter, eg: eithre single point of failure or chassis redundancy or
the like.

Teardown:

Explicit teardown in TCP doesn't seem to be bad enough of a
problem that TCP was changed, right ? And it is sen as valuable by
middlebox vendors. 


On Mon, Jul 13, 2015 at 05:19:54PM +0000, Christian Huitema wrote:
> 
> 
> > -----Original Message-----
> > From: Spud [mailto:spud-bounces@ietf.org] On Behalf Of 
> > On Monday, July 13, 2015 5:10 AM, Mirja Kühlewind wrote:
> > ...
> > As described above it???s more about network state then client state. However,
> > you probably will always need timers because you can never be sure that certain
> > information will be delivered. However, if you can get more explicitly signals
> > (and that???s why we also would like to have a SPUD finish/stop packet) you can
> > assist network nodes as well as end host to e.g remove state quicker  and maybe
> > also use SPUD to set timer values correctly (see the use case draft).
> 
> We have to account for possible route changes, without the endpoint being aware. That means that the first packet visible on the new path will not be the first packet end-to-end. This is a strong argument for NOT relying on an explicit "Start" flag. 
> 
> Then there is the flip side that any explicit signal STOP can be spoofed, which enables DOS attacks. On the other hand, "absence of traffic" cannot be easily spoofed.
> 
> -- Christian Huitema
> 
> 
> _______________________________________________
> Spud mailing list
> Spud@ietf.org
> https://www.ietf.org/mailman/listinfo/spud

-- 
---
Toerless Eckert, eckert@cisco.com

v2.8.7 | Report a Bug | By Email