Telechat Review of draft-ietf-nvo3-hpvr2nve-cp-req-13
review-ietf-nvo3-hpvr2nve-cp-req-13-genart-telechat-carpenter-2018-02-06-00

Request Review of draft-ietf-nvo3-hpvr2nve-cp-req
Requested revision No specific revision (document currently at 17)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2018-02-20
Requested 2018-01-31
Authors Yizhou Li , Donald E. Eastlake 3rd , Larry Kreeger , Dr. Thomas Narten , David L. Black
I-D last updated 2018-02-06
Completed reviews Genart Telechat review of -13 by Brian E. Carpenter (diff)
Opsdir Telechat review of -15 by Scott O. Bradner (diff)
Genart Telechat review of -15 by Brian E. Carpenter (diff)
Assignment Reviewer Brian E. Carpenter
State Completed
Request Telechat review on draft-ietf-nvo3-hpvr2nve-cp-req by General Area Review Team (Gen-ART) Assigned
Reviewed revision 13 (document currently at 17)
Result Ready w/issues
Completed 2018-02-06
review-ietf-nvo3-hpvr2nve-cp-req-13-genart-telechat-carpenter-2018-02-06-00
Gen-ART Last Call review of draft-ietf-pce-pcep-exp-codepoints-04

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-nvo3-hpvr2nve-cp-req-13.txt
Reviewer: Brian Carpenter
Review Date: 2018-02-07
IETF LC End Date: 2018-02-20
IESG Telechat date: 2018-02-22

Summary: Ready (with minor issue)
--------

Comment:
--------

This is a Last Call review despite the subject field.

Minor issue:
------------

   Req-10: The protocol MUST allow an End Device initiating a request to
   add, remove or update address(es) associated with a TSI instance on
   the external NVE. Addresses can be expressed in different formats,
   for example, MAC, IP or pair of IP and MAC.

Here and elsewhere, it seems necessary to specify that an IP address
can be in either IPv4 or IPv6 format. (This is implied in Table 1
and at the end of Appendix A, but that's quite well hidden.)
I suggest clarifying this early, in Section 1.2 "Target Scenarios".