Re: Why Scopes? (was: Re: [saad] About saad)

Melinda Shore <mshore@cisco.com> Fri, 17 October 2003 22:05 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 SAA26386 for <saad-archive@odin.ietf.org>; Fri, 17 Oct 2003 18:05: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 1AAciU-0005eR-Up for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 18:05:02 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HM52Vm021724 for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 18:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAciU-0005eH-Oo for saad-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 18:05: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 SAA26331 for <saad-web-archive@ietf.org>; Fri, 17 Oct 2003 18:04:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAciR-00027K-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 18:05:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAciR-00027H-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 18:04:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAciT-0005df-7A; Fri, 17 Oct 2003 18:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAchZ-0005d5-1N for saad@optimus.ietf.org; Fri, 17 Oct 2003 18:04:05 -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 SAA26228 for <saad@ietf.org>; Fri, 17 Oct 2003 18:03:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAchW-00026w-00 for saad@ietf.org; Fri, 17 Oct 2003 18:04:02 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AAchV-00026X-00 for saad@ietf.org; Fri, 17 Oct 2003 18:04:01 -0400
Received: from cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 17 Oct 2003 15:13:40 -0700
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9HM3T1b005677; Fri, 17 Oct 2003 15:03:29 -0700 (PDT)
Received: from cisco.com (stealth-10-32-241-42.cisco.com [10.32.241.42]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with SMTP id ANG77459; Fri, 17 Oct 2003 15:03:28 -0700 (PDT)
Date: Fri, 17 Oct 2003 18:03:26 -0400
Subject: Re: Why Scopes? (was: Re: [saad] About saad)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <saad@ietf.org>
To: "James Kempf" <kempf@docomolabs-usa.com>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <035501c394eb$c0f0fc70$396015ac@dclkempt40>
Message-Id: <BB9B7228-00ED-11D8-B6D5-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
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

On Friday, October 17, 2003, at 04:17 PM, James Kempf wrote:
> Suppose that, instead of a NAT, I could buy a box that had some number 
> of
> globally routable IP addresses preconfigured into it (and I could get 
> more
> by downloading them from the manufacturer via their Web page, maybe 
> paying a
> small fee).

This is not obviously going to work for v4 but I think is
one piece of a reasonably attractive approach.  Conflating
reachability and routing has caused some real problems.  But
when we look at stuff like VoIP applications it becomes
reasonably clear (at least to me, but obviously I'm biased)
that that sort of access device is still going to introduce
a heap of problems unless there's some sort of communication
with the host about what the host *really* wants (instead of
having the software on the access device make informed guesses).
Receiving end-to-end (i.e. unmediated signaling) telephone
calls is a good test case for whether or not these things can
work.

Melinda


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