Skip to main content

Last Call Review of draft-ietf-lisp-interworking-
review-ietf-lisp-interworking-genart-lc-garcia-2012-02-17-00

Request Review of draft-ietf-lisp-interworking
Requested revision No specific revision (document currently at 06)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2012-02-23
Requested 2012-02-09
Authors Darrel Lewis , David Meyer , Dino Farinacci , Vince Fuller
I-D last updated 2012-02-17
Completed reviews Genart Last Call review of -?? by Miguel Angel García
Tsvdir Last Call review of -?? by Rolf Winter
Assignment Reviewer Miguel Angel García
State Completed
Request Last Call review on draft-ietf-lisp-interworking by General Area Review Team (Gen-ART) Assigned
Completed 2012-02-17
review-ietf-lisp-interworking-genart-lc-garcia-2012-02-17-00
I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other comments you may receive.

Document: draft-ietf-lisp-interworking-03.txt
Reviewer: Miguel Garcia <miguel.a.garcia at ericsson.com>
Review Date: 2012-02-17
IETF LC End Date: 2012-02-23
IESG Telechat date: 2012-03-01

Summary: The document is ready for publication as an experimental RCFc.

Major issues: none

Minor issues: none

Nits/editorial comments:



- Section 5.2 describes a sequence of packet flows. I think it would be 


easier to understand if there is a companion figure to which the text can 


refer to. Otherwise, the reader has to compose this figure in his mind.




- Please expand acronyms at first occurrence. This includes: RLOC, CRIO

- Perhaps the terminology section should include RLOC, xTR, ETR, ITR, DFZ



- Idnits reveals a number of unused references: LIPS-MS, RFC4632, 


LISP-DEPLOY, RFC4787, RFC5382. They should be deleted.




- Idnits reveals an obsolete reference: RFC 2434 (Obsoleted by RFC 5226)



- Idnits reveals a number of instances where IP addresses are not 


compliant with RFC 5735. I am trying to identify which ones of these are. 


I guess they are the 220.x.x.x, 128.x.x.x EIDs. I think most of them are 


technically EIDs for LISP-NR, LISP-R LISP-NAT, etc. I don't know if RFC 


5735 applies to this draft or not, I am just letting you know in case you 


need to fix something.




BR,

     Miguel


--
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain