Last Call Review of draft-ietf-bmwg-issu-meth-01
review-ietf-bmwg-issu-meth-01-genart-lc-even-2015-07-01-00

Request Review of draft-ietf-bmwg-issu-meth
Requested revision No specific revision (document currently at 02)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2015-07-02
Requested 2015-06-18
Authors Sarah Banks , Fernando Calabria , Gery Czirjak , Ramdas Machat
I-D last updated 2015-07-01
Completed reviews Genart Last Call review of -01 by Roni Even (diff)
Secdir Last Call review of -01 by Liang Xia (diff)
Assignment Reviewer Roni Even
State Completed
Review review-ietf-bmwg-issu-meth-01-genart-lc-even-2015-07-01
Reviewed revision 01 (document currently at 02)
Result Ready with Issues
Completed 2015-07-01
review-ietf-bmwg-issu-meth-01-genart-lc-even-2015-07-01-00
I am the assigned 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 Last Call comments you may
receive.

Document:

draft-ietf-bmwg-issu-meth-01

Reviewer: Roni Even

Review Date: 2015–7-1

IETF LC End Date: 2015–7-2

IESG Telechat date:



Summary: This draft is ready for publication as an Informational  RFC.





Major issues:



Minor issues:



According to the abstract this document specifies a set of common methodologies
and procedures designed to characterize the overall behavior of a Device Under
Test (DUT), subject to an ISSU event. My reading is that it captures the
typical procedures and as such is an informational document. It does not
recommend any specific procedure yet it RECOMMEND in section 7 defines
normative recommendation of which parameters SHOULD be reported in what I
understand is a written statement.  I was wondering if all parameters are
needed and when you can report only part of them , maybe just make it non
normative



Nits/editorial comments: