Re: IPv6 Address Architecture update question

Pekka Savola <pekkas@netcore.fi> Mon, 07 February 2005 07:57 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 CAA02804 for <ipv6-web-archive@ietf.org>; Mon, 7 Feb 2005 02:57:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy450-0001KQ-8Y for ipv6-web-archive@ietf.org; Mon, 07 Feb 2005 03:17:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy3dL-0007Vu-6f; Mon, 07 Feb 2005 02:48:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy3ck-0007NH-Mh for ipv6@megatron.ietf.org; Mon, 07 Feb 2005 02:48:02 -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 CAA02222 for <ipv6@ietf.org>; Mon, 7 Feb 2005 02:47:56 -0500 (EST)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy3w4-00018r-Og for ipv6@ietf.org; Mon, 07 Feb 2005 03:07:58 -0500
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id j177lEE30417; Mon, 7 Feb 2005 09:47:14 +0200
Date: Mon, 07 Feb 2005 09:47:14 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20050202154709.GX22722@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.61.0502070944320.30326@netcore.fi>
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> <20050202154709.GX22722@login.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: IPv6 WG <ipv6@ietf.org>
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: bb8f917bb6b8da28fc948aeffb74aa17

Now that the thread has quieted down..

On Wed, 2 Feb 2005, Tim Chown wrote:
> 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.

Totally agree, of course.  Including them here just adds confusion 
because the readers think that is another addressing format they will 
have to remember.

> 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?

Application-transition was approved about 3-4 months ago, and is very 
soon to become RFC, and could be cited here as an informative 
reference.

draft-ietf-v6ops-application-transition-03.txt also discusses briefly 
the tradeoffs that the app writer has to make regarding portability 
because the mapped addresses are not available on all the platforms.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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