Re: [lisp] [5gangip] Bandwidth savings with LISP

Dino Farinacci <farinacci@gmail.com> Tue, 05 July 2016 17:56 UTC

Return-Path: <farinacci@gmail.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 75FA412D731; Tue, 5 Jul 2016 10:56:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1rBpKaVsKToU; Tue, 5 Jul 2016 10:56:30 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E005612D732; Tue, 5 Jul 2016 10:56:15 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id c2so72249915pfa.2; Tue, 05 Jul 2016 10:56:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i19cZokdNgwXhtR/sCvsiHJGTaPP807DvgypfZfULNs=; b=PCtrF95I/4Un5/icc0TE1LmsGc6ilWlC0/Y5pOI/X5Gw+FQepRC+FqEoULARXnB/7V C1qE99fWT4XyKPnrEHH0A7wzJsDfUiTZcsjWLf9JAxcmaRGfS8qSdhjiJX/X6Y+mv6Y8 rqzFNF+EliwhN3wXNdqXsv6NEhfSwjOmH3LdN/z+l3NUGIHZgvWaNudtyj8xtYjDU3yE vrc0UYh5dwqw8aeHCO7fHREzn+nHHZnRr2LQTvC+Q9BVDgz6Ktd8TK7jmIOF+xP1glOB +rrVEcOeZFSnmrCk0i9OnYZqNQSI91PN3jMvyU629gnALTojowj4UooS06odrkMfipYo amQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i19cZokdNgwXhtR/sCvsiHJGTaPP807DvgypfZfULNs=; b=mPjyVtZlmUTzFWc1f7isLKNMo5SypSgsORyO5eDchVjren5m4GJ9WtNPfugmKFKkzR cUqszBKUwBfVMoSHdZ36W+0x/aysemlbOVpVO/f0YLWlrc5PyKkgp6ZrwZDPN2SvnuV1 TtxThG56W+22dhqkp4XsE5oHwc+X1JtR50OspRoQKRFY+CKlo812XR9YcKNYXDIPnC1h IlRdG6V80fRQzGBbCjdpPCcD+7wyRknYLQg4bXCpLE0fNam9sGfdj/6YQdVNs5hfH8U7 1OAj7QR8UNcAiPz7foXzggdgFUi+GeDWPGIJWbx3lg+DvYkT6q2yuFcnAQz88UBljEzM OQ8w==
X-Gm-Message-State: ALyK8tKUwf7tq3QH7OPVYpbRV2+toCn06xHVy1MCckgzVoPr8S0RKb2V/78LOY9Vg+SzdQ==
X-Received: by 10.98.102.133 with SMTP id s5mr34600664pfj.75.1467741375444; Tue, 05 Jul 2016 10:56:15 -0700 (PDT)
Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id zv2sm6903440pac.43.2016.07.05.10.56.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 05 Jul 2016 10:56:14 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <7AE6A4247B044C4ABE0A5B6BF427F8E230952CF1@YYZEML701-CHM.china.huawei.com>
Date: Tue, 05 Jul 2016 10:57:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <00E46299-0548-4A69-A36C-7DE88BA3333C@gmail.com>
References: <007601d1cd2f$3a8cad70$afa60850$@unizar.es> <576C060C.2070907@cisco.com> <00ab01d1d38d$17365060$45a2f120$@unizar.es> <6C1441C1-90C3-457B-8146-4869C9FE5929@gmail.com> <7AE6A4247B044C4ABE0A5B6BF427F8E230952CF1@YYZEML701-CHM.china.huawei.com>
To: AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/fbQwpmWxIDuYuivUzFDvboX_BNI>
Cc: "5gangip@ietf.org" <5gangip@ietf.org>, José Ruiz Mas <jruiz@unizar.es>, LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] [5gangip] Bandwidth savings with LISP
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: Tue, 05 Jul 2016 17:56:32 -0000

> Hey Dino,
> 
> Queuing also happens when a UE is has been idle for a while and is being paged. 
> 
> On the header size issue, one of the complaints I've made about ICN/CCN etc. and 5G is the increased header sizes and the impact that this has on the most expensive resource (by a wide margin), the RF spectrum. 

So you are saying large packets would have the same disadvanage. Therefore, small headers on small payloads is the most optimal design space?

> Not much point optimizing all the relatively cheap wired links if the tax then goes up on the incredibly expensive wireless links.

Right.

