Re: [lisp] I-D Action: draft-ietf-lisp-introduction-06.txt

[Albert Cabellos <[e-mail]>]

Hi Dino

Thanks for your review. I am attaching -07 + diff (not published yet)
where I have addressed all your comments, please let me know if you
agree and we´ll proceed to publish it.

There are some comments that I would like to discuss, please see below:

On Fri, Oct 24, 2014 at 12:35 AM, Dino Farinacci <[e-mail]> wrote:
>>        Title           : An Architectural Introduction to the Locator/ID Separation Protocol (LISP)
>>        Authors         : Albert Cabellos
>>                          Damien Saucez
>>       Filename        : draft-ietf-lisp-introduction-06.txt
>>       Pages           : 25
>>       Date            : 2014-10-2
>
> Thanks for the update guys. Here are some final (I hope) editorial comments. Thanks for the huge and timely effort.
>

[snip]

>
>>
>>    Map-Resolver:  A network infrastructure component that interfaces
>>       ITRs with the Mapping System by proxying queries and -in some
>>       cases- responses.
>
> I would say "receive queries and sends negative replies".
>

This is already explained in "Map-Reply", at this point Map-Reply has
not been introduced yet. I think that this way is clearer.

> But why don't you order the messages first and then refer to them when you define the Map-Server and Map-Resolver afterwards?

There is a circular dependency, then I won't be able to use the terms
Map-Server/Map-Resolver when explaining what Map-Request/Map-Reply,
etc are.

[snip]

>
>>    Map-Request:  This message is used by ITRs or Map-Resolvers to
>>       resolve the mapping of a given EID.
>
> This message is also used by ETRs to request an ITR to do a Mapping System request. This message is also used by ITRs to probe the underlying path to an ETR.
>

This is early in the document and I think that it is preferable to
keep things simple. The fact that SMR/RLOC probing functionalities use
a Map-Request type of message is not important when considering LISP's
big picture. SMR/RLOC probing are explained in section 4 with the
relevant context.

Albert