[quicwg/base-drafts] Checking duplicate TPs is onerous (#2689)

Dmitri Tikhonov <notifications@github.com> Fri, 10 May 2019 14:42 UTC

Date: Fri, 10 May 2019 07:42:06 -0700
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4FZVIGE5ETGQB5GEF24LAD5EVBNHHBUY7D5E@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2689@github.com>
Subject: [quicwg/base-drafts] Checking duplicate TPs is onerous (#2689)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd58dbe4993f_291b3feb080cd964103281"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Tkn1fCdYwhrjFMtlYQdMGUwHh8g>

Unlike HTTP/3 settings, receipt of [duplicated transport parameters must be treated as an error](https://tools.ietf.org/html/draft-ietf-quic-transport-20#section-7.3):

```
                                                    An endpoint MUST
   treat receipt of duplicate transport parameters as a connection error
   of type TRANSPORT_PARAMETER_ERROR.
```

Why the inconsistency?

The checks for duplicated transport (or settings) parameters are expensive, because one has to maintain an arbitrarily-sized set of possibly large numbers.

I propose we switch the duplicate transport parameters enforcement to "MAY treat as error."


-- 
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/2689

[quicwg/base-drafts] Checking duplicate TPs is on… Dmitri Tikhonov
Re: [quicwg/base-drafts] Checking duplicate TPs i… ianswett
Re: [quicwg/base-drafts] Checking duplicate TPs i… Mike Bishop
Re: [quicwg/base-drafts] Checking duplicate TPs i… Jana Iyengar
Re: [quicwg/base-drafts] Checking duplicate TPs i… Jana Iyengar