Re: [lisp] draft-ietf-lisp-introduction

Hi Ronald

Thanks for your comment.

I agree that none of such design principles are unique to LISP, but -I
think- you are reading them independently and they should be
considered the four of them *at the same time*. With this I expect
that the reader gets -very quickly- LISP's big picture.

I don´t think that pull is such a unique characteristic, DNS works
based on exactly the same principle: "pull locators".

Albert

On Sun, Oct 12, 2014 at 3:32 AM, Dino Farinacci <farinacci@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 <rbonica@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:farinacci@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 <rbonica@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

Re: [lisp] draft-ietf-lisp-introduction - Design Principles and Use Cases