Re: IPv6 Address Architecture update question

Tim Chown <tjc@ecs.soton.ac.uk> Wed, 02 February 2005 15:58 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20578 for <ipv6-web-archive@ietf.org>; Wed, 2 Feb 2005 10:58:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwNBl-0003Qk-ML for ipv6-web-archive@ietf.org; Wed, 02 Feb 2005 11:17:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwMrq-0003Ho-1v; Wed, 02 Feb 2005 10:56:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwMiv-0008UL-MT for ipv6@megatron.ietf.org; Wed, 02 Feb 2005 10:47:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19163 for <ipv6@ietf.org>; Wed, 2 Feb 2005 10:47:16 -0500 (EST)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwN1H-00031e-Cw for ipv6@ietf.org; Wed, 02 Feb 2005 11:06:21 -0500
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131]) by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j12Fkwi3000052 for <ipv6@ietf.org>; Wed, 2 Feb 2005 15:46:58 GMT
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162]) by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id PAA08898 for <ipv6@ietf.org>; Wed, 2 Feb 2005 15:47:10 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j12FlAf31513 for ipv6@ietf.org; Wed, 2 Feb 2005 15:47:10 GMT
Date: Wed, 02 Feb 2005 15:47:10 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: IPv6 WG <ipv6@ietf.org>
Message-ID: <20050202154709.GX22722@login.ecs.soton.ac.uk>
Mail-Followup-To: IPv6 WG <ipv6@ietf.org>
References: <6.1.2.0.2.20050131043340.02fbf0c0@mailhost.iprg.nokia.com> <6.1.2.0.2.20050201032232.02f44e90@mailhost.iprg.nokia.com> <Pine.LNX.4.61.0502011737050.17853@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0502011737050.17853@netcore.fi>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: Re: IPv6 Address Architecture update question
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

On Tue, Feb 01, 2005 at 05:39:15PM +0200, Pekka Savola wrote:
> On Tue, 1 Feb 2005, Bob Hinden wrote:
> >My take of this is that they should remain in the IPv6 address 
> >architecture. There is current usage and removing them would break other 
> >specifications.
> 
> I would agree with that conclusion for mapped addresses, but I have 
> heard NO ONE explicitly saying anything about the usefulness of 
> compatible addresses.
> 
> Thus my take is that compatibles should be removed, and some kind of 
> warning/reference text added to the mapped addresses. 
> draft-ietf-v6ops-application-transition-03 (soon to be RFC) discusses 
> some of this.

Hi Pekka,

I thought compatibles had (or were) being removed.  That's why all reference
to them was removed from the new transition mechanisms RFC update?  See
section 9 of draft-ietf-v6ops-mech-v2-06.txt.   If we're doing a u-turn on
that, we should catch it in this draft too.

The docs at http://gsyc.escet.urjc.es/~eva/IPv6-web/ipv6.html and as
draft-ietf-v6ops-application-transition-03.txt (not -02!) show good 
practice.   Has the application-transition draft been last called yet?  
Could we get it pushed and cited here in this RFC update?

I didn't realise mapped was disabled on so many systems, very interesting.
I am indifferent on mapped addresses; they clearly have use, and are being 
used, but it's not a wholly 'clean' solution for some of the reasons posted
here and were we to start again...

I think Itojun's mapped-on-the-wire-harmful draft is also good to cite,
but that seems unlikely to ever complete?

-- 
Tim



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------