Re: [AVT] I-D ACTION:draft-ietf-avt-app-rtp-keepalive-02.txt

[Colin Perkins <csp at csperkins.org>]

On 8 Feb 2008, at 22:30, Internet-Drafts at ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working  
> Group of the IETF.
>
> 	Title		: Application Mechanism for maintaining alive the Network  
> Address Translator (NAT) mappings associated to RTP flows.
> 	Author(s)	: X. Marjou, A. Sollaud
> 	Filename	: draft-ietf-avt-app-rtp-keepalive-02.txt
> 	Pages		: 11
> 	Date		: 2008-2-8
> 	
> This document lists the different mechanisms that enable applications
>    using Real-time Transport Protocol (RTP) to maintain their RTP
>    Network Address Translator (NAT) mappings alive.  It also makes a
>    recommendation for a preferred mechanism.  This document is not
>    applicable to Interactive Connectivity Establishment (ICE) agents.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-app-rtp- 
> keepalive-02.txt

The changes in this revision look generally very good. Two minor  
comments:

- Rather than make a special case for T.140 text using a different  
fallback keep-alive mechanism than other payload formats, should the  
draft recommend that payload format specific mechanisms should  
generally be used in multiplexed RTCP cannot? Empty T.140 blocks  
would be one example of this, as would comfort noise, etc.

- Section 6 should discuss how the interval Tr relates to the RTCP  
timing rules.

-- 
Colin Perkins
http://csperkins.org/


_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
http://www.ietf.org/mailman/listinfo/avt