Re: about the coexistance scenarios in draft-ietf-v6ops-nat64-pb-statement-req-01

Iljitsch van Beijnum <iljitsch@muada.com> Sun, 27 July 2008 21:52 UTC

Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0BF53A6956 for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 27 Jul 2008 14:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QUFjcgqWnQBy for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 27 Jul 2008 14:52:27 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id CC3483A6804 for <v6ops-archive@lists.ietf.org>; Sun, 27 Jul 2008 14:52:26 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1KNE9A-00081X-48 for v6ops-data@psg.com; Sun, 27 Jul 2008 21:51:20 +0000
Received: from [2001:1af8:2:5::2] (helo=sequoia.muada.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <iljitsch@muada.com>) id 1KNE8V-0007wu-Qv for v6ops@ops.ietf.org; Sun, 27 Jul 2008 21:50:41 +0000
Received: from [172.16.9.89] (guestroom-nat.meeting.ietf.org [130.129.64.64]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m6RLoB2p037505 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 27 Jul 2008 23:50:12 +0200 (CEST) (envelope-from iljitsch@muada.com)
Cc: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>, 'IPv6 Operations' <v6ops@ops.ietf.org>
Message-Id: <86E8999A-35B7-4594-B793-446B2E1C18FB@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
In-Reply-To: <4889E7AF.6080903@it.uc3m.es>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Re: about the coexistance scenarios in draft-ietf-v6ops-nat64-pb-statement-req-01
Date: Sun, 27 Jul 2008 22:50:22 +0100
References: <4889E7AF.6080903@it.uc3m.es>
X-Mailer: Apple Mail (2.926)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On 25 jul 2008, at 15:48, marcelo bagnulo braun wrote:

>  o  a dual stack system connected to a IPv6 domain that is connecting
>     to an IPv4 system.

Point of terminology:

Could we please all agree on what "dual stack" means?

The way I've always used the term is "a system that has both IPv4 and  
IPv6 connectivity, which is global in nature unless explicitly stated  
that it's only local or site-local". However, the above seems to use  
it in the sense "a system that is capable of using both IPv4 and IPv6".

The set of systems conforming to the former definition is obviously a  
subset of those conforming to the latter.

I contend that in 99% of all our discussions, it's useless to make the  
distinction between systems that have certain reachability for  
operational reasons and systems that have certain reachability because  
they don't support both IP versions. Using my definition of "dual  
stack" avoid wasting time in that 99% of cases.

Note also that the use case cited above is based on an unstated  
assumption, which is that if a host supports the second definition of  
dual stack, it must therefore be connected to the IPv4 internet.

The situation we want to reach is where hosts can have just IPv6  
connectivity and still be fully functional.