IETF Logo Mail Archive

Re: [lisp] [Ila] LISP for ILA

Uma Chunduri <uma.chunduri@huawei.com> Fri, 16 March 2018 20:36 UTC

Return-Path: <uma.chunduri@huawei.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 7B179124C27; Fri, 16 Mar 2018 13:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 IrYpUlAWmrfd; Fri, 16 Mar 2018 13:36:50 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBE21124BAC; Fri, 16 Mar 2018 13:36:49 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id F253E76807969; Fri, 16 Mar 2018 20:36:44 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 16 Mar 2018 20:36:47 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.91]) by SJCEML702-CHM.china.huawei.com ([169.254.4.179]) with mapi id 14.03.0382.000; Fri, 16 Mar 2018 13:36:38 -0700
From: Uma Chunduri <uma.chunduri@huawei.com>
To: Dino Farinacci <farinacci@gmail.com>
CC: David Meyer <dmm@1-4-5.net>, "ila@ietf.org" <ila@ietf.org>, Tom Herbert <tom@quantonium.net>, "lisp@ietf.org" <lisp@ietf.org>, Paul Vinciguerra <pvinci@VinciConsulting.com>
Thread-Topic: [Ila] [lisp] LISP for ILA
Thread-Index: AQHTvVhWEFyKOcHLDE2x54v999WwnaPTN8zggACIeID//4/tsA==
Date: Fri, 16 Mar 2018 20:36:38 +0000
Message-ID: <25B4902B1192E84696414485F57268541354C7E8@SJCEML521-MBB.china.huawei.com>
References: <F1093230-C087-4168-9C5F-8DA7AB677677@cisco.com> <CAPDqMer58nxEixtH=JuZh9WgM0xKkEQYEjwZ6zg3wTjD76gOHQ@mail.gmail.com> <F920CAE2-9042-41DF-B013-E8FE6F891596@cisco.com> <CAPDqMeriMzM82-R-JOgx4zuqJTk2YOoBaWV_58no2V8yPas9QA@mail.gmail.com> <CF1C238D-FBE9-48BC-A7A6-49E45249E5E2@cisco.com> <CAPDqMeqL1kE+N9APFOSR4fUaek0TjZuDZMZDzDmJfMvyLO38GA@mail.gmail.com> <DA74C61A-647A-44BA-8FE7-916CF8895C49@gmail.com> <CAPDqMeqkGH0ELN=XmqF3dmsdeAurE-y+_H9+_E8mzhHo9d9nXw@mail.gmail.com> <7793B214-A235-4795-983B-CCC75A0B90BE@gmail.com> <CAPDqMeo2bdmwSEkPk002W9oxPhyxnLrr-k9MYeR5ZXEG_OGH0g@mail.gmail.com> <11EDF4FB-8636-4DF2-B687-1AB4934C4F9D@gmail.com> <CAPDqMeoSLqC=mN_hcgiLe-3Dv0c=uezbrZZ9xHn47Osb7rfLVQ@mail.gmail.com> <16F3AEC4-EDCF-417B-8165-D22C48A06F3D@gmail.com> <B5A8E79CDD2131468993EFC2426361DD9FB450C3@NYDC-EXCH01.vinci-consulting-corp.local> <25B4902B1192E84696414485F57268541354C741@SJCEML521-MBB.china.huawei.com> <721A6669-9875-464D-9AA4-8BD4F270EBDA@gmail.com>
In-Reply-To: <721A6669-9875-464D-9AA4-8BD4F270EBDA@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.209.216.249]
Content-Type: multipart/alternative; boundary="_000_25B4902B1192E84696414485F57268541354C7E8SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/1wvK6imeHRU3dTD-SuZJkui5IHo>
Subject: Re: [lisp] [Ila] LISP for ILA
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Mar 2018 20:36:53 -0000



            -----Original Message-----
            From: ila [mailto:ila-bounces@ietf.org] On Behalf Of Dino Farinacci
            Sent: Friday, March 16, 2018 1:10 PM
            To: Uma Chunduri <uma.chunduri@huawei.com>
            Cc: David Meyer <dmm@1-4-5.net>; ila@ietf.org; Tom Herbert <tom@quantonium.net>; lisp@ietf.org; Paul Vinciguerra <pvinci@VinciConsulting.com>
            Subject: Re: [Ila] [lisp] LISP for ILA

            > A. Scalability
            > B. Security
            > C. Privacy
            > D.  Dos/DDOS Prevention
            >
            > While one can relatively handle #A and #B IMO - #C* and #D are still
            > the hardest problems (despite all the research).

            Was there a reason you singled out privacy and just didn’t include it under security?

You can easily secure (origin auth, integrity protection, encryption, protection from reply attacks etc) all on the wire stuff with matured protocols from outside observers/from intermediate nodes in the network.

This is obviously not true w.r.t keeping the secured data anonymously. Remember the argument, how your provider itself is compromised (all bets are off)??

A great reference to the privacy topic to me though: https://tools.ietf.org/html/rfc6973

--
Uma C.

v2.23.0 | Report a Bug | By Email