IETF Logo Mail Archive

Re: [lisp] We need LISP over HTTP!

Michael Menth <menth@uni-tuebingen.de> Wed, 30 September 2015 18:15 UTC

Return-Path: <menth@uni-tuebingen.de>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E32011A8884 for <lisp@ietfa.amsl.com>; Wed, 30 Sep 2015 11:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level:
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 wXNtlYa9AsWD for <lisp@ietfa.amsl.com>; Wed, 30 Sep 2015 11:15:41 -0700 (PDT)
Received: from mx09.uni-tuebingen.de (mx09.uni-tuebingen.de [134.2.5.219]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76A651A8857 for <lisp@ietf.org>; Wed, 30 Sep 2015 11:15:41 -0700 (PDT)
Received: from [192.168.1.100] (hsi-kbw-095-208-119-238.hsi5.kabel-badenwuerttemberg.de [95.208.119.238]) (authenticated bits=0) by mx09.uni-tuebingen.de (8.14.3/8.14.3) with ESMTP id t8UIFTk0010999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 30 Sep 2015 20:15:34 +0200
To: Richard Li <renwei.li@huawei.com>, Damien Saucez <damien.saucez@gmail.com>
References: <74B6E61C-5E38-4CA4-BD6C-90E9B6F7C4E9@gmail.com> <F061CEB6876F904F8EA6D6B92877731C38FF4174@SJCEML701-CHM.china.huawei.com>
From: Michael Menth <menth@uni-tuebingen.de>
X-Enigmail-Draft-Status: N1110
Message-ID: <560C26C1.1030206@uni-tuebingen.de>
Date: Wed, 30 Sep 2015 20:15:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <F061CEB6876F904F8EA6D6B92877731C38FF4174@SJCEML701-CHM.china.huawei.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2289
X-purgate-ID: 154962::1443636935-00000B99-28A2AB01/0/0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/LxSFR5qG0JPOI-2rMauRH2cCnmo>
Cc: Andreas Stockmayer <andreas.stockmayer@uni-tuebingen.de>, Mark Schmidt <mark-thomas.schmidt@uni-tuebingen.de>, LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] We need LISP over HTTP!
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 30 Sep 2015 18:15:44 -0000

Hi Renwei, hi Damien,

when using NAT traversal there is state anyway between the NAT traversal
router and the mobile node. What about just using HTTP instead of LISP
in the outer header between the mobile node and the NAT traversal router
for tunneling purposes? I don't see this causes more state than normal
NAT traversal.

If the NAT traversal functionality itself is not needed, one might still
use it to use an http tunnel to just one other node in the Internet
instead to many others which avoids the general state problem.

Regards,

Michael

Am 30.09.2015 um 18:54 schrieb Richard Li:
> It might solve your NAT problem, but I am afraid it is not a good idea to have something like LISP carried by TCP since you have to hold up the connection and transporting states between xTRs for each flow or each packet, which will bring you a huge scale problem. You could do experiments with it, but it is unlikely to get accepted in production networks.
> 
> Can you re-try it by re-configuring your NAT?
> 
> 
> Renwei
> 
> 
> -----Original Message-----
> From: lisp [mailto:lisp-bounces@ietf.org] On Behalf Of Damien Saucez
> Sent: Wednesday, September 30, 2015 6:48 AM
> To: LISP mailing list list
> Subject: [lisp] We need LISP over HTTP!
> 
> Dear all,
> 
> Today again I was in the situation where I was not able to run my LISP setup in the place I visited.
> All was supposed to work well using the NAT traversal. But reality was different: UDP traffic was filtered in the place.
> 
> So my question to the working group: who would be ready to start working on a technique to cary LISP over TCP and, even more horrible, over HTTP?
> 
> Thanks,
> 
> Damien Saucez
> _______________________________________________
> 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
> 

-- 
Prof. Dr. habil. Michael Menth
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505
fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de
http://kn.inf.uni-tuebingen.de

v2.23.0 | Report a Bug | By Email