Archives/namecoin-proposals
2
0
Fork 0
mirror of https://github.com/namecoin/proposals synced 2024-11-12 19:10:43 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #15 from hlandauf/master

Browse Source 
Add non-numeric name constraint
This commit is contained in:
Hugo Landau 2015-06-06 15:50:07 +01:00
commit 5aee392542
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ifa-0001.md
View File

@ -53,6 +53,8 @@ The key of the key-value pair SHALL be an ASCII-encoded name in the form `d/NAME
Note that as per the above regex, the standard rules for domain names are enforced. Domain names MUST NOT begin or end with a hyphen, and consecutive hyphens MUST NOT appear except as permitted by the Internationalized Domain Names (IDN) specification (RFC 3492).
As an additional constraint, wholly numeric names, such as `d/123`, are not permitted. Names which begin with a digit but which are not wholly numeric, such as `d/123four` are permitted. (Historically, in the ICANN DNS system, fully numeric names such as `2600.org` were permitted. However such registrations are no longer allowed, although existing registrations such as `2600.org` itself are grandfathered. Namecoin adopts this constraint firstly for parity with contemporary domain naming policy, and secondly to enable the future assignment of all-numeric domains to denote name epoch for secure disambiguation purposes.)
The `d/` prefix identifies the Domain Names namespace within the Namecoin key namespace. Names under this prefix are reserved for use in relation to this specification and preceding versions of it. Keys not beginning with that prefix are wholly unrelated to this specification and are not required to conform to it.
The part of the name following the `d/` prefix is the name which manifests in the .bit TLD. A key of `d/example` registers the name `example.bit.`
@ -712,8 +714,6 @@ The following item types are deprecated by this document and SHOULD NOT be used.
- "delegate": The "import" item type provides a superset of the functionality of "delegate". Further, support for "import" is as of writing greater than support for "delegate", which is negligible. Thus, the "delegate" item type is deprecated.
- "i2p": The format proposed previously does not appear to make sense and includes extraneous fields. Since no actual implementations of that format are known, it has been deprecated in favour of a format more uniform with the "tor" item type.
Possible Future Directions
--------------------------