I like it; will append to the issue. Thanks.
> On 5 Feb 2019, at 11:50 am, Joe Abley wrote:
>
> Hi Mark,
>
> On 4 Feb 2019, at 19:30, Mark Nottingham wrote:
>
>> I've modified that slightly to come up with this proposal:
>>
>> """
>> HTTP and HTTPS URIs rely on some name resolution mechanism
Hi Mark,
On 4 Feb 2019, at 19:30, Mark Nottingham wrote:
> I've modified that slightly to come up with this proposal:
>
> """
> HTTP and HTTPS URIs rely on some name resolution mechanism(s) to interpret
> the authority field and ultimately convert it into an identifier (typically,
> IPv4 or I
I've modified that slightly to come up with this proposal:
"""
HTTP and HTTPS URIs rely on some name resolution mechanism(s) to interpret the
authority field and ultimately convert it into an identifier (typically, IPv4
or IPv6 addresses). Often, this is DNS [ref].
When DNS is consulted for res
There is not yet a proper IANA allocated option code for this.
Might I suggest that all interested parties settle on 65015 from the
local/experimental block until the real thing arrives.
Dick Franks
On Fri, 1 Feb 2019 at 17:33, Wes Hardaker wrote:
>
> Folks,
>
> We
Wes,
On 01/02/2019 22.21, Wes Hardaker wrote:
Shane Kerr writes:
I was thinking about adding some support for this at the IETF hackathon, but
I'll be
meeting with some of the open source DNS folks this weekend at FOSDEM, and
seeing if
that collides with their existing plans.
Excellent! I
Anbang Wen,
On 02/02/2019 20.04, Anbang Wen wrote:
At Cloudflare, we are testing our crude implementation on our public
resolver which is built on top of knot-resolver. It would be good to
nudge others into working on it.
Is it already on GitHub or GitLab or something like that? Nudging is
e
