- From: Dragana Damjanovic <dragana.damjano@gmail.com>
- Date: Wed, 20 Oct 2021 10:36:46 +0200
- To: Ben Schwartz <bemasc@google.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CAG0m4gTHLtM750-ZT3qsxLaRpgWixddYy_vJG4Deicf3JP0FTQ@mail.gmail.com>
Hi, On Tue, Oct 19, 2021 at 11:53 PM Ben Schwartz <bemasc@google.com> wrote: > Thanks for this draft, Dragana! > > As a matter of IETF procedure, I think it's best to avoid specifying a > number for the SvcParam in your draft at least until it is adopted by a > working group. (Right now we are in a slightly awkward position, as the > SvcParam registry will be First-Come-First-Served, but it does not yet > exist.) Your chosen value, for example, happens to collide with > draft-ietf-dnsop-svcb-dns. > Thank you. I will fix it and I will remember for further drafts. > > On the technical side, I wonder if you've looked at > https://datatracker.ietf.org/doc/html/draft-vvv-httpbis-alps? That > proposal would provide the SETTINGS frame earlier in the handshake, > achieving the same goal of avoiding this delay. Compared to delivery over > DNS, it has some important benefits. For example, it reduces the amount of > information that needs to be synchronized between HTTP servers and their > DNS zones, and encompasses any future HTTP SETTINGS as well. > The draft will eliminate some of this delay, but the TLS handshake still needs to be completed. There can be situation where it is possible to use HTTP/3 and HTTP/2, the client could choose to try HTTP/3, fallback to HTTP/2 and than to HTTP/1.1 or skip one of the steps. Dragana > > On Tue, Oct 19, 2021 at 5:41 PM Dragana Damjanovic < > dragana.damjano@gmail.com> wrote: > >> Hi, >> >> I wrote a sort draft to support advertising WebSocket support using HTTPS >> RR records. >> >> Any feedback is welcome. >> >> Kind Regards, >> Dragana >> >> >> ---------- Forwarded message --------- >> From: <internet-drafts@ietf.org> >> Date: Tue, Oct 19, 2021 at 10:54 PM >> Subject: New Version Notification for >> draft-damjanovic-websockets-https-rr-00.txt >> To: Dragana Damjanovic <dragana.damjano@gmail.com> >> >> >> >> A new version of I-D, draft-damjanovic-websockets-https-rr-00.txt >> has been successfully submitted by Dragana Damjanovic and posted to the >> IETF repository. >> >> Name: draft-damjanovic-websockets-https-rr >> Revision: 00 >> Title: Advertising WebSocket support in the HTTPS resource record >> Document date: 2021-10-19 >> Group: Individual Submission >> Pages: 5 >> URL: >> https://www.ietf.org/archive/id/draft-damjanovic-websockets-https-rr-00.txt >> Status: >> https://datatracker.ietf.org/doc/draft-damjanovic-websockets-https-rr/ >> Htmlized: >> https://datatracker.ietf.org/doc/html/draft-damjanovic-websockets-https-rr >> >> >> Abstract: >> This specification introduces a way to advertise the support for the >> extended CONNECT feature that is used for running the WebSocket >> protocol over a single stream of an HTTP/2 and HTTP/3 connection >> using HTTPS resource records [HTTPSRR]. >> >> >> >> >> The IETF Secretariat >> >> >>
Received on Wednesday, 20 October 2021 08:48:43 UTC