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;
boolinit
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 minim
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 encod
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
>
