Re: question about draft-irtf-nsrg-report-09.txt

Eliot Lear <lear@cisco.com> Thu, 24 April 2003 15:20 UTC

Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19649; Thu, 24 Apr 2003 11:20:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 198io1-0004iT-00 for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 11:38:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 198ins-0004h4-00 for ietf@ran.ietf.org; Thu, 24 Apr 2003 11:38:28 -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 LAA19546 for <ietf@ietf.org>; Thu, 24 Apr 2003 11:16:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 198iUa-0006X7-00 for ietf@ietf.org; Thu, 24 Apr 2003 11:18:32 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237]) by ietf-mx with esmtp (Exim 4.12) id 198iUZ-0006Wy-00 for ietf@ietf.org; Thu, 24 Apr 2003 11:18:31 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164]) by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3OFIQ08019310; Thu, 24 Apr 2003 08:18:27 -0700 (PDT)
Received: from cisco.com (sjc-vpn2-765.cisco.com [10.21.114.253]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA29313; Thu, 24 Apr 2003 08:18:25 -0700 (PDT)
Message-ID: <3EA80042.7040301@cisco.com>
Date: Thu, 24 Apr 2003 08:18:26 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
CC: ietf@ietf.org
Subject: Re: question about draft-irtf-nsrg-report-09.txt
References: <20030424124705.GB23217@rvdp.org>
In-Reply-To: <20030424124705.GB23217@rvdp.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

In answer to your questions, various people felt that IPv6 was enough, 
and that the IP address could be used as the end point identifier.  Even 
in the case of mobility it was felt that MIPv6 would serve the purpose 
of a stable identifier.  As is pointed out in the draft, the flaw in 
this idea is that even the MIPv6 MN address is tied to the topology.

Eliot

Ronald van der Pol wrote:

> <quote>
> 4. Conclusions or Questions
> 
>    The NSRG was not able to come to unanimity as to whether an
>    architectural change is needed.
> </quote>
> 
> There has been a lot of discussion about the separation of identifiers
> and locators (in various forms) on the multi6, ipv6 and ietf lists.
> A lot of people seem to think this is in some form needed.
> 
> I would like to know the arguments against such a change. I don't
> think the document has much text about this. It lists a lot of
> questions. But most are more "how" than "why" questions. Are there
> many people fundamentally against a change and if so, why?
> 
> 	rvdp
> 
> 
>