Skip to main content

Last Call Review of draft-ietf-mmusic-rtsp-nat-21
review-ietf-mmusic-rtsp-nat-21-genart-lc-dupont-2014-06-23-00

Request Review of draft-ietf-mmusic-rtsp-nat
Requested revision No specific revision (document currently at 22)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-06-20
Requested 2014-06-09
Authors Jeff Goldberg , Magnus Westerlund , Thomas Zeng
I-D last updated 2014-06-23
Completed reviews Genart Last Call review of -21 by Francis Dupont (diff)
Assignment Reviewer Francis Dupont
State Completed
Request Last Call review on draft-ietf-mmusic-rtsp-nat by General Area Review Team (Gen-ART) Assigned
Reviewed revision 21 (document currently at 22)
Result Ready
Completed 2014-06-23
review-ietf-mmusic-rtsp-nat-21-genart-lc-dupont-2014-06-23-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-mmusic-rtsp-nat-21.txt
Reviewer: Francis Dupont
Review Date: 20140620
IETF LC End Date: 20140620
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

(a metacomment anyway: with the arrival of IPv6 we should not spend
too much time/effort on NAT traversal...)

Nits/editorial comments:
 - Abstract page 1 (and many other places): signalling -> signaling

 - ToC page 3 and 12 page 30: Acknowledgements -> Acknowledgments

 - 1 page 3: (style) too many "number" in
   There have been a number of suggested ways of resolving the NAT-
   traversal of media for RTSP of which a large number are already used
   in implementations.

 - 3 page 5 (4) (and 6.10 page 20, 9 page 27): e.g. -> e.g.,

 - 4.1 page 6: (style) must be -> has to be

 - 4.2 page 9 (connection-address): (ambiguous wording)
      ...  An IP address
      SHOULD be used, but an FQDN MAY be used in place of an IP address.

 - 4.2 page 10 (extension-att-*): delimeter -> delimiter

 - 6.3 page 16 (and 6.13 pages 22 and 23):
    (uniform use of a space after ';')
     RTP/AVP/TCP;unicast;interleaved=0-1 ->
     RTP/AVP/TCP; unicast; interleaved=0-1   

 - 6.7 pages 18 and 19: Succeded -> Succeeded

 - 7.1 page 23: will need to be run -> will be run

 - 9 page 26: i.e. -> i.e.,

Regards

Francis.Dupont at fdupont.fr