Re: [DNSOP] Adoption and Working Group Last Call for draft-appelbaum-dnsop-onion-tld

[hellekin <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/21/2015 04:21 PM, Ted Lemon wrote:
> 
> It would make sense to call it a reserved special-use top-level domain
 name.
> It's not a top-level domain in the DNS, though.
> I think that's the distinction to make.
> 
*** A distinction that the P2PNames draft made:

   The abbreviation "pTLD" is used in this document to mean a pseudo
   Top-Level Domain, i.e., a Special-Use Domain Name per [RFC6761]
   reserved to P2P Systems in this document.  A pTLD is mentioned in
   capitals, and within double quotes to mark the difference with a
   regular DNS gTLD.

In the introduction, we specify the shared characteristics of pTLDs:

The set of Special-Use Domain Names for Peer-to-Peer Systems (pTLDs)
   reserved by this document meet this requirement, as they share the
   following specificities:

   o  pTLDs are not manageable by some designated administration.
      Instead, they are managed according to various alternate
      strategies or combinations thereof, introduced in this document,
      and their respective protocol specifications: automated
      cryptographic assignment (".onion", ".zkey"), user-controled
      assignment in a private scope (".gnu", ".i2p"), or in a global
      public ledger (".bit"), or used as a source-routing mechanism to
      delegate DNS resolution to a remote peer (".exit").

   o  pTLDs do not depend on the DNS context for their resolution: GNS
      and Namecoin domains MAY use the DNS servers infrastructure, as
      they return DNS-compatible results; and all pTLDs use specific P2P
      protocols for regular name resolution, covered by their respective
      protocol specifications.

   o  When a pTLD protocol has been implemented, the implementation MUST
      intercept queries for the pTLD to ensure P2P names cannot leak
      into the DNS.

   o  The appropriate pTLD protocols can be implemented in existing
      software libraries and APIs to extend regular DNS operation and
      enable P2P name resolution.  However, the default hierarchical DNS
      response to any request to any pTLD MUST be NXDOMAIN.

   o  Finally, in order for pTLDs to realize a censorship-resistant,
      fully-decentralized name system, and provide security and privacy
      features matching user expectations, this document specifies
      changes required in existing DNS software and DNS operations.

==
hk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJVXjKhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0
ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9sR0P/RdE7DV7G8tmeJ75tAAS3lmC
Au1SiOjeCdB1kN5ztifd6AvffeOqxueIUisvw7P1Tefow94kLOqR01gcfNd3q5kq
nj52NmAya6dvnG3pCiyzclQviaZ3FxPOy5Bc1a8nwgCf+Km5Ze0AAjPmev7Y7QUD
yrTaw7GpOdn6Q63VgFcekMbN7hEXpV2wY7U0dLEXvn0IKbggVFTjMf2T81FBNrlv
6shf9iqgso4ocUHz7CjZo3oyc+7uZcIZxJkBoi6a4AYO/s8nDWCv/cJF4Vx69Eej
FRhBdqcngZtlDuUAcSTX6tCfYL8OAu2Lr3qKfL5seYxyluoghaRZ2RxR0kJbPgPa
xI58qJZ44R5mNHfQ9JYJzo6Y4RU9XaK7/Wf7GanwnImYw0S/XbokwsJjf45rqhVj
HYee6KuKNMj6Q46bIclBa/tmyVmWkRVoTnjr2dWf9L9+HzK4MfmRnzFim+9+jnYb
8ultuqWsmh7s5NnTaUlincGO1m9tXoqxSmAy9y6IG2LnkvDUOUelQAhtkFOEy4iB
6vnWv25V9vBewX9akqdCTZL53TAp3hFzcr+ku1j5qNjrkbTrUVHqENbf0fUUp7Rj
U+wIky95YOrHDECiPDvPzAJw6dLQI+3TuytFChTFBV53yOH4bRCoiLUOcISJ5ULS
ELRKa+P9ejBy73uJJVr7
=bz5s
-----END PGP SIGNATURE-----