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

"Jose Saldana" <jsaldana@unizar.es> Fri, 01 April 2016 08:48 UTC

Return-Path: <jsaldana@unizar.es>
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 3BE6512D175; Fri, 1 Apr 2016 01:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 d3HNABY6HWxu; Fri, 1 Apr 2016 01:48:35 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36E5912D0EA; Fri, 1 Apr 2016 01:48:34 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id u318mR1X026984; Fri, 1 Apr 2016 10:48:27 +0200
From: Jose Saldana <jsaldana@unizar.es>
To: lisp@ietf.org, draft-boucadair-lisp-v6-compact-header@ietf.org
Date: Fri, 01 Apr 2016 10:48:54 +0200
Message-ID: <010d01d18bf3$5280edb0$f782c910$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_010E_01D18C04.160B4450"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdGL73j8/RBCR25FRcWH+WbTF0V2Lw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/wPnSgYU8aIUJy4Yecfo6PzMzD3U>
Subject: [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 08:48:38 -0000

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.
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).
 
 
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.
 
 
BR,
 
Jose