Date: Mon, 24 Dec 2018 08:39:04 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abd2c6b91cc5fd6ee30fc4463df0f4db4fa1e4f12992cf000000011838cda892a169ce17792cde@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2253/449753311@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2253@github.com>
References: <quicwg/base-drafts/issues/2253@github.com>
Subject: Re: [quicwg/base-drafts] Consider making h3 frame types varint (#2253)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c210ba84330e_50a03fc0626d45b812075";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/CXtQ0P-6H49nD4oWp5e5mU1QwCo>


----==_mimepart_5c210ba84330e_50a03fc0626d45b812075
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

How do we decide how the varint 62-bits are used? I recall this being a discussion topic that led to the invariants saying the space is used however the endpoints decide. Would H3 frames need to coordinate with SETTINGS or just assume varint encodes 1-byte updwards?

-- 
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/2253#issuecomment-449753311
----==_mimepart_5c210ba84330e_50a03fc0626d45b812075
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>How do we decide how the varint 62-bits are used? I recall this being a discussion topic that led to the invariants saying the space is used however the endpoints decide. Would H3 frames need to coordinate with SETTINGS or just assume varint encodes 1-byte updwards?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/2253#issuecomment-449753311">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkqz6UNJD6VzQdWcMU7hLywG-hcfrxks5u8QMogaJpZM4ZgKQr">mute the thread</a>.<img src="https://github.com/notifications/beacon/AWbkq0-MgD9-hhUZmvMprA0_vnKfhj6gks5u8QMogaJpZM4ZgKQr.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@LPardue in #2253: How do we decide how the varint 62-bits are used? I recall this being a discussion topic that led to the invariants saying the space is used however the endpoints decide. Would H3 frames need to coordinate with SETTINGS or just assume varint encodes 1-byte updwards?"}],"action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/2253#issuecomment-449753311"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2253#issuecomment-449753311",
"url": "https://github.com/quicwg/base-drafts/issues/2253#issuecomment-449753311",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5c210ba84330e_50a03fc0626d45b812075--