I am like 2 minutes behind Joe on the XML link
Thanks Joe
On Fri, Aug 16, 2019 at 3:29 PM Joe Abley wrote:
> On 16 Aug 2019, at 14:28, Erik Kline wrote:
>
> >
> https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml#special-use-domain
> >
> >
> > I have won
On 16 Aug 2019, at 14:28, Erik Kline wrote:
> https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml#special-use-domain
>
>
> I have wondered whether or not it would be useful for IANA to have a git repo
> where these canonical data could live alongside script
https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml#special-use-domain
I have wondered whether or not it would be useful for IANA to have a git
repo where these canonical data could live alongside scripts that transform
them into things like C #include header
To put things in perspective, the special use TLD defined according to
RFC 6761 account for about 4% of the traffic seen at the L root,
according to https://ithi.research.icann.org/graph-m3.html. Of those,
".local" account for a bit more than 3%, ".localhost" a bit less than
0.5%, and ".invalid" a
Ack. Tnx.
On Fri, Aug 16, 2019 at 11:56 AM Joe Abley wrote:
> On 16 Aug 2019, at 10:59, Steve Crocker wrote:
>
> > At the risk of revealing that I haven't been following this thread
> carefully, I don't understand how a resolver is supposed to know all of the
> special names. Resolvers that a
On 16 Aug 2019, at 10:59, Steve Crocker wrote:
> At the risk of revealing that I haven't been following this thread carefully,
> I don't understand how a resolver is supposed to know all of the special
> names. Resolvers that are configured to know that invalid, local, onion, and
> test are s
On Friday, 16 August 2019 13:10:02 UTC Ted Lemon wrote:
> ...
>
> What’s the motivation behind this proposal?
>
> ...
i think it's to reduce the time between a mouse click and an advertising
impression, but i'm not an author so that's not "authoritative". it seems to
me that the web's technica
At the risk of revealing that I haven't been following this thread
carefully, I don't understand how a resolver is supposed to know all of the
special names. Resolvers that are configured to know that invalid,
local, onion,
and test are special will not know about the next name that's put on the
s
As I often note, I work for ISOC but I'm not speaking for it.
On Fri, Aug 16, 2019 at 11:30:06AM +0200, Vladimír Čunát wrote:
> I've been wondering what's best to do around these TLDs: invalid, local,
> onion, test. The RFCs say that resolvers SHOULD recognize them as
> special and answer NXDOMA
On Aug 16, 2019, at 09:26, Vladimír Čunát wrote:
>
> On 8/16/19 3:10 PM, Ted Lemon wrote:
>> If you look up “onion”, you have revealed that the user is trying to
>> use tOR, even if you haven’t revealed where they are going.
>
> Well, in this particular case the tOR client would probably better
On 8/16/19 3:10 PM, Ted Lemon wrote:
> If you look up “onion”, you have revealed that the user is trying to
> use tOR, even if you haven’t revealed where they are going.
Well, in this particular case the tOR client would probably better not
send onion queries to DNS resolver, but generally there w
If you look up “onion”, you have revealed that the user is trying to use tOR,
even if you haven’t revealed where they are going.
What’s the motivation behind this proposal?
Sent from my iPhone
> On Aug 16, 2019, at 05:30, Vladimír Čunát wrote:
>
>
> Hello,
>
> I've been wondering what's b
All
The Call for Adoption for draft-sah-resolver-information has ended, and
there seems to be strong consensus.
The consensus is "Let's adopt this document, but let's do more work on the
details". The chairs here this quite
strongly.
We'll adopt the document and if the working group should be ab
On 10/08/2019 06:26, Wes Hardaker wrote:
8.2.2 DONE The biggest issue is of course to find out what to put in the
extended
-
error code. On some resolvers (at least on Knot), the place where the
error is n
Hello,
I've been wondering what's best to do around these TLDs: invalid, local,
onion, test. The RFCs say that resolvers SHOULD recognize them as
special and answer NXDOMAIN without any interaction with nameservers (by
default). What do you think about NOT following this "advice", subject
to som
15 matches
Mail list logo