Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS

Rémi Després <despres.remi@laposte.net> Tue, 18 October 2011 08:59 UTC

Return-Path: <despres.remi@laposte.net>
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 67E3B21F8C08 for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level:
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 2y86I59tv9ir for <softwires@ietfa.amsl.com>; Tue, 18 Oct 2011 01:59:22 -0700 (PDT)
Received: from smtp25.services.sfr.fr (smtp25.services.sfr.fr [93.17.128.121]) by ietfa.amsl.com (Postfix) with ESMTP id B4F5721F8BF7 for <softwires@ietf.org>; Tue, 18 Oct 2011 01:59:21 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id E5F66700062A; Tue, 18 Oct 2011 10:59:20 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2517.sfr.fr (SMTP Server) with ESMTP id BA35870001F2; Tue, 18 Oct 2011 10:59:20 +0200 (CEST)
X-SFR-UUID: 20111018085920762.BA35870001F2@msfrf2517.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <despres.remi@laposte.net>
In-Reply-To: <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net>
Date: Tue, 18 Oct 2011 10:59:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8481586C-8F3D-48C8-A9F6-C05BEFF5C067@laposte.net>
References: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net> <83A72484-7A54-4A30-AF9B-5FC9D97A9E14@gmail.com> <CAFUBMqWrw8e7sO80U74Q+UvJwW_sqxZZnnwTo7jhyayFBn5_Mg@mail.gmail.com> <6668E2F8-EEBA-4AF3-8110-2B0B43D3BC3E@gmail.com> <CAFUBMqVbZ7uTvHRpQDV1Y1eN9hJZ2tofzNvAM0hFHCrWZ_mA6g@mail.gmail.com> <596276A4-1C63-4A92-90FA-BC958DFB2053@gmail.com> <C7601B91-24ED-4C7F-A771-10F6AFE93F2F@laposte.net> <9D55CDB2-0DE1-441B-A622-22C3E2C66D4E@employees.org> <87BE3426-9B03-4D3E-AFBF-AB12923D2D84@laposte.net> <CAC8QAcd6TSnBkpE2+o0WS+QLdbEwRTO_NTgwqaN8ikWfmu2bpw@mail.gmail.com> <0A5AA31A-0A96-4D78-AC99-11FF58FDD217@laposte.net> <D2FC2906-23F3-4970-B35B-EECEBEBA1382@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] 4rd-U complement - e2e transparency to IPv4 TOS
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, 18 Oct 2011 08:59:22 -0000

Le 18 oct. 2011 à 10:21, Mark Townsley a écrit :

> 
> While it is interesting to explore the various design spaces, we do not need more ways to munge an IPv4 packet into an IPv6 packet and back to an IPv4 packet. Any alternative beyond the simple and obvious encap/decap that routers have used for decades is already too much IMHO, we certainly don't need a 3rd or 4th method.

> Let's please curtail new the inventions, and get back to the standardization.

Sorry that you see it that way.

The interim meeting has been useful in that objectives of present parties were clarified better than ever before.
Standardization is, and has always been, a process in which understanding each other, and finding ways to accommodate all valid concerns, are been key to success.
That's what I have been working for: good standardization. 

Would you please indicate what you personally challenge in this:
a) One standard is better than two.
b) Maintaining network transparency to IPv4 packets is a useful feature
c) Being able to apply IPv6 O&M tools to IPv4 traffic, e.g. with ACLs, is a useful feature
d) Encapsulation has b) but not c)
e) Double translation has c) but not b)
f) 4rd-U has both b) and c)
  
Regards,
RD