Re: [saad] About saad

Brian E Carpenter <brc@zurich.ibm.com> Fri, 17 October 2003 13:39 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 JAA01761 for <saad-archive@odin.ietf.org>; Fri, 17 Oct 2003 09:39:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAUos-0005QK-Uf for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 09:39:07 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HDd6hf020842 for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 09:39:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAUos-0005Q5-Lq for saad-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 09:39:06 -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 JAA01757 for <saad-web-archive@ietf.org>; Fri, 17 Oct 2003 09:38:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAUoq-0003Ug-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 09:39:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAUoq-0003Ud-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 09:39:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAUoo-0005PN-76; Fri, 17 Oct 2003 09:39:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAUog-0005P4-LT for saad@optimus.ietf.org; Fri, 17 Oct 2003 09:38:54 -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 JAA01754 for <saad@ietf.org>; Fri, 17 Oct 2003 09:38:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAUoe-0003Ua-00 for saad@ietf.org; Fri, 17 Oct 2003 09:38:52 -0400
Received: from d12lmsgate-2.de.ibm.com ([194.196.100.235] helo=d12lmsgate.de.ibm.com) by ietf-mx with esmtp (Exim 4.12) id 1AAUod-0003UL-00 for saad@ietf.org; Fri, 17 Oct 2003 09:38:51 -0400
Received: from d12relay01.megacenter.de.ibm.com (d12relay01.megacenter.de.ibm.com [9.149.165.180]) by d12lmsgate.de.ibm.com (8.12.10/8.12.8) with ESMTP id h9HDc6oS115336; Fri, 17 Oct 2003 15:38:06 +0200
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140]) by d12relay01.megacenter.de.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9HDc5mw237662; Fri, 17 Oct 2003 15:38:05 +0200
Received: from zurich.ibm.com (sig-9-145-145-206.de.ibm.com [9.145.145.206]) by ochsehorn.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id PAA70426; Fri, 17 Oct 2003 15:38:04 +0200
Message-ID: <3F8FF09D.7A9B0787@zurich.ibm.com>
Date: Fri, 17 Oct 2003 15:37:34 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: saad@ietf.org
Subject: Re: [saad] About saad
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C658@server2003.arneill-py.sacramento.ca.us> <018201c393ff$a7431200$396015ac@dclkempt40> <6.0.0.22.2.20031016120745.04522090@mira-sjc5-b.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This raises a meta-question in my mind.

How are we going to prevent this list simply repeating all the discussion
that took place in the NSRG and elsewhere?

The reasons why FQDNs are imperfect EIDs have been listed quite recently
(on one of the IPV6 lists I think).

   Brian

Fred Baker wrote:
> 
> At 12:07 PM 10/16/2003, James Kempf wrote:
> >An IP address acts in two roles:
> >
> >1) As a node or endpoint identifier to the transport layer for an end to end
> >conversation.
> >
> >2) As a locator for routing packets to a particular topological location.
> 
> actually, I will argue that the endpoint identifier is the dns name. That
> has problems in that
> 
>   - it needs to be able to name a service and get the address of the most
> serviceable instance of a computer offering it to the requestor; it
> currently simply offers *an* address of a list of addresses from which the
> requestor needs to choose at random
> 
>   - it presumes a global address space (there is no concept of "source
> route to this gateway address and then to that private address", or the
> obvious generalization)
> 
>   - A list of other things I will think of just after I send this email
> 
> But it in fact acts to identify the intended endpoint.
> 
> _______________________________________________
> Saad mailing list
> Saad@ietf.org
> https://www1.ietf.org/mailman/listinfo/saad

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Distinguished Engineer, Internet Standards & Technology, IBM 

NEW ADDRESS <brc@zurich.ibm.com> PLEASE UPDATE ADDRESS BOOK

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