Last Call Review of draft-ietf-avtcore-clksrc-09
review-ietf-avtcore-clksrc-09-genart-lc-brim-2014-01-02-00

Request Review of draft-ietf-avtcore-clksrc
Requested revision No specific revision (document currently at 11)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-01-16
Requested 2014-01-02
Authors Aidan Williams , Kevin Gross , Ray van Brandenburg , Hans Stokking
I-D last updated 2014-01-02
Completed reviews Genart Last Call review of -09 by Scott W. Brim (diff)
Genart Last Call review of -09 by Scott W. Brim (diff)
Secdir Last Call review of -09 by Derek Atkins (diff)
Assignment Reviewer Scott W. Brim
State Completed
Request Last Call review on draft-ietf-avtcore-clksrc by General Area Review Team (Gen-ART) Assigned
Reviewed revision 09 (document currently at 11)
Result Ready w/issues
Completed 2014-01-02
review-ietf-avtcore-clksrc-09-genart-lc-brim-2014-01-02-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-avtcore-clksrc-09
Reviewer: Scott Brim
Review Date: 2014-01-13
IETF LC End Date: 2014-01-16
IESG Telechat date: (if known)

Summary: Ready with a minor issue

Major issues:

Minor issues:

In 6.1.2 and 6.1.3: "If the answerer rejects the offer because the
available reference clocks are incompatible, the rejection MUST
contain at least one timestamp reference clock specification usable by
the answerer." If the answerer suggests a clock that is not among
those offered, what happens next?  The offerer could abort, but could
it start over and use what the answerer suggested? That's not
documented -- is it obvious to those more familiar with SDP?

Scott