Re: [DNSOP] WGLC for draft-ietf-dnsop-let-localhost-be-localhost-02

> On 5 Feb 2018, at 5:10 pm, Ted Lemon wrote: > > On Feb 5, 2018, at 12:18 AM, Mark Andrews wrote: >> The original problem is that HTTP doesn’t specify that names learn across the >> wire, including from on disk html files, need to be treated as absolute >>

Re: [DNSOP] WGLC for draft-ietf-dnsop-let-localhost-be-localhost-02

On Feb 5, 2018, at 12:18 AM, Mark Andrews wrote: > The original problem is that HTTP doesn’t specify that names learn across the > wire, including from on disk html files, need to be treated as absolute names. > This is HTTP’s mess due to allowing relative names in what is

Re: [DNSOP] WGLC for draft-ietf-dnsop-let-localhost-be-localhost-02

> On 5 Feb 2018, at 3:20 pm, Ted Lemon wrote: > > On Feb 4, 2018, at 9:49 PM, Mark Andrews wrote: >> We may as well ban www.example because that can return 127.0.0.1 as well. :-) > > www.example.com is never presumed to be local. And localhost.example.com

Re: [DNSOP] WGLC for draft-ietf-dnsop-let-localhost-be-localhost-02

On Feb 4, 2018, at 9:49 PM, Mark Andrews wrote: > We may as well ban www.example because that can return 127.0.0.1 as well. :-) www.example.com is never presumed to be local. ___ DNSOP mailing list

Re: [DNSOP] WGLC for draft-ietf-dnsop-let-localhost-be-localhost-02

> On 4 Feb 2018, at 2:31 pm, Lanlan Pan wrote: > > > > Mark Andrews 于2018年2月3日周六 上午4:11写道： > The problem is that search lists are being applied when “localhost” is being > entered into name lookup APIs and is being matched against localhost.example > which

Re: [DNSOP] A conversational description of sentinel.

> > Now when I see that this kind of problems is real, it is probably the > right time to ask Geoff to use his tools and get some data from large > scale measurement... > > Underscore is now out of the question because we know about the > Android/Chrome problem se might test alternative labels.