[RAM] (no subject)

RJ Atkinson <rja@extremenetworks.com> Fri, 15 June 2007 13:48 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzCAA-00059i-CT; Fri, 15 Jun 2007 09:48:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzCA8-00059M-GR for ram@iab.org; Fri, 15 Jun 2007 09:48:28 -0400
Received: from eastrmmtao103.cox.net ([68.230.240.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzCA7-0008K7-6H for ram@iab.org; Fri, 15 Jun 2007 09:48:28 -0400
Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20070615134826.BKAY8543.eastrmmtao103.cox.net@eastrmimpo01.cox.net> for <ram@iab.org>; Fri, 15 Jun 2007 09:48:26 -0400
Received: from [10.30.20.61] ([68.10.118.38]) by eastrmimpo01.cox.net with bizsmtp id BpoS1X0080pnMhQ0000000; Fri, 15 Jun 2007 09:48:26 -0400
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <CE47DB60-42D8-4039-9EDF-2D08008A007B@extremenetworks.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: ram@iab.org
From: RJ Atkinson <rja@extremenetworks.com>
Date: Fri, 15 Jun 2007 09:48:25 -0400
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 1.6 (+)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [RAM] (no subject)
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

Earlier, Ved Kafle wrote:
> So, the distinction between an identifier and a locator is  
> dependent on
> the avalaibility of routing/switching infrastructure.
> If networks possess routing/switching insfrastructure based on a
> identifier namespace, the identifier simultaneously functions as a
> locator.

No.  An identifier cannot ever be a locator -- and the inverse
is also true.

If one has an object that functions both for identity and location,
that object is an "address", and is NOT an "identifier" or a
"locator".

Cheers,

Ran


_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram