IETF Logo Mail Archive

Re: New Plaintext QUIC-LB Design

Christian Huitema <huitema@huitema.net> Tue, 12 January 2021 00:52 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9803A0A2D for <quic@ietfa.amsl.com>; Mon, 11 Jan 2021 16:52:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level:
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=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 tVJ5PC8uBmMH for <quic@ietfa.amsl.com>; Mon, 11 Jan 2021 16:52:31 -0800 (PST)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2BA73A0A2C for <quic@ietf.org>; Mon, 11 Jan 2021 16:52:31 -0800 (PST)
Received: from xse127.mail2web.com ([66.113.196.127] helo=xse.mail2web.com) by mx133.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1kz7v9-000bfh-Nx for quic@ietf.org; Tue, 12 Jan 2021 01:52:29 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4DFBqv0Rmhz2C1t for <quic@ietf.org>; Mon, 11 Jan 2021 16:52:27 -0800 (PST)
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1kz7v8-0001S6-VS for quic@ietf.org; Mon, 11 Jan 2021 16:52:26 -0800
Received: (qmail 10401 invoked from network); 12 Jan 2021 00:52:26 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.58.43.253]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 12 Jan 2021 00:52:26 -0000
Subject: Re: New Plaintext QUIC-LB Design
To: Martin Duke <martin.h.duke@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
References: <CAM4esxRRp5=-YvcPsCdsgB=8O=_RAXq05Ldma0smGsjy95T4=g@mail.gmail.com> <6B05568D-1905-4416-904C-2EEC25491920@gmail.com> <CAM4esxSyn7uEiUsYvtiUbQ=4Qt-Bp+yLYBK+re+a+V3ea0BjcQ@mail.gmail.com> <B4D950F6-452A-4CFC-9707-DC1C9B3AB49B@gmail.com> <EB8897FC-1A57-4C45-ABDE-B87E36E519E8@gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <03ba27b1-3d27-d66b-4fc0-a952c24c993d@huitema.net>
Date: Mon, 11 Jan 2021 16:52:25 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <EB8897FC-1A57-4C45-ABDE-B87E36E519E8@gmail.com>
Content-Type: multipart/alternative; boundary="------------2E8089C9C415D84D030DB18A"
Content-Language: en-US
X-Originating-IP: 66.113.196.127
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.127/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.127/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x6h2yQpzTslcOqazQkKtAFKj/EwzSHE5FGYwwjsNRPCIR+ WPYs0hlxiN3VMzptG3rmD6wdmZPcItWbGe10hXJtyz/MWLF6jnm7fdxjsJMmvwzR/hTGZT+Rq3LO Lr56rGrocJZHhVJQHybQm8TwmCKQE5LN1n8YXzQY0mQUNzTGA6mwRNpj5snmK3jmyZjmm2JH3v3Q 7PQeNoNQjwiv3IhNPpDsdaHHqGG7YXgprtn5XLToE7g5LY8o1a6sSJrLl3xdARnv/HGR54G9CHRY hyVqYO/Ae1h1hLGGi4ebv387hThA9A+LrmkGouiRB8qN/5RbHDa6yUUKFnWNneAcuva3BS+iyyNq bT8dUMXMJ4tUCMj6G37ZfAMLceP5aNHPt26RBupu5v1nytoNnc138GfEJRQ2qC7jjynPIHPNqSn4 QTXUjLjYWQt1/5xnQymMoPsgr/U0flMcy2Vi/IcBgY4arPaiJ1W6hAyiRC61jekdwIcXNugoOEbH RyFULpSjm7jZ1h/HfDRQ5Ig8VhPsPE8NaP2gA77cO7WeI9Ftai6fuu3WSgTJtuWU4E6Qe14xEdAk TI7I3UUls3xR8IUuLrJe2JUne37EdXOqrRyXv4wznvGlnAQGJ8gHIt0bedp1TN411lqdy1V/0aEk MCdb3YpWUo4/+EUytKrR9Md9I2Rs1wKt5Jpxta3N/bYE1rWTw6BPCC/cRgvQKtcrMMueERx3sXaw gKLRDa2hpOTsYKstn//cN1ofy54FG+n/EgzVYuaIaIzNoZzswxuMaWjBAlpwaPiCX3fE65K5+XOI mO43vvUf9oDBqtClgM5jH/om1Q5UomG0v+rwIiID/kwKc8V5Tj9+FRkaOS/DNjANmb8tO61SbYdY AwdpaVzHW7wHO7YhEWyJzIkwSFAW0Pw8uiKeubcolFl/rX+2ReQklqJDASQX2Id+W5hjJNcdGs0+ iHjXODmj5PX/tZQU3bYnWKpb
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/LMaFalSLLS2acWt7h__AP3J-GV8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 00:52:33 -0000

I am looking at the text of section 4.2, and I am not sure how I would 
implement that. What should be the value of the config rotation bits in 
CID created by the server? Should the 6 other bits in the first octet be 
set to a CID Len or to a random value? Is the timer set when the server 
ID is first added to the table, or is the timer reset each time a packet 
is received with that CID? In the latter case, is it reset when any 
packet is received, or only when a "first initial" packet is received?

-- Christian Huitema

On 1/11/2021 4:14 PM, Mikkel Fahnøe Jørgensen wrote:
> Sorry, the following text is out of context - it was a suggestion that 
> I decided not to persue.
>
>> On 12 Jan 2021, at 01.10, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com 
>> <mailto:mikkelfj@gmail.com>> wrote:
>>
>> If the DCID is not understood by the LB, the LB chooses a random 
>> target server but does not store any state. The expectation being 
>> that the server will assign its own DCID on the return path.
>>
>> The LB will understand how to route the server assigned DCID. The 
>> problem being that this generally requires shared state - which 
>> Low-Config aims to avoid in exchange of local state.
>>
>

v2.23.0 | Report a Bug | By Email