Re: [saad] About saad

Fred Baker <fred@cisco.com> Fri, 17 October 2003 17:59 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13563 for <saad-archive@odin.ietf.org>; Fri, 17 Oct 2003 13:59:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAYsQ-000248-3w for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 13:59:02 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HHx2dc007934 for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 13:59:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAYsP-00023t-V8 for saad-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 13:59:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13515 for <saad-web-archive@ietf.org>; Fri, 17 Oct 2003 13:58:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAYsN-0006WI-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 13:58:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAYsN-0006WF-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 13:58:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAYsO-00023W-Eh; Fri, 17 Oct 2003 13:59:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAYrU-0001yi-LG for saad@optimus.ietf.org; Fri, 17 Oct 2003 13:58:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13408 for <saad@ietf.org>; Fri, 17 Oct 2003 13:57:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAYrS-0006Tm-00 for saad@ietf.org; Fri, 17 Oct 2003 13:58:02 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1AAYrR-0006Sb-00 for saad@ietf.org; Fri, 17 Oct 2003 13:58:01 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9HHvSeA005555; Fri, 17 Oct 2003 10:57:29 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (sjc-vpn4-871.cisco.com [10.21.83.102]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AMQ03697; Fri, 17 Oct 2003 10:57:13 -0700 (PDT)
Message-Id: <6.0.0.22.2.20031017133440.045fb7e8@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 17 Oct 2003 13:38:11 -0400
To: "James Kempf" <kempf@docomolabs-usa.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: [saad] About saad
Cc: <saad@ietf.org>
In-Reply-To: <009d01c394c3$c91c3b30$396015ac@dclkempt40>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C658@server2003.arneill-py.sacramento.ca.us> <018201c393ff$a7431200$396015ac@dclkempt40> <6.0.0.22.2.20031016120745.04522090@mira-sjc5-b.cisco.com> <009d01c394c3$c91c3b30$396015ac@dclkempt40>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: saad-admin@ietf.org
Errors-To: saad-admin@ietf.org
X-BeenThere: saad@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/saad>, <mailto:saad-request@ietf.org?subject=unsubscribe>
List-Id: Scope Addressing Architecture Discussion <saad.ietf.org>
List-Post: <mailto:saad@ietf.org>
List-Help: <mailto:saad-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/saad>, <mailto:saad-request@ietf.org?subject=subscribe>

At 11:31 AM 10/17/2003, James Kempf wrote:
>The DNS is a node identifier, but it currently can't be used by the 
>transport layer as a connection endpoint identifier.

And neither can a interface address, at least not in the same way. As you 
noted, one could use a MIP Home Address as a CEPID, because it is invariant 
across interface failures, routing changes, and motion.

>There are have also been some experimental proposals (viz. Cheriton's 
>TRIAD work) to use DNS names for routing.

Yes. If you believe that names should be in the application layer and 
addresses should be in the network layer, moving names down is as 
problematic as moving addresses up, for the same reason. 


_______________________________________________
Saad mailing list
Saad@ietf.org
https://www1.ietf.org/mailman/listinfo/saad