Last Call Review of draft-ietf-avtext-rtp-duplication-04

Request Review of draft-ietf-avtext-rtp-duplication
Requested rev. no specific revision (document currently at 06)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-02-04
Requested 2014-01-23
Authors Ali Begen, Colin Perkins
Draft last updated 2014-02-05
Completed reviews Genart Last Call review of -04 by Suresh Krishnan (diff)
Secdir Last Call review of -04 by David Harrington (diff)
Opsdir Last Call review of -04 by Linda Dunbar (diff)
Opsdir Last Call review of -04 by David Harrington (diff)
Assignment Reviewer Suresh Krishnan 
State Completed
Review review-ietf-avtext-rtp-duplication-04-genart-lc-krishnan-2014-02-05
Reviewed rev. 04 (document currently at 06)
Review result Almost Ready
Review completed: 2014-02-05


I am the assigned Gen-ART reviewer for draft-ietf-avtext-rtp-duplication-04

For background on Gen-ART, please see the FAQ at 



Please resolve these comments along with any other Last Call comments 

you may receive.

Summary: This draft is almost ready for publication as a Proposed 

Standard but I have one issue that probably needs further clarification 

in the draft.

* Section 7

I am not sure how the following MUST NOT is testable.

"First of all, RTP duplication MUST NOT be used
 in cases where the primary cause of packet loss is congestion since
 duplication can make congestion only worse."

I my understanding (correct me if I am wrong) neither the source of the 

duplication nor the destination will know whether the packet loss was 

due to congestion or something else. Can you please clarify how this 

"MUST NOT" would be followed?