On 25 Sep 2019, at 12:18, Jan Včelák wrote:
> On Tue, Sep 24, 2019 at 3:19 PM Erik Nygren wrote:
>> Following discussions around the "HTTPSSVC" record proposal in Montreal with
>> the DNSOP, HTTP and TLS WGs, we've updated what was previously
>> "draft-nygren-httpbis-httpssvc-03". The new
I also support the adoption of the draft.
On Wed, Oct 2, 2019 at 1:47 AM Måns Nilsson
wrote:
> Subject: [DNSOP] SVCB and HTTPSSVC records:
> draft-nygren-dnsop-svcb-httpssvc-00 Date: Tue, Sep 24, 2019 at 09:17:59AM
> -0400 Quoting Erik Nygren (erik+i...@nygren.org):
> > Follow
Subject: [DNSOP] SVCB and HTTPSSVC records: draft-nygren-dnsop-svcb-httpssvc-00
Date: Tue, Sep 24, 2019 at 09:17:59AM -0400 Quoting Erik Nygren
(erik+i...@nygren.org):
> Following discussions around the "HTTPSSVC" record proposal in Montreal
> with the DNSOP, HTTP and TLS WGs, we
> On Sep 24, 2019, at 6:17 AM, Erik Nygren wrote:
>
> Following discussions around the "HTTPSSVC" record proposal in Montreal with
> the DNSOP, HTTP and TLS WGs, we've updated what was previously
> "draft-nygren-httpbis-httpssvc-03". The new version is
>
(I joined the list late so I don't have the thread to use for a direct reply.
Sorry!)
On Tue, Sep 24, 2019 at 3:19 PM Erik Nygren wrote:
> Following discussions around the "HTTPSSVC" record proposal in Montreal
with the DNSOP, HTTP and TLS WGs, we've updated what was previously
And from an actual implementation.
enum encoding {
sbpr_text,
sbpr_port,
sbpr_ipv4s,
sbpr_ipv6s,
sbpr_base64
};
static const struct {
const char *name;
unsigned intvalue;
enum encoding encoding;
bool
Implementing the encoder isn’t hard but it needs to be clearer that there are
specific encodings. It is easy to miss this. I did initially.
--
Mark Andrews
> On 26 Sep 2019, at 20:41, Vladimír Čunát wrote:
>
>
>> On 9/26/19 12:30 PM, Jan Včelák wrote:
>>> The current draft attempts to
On 9/26/19 12:30 PM, Jan Včelák wrote:
The current draft attempts to minimize complexity for implementers by offering a fully generic encoding for unknown key
types. For example, "alpn=h3" can also be expressed as "key1=h3", and "port=8003" can
also be expressed as "key2=\031\067". This
On Wed, Sep 25, 2019 at 7:17 PM Ben Schwartz wrote:
>> example.com. 7200 IN HTTPSSVC 0 svc.example.net. ""
>> svc.example.net. 7200 IN HTTPSSVC 2 svc3.example.net. "alpn=h3
>> port=8003 esnikeys=\"ABC...\""
>
>
> The original proposal used a text encoding similar to your description. We
On Wed, Sep 25, 2019 at 12:18 PM Jan Včelák wrote:
> On Tue, Sep 24, 2019 at 3:19 PM Erik Nygren wrote:
> > Following discussions around the "HTTPSSVC" record proposal in Montreal
> with the DNSOP, HTTP and TLS WGs, we've updated what was previously
> "draft-nygren-httpbis-httpssvc-03". The new
On Tue, Sep 24, 2019 at 3:19 PM Erik Nygren wrote:
> Following discussions around the "HTTPSSVC" record proposal in Montreal with
> the DNSOP, HTTP and TLS WGs, we've updated what was previously
> "draft-nygren-httpbis-httpssvc-03". The new version is
> "draft-nygren-dnsop-svcb-httpssvc-00".
On Tue, Sep 24, 2019 at 9:18 AM Erik Nygren wrote:
> Following discussions around the "HTTPSSVC" record proposal in Montreal
> with the DNSOP, HTTP and TLS WGs, we've updated what was previously
> "draft-nygren-httpbis-httpssvc-03". The new version is
> "draft-nygren-dnsop-svcb-httpssvc-00".
Following discussions around the "HTTPSSVC" record proposal in Montreal
with the DNSOP, HTTP and TLS WGs, we've updated what was previously
"draft-nygren-httpbis-httpssvc-03". The new version is
"draft-nygren-dnsop-svcb-httpssvc-00". This incorporates much of the
feedback from the WG
13 matches
Mail list logo
