{"action":"created","issue":{"url":"https://api.github.com/repos/ifa-wg/proposals/issues/10","labels_url":"https://api.github.com/repos/ifa-wg/proposals/issues/10/labels{/name}","comments_url":"https://api.github.com/repos/ifa-wg/proposals/issues/10/comments","events_url":"https://api.github.com/repos/ifa-wg/proposals/issues/10/events","html_url":"https://github.com/ifa-wg/proposals/issues/10","id":82984802,"number":10,"title":"Specify Overlay Network via URI?","user":{"login":"indolering","id":44454,"avatar_url":"https://avatars.githubusercontent.com/u/44454?v=3","gravatar_id":"","url":"https://api.github.com/users/indolering","html_url":"https://github.com/indolering","followers_url":"https://api.github.com/users/indolering/followers","following_url":"https://api.github.com/users/indolering/following{/other_user}","gists_url":"https://api.github.com/users/indolering/gists{/gist_id}","starred_url":"https://api.github.com/users/indolering/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/indolering/subscriptions","organizations_url":"https://api.github.com/users/indolering/orgs","repos_url":"https://api.github.com/users/indolering/repos","events_url":"https://api.github.com/users/indolering/events{/privacy}","received_events_url":"https://api.github.com/users/indolering/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ifa-wg/proposals/labels/Domain%20Names%20(Long%20Term)","name":"Domain Names (Long Term)","color":"207de5"},{"url":"https://api.github.com/repos/ifa-wg/proposals/labels/Domain%20Names%20-%20Non-DNS%20Types%20(IFA-0002)","name":"Domain Names - Non-DNS Types (IFA-0002)","color":"fad8c7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-05-31T03:33:00Z","updated_at":"2015-07-17T20:19:10Z","closed_at":null,"body":"It would be ideal if users could specify overlay networks within the URI.  This is somewhat similar to Ryan's unofficial epoch proposal which specifies the ownership period using a integer, such as `example.1.bit`.  Note, however, that from a usability/psych standpoint **users cannot be relied upon to validate the URI** and the primary use case is for security conscious configurations.\r\n\r\nI'm unsure of the best way to go about this and I'm sure that the following ignores a raft of implementation issues.  Whatever the method, it is preferable that the lookup fail if the system does not support the given transport.\r\n\r\nOne option is to append the transport like a domain such as `example.bit.onion`, which would be passed to the DNS layer.   Given the likelihood that .onion will be reserved to prevent piracy leaks, it may be prudent to add this to the section on Tor in IFA-0002, which deals with non-DNS record types, including Tor.  While a `.bit.onion` address would never collide with real onion address, I am ignorant to how .onion addresses are handled and someone should at least check with them before adding support.\r\n\r\nWe cannot ensure that other suffixes can be used without risking stepping on future gTLDs.  One possible workaround would be to use a single character, such as `example.bit.i2p.x` or a reserved suffix such as [.invalid](https://en.wikipedia.org/wiki/.invalid) (which SIP apparently uses).  It is also possible that the IEFT or ICANN could reserve a TLD for special use names, such as [.alt](http://datatracker.ietf.org/doc/draft-wkumari-dnsop-alt-tld/).  At the very least, it would probably be wise to keep IFA-0002 as a Draft until the fate of the `.alt` proposal is resolved."},"comment":{"url":"https://api.github.com/repos/ifa-wg/proposals/issues/comments/122401872","html_url":"https://github.com/ifa-wg/proposals/issues/10#issuecomment-122401872","issue_url":"https://api.github.com/repos/ifa-wg/proposals/issues/10","id":122401872,"user":{"login":"JeremyRand","id":244188,"avatar_url":"https://avatars.githubusercontent.com/u/244188?v=3","gravatar_id":"","url":"https://api.github.com/users/JeremyRand","html_url":"https://github.com/JeremyRand","followers_url":"https://api.github.com/users/JeremyRand/followers","following_url":"https://api.github.com/users/JeremyRand/following{/other_user}","gists_url":"https://api.github.com/users/JeremyRand/gists{/gist_id}","starred_url":"https://api.github.com/users/JeremyRand/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JeremyRand/subscriptions","organizations_url":"https://api.github.com/users/JeremyRand/orgs","repos_url":"https://api.github.com/users/JeremyRand/repos","events_url":"https://api.github.com/users/JeremyRand/events{/privacy}","received_events_url":"https://api.github.com/users/JeremyRand/received_events","type":"User","site_admin":false},"created_at":"2015-07-17T20:19:10Z","updated_at":"2015-07-17T20:19:10Z","body":"> I meant it as a security feature, to ensure a connection is using a specific transport.\r\n\r\nSpecifically under what circumstances does this improve security?\r\n\r\n> Uhh, a domain name is a URL and a URL is a URI.\r\n\r\nA URI may sometimes contain a substring that is a domain name (though this does not always occur), but I have never seen a URI that is a domain name."}}