On Fri, Mar 16, 2018 at 1:36 PM, Uma Chunduri <uma.chund...@huawei.com> wrote: > > > > -----Original Message----- > From: ila [mailto:ila-boun...@ietf.org] On Behalf Of Dino Farinacci > Sent: Friday, March 16, 2018 1:10 PM > To: Uma Chunduri <uma.chund...@huawei.com> > Cc: David Meyer <d...@1-4-5.net>; i...@ietf.org; Tom Herbert > <t...@quantonium.net>; lisp@ietf.org; Paul Vinciguerra > <pvi...@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 > i...@ietf.org > https://www.ietf.org/mailman/listinfo/ila > _______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
