Re: [Pearg] Tsvart early review of draft-irtf-pearg-numeric-ids-generation-02

[Eric Rescorla <[e-mail]>]

On Thu, Aug 27, 2020 at 5:10 AM Fernando Gont <[e-mail]> wrote:

> Hi, Michael,
>
> Thanks a lot for your feedback! In-line...
>
> On 7/8/20 09:22, Michael Tüxen via Datatracker wrote:
> > Reviewer: Michael Tüxen
> > Review result: Ready with Issues
> >
> > The document is well written, provides algorithms which could be used to
> > address identified problems. One  could add some text covering TCP
> timestamps.
>
> You mean e.g. to spell out which of the proposed algorithms one might
> use for TCP timestamps?
>
>
> > Section 1 states:
> > "Recent history indicates that when new protocols are standardized or
> > new protocol implementations are produced, the security and privacy
> > properties of the associated identifiers tend to be overlooked,..."
> > How does this related to recent/current activities like SCTP/DTLS or
> QUIC?
>
> SCTP (RFC4960) is similar to TCP, in this respect. OTOH, I have only
> skimmed through the DTLS (RFC6347), and it seems that it initially sets
> sequence numbers to 0. -- while these are meant to be protected, I'm
> curious if they could have done with monotonically increasing sequence
> numbers ala 6528, or with a random origin.
>

We perhaps could have, but to our knowledge the security functionality of
the protocol does not depend on unpredictability of the Record Sequence
Number. The same is true of QUIC. Note that both QUIC and DTLS 1.3 protect
this portion of the header (QUIC calls it the Packet Number).

-Ekr