Re: [lisp] We need LISP over HTTP!

Richard Li <renwei.li@huawei.com> Wed, 30 September 2015 16:54 UTC

Return-Path: <renwei.li@huawei.com>
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 ED6F21A710D for <lisp@ietfa.amsl.com>; Wed, 30 Sep 2015 09:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 lrlqqNC6eL0K for <lisp@ietfa.amsl.com>; Wed, 30 Sep 2015 09:54:31 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A312F1A8782 for <lisp@ietf.org>; Wed, 30 Sep 2015 09:54:30 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BYF40009; Wed, 30 Sep 2015 16:54:28 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.218.25.35) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 30 Sep 2015 17:54:27 +0100
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.220]) by SJCEML702-CHM.china.huawei.com ([169.254.4.95]) with mapi id 14.03.0235.001; Wed, 30 Sep 2015 09:54:22 -0700
From: Richard Li <renwei.li@huawei.com>
To: Damien Saucez <damien.saucez@gmail.com>
Thread-Topic: [lisp] We need LISP over HTTP!
Thread-Index: AQHQ+4a1sy9jdTmKJEGFTUD81fk9NZ5VR3Qg
Date: Wed, 30 Sep 2015 16:54:21 +0000
Message-ID: <F061CEB6876F904F8EA6D6B92877731C38FF4174@SJCEML701-CHM.china.huawei.com>
References: <74B6E61C-5E38-4CA4-BD6C-90E9B6F7C4E9@gmail.com>
In-Reply-To: <74B6E61C-5E38-4CA4-BD6C-90E9B6F7C4E9@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.213.48.32]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/_IEgsFacx6rAo9B9Ma35u4sRDKA>
Cc: 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 16:54:33 -0000

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