[lisp] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt

2016-09-21 Thread Dino Farinacci
Hello folks. In draft-padma-ideas-problem-statement-00.txt, we have a section on mapping system requirements for map-n-encap and translation based loc/id split protocols. Rather than having you go into the document in detail (we wish you would and comment though), I will provide the short list b

Re: [lisp] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt

2016-09-21 Thread Dino Farinacci
Reposting since the cisco mailing lists are no longer in service. Please respond to this email. Thanks and sorry for inconvenience, Dino > On Sep 21, 2016, at 2:12 PM, Dino Farinacci wrote: > > Hello folks. In draft-padma-ideas-problem-statement-00.txt, we have a section > on mapping system r

Re: [lisp] [nvo3] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt

2016-09-21 Thread Black, David
Hi Dino, Here are a couple of areas to consider: (1) I don't see any confidentiality requirements. For this and other NVO3 security requirements, please see the security considerations section of RFC 7365 (NVO3 framework) and draft-ietf-nvo3-arch. The latter contains a new paragraph on sensit

Re: [lisp] [nvo3] Mapping System Requirements and draft-padma-ideas-problem-statement-00.txt

2016-09-21 Thread Michael Menth
Hi David, 5. The mapping system must allow request access (for subscribers) to be open and public. However, it is optional to provide confidentiality and authentication of the requesters and the information they are requesting. > > (1) I don't see any confidentiality r