[Bundled-domain-names] DNS resolution for bundled names

["Jiankang Yao" <[e-mail]>]

Dear all,

     Thanks for being interested in the bunding name resolution issue.

The initial aim of this list discussion is for 

"
CNAME maps itself to another name. DNAME maps its descendants to another domain name.
If the name wants to map
itself and its descendants to another domain name, what should we do?
We need to design some solution to this problem. "

We hope to gather some interests for this issue to see whether we can do some standardlization work for it  in  IETF.
Out initial plan is to have a bar bof in Berlin IETF meeting. 

Some background information is listed bellow.

Any comments are welcome.

thanks a lot.
Jiankang Yao



____________________________________________
The following is the description for this issue.
--------------------------------------------


Use Case 1: Bundled domain names
Bundled domain names are those who share the same TLD but whose
second level labels are variants, or those who has identical second
level labels for which certain parameters are shared in the different
TLDs. For example, public Interest Registry, request to implement
technical bundling of second level domains for .NGO and .ONG. So we
have two kinds of bundled domain names. First one is in the form of
"V-label.TLD" in which the second level labels (V-label) are varants
sharing the same TLD; Second one is in the form of "LABEL.V-tld" in
which the second level labels(LABEL) are same with the different TLDs
(V-tld). Bundled domain names usually need to map itself and its descendants to another.
for examples:
example.com == example.net same label ending with different TLDs
color.com == colour.com different labels ending with the same TLD

Use Case 2: any two domain names
One company registers 2 domain names, A and B.      A needs to 
map itself and its descendants to B in order to have a easy manangement.
for examples:
example1.com == example2.net


Use Case 3: a company register the same label in different TLDs.
With the emergence growth of gTLDs, it is very common to register one label under many TLDs for the same purpose. but the comany may just use  one label under one TLD as the primary domain name, others as the  less important one. The company may want to have all these domain names share the similar/same DNS resolution results.
So the DNS administrator hopes to have some convinient method to configure these domain names in DNS.



Many years ago, we try to solve the similar problem in DNSEXT WG.
That problem includes the variant issues. But the variant issues are too complex.
So this time, we try to exclude the variant issues, and limit the problem to 
"the name maps itself and its descendants to another name" and get the solution.


The related drafts:
https://tools.ietf.org/html/draft-yao-dnsext-identical-resolution-00 
https://tools.ietf.org/html/draft-yao-dnsext-bname-05
https://tools.ietf.org/html/draft-sury-dnsext-cname-dname-00 
https://tools.ietf.org/html/draft-barton-clone-dns-labels-fun-profit-00 
https://tools.ietf.org/html/draft-vixie-dnsext-dnsshadow-00 
--------------------------------------------------------------------------------
Jiankang Yao