Re: [dnsext] draft-diao-aip-dns

[YP Diao <[e-mail]>]

--- On Mon, 6/18/12, Fred Baker <[e-mail]> wrote:

> From: Fred Baker <[e-mail]>
> Subject: draft-diao-aip-dns
> To: [e-mail]
> Cc: [e-mail], [e-mail]
> Date: Monday, June 18, 2012, 1:31 PM
> I'm reading draft-diao-aip-dns, and
> wonder what the context is. Is this related to the BRICI
> proposal in WCIT, for support for a DNS root modeled on the
> International Calling Code structure of the telephone
> system?

I have not information about the BRICI proposal in WCIT and this is not related to it.

> My concern is for the possibility of disruption to Internet
> communications. If a country (or for that matter a business
> that simply decides to sell access to its own autonomous
> root) acts autonomously and unilaterally to add a TLD, other
> countries/services may or may not know about it, and the
> names may therefore not be usable in any context other than
> the country/service itself. If DNS resolution of names that
> are not from the country/service in question are forced to
> channel through the autonomous root, there are "interesting"
> questions of scale.

This would not affect Internet communications in traditional ways. Based on Internet practice, autonomous internet (AIP) techinology can transform the Internet into Autonomous Internet (AIP) without protocol change, using mode change, transition period.

It would be more reasonable and efficient that internal domain name resolution is no longer via the DNS outside this AIP network.

As described by AIP DNS rule 2 in Section 2.2, different AIP network default domain name suffix needs to be assigned by IANA.

> 
> 
> Comments on the paper itself:
> 
> The Introduction opens with the sentence
> 
>    Internet Domain Name System (DNS)
> distributes domain name and IP      
>    address for the host on the Internet. DNS
> automatically translates    
>    the domain name into IP address when user
> accesses Internet using     
>    domain name. 
> 
> I would dispute that. The DNS enables a client to obtain a
> resource record from a name service; the resource record
> might be for an IPv4 or IPv6 address (A/AAAA), for the name
> of one or more mail servers (MX), an encryption/signature
> key, or a variety of other types of information.
> 

Strictly, I admit!

> In section 3.2, if I understand the document correctly, the
> document proposes to use recursive DNS access between AIPs.
> I have no problem with recursive translation; it is defined
> and works now. However, it would appear that this recursive
> translation happens between AIP DNS roots, as opposed to
> happening from a DNS server closer to the original request.
> I think that is likely to have serious scaling issues.


This recursive translation would happen only in local DNS server and AIP DNS GW but not AIP DNS roots.

> 
> One general comment on sentence structure: in English, it is
> considered poor form to start a sentence with "And". For
> example
> 
>                
>              
>    And any IP node's external domain 
>    
>    name is consist of its internal domain
> name and its AIP network       
>    default domain name suffix.    
> 
> should read
> 
>                
>                
>    Any IP node's external domain 
>    
>    name consists of its internal domain name
> and its AIP network       
>    default domain name suffix. 
> 
> While the specific point is a nit, I see it frequently in
> the paper.

Thank you for detail revision! It would be helpful for its next version.

> 
> I'm not sure I understand rule 3 in section 2.2. If, for
> example, I am in a Chinese AIP and want to access
> www.example.com, but I want to get to the one that would be
> accessible from Brazil, do I access "www.example.com",
> "www.example.com.ex", www.example.com.br.ex", or something
> else? Is there any reason to believe that the resource
> record for www.example.com within the AIP is the same as the
> one for the same name in some other AIP? I worry about that,
> as much as anything, because international business and
> communication depends on a common understanding of resource
> records; if a vendor in country A wants to make a product or
> service available to a potential customer in country B (or
> for that matter in all countries), it gives one URI/URL to
> all of them and they all have access to it. If there is
> significant confusion at this level, sending for example
> requests intended for Google to Baidu, it will have a
> significant and negative effect on international business
> and communications. That not only doesn't bode well for the
> Internet as an international communication vehicle, it
> portends poor economic results for the countries that deploy
> autonomous internets.

AIP just provides more flexiblility and possibility to international business and communications. For Google or Baidu, they can apply different local URL for different country to provide differentiate services as usual(for example www.google.cn, www.google.com.hk...); or they can apply a unified URL for all countries such as www.google.com and just provide a link for different countries. 

In AIP,  The another additional possibility is to apply identical local URL for different country to provide differentiate services.  

> 
> 
> Last time China proposed this (October 2000), John Klensin
> and I flew to Beijing to discuss it with Professor Qian
> Hua-lin. He agreed that the economic importance of
> international trade far outweighed the value of having an
> autonomous naming system...
> 

I didn't have chance to disscuss this with Professor Qian Hua-lin yet. But I agree throughly that new technologies should provide more flexiblility and possibility for people equally but not limit the free and equal international communication right-it is the soul of Internet forever!

> Could you comment on the proposal, explaining in more detail
> what you have in mind, and how (a) the service remains
> scalable, and (b) the service supports the international
> objectives of business interests that use it?
> 

AIP technology is so simple as it describe in this draft. The prospect of future Internet would be more open and scalable if we can just imagine openly!
 

>

sincerely

Diao Yongping



_______________________________________________
dnsext mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dnsext