IETF Logo Mail Archive

Re: [quicwg/base-drafts] Reserve Long Header Packet Type for QUIC-LB (#1980)

Nick Banks <notifications@github.com> Thu, 08 November 2018 03:28 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32C4A130DD3 for <quic-issues@ietfa.amsl.com>; Wed, 7 Nov 2018 19:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 3YvO2dmhy0c0 for <quic-issues@ietfa.amsl.com>; Wed, 7 Nov 2018 19:28:03 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2065B12958B for <quic-issues@ietf.org>; Wed, 7 Nov 2018 19:28:03 -0800 (PST)
Date: Wed, 07 Nov 2018 19:28:02 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541647682; bh=ACsBdyJhd+TDwi1LJJsd1pA1i4zCt+D976YxGGy9Vqw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fEFXUvnwHPblHcinkQZMMcUFafegppL4qCZHW2v+aq6m3tfUuoQaWVrsaUvT08fMw e0iaYAs1ZKH+oFiuAonK/972XIvw7rcBe5x9XvlQ+JOXIPjxhUsOU2AwSkRuLTbZ5F 7RL49ARQqL4RDs2SZ9IwQly9vLb5F5r3enV1Aciw=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab294e39c1ec5b39f39b4f46a310482d5756f7306b92cf0000000117fb6f4292a169ce168cd044@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1980/436861077@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1980@github.com>
References: <quicwg/base-drafts/issues/1980@github.com>
Subject: Re: [quicwg/base-drafts] Reserve Long Header Packet Type for QUIC-LB (#1980)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5be3ad421d6af_18163fa8cead45c439768"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/p5mMsy-sriL0phE1ZX2MUJ7p5m4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2018 03:28:05 -0000

@siyengar I disagree with both of your points. For one, the QUIC-LB explicitly doesn't use CIDs. The SCID/DCID length fields are zero. Second, the QUIC-LB is itself an extensible packet. It has subtypes that can be used for configuration or things like the health check. That kind of stuff is exactly what this new packet type would allow. Because of migration, QUIC is a lot more complicated that TCP or plain UDP when it comes to load balancing so we need a standard way to do this, ideally built into the QUIC server implementations that plan to run behind a load balancer. The path of least resistance is to use the same framing logic that those server already have.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1980#issuecomment-436861077

v2.23.0 | Report a Bug | By Email