Re: Redirection to Other IP Addresses

Bin Ni <> Thu, 01 August 2019 08:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3776B1200C5 for <>; Thu, 1 Aug 2019 01:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_VISITOURSITE=2, HEADER_FROM_DIFFERENT_DOMAINS=0.201, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9f0g6WybN_RY for <>; Thu, 1 Aug 2019 01:53:18 -0700 (PDT)
Received: from ( [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3133A1200B1 for <>; Thu, 1 Aug 2019 01:53:18 -0700 (PDT)
Received: from lists by with local (Exim 4.89) (envelope-from <>) id 1ht6nH-000872-8n for; Thu, 01 Aug 2019 08:50:39 +0000
Resent-Date: Thu, 01 Aug 2019 08:50:39 +0000
Resent-Message-Id: <>
Received: from ([2603:400a:ffff:804:801e:34:0:4c]) by with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <>) id 1ht6nE-00086D-F1 for; Thu, 01 Aug 2019 08:50:36 +0000
Received: from ([2607:f8b0:4864:20::933]) by with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <>) id 1ht6nA-000441-MJ for; Thu, 01 Aug 2019 08:50:36 +0000
Received: by with SMTP id j8so28080167uan.6 for <>; Thu, 01 Aug 2019 01:50:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FjpeCuyIIr+yv/bCj4yuZZRSV650No2v9QX/lzHcR+A=; b=A/tyQQHwsQEkDO4Vmh+6WxIaLjvA3FtGZNkd2CFY5b40lKiVM3x/XNu+8kxiKAizZH eBuMdkubwzPIIia1lY30NsD7ngSBVWI3cVaos3u1AZz8oZdpUe9nM1WJbRHaY1p1Xf1E ilUA+vZGn8uybhVy4UIi3qkqnrtwm+Oe1jW/Q1Ps4IVk2X/7FJn9u752BaEryNmxivBs eCOb/RA/FolGYuUzJ9//wi2JO+ox9uAw5RG/kiLc50IyJ5yriynELP8rDaS6ML73Sb3b LriZkSsU3tWASzErRBb6oGk6UhNccilEhERASUg8CnC+X8ib8hGU2njbP7XQrRfyhYzp irSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FjpeCuyIIr+yv/bCj4yuZZRSV650No2v9QX/lzHcR+A=; b=LdhpbPCSYaN/bhngUcO1WOlX8BOOMVyHk4ZIrhDjOLQ3IBwAora612mzffYVOd5imI arQ6H4DCORUnSVhrthSxxBG+8luOxoJGvU/m+S2WGN4GP4a1OA/jn1q69A4WDb8j/Kxr R+U73lBxacr1jBB31M1Ig+L6vGUJZwQOWMV2VaAgLzWAEHjKCeJc3NoQ4wV5D+/lEKzX us/US6GTYP2sI10a4hARtl9iJIo+4/VTqsPWk9MYcSBNqRacNr+z6x1xOIVJoH37+exv e4VsBx4sl5D2FESVqKQtq3OT5CCAsPD5occfk0D/5yB6W6NHtKB44fpWopv+IV+UF8IW VVPg==
X-Gm-Message-State: APjAAAVJfhcH32pscv2rlDwD6+GOYYZlwRaUgcPZy2S4n9sA+PCI4WO9 2tiWBcznVyLEyP5lxekx780MuSkJe+lMvR9uX4pf1A==
X-Google-Smtp-Source: APXvYqzA/eD9tUBsaHJ1UCqsDmaR6sutqOmZiqSUa3+HNg+j8DLvUvoguuQXxxWnLYfWAaSnVPQ26Z92SmfpcIkh2mU=
X-Received: by 2002:ab0:168a:: with SMTP id e10mr33545527uaf.87.1564649409897; Thu, 01 Aug 2019 01:50:09 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Bin Ni <>
Date: Thu, 1 Aug 2019 01:49:58 -0700
Message-ID: <>
To: Daniel Stenberg <>
Cc: Jack Firth <>, Chris Lemmons <>, Amos Jeffries <>, HTTP Working Group <>
Content-Type: multipart/alternative; boundary="000000000000468abd058f0a54f3"
Received-SPF: pass client-ip=2607:f8b0:4864:20::933;;
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=0.477, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1ht6nA-000441-MJ 0fadb5792d360d20620797478c25a8aa
Subject: Re: Redirection to Other IP Addresses
Archived-At: <>
X-Mailing-List: <> archive/latest/36913
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

Let me try to explain my proposal with some human language :)
1. the "Alt-Svc" behavior:
Client: Hi Server-, can you send me the movie XXX?
Server- Here is the movie, but next time, you'd better ask server for this movie.
(It then took 2 hours to deliver the movie)
2. my proposed behavior:
Client: Hi Server-, can you send me the movie XXX?
Server- Sorry, I can't give you the movie, you need to ask server for this movie.
Client: Hi Server-, can you send me the movie XXX?
Server- Here is the movie.
(It then took 0.5 hours to deliver the movie, because server- is
closer to the client, or less loaded)


On Thu, Aug 1, 2019 at 12:56 AM Daniel Stenberg <> wrote:

> On Thu, 1 Aug 2019, Jack Firth wrote:
> > Yes you could make a status code, but I don't follow why you need a new
> > status code instead of reusing a generic 300 response with body
> explaining
> > they need to follow Alt-Svc. A special status code requires clients to
> > implement new behavior, and if they're doing that already can't they just
> > implement Alt-Svc support instead?
> No, because Bin wants to (as I understand it) force the next request that
> uses
> that origin to *forcibly* use the new alternative IP address. I'm pretty
> sure
> most alt-svc implementations will not do that but will rather reuse
> existing
> connections (since the spec allows that and it is much faster) and then
> switch
> to the alternative only once a connection to that has been setup...
> --
>   /


Bin Ni
VP of Engineering
[image: Quantil]

Connecting users with's that simple.

Office: +1-888-847-9851 <(888)%20847-9851>

[image: Tweeter] <>  [image: Google Plus]
<>  [image: Linked In]

The information contained in this email may be confidential and/or legally
privileged. It has been sent for the sole use of the intended recipient(s).
If the reader of this message is not an intended recipient, you are hereby
notified that any unauthorized review, use, disclosure, dissemination,
distribution, or copying of this communication, or any of its contents, is
strictly prohibited. If you have received this communication in error,
please reply to the sender and destroy all copies of the message. To
contact us directly, send to QUANTIL, INC. at 1919 S Bascom Ave #600,
Campbell, CA 95008
or visit our website at <>