Last Call Review of draft-ietf-lisp-ddt-08
review-ietf-lisp-ddt-08-opsdir-lc-dunbar-2016-11-03-00

Request Review of draft-ietf-lisp-ddt
Requested revision No specific revision (document currently at 09)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2016-10-25
Requested 2016-10-05
Authors Vince Fuller , Darrel Lewis , Vina Ermagan , Amit Jain , Anton Smirnov
I-D last updated 2016-11-03
Completed reviews Genart Last Call review of -08 by Dale R. Worley (diff)
Secdir Last Call review of -08 by Radia Perlman (diff)
Opsdir Last Call review of -08 by Linda Dunbar (diff)
Rtgdir Early review of -07 by Ben Niven-Jenkins (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Last Call review on draft-ietf-lisp-ddt by Ops Directorate Assigned
Reviewed revision 08 (document currently at 09)
Result Has nits
Completed 2016-11-03
review-ietf-lisp-ddt-08-opsdir-lc-dunbar-2016-11-03-00

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the operational area
directors.

Document editors and WG chairs should treat these comments just like any other
last call comments.



I think the messages format and the mechanism for invoking DDT are very well
written and very clear.



One question:



4.1 states

LISP-DDT does not store actual EID-to-

RLOC mappings; it is, rather, a distributed index that can be used to

find the devices (Map Servers and their registered EIDs) that can be

queried with LISP to obtain those mappings





If mapping in Map Servers are organized in a way that each Map Server maintains
EIDs-RLOC mappings for a set of  VPNs or Tenants, then the Ingress node can use
the VPN-ID or Tenant ID to find the desired MapServer.

Under this circumstance, do you still need LISP-DDT?



It will be very helpful to have a paragraph describing what kind of environment
will need LISP-DDT.



Thanks, Linda Dunbar