IETF Logo Mail Archive

Re: [Spud] SPUD and anycast... ?!

Toerless Eckert <eckert@cisco.com> Fri, 14 August 2015 11:59 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 297881ACE42 for <spud@ietfa.amsl.com>; Fri, 14 Aug 2015 04:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.517
X-Spam-Level:
X-Spam-Status: No, score=-13.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, PLING_QUERY=0.994, 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 Q2ayVoMOGC0j for <spud@ietfa.amsl.com>; Fri, 14 Aug 2015 04:59:41 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD8E01ACE3B for <spud@ietf.org>; Fri, 14 Aug 2015 04:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1799; q=dns/txt; s=iport; t=1439553581; x=1440763181; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=kwSMrz4WCrG+9iHMMw7FKjEUl+z3kbVE7d7Cr5+Na0o=; b=ZzJeYuespvF1CiXuHCNMZsrx1GGFA9GHnfroEF/sB2Q8N4YZvNfPrDLK HsHdtnrJlgdjJRBwEnkxIqLkEuVbIyBtSsBw0/wmVpTCfxKzpDhrWqc9S cCSZjNlXFXM0Ppkjzbo733lXXjQPj1G+lY0/OrTTE5pwuumoRsNIztf+b U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0APBgDq1s1V/4ENJK1dgxtULTy+BwEJgWsMhXcCgT8MOBQBAQEBAQEBgQqEJAEBBAEBATc0CxALGAklDwUTNhMbiBMN0D8BAQEBAQEBAQEBAQEBAQEBAQEBAQEXi1OFCQeELAWNT4dMjGkDmiQmhB0eM4JMAQEB
X-IronPort-AV: E=Sophos;i="5.15,677,1432598400"; d="scan'208";a="24241656"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Aug 2015 11:59:40 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t7EBxeWl004723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Aug 2015 11:59:40 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 t7EBxd21028404; Fri, 14 Aug 2015 04:59:39 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t7EBxdEQ028403; Fri, 14 Aug 2015 04:59:39 -0700
Date: Fri, 14 Aug 2015 04:59:39 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Message-ID: <20150814115939.GS1667@cisco.com>
References: <20150814070411.GQ1667@cisco.com> <07E2D217-F71A-47DD-850D-F6F21855FBC1@lurchi.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <07E2D217-F71A-47DD-850D-F6F21855FBC1@lurchi.franken.de>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/QODB4KgfbU0KzBlR1tx9d4MV9z0>
Cc: spud@ietf.org
Subject: Re: [Spud] SPUD and anycast... ?!
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: Fri, 14 Aug 2015 11:59:43 -0000

http://www.cachefly.com/2014/07/11/measuring-throughput-performance-dns-vs-tcp-anycast-routing/

Even beyond this easily googled example, i think that anycast TCP is
used quite a bit and on web application you can often just have short
lived TCP connection running completely on the anycast address and just
redirect to a unicast URL when you know it's going to be long-lived (streaming).
So i think the reason why this  may not have come up is because for a good amount
of applications, just ignoring the anycast problem leads to good enough
solutions, and the solutions where this would not work may not had
enough of a business case / working strategy to get this type of extension
forced into TCP.

Cheers
   toerless

On Fri, Aug 14, 2015 at 09:39:57AM +0200, Michael Tuexen wrote:
> > On 14 Aug 2015, at 09:04, Toerless Eckert <eckert@cisco.com> wrote:
> > 
> > Was there ever an extension for TCP or SCTP to "explicitly" deal with
> > anycast, eg: SYN to reponder anycast, SYN-ACK back from responder
> > unicast, but with data field indicating anycast address and nonce from
> > SYN, then ACK back to responder unicast ?
> You can do that with SCTP and dynamic address re-conifguration. Randy
> Stewart and myself discussed this ages ago but never wrote an ID, since
> we didn't see a consumer of the idea.
> 
> Best regards
> Michael
> > 
> > I can't remember / find anything like this right now. WOuld be
> > lovely for SPUD to consier including something like this. Heck,
> > could even do this with multicast and let initiator send ACK
> > back to fastest responder ;-)
> > 
> > Cheers
> >    Toerless
> > 
> > _______________________________________________
> > Spud mailing list
> > Spud@ietf.org
> > https://www.ietf.org/mailman/listinfo/spud

v2.8.7 | Report a Bug | By Email