Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-18.txt

[Colin Perkins <[e-mail]>]

This version includes the change Varun suggested on the list on 26 July (“In section 4.5, I would propose reshuffling the statements a bit to make the guidance more appropriate”):

OLD:
   What it means to cease transmission depends on the application. The
   intention is that the application will stop sending RTP data packets
   on a particular 5-tuple (transport protocol, source and destination
   ports, source and destination IP addresses), until whatever network
   problem that triggered the RTP circuit breaker has dissipated.  This
   could mean stopping a single RTP flow, or it could mean that multiple
   bundled RTP flows are stopped. 

NEW:

   What it means to cease transmission depends on the application. This
   could mean stopping a single RTP flow, or it could mean that multiple
   bundled RTP flows are stopped. The intention is that the application will 
   stop sending RTP data packets on a particular 5-tuple (transport protocol, 
   source and destination ports, source and destination IP addresses), until 
   whatever network problem that triggered the RTP circuit breaker has 
   dissipated.  

There are no other changes.

Colin



> On 18 Aug 2016, at 18:21, [e-mail] 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 Core Maintenance of the IETF.
> 
>        Title           : Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
>        Authors         : Colin Perkins
>                          Varun Singh
> 	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-18.txt
> 	Pages           : 25
> 	Date            : 2016-08-18
> 
> Abstract:
>   The Real-time Transport Protocol (RTP) is widely used in telephony,
>   video conferencing, and telepresence applications.  Such applications
>   are often run on best-effort UDP/IP networks.  If congestion control
>   is not implemented in these applications, then network congestion can
>   lead to uncontrolled packet loss, and a resulting deterioration of
>   the user's multimedia experience.  The congestion control algorithm
>   acts as a safety measure, stopping RTP flows from using excessive
>   resources, and protecting the network from overload.  At the time of
>   this writing, however, while there are several proprietary solutions,
>   there is no standard algorithm for congestion control of interactive
>   RTP flows.
> 
>   This document does not propose a congestion control algorithm.  It
>   instead defines a minimal set of RTP circuit breakers: conditions
>   under which an RTP sender needs to stop transmitting media data, to
>   protect the network from excessive congestion.  It is expected that,
>   in the absence of long-lived excessive congestion, RTP applications
>   running on best-effort IP networks will be able to operate without
>   triggering these circuit breakers.  To avoid triggering the RTP
>   circuit breaker, any standards-track congestion control algorithms
>   defined for RTP will need to operate within the envelope set by these
>   RTP circuit breaker algorithms.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-18
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-18
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> [e-mail]
> https://www.ietf.org/mailman/listinfo/avt



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