Date: Sun, 10 Nov 2019 14:41:05 -0800
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK2Y6YJZJG3467CB2CN32XCIDEVBNHHB6CGIZA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3212@github.com>
Subject: [quicwg/base-drafts] Remove handshake confirmed test for KeyUpdte
 (#3212)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5dc89201dace2_36aa3fbe58ecd96013530c4";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FBD0gNlXB-yv-E_CwBJlLt8weeo>


----==_mimepart_5dc89201dace2_36aa3fbe58ecd96013530c4
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

S 6.1 Says

   An endpoint MUST NOT initiate a key update prior to having confirmed
   the handshake (Section 4.1.2).  An endpoint MUST NOT initiate a
   subsequent key update prior unless it has received an acknowledgment
   for a packet that was sent protected with keys from the current key
   phase.

However, I believe that the requirement to have confirmed the
handshake is redundant. As a reminder, the conditions under which the
handshake is confirmed are:

   (1) the handshake is complete, and
   (2) the endpoint has received an acknowledgment for a
       packet sent with 1-RTT keys

1. On the client side, the 1-RTT keys aren't available until the handshake
   is complete, so it's not possible to send 1-RTT packet and therefore
   not possible to have them ACKed.

2. On the server side, the 1-RTT keys are available before the handshake
   is complete, but because the server is forbidden from reading any
   1-RTT data before processing CFIN (S 5.6), it *also* cannot have
   received an acknowledgement for a packet sent with 1-RTT keys.

In other words, condition (2) implies condition (1), no?


-- 
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/3212
----==_mimepart_5dc89201dace2_36aa3fbe58ecd96013530c4
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>S 6.1 Says</p>
<p>An endpoint MUST NOT initiate a key update prior to having confirmed<br>
the handshake (Section 4.1.2).  An endpoint MUST NOT initiate a<br>
subsequent key update prior unless it has received an acknowledgment<br>
for a packet that was sent protected with keys from the current key<br>
phase.</p>
<p>However, I believe that the requirement to have confirmed the<br>
handshake is redundant. As a reminder, the conditions under which the<br>
handshake is confirmed are:</p>
<p>(1) the handshake is complete, and<br>
(2) the endpoint has received an acknowledgment for a<br>
packet sent with 1-RTT keys</p>
<ol>
<li>
<p>On the client side, the 1-RTT keys aren't available until the handshake<br>
is complete, so it's not possible to send 1-RTT packet and therefore<br>
not possible to have them ACKed.</p>
</li>
<li>
<p>On the server side, the 1-RTT keys are available before the handshake<br>
is complete, but because the server is forbidden from reading any<br>
1-RTT data before processing CFIN (S 5.6), it <em>also</em> cannot have<br>
received an acknowledgement for a packet sent with 1-RTT keys.</p>
</li>
</ol>
<p>In other words, condition (2) implies condition (1), no?</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/3212?email_source=notifications&amp;email_token=AFTOJK34HOMCZWXUWQBTOQDQTCEYDA5CNFSM4JLOVOK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYIZDEA">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK3OXJAZZWYPZJQ4PMTQTCEYDANCNFSM4JLOVOKQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK473AUXOI3LYNNKFLTQTCEYDA5CNFSM4JLOVOK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYIZDEA.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/3212?email_source=notifications\u0026email_token=AFTOJK34HOMCZWXUWQBTOQDQTCEYDA5CNFSM4JLOVOK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYIZDEA",
"url": "https://github.com/quicwg/base-drafts/issues/3212?email_source=notifications\u0026email_token=AFTOJK34HOMCZWXUWQBTOQDQTCEYDA5CNFSM4JLOVOK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYIZDEA",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5dc89201dace2_36aa3fbe58ecd96013530c4--