W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2015

Applications and special use domain names | Re: Browsers and .onion names

From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Date: Sun, 29 Nov 2015 08:33:09 +0000
To: Willy Tarreau <w@1wt.eu>
Cc: Jacob Appelbaum <jacob@appelbaum.net>, Mark Nottingham <mnot@mnot.net>, Cory Benfield <cory@lukasa.co.uk>, HTTP Working Group <ietf-http-wg@w3.org>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Message-Id: <E1a2xPt-0007TU-0q@lisa.w3.org>
> Uh, I'm not sure if you're telling a joke or not but this entire
> process started because of .local as a Special-Use-Domain-Name:
> 
>  https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml
> 
> Thus the Pandora's box opened up without notice, I guess? Perhaps it
> is time to implement them both?


There is no requirements for applications because "local" is  special use domain name. 
Application is supposed to pass "local" to resolver library.


example             RFC6761 : Application software SHOULD NOT recognize example names as 
                             special and SHOULD use example names as they would other domain 
                             names.
example.com         RFC6761 :  -"- 
example.net         RFC6761 :  -"- 
example.org         RFC6761 :  -"- 
invalid             RFC6761 : Application software MAY recognize "invalid" names as special 
                             or MAY pass them to name resolution APIs as they would for other
                             domain names.
local               RFC6762 : Application software may use these names as they would other similar
                             DNS names, and is not required to recognize the names and treat them
                             specially.
localhost           RFC6761 : Application software MAY recognize localhost names as special, or MAY
                             pass them to name resolution APIs as they would for other domain
                             names.
onion               RFC7686 : Applications that do not implement the Tor protocol SHOULD generate an
                             error upon the use of .onion and SHOULD NOT perform a DNS lookup. 
test                RFC6761 : Application software SHOULD NOT recognize test names as special 



Note "onion" here. That is only special use domain name which
applications are requested recognize as special.

"invalid" and "localhost" are allowed to applications to recognize 
as special, but that is not requested.

Most special use domain name applications are supposed not to
be recognized as special.

For resolver libraries rules are different.

/ Kari Hurtta
Received on Monday, 30 November 2015 09:24:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:40 UTC