Hi, I wonder how much is important to clarify whether or not a principle is unique to LISP.
I tend to agree with Albert’s viewpoint, the document should give the list of principles LISP is based on so to provide the reader the big picture of LISP in a nutshell. The only remaining question is whether or not we want to add a bullet concerning the push/pull model & Mapping database. ciao Luigi On 12 Oct 2014, at 03:32, Dino Farinacci <farina...@gmail.com> wrote: > Well everything tends to look the same but not in this case. This is the > first mapping database that is really fully specified and tested at the > network layer. > > Dino > > >> On Oct 11, 2014, at 9:20 PM, Ronald Bonica <rbon...@juniper.net> wrote: >> >> Dino, >> >> That too! >> >> However, the mapping database system is not entirely unique to LISP. Every >> architecture that maps one address space to another needs a data base to >> maintain mapping information. The part that is unique to LISP is how the >> data is distributed >> >> Ron >> >> >>> -----Original Message----- >>> From: Dino Farinacci [mailto:farina...@gmail.com] >>> Sent: Saturday, October 11, 2014 9:02 PM >>> To: Ronald Bonica >>> Cc: lisp@ietf.org >>> Subject: Re: [lisp] draft-ietf-lisp-introduction - Design Principles and Use >>> Cases >>> >>>> On Oct 11, 2014, at 7:51 PM, Ronald Bonica <rbon...@juniper.net> wrote: >>>> >>>> In Section 2.1, we say that LISP is built on top of four basic design >>>> principles: >>>> >>>> - Locator/Identifier split >>>> - Overlay architecture >>>> - Decoupled data and control-plane >>>> - Incremental deployability >>> >>> You left out one that is really important: >>> >>> - A Mapping Database System >>> >>> Dino > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
