IETF Logo Mail Archive

Re: draft-duke-quic-load-balancers-00.txt

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Tue, 13 February 2018 21:55 UTC

Return-Path: <dtikhonov@litespeedtech.com>
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 91A1D12711B for <quic@ietfa.amsl.com>; Tue, 13 Feb 2018 13:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.com
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 gQgcC2dp23Jb for <quic@ietfa.amsl.com>; Tue, 13 Feb 2018 13:55:00 -0800 (PST)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B85BD12D954 for <quic@ietf.org>; Tue, 13 Feb 2018 13:55:00 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id z197so7428582qkb.6 for <quic@ietf.org>; Tue, 13 Feb 2018 13:55:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=A+30DrWOuVmphAk86QPSVewnS3FFP0p/v56aM8nb130=; b=hypUcb/aNFSl1aicMHEgVpSpdeIlknw4eSCrqAbp7rPBgfPXW1NBjrm8W/6F2PLzqY ty9r7A3Zz5350ZKLWQpsIlff7hBnSzV47q85Qv4sA3fNzyKcjgANRq81z+d3n5YgjnpH oZE2nXToOorEsAp0IQrMvEkyAjpmkLOVmV5WQwjG613Twgsx3v6EiENLcaIWw2ngAKub oS/EJbfa/6Cz+XRyZ3GbJNtICp10vccFHVaB8z/8xZjQ+ilf9pbBqFBxd5yGzy07uL6g 46SINRM4vmxldqgAizOuQW+rnAorEjoSkkAg42pCr2cjV3P8Fp+ExhDL/9yQJw8Y382M 6biw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=A+30DrWOuVmphAk86QPSVewnS3FFP0p/v56aM8nb130=; b=XKUYSOeseTZSsk0lhdYGRSCd3HsYGbqqHhRJm2X56o4Eugq02eP0ObW0o4B3RWV8uV qa0WHDc6uhAEguJ6NJYL7ytkz6Y93osdJhowkdF7Fg+syH7LCPhUzQrpHH3qpddCYQbj N3HtJrfbORRs/rsILnhySFAZS/dJOIaMXpSMDspvSFuzq6fSgNsvAo7yZdR3edzRTIqo 6Vcf+t2qoUs0106KWiWS1fNIc42QVnDKxNlTlfxSNRSVkpgz7Hocn3ZR7eVTfVQSh0SY JQhsVbuN3N0+dLv6plTKgm+bzuIeseN7Z53mzZiergZK2czyQbHi/rLAjEK1HCw9WWjY ZbuA==
X-Gm-Message-State: APf1xPAWmebWPjJ/PzaBFkOb/2w7SdQrBIdbGE1lUVCBAhO+68tZx9PG Aa9BtcatLpptBMIeo3Tr6x34Ew==
X-Google-Smtp-Source: AH8x226+woLIR4ZmMJtpFo6eA+Xkl6kkmgRnLh0XVL1gKYlJFxYY5bo7EugCIG1ixNlcs7obJlnK+Q==
X-Received: by 10.55.127.133 with SMTP id a127mr4203110qkd.231.1518558899844; Tue, 13 Feb 2018 13:54:59 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id o59sm3007161qte.36.2018.02.13.13.54.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 13:54:59 -0800 (PST)
Date: Tue, 13 Feb 2018 16:54:54 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Erik Kline <ek@google.com>
Cc: Martin Duke <martin.h.duke@gmail.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: draft-duke-quic-load-balancers-00.txt
Message-ID: <20180213215453.GA6686@ubuntu-dmitri>
Mail-Followup-To: Erik Kline <ek@google.com>, Martin Duke <martin.h.duke@gmail.com>, IETF QUIC WG <quic@ietf.org>
References: <CAM4esxRq131G7XOC1YNy6N943Bar08gh8vMmhU34-vYcXOAauw@mail.gmail.com> <CAAedzxrdwHOKhXKxN90yxWh1Zcb3wmHtktMnGPXsCkXNDB6DpQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAAedzxrdwHOKhXKxN90yxWh1Zcb3wmHtktMnGPXsCkXNDB6DpQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/bpiv5huNxgwsJicqa0S4-rnfS58>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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, 13 Feb 2018 21:55:02 -0000

On Mon, Feb 12, 2018 at 05:34:46PM -0800, Erik Kline wrote:
> I wasn't in Melbourne, but I'm curious: why not specify a protocol
> over QUIC itself?

+1: As I was reading the draft, I was wondering the same thing.

  - Dmitri.

v2.23.0 | Report a Bug | By Email