On 7/7/14, 5:27 PM, Marc Binderberger wrote:
Hello Darrel et al.,

few questions/comments on your updated draft:

1) not sure Figure 2 and 3 do make much sense as for P=1 the LISP header
layout is figure 4. Yes it is a very didactic approach ;-) but at the end the
OAM and version bits are there is any case with P=1 - or not?
Right, we are trying to show a feature per each sub section. Maybe we should explicitly mark as "0/1" the bits that are not shown in a given subsection. We'll work on that.


2) the layout does not fit well with draft-farinacci-lisp-crypto-00. Are
there any plans to solve this?  Should this at least be mentioned somewhere?


Both this draft and lisp-crypto are proposals to extend the LISP encap with new features. I don't think they need to refer each other at this point.

I just note that by adding multiprotocol support, one could add a shim header that provides encryption services to the LISP payload.



3) probably too trivial but section "3.3. Version Bits" is not mentioning
anything about the receiver behaviour. Sure, if you don't know the version,
drop it. Or at least I assume this is what you have in mind (?).

good point. Will add.


4) section "4.1. LISP-gpe Routers to (legacy) LISP Routers" you say

    When the P bit is set, the N, E, and V bits MUST be set to zero.  The
    receiving (legacy) LISP router will ignore N, E and V bits, when the
    P bit is set.

I would think a receiving legacy LISP router has no idea about the P bit,
which is why you explicitly set N/E/V to zero?

Right. Per LISP specification P bit is ignored, and given that NEV are set to zero, the next protocol field is ignored too. We'll rephrase the sentence to make it more clear.

5) as you even mention "Ethernet" (or 802.1Q) in the informative reference
section, what about a reference to "Network Service Header" ?
Right. Will add.

Thanks for the review!

Fabio


So just smaller points I make, overall a very interesting document!


Best regards,
Marc




On Fri, 04 Jul 2014 12:45:06 -0700, [email protected] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories.


         Title           : LISP Generic Protocol Extension
         Authors         : Darrel Lewis
                           Puneet Agarwal
                           Larry Kreeger
                           Fabio Maino
                           Paul Quinn
                           Michael Smith
                           Navindra Yadav
        Filename        : draft-lewis-lisp-gpe-02.txt
        Pages           : 15
        Date            : 2014-07-04

Abstract:
    This draft describes extending the Locator/ID Separation Protocol
    (LISP) [RFC6830], via changes to the LISP header, with three new
    capabilities: support for multi-protocol encapsulation, operations,
    administration and management (OAM) signaling, and explicit
    versioning.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-lewis-lisp-gpe/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-lewis-lisp-gpe-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-lewis-lisp-gpe-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to