IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Mon, 13 July 2015 17:50 UTC

Return-Path: <lear@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 555A31B2CD0 for <spud@ietfa.amsl.com>; Mon, 13 Jul 2015 10:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level:
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, 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 kIN5AZw__sZ0 for <spud@ietfa.amsl.com>; Mon, 13 Jul 2015 10:50:00 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7501A1B2CC3 for <spud@ietf.org>; Mon, 13 Jul 2015 10:50:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1812; q=dns/txt; s=iport; t=1436809800; x=1438019400; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=ppQQa5A2ce3eJdGqHPrZxHqddfaMIWJi3fDLV6Zz4n0=; b=B6grLV9dKMjrNqareuG7u+quvVsgLGMziUlANQI3nnnwXHmNnFXW3BDH 6253NBpOsetYyivXrzzJlrQjtM9qFtqq+XMsRn9/LGoGj2zPlB9zeTOjR CfToe0W7psD9AN1C7SnBB/26SmawGPTnicfV3C0TzolrLzc+rVe+hDhQ+ k=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DOBACj+aNV/xbLJq1bhFCDI7gph2sCgXYSAQEBAQEBAYEKhCMBAQEEI1UBDAQLFQMJDAoIAwICCQMCAQIBNBEGAQwBBQIBAYgqtSOWDgEBAQEBAQEBAQEBAQEBAQEBAQEBAReLTIUGBwqCXoFDAQSUMYItgVSIA4hEkCcmY4MaPDGCSwEBAQ
X-IronPort-AV: E=Sophos;i="5.15,464,1432598400"; d="asc'?scan'208";a="564797890"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 13 Jul 2015 17:49:58 +0000
Received: from [10.61.88.14] (ams3-vpn-dhcp6159.cisco.com [10.61.88.14]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t6DHnwHn004595; Mon, 13 Jul 2015 17:49:58 GMT
Message-ID: <55A3FA44.9010402@cisco.com>
Date: Mon, 13 Jul 2015 19:49:56 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>, =?UTF-8?B?TWlyamEgS8O8aGxl?= =?UTF-8?B?d2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>, Jacob Chappell <chappellind@gmail.com>
References: <CANJ8QndAWK1ErRsUNAUHkA00aA5xzFsaQHiArCaN9jr64qCSnQ@mail.gmail.com> <FD304957-E34A-4CA5-B05A-3394D9062F1D@tik.ee.ethz.ch> <DM2PR0301MB06551595B03037418CD24D75A89C0@DM2PR0301MB0655.namprd03.prod.outlook.com>
In-Reply-To: <DM2PR0301MB06551595B03037418CD24D75A89C0@DM2PR0301MB0655.namprd03.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kgNttGWeCh3iD3k3tMEMfSuc9eKSUJus0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/wTKYQy2lkVDG2PoJw4tFpslT3DY>
Cc: "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:50:02 -0000


On 7/13/15 7:19 PM, 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. 

Unless p2a informs the a of the change.

Eliot

v2.8.7 | Report a Bug | By Email