Or we change the way the keys are used. If the input were not just packet number, but CSN+PN, we still have the never-repeated property we need even if packet numbers are reset with each CID change.
-----Original Message----- From: QUIC <[email protected]> On Behalf Of Martin Thomson Sent: Sunday, December 6, 2020 6:24 PM To: [email protected] Subject: Re: Packet number spaces in multipath (was Re: What to do about multipath in QUIC) As this wasn't mentioned in the discussion: On Wed, Nov 25, 2020, at 14:34, Jana Iyengar wrote: > First though, a point on terminology: the receiver maintains a > separate "ReceivedPackets" for each CID, probably for each CID > sequence number (CSN). Let's please not call this a SACK Dashboard, to avoid confusion. > > On the question of sending more than 2^32 packets, I think that > resetting the packet number (PN) is ok on new CIDs. A design like this would require changes to the way that keys are generated. Unfortunately, I think that this also increases the cost of key generation a little for reasons specific to the internal workings of the key derivation function.
smime.p7s
Description: S/MIME cryptographic signature
