draft for alternative namespace resolution standard proposal

HIP-xxxx.md

@@ -0,0 +1,41 @@
+# HIP-xxxx : Name data standard for alternative namespace resolution
+
+```
+Number:  HIP-xxxx
+Title:   Name data standard for alternative namespace resolution
+Type:    Informational
+Status:  Draft
+Authors: Mike Carson <https://impervious.com/>
+Created: 2021-02-08
+```
+
+## Abstract
+
+This HIP describes how to set the data for a Handshake name so that it resolves via an alternative namespace, for example via a sidechain.
+
+## Motivation
+
+There may be various reasons to resolve a name on an alternative namespace other than a domain name or an ip address.  One example is for decentralized subdomains on Ethereum.  Software could recognize the data on a name in a way to resolve it with Ethereum.
+
+## Name data standard
+
+We propose setting the NS records for the name with an underscore suffix which will resolve to an alternative protocol.  The prefix will be used as data for the protocol. For example:
+
+```
+{
+  "records": [{
+    "type": "NS",
+    "ns": "0x36fc69f0983E536D1787cC83f481581f22CCA2A1._eth."
+  }]
+}
+```
+
+This would use a specific Ethereum contract address (0x36fc69f0983E536D1787cC83f481581f22CCA2A1) to resolve subdomains under the Handshake top-level domain.  In this example, the contract is an ENS fork.  Software would query a specific subdomain in the ENS contract, get the DNS data stored on the subdomain, and use this to resolve the subdomain.
+
+## Registered protocols
+
+data_suffix | plugin
+--------------------------------|-----------------------------------
+[ethereum contract address]._eth| Ethereum contract address
+
+

README.md

@@ -1,31 +1,7 @@
 # HIPs
-
 Handshake Improvement Proposals
 
 | Number                  | Title                                                               | Type          | Status   |
 |-------------------------|---------------------------------------------------------------------|---------------|----------|
 | [HIP-0000](HIP-0000.md) | HIP Template                                                        | Informational | Draft    |
-
-# What is a HIP?
-
-A Handshake Improvement Proposal is a technical document that attempts to standardize a feature
-or protocol extension across the Handshake ecosystem. It should be implementation-agnostic. If
-you would like to propose a specific change to `hsd` or `hnsd`, open an issue or pull request
-in the appropriate repository. HIPs are not consensus, they are not law, they may never be
-actually implemented in production. HIPs are just solutions to common problems that the Handshake
-developer community can use as reference in their own projects. They may change over time,
-or be replaced with newer HIPs.
-
-# How to submit a HIP
-
-It's best to discuss with other developers familiar with the project before writing a proposal.
-There is a [HNS Developer Channel on Telegram](https://t.me/hns_tech) and `#handshake` on IRC.
-
-HIPs may be submitted by opening a pull request to this repository with a format resembling HIP-0000.
-Please do not assign yourself a HIP number, just use the placeholder `HIP-xxxx` where applicable.
-Pull requests should also add a row to the table of contents in the README.md file with the placeholder
-and working title of the proposal.
-
-If the proposal is well-formatted it may be assigned a HIP number by a project maintainer. The
-author will then be expected to revise the pull request with this number, along with any other
-comments about the proposal itself, before being merged.
+| [HIP-xxxx](HIP-xxxx.md) | Name data standard for alternative namespace resolution                                                        | Informational | Draft    |