[ipv6-dir] RE: Updated document

john.loughney@nokia.com Fri, 06 January 2006 03:58 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Euik9-0001FC-1m; Thu, 05 Jan 2006 22:58:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuWSl-0006dI-Ib; Thu, 05 Jan 2006 09:51:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23073; Thu, 5 Jan 2006 09:50:18 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuWYR-00056I-2p; Thu, 05 Jan 2006 09:57:28 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k05El94C013006; Thu, 5 Jan 2006 16:47:09 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Jan 2006 16:50:45 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Jan 2006 16:50:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 05 Jan 2006 16:50:44 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D01869A64@esebe100.NOE.Nokia.com>
Thread-Topic: Updated document
Thread-Index: AcYSALZl4QBQoDyaSQiZ2RmXJaz7oQABcilQ
To: pekka.nikander@nomadiclab.com, kurtis@kurtis.pp.se
X-OriginalArrivalTime: 05 Jan 2006 14:50:45.0570 (UTC) FILETIME=[689B0A20:01C61207]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 05 Jan 2006 22:58:17 -0500
Cc: leslie@thinkingcat.com, iab@ietf.org, MRW@devicescape.com, swb@employees.org, sob@harvard.edu, ipv6-dir@ietf.org
Subject: [ipv6-dir] RE: Updated document
X-BeenThere: ipv6-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IPv6 Directorate <ipv6-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6-dir>, <mailto:ipv6-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6-dir@ietf.org>
List-Help: <mailto:ipv6-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6-dir>, <mailto:ipv6-dir-request@ietf.org?subject=subscribe>
Sender: ipv6-dir-bounces@ietf.org
Errors-To: ipv6-dir-bounces@ietf.org

Pekka,

Wouldn't be correct to say that the IETF is working on the
identifier/locator split. I'm not
sure we need to say that it is a approach, but this is an area that the
IETF is working on.
I doubt we want the ITU-T making there own locator-split solutions!

Also, there are various MIPv4/MIPv6 dual stack approaches in the works
as well.   Various people
have talked about SCTP as a IPv4/IPv6 transition mechansims, and then
some people want to 'port'
SHIM6 to IPv4 as well ... 

I still like to think that IETF makes protocols and works on the
end-to-end architecture, and
other SDOs use the stuff we make, as they need them.

John

>-----Original Message-----
>From: ext Pekka Nikander [mailto:pekka.nikander@nomadiclab.com] 
>Sent: 05 January, 2006 16:02
>To: Kurt Erik Lindqvist
>Cc: ipv6-dir@ietf.org; Margaret Wasserman; IAB IAB; Loughney 
>John (Nokia-NRC/Helsinki); Brim Scott W; Bradner Scott; Leslie Daigle
>Subject: Re: Updated document
>
>> Please send comments!
>> <q.9-sg13-liasion-20060105.doc>
>>
>
>If we want to include speculative and forward looking text, I 
>propose the following for the "IPv4/IPv6 transition" bullet:
>
>---
>
>A potential future approach to IPv6/IPv4 interaction is to 
>implement the so called identifier/locator split in some way.  
>Among the various potential approaches being considered, the 
>approach used in the HIP working group 
>(draft-ietf-hip-arch-03.txt, in RFC Editor
>Queue) is among the more developed.  The parallel HIP research group  
>is studying the problems related to real life deployability of HIP.   
>If later decided to be adopted, HIP or some other 
>identifier/locator split approach may make the difference of 
>IPv4 and IPv6 irrelevant, allowing nodes to be mobile and 
>multi-homed between the two versions of IP, without any 
>IP-version related visibility to the applications.  [Technical 
>remark:  While the architectural approach taken by 
>identifier/locator split is different from the current 
>tunnelling and encapsulation approaches, at the actual 
>data-transport protocol level there is little if any 
>difference.  The differences lie in IP-layer state set up 
>between peer nodes and at the APIs available to the upper 
>layer protocols and applications.]
>
>---
>
>However, that text may be too speculative and/or something 
>that cannot be considered as a part of the IETF consensus.  I 
>am definitely biased here, and leave it for others to make the 
>evaluation.
>
>--Pekka
>
>

_______________________________________________
ipv6-dir mailing list
ipv6-dir@ietf.org
https://www1.ietf.org/mailman/listinfo/ipv6-dir