Date: Mon, 03 Jun 2019 01:40:36 -0700
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK4NNXQOAPMTQFUXM653AIHYJEVBNHHBVVRQLI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2760/498166706@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2760@github.com>
References: <quicwg/base-drafts/issues/2760@github.com>
Subject: Re: [quicwg/base-drafts] NEW_TOKEN should be symmetric (#2760)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5cf4dd04221e8_475e3ff5860cd968135721d";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/7BEwzSuShLzWMlz5-J4YC_FaXFY>


----==_mimepart_5cf4dd04221e8_475e3ff5860cd968135721d
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

When establishing a new connection, how a token was obtained doesn't play any role. Endpoints can distribute tokens by any way they want. NEW_TOKEN frames are just one way to do so, but tokens might as well be distributed out-of-band.

We made a lot of effort to make QUIC as symmetric as possible. The only exceptions are the 0-RTT feature of the handshake (we inherited this from TLS), and connection migration (which would cause a lot of corner cases). I don't understand why the NEW_TOKEN mechanism fits any of these criteria. Conceptionally, if at all, it seems to be less complexity to allow this frame in both directions.

-- 
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/2760#issuecomment-498166706
----==_mimepart_5cf4dd04221e8_475e3ff5860cd968135721d
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>When establishing a new connection, how a token was obtained doesn't play any role. Endpoints can distribute tokens by any way they want. NEW_TOKEN frames are just one way to do so, but tokens might as well be distributed out-of-band.</p>
<p>We made a lot of effort to make QUIC as symmetric as possible. The only exceptions are the 0-RTT feature of the handshake (we inherited this from TLS), and connection migration (which would cause a lot of corner cases). I don't understand why the NEW_TOKEN mechanism fits any of these criteria. Conceptionally, if at all, it seems to be less complexity to allow this frame in both directions.</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/2760?email_source=notifications&amp;email_token=AFTOJK2RIUNWZWCNQOIINP3PYTKIJA5CNFSM4HRC37V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWYWXMQ#issuecomment-498166706">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5NYKLSKM2A4K7B2TDPYTKIJANCNFSM4HRC37VQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK6VOYCLAXOT26E5L5DPYTKIJA5CNFSM4HRC37V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWYWXMQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2760?email_source=notifications\u0026email_token=AFTOJK2RIUNWZWCNQOIINP3PYTKIJA5CNFSM4HRC37V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWYWXMQ#issuecomment-498166706",
"url": "https://github.com/quicwg/base-drafts/issues/2760?email_source=notifications\u0026email_token=AFTOJK2RIUNWZWCNQOIINP3PYTKIJA5CNFSM4HRC37V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWYWXMQ#issuecomment-498166706",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5cf4dd04221e8_475e3ff5860cd968135721d--