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

Rémi Després <despres.remi@laposte.net> Mon, 17 October 2011 12:36 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 AA17321F8772 for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 05:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.614
X-Spam-Level:
X-Spam-Status: No, score=-1.614 tagged_above=-999 required=5 tests=[AWL=0.335, 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 QQxi2bqkDPvb for <softwires@ietfa.amsl.com>; Mon, 17 Oct 2011 05:36:33 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086BE21F8713 for <softwires@ietf.org>; Mon, 17 Oct 2011 05:36:33 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2103.sfr.fr (SMTP Server) with ESMTP id E7237700016C; Mon, 17 Oct 2011 14:36:31 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2103.sfr.fr (SMTP Server) with ESMTP id B7AEE70001C2; Mon, 17 Oct 2011 14:36:27 +0200 (CEST)
X-SFR-UUID: 20111017123627752.B7AEE70001C2@msfrf2103.sfr.fr
From: Rémi Després <despres.remi@laposte.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 17 Oct 2011 14:36:27 +0200
Message-Id: <85015B23-C124-43DB-913D-3829B895C2A9@laposte.net>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>
Subject: [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: Mon, 17 Oct 2011 12:36:33 -0000

Hi Satoru-san,

Thank you for identifying a limitation of the 4rd-U  
You are right, as currently specified, "it doesn't support diff-serv tunneling model, pipe and short-pipe".
All these need e2e transparency to the IPv4 Type of Service.

Fortunately, this is easy to fix: in the Identification field of the IPv6 Fragment header, copy not only the DF bits but also the IPv4 TOS.
  
The proposed 4r-U packet format becomes:


   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Vers=6 |   TrafClass   |            Flow Label                 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Payload Length        |Next Header=44 |   Hop Limit   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                                                               |
   +                  IPv6 Source Address                          +
   |                                                               |
   +                                                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   +                                                               +
   |                                                               |
   +                IPv6 Destination Address                       +
   |                                                               |
   +                                                               +
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Next Header  |    Reserved   | IPv6  Fragment Offset   | 0 |M|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |D|      0      |    IPv4 TOS   |       IPv4 Identification     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
   |                        IPv4 Payload                           |
   |                                                               | 

With this added, I believe that 4rd-U is a real progress over previously proposed Double translation and Encapsulation.
It can make IMHO a valuable unified standard.

Yet, I may have missed something else. 
New justified objections are therefore most welcome..


Regards,
RD