Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443)

ianswett <> Tue, 24 July 2018 02:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B3BA2130F6A for <>; Mon, 23 Jul 2018 19:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vybJnNDjgENB for <>; Mon, 23 Jul 2018 19:02:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B1720130F6D for <>; Mon, 23 Jul 2018 19:02:07 -0700 (PDT)
Date: Mon, 23 Jul 2018 19:02:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1532397726; bh=5weMw3FwnhL8LG45c0kY3XG43M2em2R3ZE9pnAPoNKU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZXNIQL4TyTbMOUt21hGg72mzuGBweN4FGWVtXptEsUwWaVVaGPF6QB1wfnJze8zXw RQFo+ISmnB7n0vu4DmE1HiPfzuB+PknUolF21bsvz41/sotkJT0yiN8q5y67Ue3A1y oPYOt4j9TEbLsM5/nVxwjP9Rk9vdSRCimHRQVVQg=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1443/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Stateless Reset Eternal Ping Pong (#1443)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b56889ed06a2_52b43f95920d45b4389ad"; 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
Archived-At: <>
X-Mailman-Version: 2.1.27
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Jul 2018 02:02:10 -0000

That's a good question.  At the moment for HTTP, I think it's reasonable to expect <=8 byte CIDs towards the client, with 0 being very common.   For WebRTC, I expect 0 bytes to also be very common, but there may be use cases when non-zero is necessary.  It's difficult for me to speculate about other applications.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: