IETF Logo Mail Archive

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

ianswett <notifications@github.com> Fri, 04 January 2019 08:44 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 A05A7130FB8 for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 00:44:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level:
X-Spam-Status: No, score=-6.447 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_24=1.618, 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 pVve7zNYVh5Q for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 00:44:06 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 099EB129AA0 for <quic-issues@ietf.org>; Fri, 4 Jan 2019 00:44:06 -0800 (PST)
Date: Fri, 04 Jan 2019 00:44:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546591445; bh=hvy8ouMVo3JreoVU9ONk3UCgJ5R6mJhpLvbRCOunxtU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dR/8UbjKc2zReiMmZB2srYE+IPleKiW96CwFMLONq2IoLUgDc40xgUxr8cm50FKgy 3tIXZfSnNAswAfv4XLQsqJZmmwCA0ioT3T6uwISSNFUxtA5fLj7pkACSn4r1gdKu3f IF2kq3PHmyO1UL5kmIvHI/zsplMwBpVd1C65hDl8=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb6042d6c74fff18063e70bdd45fa5975036eca9b92cf000000011846ded492a169ce17706c1f@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/451385337@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_5c2f1cd4f256b_b853f94452d45c489703f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/dlk1CS4YMjB41eG9dMqxgi3Gxjs>
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:44:08 -0000

Yes, it'd be good to capture something more up-to-date if we can come to consensus on that.

Is explicit signal meant to indicate DNS and/or ORIGIN frame?  If so, maybe call those two out as examples?

-- 
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-451385337

v2.23.0 | Report a Bug | By Email