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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Fri, 14 August 2015 13:19 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 15ECF1A1A79 for <spud@ietfa.amsl.com>; Fri, 14 Aug 2015 06:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.567
X-Spam-Level:
X-Spam-Status: No, score=-0.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, PLING_QUERY=0.994, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 2KhwR0EZ98iy for <spud@ietfa.amsl.com>; Fri, 14 Aug 2015 06:19:04 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF0181A00E9 for <spud@ietf.org>; Fri, 14 Aug 2015 06:19:03 -0700 (PDT)
Received: from [192.168.1.200] (p508F1E60.dip0.t-ipconnect.de [80.143.30.96]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 733281C0C0BCF; Fri, 14 Aug 2015 15:19:01 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <20150814115939.GS1667@cisco.com>
Date: Fri, 14 Aug 2015 15:19:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8C02E01-673A-4F3A-BE91-6F8646CC791F@lurchi.franken.de>
References: <20150814070411.GQ1667@cisco.com> <07E2D217-F71A-47DD-850D-F6F21855FBC1@lurchi.franken.de> <20150814115939.GS1667@cisco.com>
To: Toerless Eckert <eckert@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/mRvgWVw7qh5EuSVxugWJ9Pxdpwg>
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 13:19:06 -0000

> On 14 Aug 2015, at 13:59, Toerless Eckert <eckert@cisco.com> wrote:
> 
> 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
If you want to use anycast with TCP, how do you make sure that all TCP
packets with the same anycast destination address end up at the same host?
For SCTP you would only use an anycast address as the destination address of
the first packet and then the server uses a unicast address. Since SCTP
supports multiple IP addresses and dynamic address reconfiguration, that
is possible. Similar things can be done with MPTCP, but not with TCP.

Best regards
Michael
> 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
>