IETF Logo Mail Archive

Re: [Softwires] Fw: I-D Action: draft-mawatari-softwire-464xlat-00.txt

"Jan Zorz @ go6.si" <jan@go6.si> Tue, 29 November 2011 19:18 UTC

Return-Path: <jan@go6.si>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA8621F8C73 for <softwires@ietfa.amsl.com>; Tue, 29 Nov 2011 11:18:08 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7qfGPP4OAl2 for <softwires@ietfa.amsl.com>; Tue, 29 Nov 2011 11:18:08 -0800 (PST)
Received: from ipv6.go6.si (go6.si [212.44.108.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0755621F8C78 for <softwires@ietf.org>; Tue, 29 Nov 2011 11:18:08 -0800 (PST)
Received: from 76.9.wired.gter.nic.br (unknown [200.160.9.76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jan) by ipv6.go6.si (Postfix) with ESMTP id 429BE23780B5 for <softwires@ietf.org>; Tue, 29 Nov 2011 20:18:05 +0100 (CET)
Message-ID: <4ED52FF6.2020906@go6.si>
Date: Tue, 29 Nov 2011 20:18:14 +0100
From: "Jan Zorz @ go6.si" <jan@go6.si>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: softwires@ietf.org
References: <20111016084011.28691.24648.idtracker@ietfa.amsl.com> <20111016175357kawashimam@mail.jp.nec.com> <4ECE3B3C.8070703@skoberne.net> <CAD6AjGT4s1HUrcmy+79=Y45zsHuN_b4A5xpDP9Q2uQ7CM2s+Kg@mail.gmail.com>
In-Reply-To: <CAD6AjGT4s1HUrcmy+79=Y45zsHuN_b4A5xpDP9Q2uQ7CM2s+Kg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Softwires] Fw: I-D Action: draft-mawatari-softwire-464xlat-00.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2011 19:18:08 -0000

On 11/24/11 3:01 PM, Cameron Byrne wrote:
> I would also like to make it clear, that i believe softwires and
> behave should both be closed, all in-flight yet-another-transition
> mechanism work be abandoned as they are a hindrance and distraction to
> IPv6 deployment.  We already have 6 over 4, 4 over 6, and more than
> enough forms of translation.  Anything else is just counterproductive
> life-support and sends a confusing message from the IETF to the world
> that IPv6 is still not ready.

...and transition to IPv6 is not late due to lack of transition 
mechanisms, is it? :)

Moving IPv4 to deprecated would probably result in stopping developing 
v4-life-support mechanisms, that are actually just tools to avoid IPv6 
deployment, right?

>
> Perhaps the closing of softwire and behave can be followed by a new
> group called trans-man which does maintenance similar to 6man.

trans-man :)

Cheers, Jan

v2.23.0 | Report a Bug | By Email