IETF Logo Mail Archive

Re: [quicwg/base-drafts] When can you coalesce connections (#2223)

Lucas Pardue <notifications@github.com> Fri, 04 January 2019 08:52 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 B5FA8130E51 for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 00:52:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, 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 kFjbtW5-ul8W for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 00:52:24 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B2F8124B0C for <quic-issues@ietf.org>; Fri, 4 Jan 2019 00:52:24 -0800 (PST)
Date: Fri, 04 Jan 2019 00:52:23 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546591943; bh=hJ2iqctwIjCFwUA46c6LP8oboODkwlHaIumiv8KWvLI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZHF7du0FIRYhowjN4vB4UuBRakkmQNN2eNT8RNlzrvRVDuywDMP12tpt7Cs/TFaT+ kBw4pls36NcbRO/JyNIUz9ky2y7yGL5kcX/WWf8JFqRtY+kUPYMbOLAUlMWRTXvlyT S2L5jItvDkGuiViwfEibZ0GrjrqJC7fPWDQZABGE=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbd9db04450d599ad366d8af33702e8b495b1deaf92cf000000011846e0c792a169ce17706c1f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2223/451386793@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2223@github.com>
References: <quicwg/base-drafts/issues/2223@github.com>
Subject: Re: [quicwg/base-drafts] When can you coalesce connections (#2223)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c2f1ec762d38_66543ff0d0ed45bc155726"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/3TlfLBwKU9Y4AhQKysd8-1SPg74>
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: Fri, 04 Jan 2019 08:52:26 -0000

@ianswett I think the dilemma is that some of those things don't exist yet for H3. For example, Mike did some earlier work to redefine ALTSVC frame for H3 but there is yet to be equivalent for ORIGIN or secondary certs.

-- 
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/2223#issuecomment-451386793

v2.29.0 | Report a Bug | By Email | System Status