Re: [lisp] [Ila] LISP for ILA

Tom Herbert <tom@quantonium.net> Fri, 16 March 2018 20:49 UTC

Return-Path: <tom@quantonium.net>
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 D35A8124BAC for <lisp@ietfa.amsl.com>; Fri, 16 Mar 2018 13:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.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 prwxjNAg-VOX for <lisp@ietfa.amsl.com>; Fri, 16 Mar 2018 13:49:57 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 AF6A7124C27 for <lisp@ietf.org>; Fri, 16 Mar 2018 13:49:56 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id h21so5394969wmd.1 for <lisp@ietf.org>; Fri, 16 Mar 2018 13:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ffP0JT2ofFdDz6/EoqTwoUe1ybTyRYftVHAY3YVmftU=; b=cJz5M2iC8NkouDCsYxDc7MWTp5GTqib2+d61R+cExJroJ7n+lTqRPe/NABCcvXZQvf 2v50xDiFp2onTfZaedZ2IzLBqVkqTdy4X6PMPzroIssH7JK3hvYwBwFQ2nThJu+/1Qo+ bji+zqcPu2UBkZMI+VIfq6YHmJ76VRuRWBS+oSB+YOPbvcX8M3oG1ajStr2Ld2D5Bwk/ w85Kp3vqt5l5RbdPBp2KtA2th/n5F6udEprIGe/R70Se7kf60dPe5XDbvujTQNAoFyht 7gXSfNIifhApzFrVb0KpQAcxXCoUd7LHHsI76fbLKn4IKkGCk2wH/djnXMU0oNUeV42q dKIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ffP0JT2ofFdDz6/EoqTwoUe1ybTyRYftVHAY3YVmftU=; b=AFmDIfTcXp5JcW4E0QT6Fo8TFdLAuB17L1BH3K79rmwxb7x3Uqt6Xx6RCHDLtAons/ vq1L9hHGi6IMFhXzN9W9rbtHw7wy0GazOsRi50ipHQbz+YkJc4NgtyRMrYqljb6O9qW5 twrseymUmnSVxTcH5qACgvvAZ7QaXlo07kFStzkyMaSmhRIPQNz/PooIJz160cWpPvu9 JCiFbv6qODamBVgPorPlNcDUBnHiT/s/e/9+Jvr8rgWMqbKN8vw3dESRiMi2+qdYGSJe EewgN2xS5aG4h7c7qgV2BaScmzFS7JFl1r6naB2JUaRb9gRu/285LwudlfF880gVFG2g Xoqw==
X-Gm-Message-State: AElRT7GqCHBzxn5S8odpSKOIGsfk3T87RjHhgSWQwiVT0NLmmWUZGkHP +nj/ayb6GUX3Rl1BGoeaHda5ShIpvGTJYSkdGUbZxQ==
X-Google-Smtp-Source: AG47ELtj9hsd4g7jGSpmS97AOFl3auWTbwEk+Hrleo1H0riJD40Sk8abrZS5LWwmOsDLD0Y6jHCwOlW1kdoiUxPDaAI=
X-Received: by 10.28.118.1 with SMTP id r1mr2770295wmc.80.1521233395136; Fri, 16 Mar 2018 13:49:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.135.74 with HTTP; Fri, 16 Mar 2018 13:49:54 -0700 (PDT)
In-Reply-To: <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> <25B4902B1192E84696414485F57268541354C7E8@SJCEML521-MBB.china.huawei.com>
From: Tom Herbert <tom@quantonium.net>
Date: Fri, 16 Mar 2018 13:49:54 -0700
Message-ID: <CAPDqMervCZuQNv05hQxwJVVM8duom_yPX28tF9o5pp4EAg6big@mail.gmail.com>
To: Uma Chunduri <uma.chunduri@huawei.com>
Cc: Dino Farinacci <farinacci@gmail.com>, David Meyer <dmm@1-4-5.net>, "ila@ietf.org" <ila@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, Paul Vinciguerra <pvinci@vinciconsulting.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/C2ZZ1Fx16REZUpQO5-iouc88e78>
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:49:59 -0000

On Fri, Mar 16, 2018 at 1:36 PM, Uma Chunduri <uma.chunduri@huawei.com> wrote:
>
>
>
> -----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.
>
I can buy that, but then would wonder why you think Scalability is
easy :-) We're anticipating systems with many billions of mappings and
potentially high rates of change. No doubt were in the realm of some
seriously distributed databases!

Tom

> 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.
>
>
>
> _______________________________________________
> ila mailing list
> ila@ietf.org
> https://www.ietf.org/mailman/listinfo/ila
>