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

Varun Singh <vsingh.ietf@gmail.com> Tue, 26 July 2016 10:32 UTC

Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C21F912D19B for <avt@ietfa.amsl.com>; Tue, 26 Jul 2016 03:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XlAHAxnOyGz6 for <avt@ietfa.amsl.com>; Tue, 26 Jul 2016 03:32:05 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2410D12D0B3 for <avt@ietf.org>; Tue, 26 Jul 2016 03:32:05 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id g62so1867848lfe.3 for <avt@ietf.org>; Tue, 26 Jul 2016 03:32:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=xUZubJnnYtZ7HfCdh4WvwAhHa4IYCtYwjYIX4nwa4fA=; b=tunQi/rDQ38vUgfclQvxwtykLw13xQHsLb6pSzuvbNIDd/AhthXpmW7Hajq7RY8Skg U5PInZNBYW4Kf6voDjBTLTfY4smR5OZfsXOGK8AqwI6YK6zdaHyIRUbfco2MnbXSJw9G NI5AIr0jOhfRIx84AbH4L6C6/PZ/PI1ex66hMH8lA77b4BdPHTFq9/Z0SBN/rSEk1omC OOzZQI1Cgqwt9edtuGi3CZ8MzJvP187/73r7KuqHuBHcdl65Mvc0mQyWxO+NvbHcv6xs RBDI8Ml6LYEE2WAH09/Q28eDqJ2N7sQVa6Oq95xhNQwIgfgA3UDU8qbB7pkqdSuqyUWe NjJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xUZubJnnYtZ7HfCdh4WvwAhHa4IYCtYwjYIX4nwa4fA=; b=UtdRXH36Iw05bw8OM/o0l8K6EDhT0TAs4Wp7qZn9kys52yylo7UHNjjn37OY+2wOcR /dJMS+OymK6ew4fMuXJbJt3qBkRXYIMlBJanQxpudqW1QKiTM2QUyGizbkvXrx2GCv/i IEL39pAiBnFjwa6/ypS4IGIXDzgVjPOYpTCbqff00z0x1IGnv1mHSxAkUg9AmMxG8ALb T4Hq3dSCddafaJQbv9egL1RAO5TL0rwvA9u3wZMrxR/guTbeNNmDoPY/WIwtwVn3BRn7 vxaryNjycLkOzvq1I1HU8KuG0GOFroVuzqsEI5yNiyP2yEBZ8fgqsftZPfMKoMXWbj8f V6eA==
X-Gm-Message-State: AEkoout4H2j4guY76sWRliyXub/b+3Z5jVnzkLvb/u9Uv0G86OaDTOigGl0q32/S1C24Ky+VhxdNpHqASxdBHA==
X-Received: by 10.25.219.10 with SMTP id s10mr8036662lfg.101.1469529123048; Tue, 26 Jul 2016 03:32:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.18.153 with HTTP; Tue, 26 Jul 2016 03:31:43 -0700 (PDT)
In-Reply-To: <20160720080244.22515.31653.idtracker@ietfa.amsl.com>
References: <20160720080244.22515.31653.idtracker@ietfa.amsl.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Tue, 26 Jul 2016 13:31:43 +0300
Message-ID: <CAEbPqrzjLrXyRNzUQsc1=WpVWFpft9RCRrc0S_6Gvym-ULJy2A@mail.gmail.com>
To: "avt@ietf.org" <avt@ietf.org>, Bernard Aboba <Bernard.Aboba@microsoft.com>, Varun Singh <varun@callstats.io>
Content-Type: multipart/alternative; boundary=94eb2c07a4145dd70e05388769d8
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/4gW0aSWP80ROu_5fVQAHhrYGAT8>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-17.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2016 10:32:08 -0000

Another issue that was brought up during the Berlin IETF meeting, to
clarify the cease transmission for 5-tuple.

I believe section Section 8 provides more concrete guidance on
bundling/grouping media flows and even states that the application should
consider the 6-tuple (+DSCP) when deciding to cease transmission.

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.


Regards,
Varun.

On Wed, Jul 20, 2016 at 11:02 AM, <internet-drafts@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 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-17.txt
>         Pages           : 25
>         Date            : 2016-07-20
>
> 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-17
>
> A diff from the previous version is available at:
>
> https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-17
>
>
> 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
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>



-- 
http://www.callstats.io