IETF Logo Mail Archive

Re: [Speermint] Updated Draft: SPEERMINT Peering Architecture

Otmar Lendl <lendl@nic.at> Sat, 27 May 2006 12:56 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjyLG-0006bh-Lx; Sat, 27 May 2006 08:56:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjyLF-0006bc-5j for speermint@ietf.org; Sat, 27 May 2006 08:56:29 -0400
Received: from arachne.bofh.priv.at ([193.154.150.108] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjyLD-0002fB-SN for speermint@ietf.org; Sat, 27 May 2006 08:56:29 -0400
Received: by mail.bofh.priv.at (Postfix, from userid 1000) id 5F60D1A385; Sat, 27 May 2006 14:56:15 +0200 (CEST)
Date: Sat, 27 May 2006 14:56:15 +0200
From: Otmar Lendl <lendl@nic.at>
To: Duane <duane@e164.org>
Subject: Re: [Speermint] Updated Draft: SPEERMINT Peering Architecture
Message-ID: <20060527125615.GK1811@nic.at>
Mail-Followup-To: Otmar Lendl <lendl@nic.at>, Duane <duane@e164.org>, Reinaldo Penno <rpenno@juniper.net>, Patrick Melampy <PMelampy@acmepacket.com>, "Khan, Sohel Q [CTO]" <Sohel.Q.Khan@sprint.com>, speermint@ietf.org
References: <20060527082920.GI1811@nic.at> <9BD5D7887235424FA97DFC223CAE3C2804652E6B@proton.jnpr.net> <20060527095124.GJ1811@nic.at> <4478439B.80802@e164.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4478439B.80802@e164.org>
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: "Khan, Sohel Q [CTO]" <Sohel.Q.Khan@sprint.com>, speermint@ietf.org
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
Errors-To: speermint-bounces@ietf.org

On 2006/05/27 14:05, Duane <duane@e164.org> wrote:
> Otmar Lendl wrote:
> 
> >Domains are NAMES. Not addresses. You usually own your domain and take
> >it with you if you switch email provider or web-hoster. Domains itself
> >contain NO ROUTING INFORMATION. Their hierarchical structure reflects
> >the delegation chain but in no way L3 or application layer routing.
> 
> Ummm does DNS servers (like pdns which has a geo module) that return 
> info on closest server based on your IP count?

No, as the domain (we're talking normal gTLD or ccTLD) name itself
does not contain the topology information. 

Only after you plug that name into a mapping protocol (in this
case DNS) you get topology-relevant information.

Example:

    www.google.com is a name. In itself it contains no information 
    where the server is located. 

    If I make a lookup from here in Austria, I get

    www.google.com is an alias for www.l.google.com.
    www.l.google.com has address 66.249.85.104
    www.l.google.com has address 66.249.85.99

    The two addresses (if we ignore IP anycasting)
    define where on the Internet the server is located.

    Asking a traceroute server in australia I get

    www.google.com canonical name = www.l.google.com. 
    Name: www.l.google.com 
    Address: 66.102.7.99 
    Name: www.l.google.com 
    Address: 66.102.7.147 
    Name: www.l.google.com 
    Address: 66.102.7.104 

/ol 
-- 
< Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer >

_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint

v2.23.0 | Report a Bug | By Email