> Finding a way to properly map multicast/broadcast to the natural RF multicast would seem like a smart thing to do to extend some of the bandwidth savings protocols like ICN/CCN give but there are challenges with this as each UE may have a different RF encoding (due to different channel conditions) and therefore require separate copies anyway.

Right, another topic. But thanks for raising it.

Dino

> 
> Cheers
> 
> Peter
> 
> -----Original Message-----
> From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of Dino Farinacci
> Sent: Friday, July 01, 2016 1:06 PM
> To: Jose Saldana
> Cc: 5gangip@ietf.org; José Ruiz Mas; LISP mailing list list; Anton Smirnov
> Subject: Re: [5gangip] [lisp] Bandwidth savings with LISP
> 
> So I have been thinking about a compelling use-case for LISP header-compression and the super-framing feature (sorry for using my own term).
> 
> I have been told that the Radio Access Network (RAN) tends to be sensitive to overlay solutions due to large headers. I have also heard that there seems to be queuing behavior for the base-stations that send to UEs (i.e. phones). The fact that queuing is happening while waiting for a handoffs to occur can be a good opportunity to pack IP packets into super-frames to send over the RAN.
> 
> Using this solution means the eNodeB (base-station) and the UE (phone) would have to run LISP. I would like to hear comments from the WG. I have copied 5gangip to see if they have opinions.
> 
> Dino
> 
>> On Jul 1, 2016, at 4:38 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>> 
>> Hi again, Anton.
>> 
>> I have just uploaded a new presentation including more ideas and also a section about backward compatibility:
>> 
>> http://es.slideshare.net/josemariasaldana/header-compression-and-multi
>> plexing-in-lisp
>> 
>> BR and thanks,
>> 
>> Jose
>> 
>>> -----Mensaje original-----
>>> De: Anton Smirnov [mailto:asmirnov@cisco.com] Enviado el: jueves, 23 
>>> de junio de 2016 17:54
>>> Para: Jose Saldana <jsaldana@unizar.es>; lisp@ietf.org
>>> CC: 'José Ruiz Mas' <jruiz@unizar.es>
>>> Asunto: Re: [lisp] Bandwidth savings with LISP
>>> 
>>>   Hi Jose,
>>>   there is a theoretical aspect of the work (it's curious) and then 
>>> there is a practical one. For the latter one - section "Backward 
>>> compatibility" is conspicuously missing from the document. On the 
>>> first glance, it looks like backward compatibility of the solution was not investigated. Is this correct?
>>> 
>>> Anton
>>> 
>>> 
>>> On 06/23/2016 11:11 AM, Jose Saldana wrote:
>>>> Hi all,
>>>> 
>>>> As you may know, we recently submitted a draft
>>> (https://datatracker.ietf.org/doc/draft-saldana-lisp-compress-mux/) 
>>> with a proposal allowing bandwidth and pps reductions.
>>>> 
>>>> The idea is to send together a number of small packets, which are in 
>>>> the buffer of
>>> an ITR and have the same ETR as destination, into a single packet. 
>>> Therefore, they will share a single LISP header. And this can be 
>>> combined with ROHC (header compression).
>>>> 
>>>> We have a running implementation, based on LISPMob 
>>>> (https://github.com/Simplemux/lispmob-with-simplemux), which we have 
>>>> used to run some tests
>>>> 
>>>> This is a summary of the results.
>>>> 
>>>> - When small packets (100 bytes) are sent, up to 63% of throughput 
>>>> increase can
>>> be observed (in our example, we pass from 550kbps to 910kbps).
>>>> 
>>>> - In the case of securing the LISP tunnel with IPSec, the increase 
>>>> can be 935
>>> (from 470kbps to 870kbps).
>>>> 
>>>> You can find more detailed information in this presentation:
>>>> http://es.slideshare.net/josemariasaldana/header-compression-and-mul
>>>> ti
>>>> plexing-in-lisp
>>>> 
>>>> Your feedback will be highly appreciated.
>>>> 
>>>> Best regards,
>>>> 
>>>> The authors
>>>> 
>>>>> -----Mensaje original-----
>>>>> De: lisp [mailto:lisp-bounces@ietf.org] En nombre de Jose Saldana 
>>>>> Enviado el: miércoles, 04 de mayo de 2016 18:41
>>>>> Para: lisp@ietf.org
>>>>> CC: 'Jose Ruiz Mas' <jruiz@unizar.es>
>>>>> Asunto: [lisp] New draft posted:
>>>>> draft-saldana-lisp-compress-mux-00.txt
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> We have just posted this draft
>>>>> https://datatracker.ietf.org/doc/draft-saldana-lisp-
>>>>> compress-mux/.
>>>>> 
>>>>>              Header compression and multiplexing in LISP
>>>>>                   draft-saldana-lisp-compress-mux-00
>>>>> 
>>>>> Abstract
>>>>> 
>>>>>   When small payloads are transmitted through a packet-switched
>>>>>   network, the resulting overhead may result significant.  This is
>>>>>   stressed in the case of LISP, where a number of headers are prepended
>>>>>   to a packet, as new headers have to be added to each packet.
>>>>> 
>>>>>   This document proposes to send together a number of small packets,
>>>>>   which are in the buffer of a ITR, having the same ETR as destination,
>>>>>   into a single packet.  Therefore, they will share a single LISP
>>>>>   header, and therefore bandwidth savings can be obtained, and a
>>>>>   reduction in the overall number of packets sent to the network can be
>>>>>   achieved.
>>>>> 
>>>>> A running implementation can be found here:
>>>>> https://github.com/Simplemux/lispmob-with-simplemux. I has been 
>>>>> built as a fork of lispmob.
>>>>> 
>>>>> The idea is very similar to what was published in this paper:
>>>>> http://diec.unizar.es/~jsaldana/personal/budapest_ICC_2013_in_proc.
>>>>> pd
>>>>> f
>>>>> 
>>>>> Your feedback about the draft will be appreciated.
>>>>> 
>>>>> Thanks in advance,
>>>>> 
>>>>> Jose Saldana
>>>>> Julián Fernández Navajas
>>>>> José Ruiz Mas
>>>>> 
>>>>>> -----Mensaje original-----
>>>>>> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
>>>>>> Enviado
>>>>>> el: miércoles, 04 de mayo de 2016 18:20
>>>>>> Para: Jose Ruiz Mas <jruiz@unizar.es>; Jose Saldana 
>>>>>> <jsaldana@unizar.es>; Julian Fernandez Navajas <navajas@unizar.es>
>>>>>> Asunto: New Version Notification for 
>>>>>> draft-saldana-lisp-compress-mux-00.txt
>>>>>> 
>>>>>> 
>>>>>> A new version of I-D, draft-saldana-lisp-compress-mux-00.txt
>>>>>> has been successfully submitted by Jose Saldana and posted to the 
>>>>>> IETF repository.
>>>>>> 
>>>>>> Name:		draft-saldana-lisp-compress-mux
>>>>>> Revision:	00
>>>>>> Title:		Header compression and multiplexing in LISP
>>>>>> Document date:	2016-05-04
>>>>>> Group:		Individual Submission
>>>>>> Pages:		8
>>>>>> URL:
>>>>>> https://www.ietf.org/internet-drafts/draft-saldana-lisp-compress-m
>>>>>> ux
>>>>>> -
>>>>>> 00.txt
>>>>>> Status:
>>>>>> https://datatracker.ietf.org/doc/draft-saldana-lisp-compress-mux/
>>>>>> Htmlized:
>>>>>> https://tools.ietf.org/html/draft-saldana-lisp-compress-mux-00
>>>>>> 
>>>>>> 
>>>>>> Abstract:
>>>>>>   When small payloads are transmitted through a packet-switched
>>>>>>   network, the resulting overhead may result significant.  This is
>>>>>>   stressed in the case of LISP, where a number of headers are prepended
>>>>>>   to a packet, as new headers have to be added to each packet.
>>>>>> 
>>>>>>   This document proposes to send together a number of small packets,
>>>>>>   which are in the buffer of a ITR, having the same ETR as destination,
>>>>>>   into a single packet.  Therefore, they will share a single LISP
>>>>>>   header, and therefore bandwidth savings can be obtained, and a
>>>>>>   reduction in the overall number of packets sent to the network can be
>>>>>>   achieved.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Please note that it may take a couple of minutes from the time of 
>>>>>> submission until the htmlized version and diff are available at 
>>>>>> tools.ietf.org.
>>>>>> 
>>>>>> The IETF Secretariat
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> lisp mailing list
>>>>> lisp@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>> 
>>>> 
>>>> _______________________________________________
>>>> lisp mailing list
>>>> lisp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>> 
>> 
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip