Re: [lisp] A question regarding draft-boucadair-lisp-v6-compact-header

<mohamed.boucadair@orange.com> Fri, 01 April 2016 12:31 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8DF912D581; Fri, 1 Apr 2016 05:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GxjuWj9HzmO3; Fri, 1 Apr 2016 05:31:29 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7496512D1AC; Fri, 1 Apr 2016 05:31:28 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 8F62E3B41F0; Fri, 1 Apr 2016 14:31:26 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.69]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 6203435C078; Fri, 1 Apr 2016 14:31:26 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%18]) with mapi id 14.03.0279.002; Fri, 1 Apr 2016 14:31:26 +0200
From: mohamed.boucadair@orange.com
To: Jose Saldana <jsaldana@unizar.es>, "lisp@ietf.org" <lisp@ietf.org>, "draft-boucadair-lisp-v6-compact-header@ietf.org" <draft-boucadair-lisp-v6-compact-header@ietf.org>
Thread-Topic: A question regarding draft-boucadair-lisp-v6-compact-header
Thread-Index: AdGL73j8/RBCR25FRcWH+WbTF0V2LwAHq/Iw
Date: Fri, 01 Apr 2016 12:31:24 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008D2710F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <010d01d18bf3$5280edb0$f782c910$@unizar.es>
In-Reply-To: <010d01d18bf3$5280edb0$f782c910$@unizar.es>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933008D2710FOPEXCLILMA3corp_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.4.1.114517
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/nUQl5C687tpMX1L2AQN-PZqLXSc>
Subject: Re: [lisp] A question regarding draft-boucadair-lisp-v6-compact-header
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 12:31:31 -0000

Dear Jose,

Thank you for sharing the comment.

Please see inline.

Cheers,
Med

De : Jose Saldana [mailto:jsaldana@unizar.es]
Envoyé : vendredi 1 avril 2016 10:49
À : lisp@ietf.org; draft-boucadair-lisp-v6-compact-header@ietf.org
Objet : A question regarding draft-boucadair-lisp-v6-compact-header

Dear Mohamed and Christian,

I have read your draft about a compact header for LISP to avoid MTU issues.

However, have you also considered bandwidth savings for small packets as an additional benefit? I mean, when you use LISP to send small packets between two locations, the overhead is huge:

a) For example, if you are sending an IPv4 TCP ACK (40 bytes), with standard LISP over IPv6 you need 96 bytes:

OH (IPv6): 40 bytes
UDP: 8 bytes
LISP: 8 bytes
IH (IPv4): 20 bytes
TCP: 20 bytes

However, if you use the compact header proposed in your draft, you will only need 72 bytes (if I am right), so you are saving 25% of the bandwidth.

[Med] You are right about the bandwidth saving. In fact, the saving depends on the version of the compact header you consider. Indeed:
* Compact header 1 requires: 68 (40 (IPv6 OH) + 8 (UDP) + 12 (Truncated TCP) + 8 (LISP))
* Compact header 2 requires: 64 (40 (IPv6 OH) + 8 (UDP) + 12 (Truncated TCP) + 4 (LISP)).

The gain is much more important compared to the legacy LISP IPv4-in-IPv6 encapsulation: 29% or 33%.

Taking into account that there is a high amount of TCP ACKs, this may perhaps have an impact.


b) Or if you are sending an RTP sample with e.g. 20 bytes of payload, using standard LISP over IPv6, you need 116 bytes:

OH (IPv6): 40 bytes
UDP: 8 bytes
LISP: 8 bytes
IH (IPv4): 20 bytes
UDP: 8 bytes
RTP: 12 bytes
Payload: 20 bytes

But if you use the compact header, you will only need 88 bytes (24% saving).

[Med] Yes, modulo the following clarifications. The size of the packet will be:

* Compact header 1: 80 (40 (IPv6 OH) + 8 (UDP) + 8 (LISP) + 12 (RTP) + 20 (Payload))
* Compact header 2: 76 (40 (IPv6 OH) + 8 (UDP) + 4 (LISP) + 12 (RTP) + 20 (Payload)).

Which means, a saving of 31% (Compact header 1) and 34% (Compact header 2).

In order to increase these savings, we are currently considering the possibility of submitting a draft adding header compression with ROHC, and multiplexing a number of small packets into a single LISP one, if the ITR has a number of small packets in its buffer. Reducing the number of packets will reduce the processing in intermediate routers, also reducing e.g. energy consumption and perhaps some processing delays.

[Med] that's another complementary interesting approach to investigate.



BR,

Jose