
From nobody Mon Feb  8 01:59:09 2016
Return-Path: <joe@salowey.net>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A8CE1A9119 for <avt@ietfa.amsl.com>; Sun,  7 Feb 2016 21:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 4FuTVDjsgbz7 for <avt@ietfa.amsl.com>; Sun,  7 Feb 2016 21:21:04 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (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 6DABC1A9118 for <avt@ietf.org>; Sun,  7 Feb 2016 21:21:04 -0800 (PST)
Received: by mail-lb0-x230.google.com with SMTP id dx2so76854366lbd.3 for <avt@ietf.org>; Sun, 07 Feb 2016 21:21:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=k8hLHGX388Vp51mmISc1X1UwXU1f8Eb6fC8qb9Tc5Tc=; b=VyiCAlXDDwtZnq80sy7M80thvqo0wAz9udMfNGbaJWK0u4nd/hOroSak1fyOUrtPTj KGSg0EMUn3R2aRKjHfJa0rzMrSsdIkY/fyq9xDaVhodRbxgeEjlaKC0QpRUV5LIKtr3p mWZUCfoii3qKeLd7oCcm8i1Tjsae5BwYQOlW3f0IKrs1XtyiwM0ybr41tN6+D2841x1T Sg+OO4GEKyuMdK9cnyXSINS2WHTF+94ccaCACezBI5DeaZNux71CBcHbiLEvbwu3Rkp2 OCXa75g1BmP/A43Z8LsQAbuvpUVwiyVZz45aA4mxeifYVbdrt+oXIzo4Sr9ppPefYoU5 xIgQ==
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:date :message-id:subject:from:to:cc:content-type; bh=k8hLHGX388Vp51mmISc1X1UwXU1f8Eb6fC8qb9Tc5Tc=; b=hHznzfkeUy3d10dsIfnkdSpK61Vwvax1LC7QWwQ4o/QW05jZAQnQuLuD748KwNkNBv 3jLR8wch73E+Z7bVvNR0cg381LozH5VrfIA7Oz1dYn+u/2fBSzHtcbKLvp0MLZAxYB+f 8bUouIme4V065mZdRFCl4wTlBzjrvN2nC15/Un74i7SxDljFO71Kn4W8ajt+FVQxN4C5 gxhCGDmb2MfKuw8LSsSEQYd5ZAykNsOW0FNRRtuURG5yzMiRtQu1goX416SeoEQnhtHk Istt+SCQQwoky/x5kb4JU2znfqVqChEfK/UWsB+MxidaoKF5oXK+24WVJ68HP4trl+Te ZsLw==
X-Gm-Message-State: AG10YOTGfsIWUr0/N9tKh30zudyigI2IXLia76xoryDRDs54EWNEYmtpiaAtJvMv5PWt0b/kPj20X20QXrGIyg==
MIME-Version: 1.0
X-Received: by 10.112.63.161 with SMTP id h1mr10351701lbs.61.1454908862501; Sun, 07 Feb 2016 21:21:02 -0800 (PST)
Received: by 10.112.2.104 with HTTP; Sun, 7 Feb 2016 21:21:02 -0800 (PST)
In-Reply-To: <56A8904D.10307@ericsson.com>
References: <56A8904D.10307@ericsson.com>
Date: Sun, 7 Feb 2016 21:21:02 -0800
Message-ID: <CAOgPGoBU+h6cA9RDxBX2m1AR-3-GnC7OYcfDLTpDepX00g73dA@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
To: "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3fe1eee3073052b3b5d67
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/O75ws5eycGttse9EQeg8evGVBFQ>
X-Mailman-Approved-At: Mon, 08 Feb 2016 01:59:07 -0800
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, avt@ietf.org
Subject: Re: [AVTCORE] [TLS] WG last call of draft-ietf-avtcore-rfc5764-mux-fixes-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Feb 2016 05:21:06 -0000

--001a11c3fe1eee3073052b3b5d67
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

This document is relevant to the TLS working because it reserves a large
portion of the TLS content type space.  The values 0-19 and 64-255 cannot
be used without checking for conflicts with SRTP-DTLS's wacky
demultiplexing scheme.   In TLS 1.3 we will move more encrypted content
types which should limit the impact this unfortunate design on TLS
evolution, but the working group should be aware of this.

Cheers,

Joe

On Wed, Jan 27, 2016 at 1:39 AM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> AVTCORE and TLS,
>
> TLS WG, you are included in this WG last call, as this document affects
> the TLS ContentType IANA registry.
>
> This email starts a two week WG last call, that ends on the 10th of
> February. The intended status of this document is standards track (Propos=
ed
> Standard).
>
> The document can be retrieved here:
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rfc5764-mux-fixes/
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

--001a11c3fe1eee3073052b3b5d67
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This document is relevant to the TLS working because =
it reserves a large portion of the TLS content type space.=C2=A0 The values=
 0-19 and 64-255 cannot be used without checking for conflicts with SRTP-DT=
LS&#39;s wacky demultiplexing scheme. =C2=A0 In TLS 1.3 we will move more e=
ncrypted content types which should limit the impact this unfortunate desig=
n on TLS evolution, but the working group should be aware of this. =C2=A0<b=
r></div><div><br></div><div>Cheers,</div><div><br></div><div>Joe</div></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jan 27, =
2016 at 1:39 AM, Magnus Westerlund <span dir=3D"ltr">&lt;<a href=3D"mailto:=
magnus.westerlund@ericsson.com" target=3D"_blank">magnus.westerlund@ericsso=
n.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">AVTCORE and T=
LS,<br>
<br>
TLS WG, you are included in this WG last call, as this document affects the=
 TLS ContentType IANA registry.<br>
<br>
This email starts a two week WG last call, that ends on the 10th of Februar=
y. The intended status of this document is standards track (Proposed Standa=
rd).<br>
<br>
The document can be retrieved here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-avtcore-rfc5764-mux-=
fixes/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/draft-ietf-avtcore-rfc5764-mux-fixes/</a><br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
----------------------------------------------------------------------<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
----------------------------------------------------------------------<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 <a href=3D"tel:%2B46%2010%207148287" value=3D"+46107148287" tar=
get=3D"_blank">+46 10 7148287</a><br>
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Mobile <a href=3D"tel:%2B46%2073%200949079" value=3D"+467309490=
79" target=3D"_blank">+46 73 0949079</a><br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
----------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org" target=3D"_blank">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/tls</a><br>
</blockquote></div><br></div>

--001a11c3fe1eee3073052b3b5d67--


From nobody Mon Feb  8 01:59:10 2016
Return-Path: <davemgarrett@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 332F01A92BC; Sun,  7 Feb 2016 22:18:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_84=0.6, SPF_PASS=-0.001] autolearn=no
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 a10kWDWn2_xo; Sun,  7 Feb 2016 22:18:03 -0800 (PST)
Received: from mail-yk0-x235.google.com (mail-yk0-x235.google.com [IPv6:2607:f8b0:4002:c07::235]) (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 431D41A92BA; Sun,  7 Feb 2016 22:18:00 -0800 (PST)
Received: by mail-yk0-x235.google.com with SMTP id z7so83246361yka.3; Sun, 07 Feb 2016 22:18:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=4AvcBTULt73lUC/NFqzjYOUBBgtiLHRZMQtgqH8v72o=; b=EwH8ix9AC9qJn0QwDlE5Y78vvOH2CsHEwzgrTFMP0JIlmK80SIJwWRH8jU/vskbszv VnaUBL8ulaIovxdkmTdB9hCCrhcT4u7b3pM1od4Ns6SIhmsrpPaItG5vnenincUqAL4y w27Gbk6Pj7WhikIVsUm0byfwp+or6vr/qP3WGqjkV7eahpMjCDFIl0A1gnG2uHD9hAJJ X7mXRvkGmUJgMrcysgoZjGlj+cioKZLirW7NC4TcF84kJe5xczzHmR0njseB9f7KlyS2 VQzBm0D/iXnCzyKk7INHY7KPQvcdPbP61F9x5O+C369OObyXAjMglaSL+tHc2aAf9WDW 5HJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; bh=4AvcBTULt73lUC/NFqzjYOUBBgtiLHRZMQtgqH8v72o=; b=cGqDazvy/f1+RtX7j0BL1YuI0zACPTSb+FOGAvLD9ha6iIUd9q2v5oKkWmT710sAcT f66K0oOFSBBb/vjAgaMC4nnxuTDNjW4VLdIWWSvwlzBfNqJ8okJzbYIJCq3O8l4yz3ar 24rC7mA/938MwEf98fIjVmZMG3jyKcHnLZSWevGZQiYXg3D6PwH/qBao7cf2zdWw2O5s EY+zknoRrv2FK/zzBIL2u/6jjrGxbhA181fLVNBvSqPaqO3SoZkJi7Ocyvb4wJb/4cMH jllF7Q8d5nEjd6tysLTwgqwwMYCGgtYJnOcve+5ZFjLBhCmQ9eb/whrTlnJv8/8joKhV lRAg==
X-Gm-Message-State: AG10YORWNTZNAIhIDg75PFdby9+QQDDezmkrXXMdFWOC+Yf7ez5A5lS3wnjyRYR3KHYByw==
X-Received: by 10.37.21.5 with SMTP id 5mr13406796ybv.22.1454912279604; Sun, 07 Feb 2016 22:17:59 -0800 (PST)
Received: from dave-laptop.localnet (pool-71-175-20-227.phlapa.fios.verizon.net. [71.175.20.227]) by smtp.gmail.com with ESMTPSA id a7sm20035824ywf.55.2016.02.07.22.17.58 (version=TLS1 cipher=AES128-SHA bits=128/128); Sun, 07 Feb 2016 22:17:59 -0800 (PST)
From: Dave Garrett <davemgarrett@gmail.com>
To: tls@ietf.org
Date: Mon, 8 Feb 2016 01:17:57 -0500
User-Agent: KMail/1.13.5 (Linux/2.6.32-74-generic-pae; KDE/4.4.5; i686; ; )
References: <56A8904D.10307@ericsson.com> <CAOgPGoBU+h6cA9RDxBX2m1AR-3-GnC7OYcfDLTpDepX00g73dA@mail.gmail.com>
In-Reply-To: <CAOgPGoBU+h6cA9RDxBX2m1AR-3-GnC7OYcfDLTpDepX00g73dA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201602080117.57742.davemgarrett@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/Wclo4qTNPj6QszISmjmHuhDMPaU>
X-Mailman-Approved-At: Mon, 08 Feb 2016 01:59:08 -0800
Cc: Joseph Salowey <joe@salowey.net>, avt@ietf.org
Subject: Re: [AVTCORE] [TLS] WG last call of draft-ietf-avtcore-rfc5764-mux-fixes-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Feb 2016 06:18:05 -0000

Permanently gobbling up the majority of the codespace feels like excessive force here. For TLS 1.3, the first byte will always be one of alert(21), handshake(22), or application_data(23), even for custom types. The stated type for TLSCiphertext has been frozen to application_data(23) with the actual type for the payload now in the encrypted fragment. (this is of course assuming we don't eventually drop the frozen type & version here, which now sounds unlikely if we're having to deal with design flaws like this) Even handshake records after the hellos will have an opaque_type of application_data(23), with the encrypted fragment.type containing the actual handshake(22) designation. All TLS 1.3+ packets will be detected with the RFC 5764 Section 5.1.2 algorithm even if new types are allocated in the proposed reserved ranges.

Locking down the <1.2 registry seems fine, however 1.3+ should be able to do whatever it needs as its encrypted type is not going to get accidentally read & misinterpreted by anything.

https://tools.ietf.org/html/draft-ietf-tls-tls13-11#section-5.2.2
https://tools.ietf.org/html/rfc5764#section-5.1.2
https://tools.ietf.org/html/draft-ietf-avtcore-rfc5764-mux-fixes-05#section-4


Dave


On Monday, February 08, 2016 12:21:02 am Joseph Salowey wrote:
> This document is relevant to the TLS working because it reserves a large
> portion of the TLS content type space.  The values 0-19 and 64-255 cannot
> be used without checking for conflicts with SRTP-DTLS's wacky
> demultiplexing scheme.   In TLS 1.3 we will move more encrypted content
> types which should limit the impact this unfortunate design on TLS
> evolution, but the working group should be aware of this.
> 
> 
> On Wed, Jan 27, 2016 at 1:39 AM, Magnus Westerlund
> <magnus.westerlund@ericsson.com> wrote:
> 
> > AVTCORE and TLS,
> >
> > TLS WG, you are included in this WG last call, as this document affects
> > the TLS ContentType IANA registry.
> >
> > This email starts a two week WG last call, that ends on the 10th of
> > February. The intended status of this document is standards track (Proposed
> > Standard).
> >
> > The document can be retrieved here:
> > https://datatracker.ietf.org/doc/draft-ietf-avtcore-rfc5764-mux-fixes/


From nobody Tue Feb  9 07:01:06 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 402B31A90EC; Tue,  9 Feb 2016 07:01:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160209150104.21383.43407.idtracker@ietfa.amsl.com>
Date: Tue, 09 Feb 2016 07:01:04 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/988ArIVNaZmEo7FMoccLDQyDb3E>
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-12.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Feb 2016 15:01:04 -0000

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-12.txt
	Pages           : 24
	Date            : 2016-02-09

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 the applications, then network congestion will
   deteriorate the user's multimedia experience.  This acts as a safety
   measure to prevent starvation of network resources denying other
   flows from access to the Internet, such measures are essential for an
   Internet that is heterogeneous and for traffic that is hard to
   predict in advance.  This document does not propose a congestion
   control algorithm; instead, it defines a minimal set of RTP circuit-
   breakers.  Circuit-breakers are conditions under which an RTP sender
   needs to stop transmitting media data in order to protect the network
   from excessive congestion.  It is expected that, in the absence of
   severe congestion, all RTP applications running on best-effort IP
   networks will be able to run without triggering these circuit
   breakers.  Any future RTP congestion control specification will be
   expected to operate within the constraints defined by these circuit
   breakers.


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-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-12


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/


From nobody Tue Feb  9 07:03:07 2016
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D977E1A90E9 for <avt@ietfa.amsl.com>; Tue,  9 Feb 2016 07:03:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 xW7qh9UVXe5f for <avt@ietfa.amsl.com>; Tue,  9 Feb 2016 07:03:04 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A42671A90ED for <avt@ietf.org>; Tue,  9 Feb 2016 07:03:04 -0800 (PST)
Received: from [130.209.247.112] (port=53581 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1aT9oj-00013b-IZ; Tue, 09 Feb 2016 15:03:02 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20160209150104.21383.43407.idtracker@ietfa.amsl.com>
Date: Tue, 9 Feb 2016 15:02:59 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <1DE78022-1DF4-479E-B1D0-EC9B862FD83E@csperkins.org>
References: <20160209150104.21383.43407.idtracker@ietfa.amsl.com>
To: IETF AVTCore WG <avt@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/31RUxNbKfiTOYinm-4-A2tgq364>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Meral Shirazipour <meral.shirazipour@ericsson.com>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-12.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Feb 2016 15:03:07 -0000

This version is intended to address the review comments from Gorry =
Fairhurst and Meral Shirazipour. There are a number of clarifications, =
but no protocol changes.=20

Colin



> On 9 Feb 2016, at 15:01, Internet-Drafts@ietf.org wrote:
>=20
>=20
> 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.
>=20
>        Title           : Multimedia Congestion Control: Circuit =
Breakers for Unicast RTP Sessions
>        Authors         : Colin Perkins
>                          Varun Singh
> 	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-12.txt
> 	Pages           : 24
> 	Date            : 2016-02-09
>=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 the applications, then network congestion will
>   deteriorate the user's multimedia experience.  This acts as a safety
>   measure to prevent starvation of network resources denying other
>   flows from access to the Internet, such measures are essential for =
an
>   Internet that is heterogeneous and for traffic that is hard to
>   predict in advance.  This document does not propose a congestion
>   control algorithm; instead, it defines a minimal set of RTP circuit-
>   breakers.  Circuit-breakers are conditions under which an RTP sender
>   needs to stop transmitting media data in order to protect the =
network
>   from excessive congestion.  It is expected that, in the absence of
>   severe congestion, all RTP applications running on best-effort IP
>   networks will be able to run without triggering these circuit
>   breakers.  Any future RTP congestion control specification will be
>   expected to operate within the constraints defined by these circuit
>   breakers.
>=20
>=20
> The IETF datatracker status page for this draft is:
> =
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-12
>=20
> A diff from the previous version is available at:
> =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-circuit-breaker=
s-12
>=20
>=20
> 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.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



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





From nobody Tue Feb  9 07:36:45 2016
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C331A92DE; Tue,  9 Feb 2016 07:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 J9NJUHeK7gjq; Tue,  9 Feb 2016 07:36:41 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CECBB1A92DC; Tue,  9 Feb 2016 07:36:40 -0800 (PST)
X-AuditID: c1b4fb30-f79a76d000000a93-92-56ba07862148
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id C5.FD.02707.6870AB65; Tue,  9 Feb 2016 16:36:39 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.74) with Microsoft SMTP Server id 14.3.248.2; Tue, 9 Feb 2016 16:36:38 +0100
References: <20160209150104.21383.43407.idtracker@ietfa.amsl.com>
To: <avt@ietf.org>, <rmcat@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <56BA0785.2080802@ericsson.com>
Date: Tue, 9 Feb 2016 16:36:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160209150104.21383.43407.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHLMWRmVeSWpSXmKPExsUyM2K7h247+64wg+udHBYve1ayW6y++YHN gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZb9+2sBYck6tY8WoaUwPjIokuRk4OCQETia53E5kh bDGJC/fWs3UxcnEICRxmlOjddIsJwlnGKPFi8g92kCphAXeJM3N+gtlCAo4S6582gXWLCKhI HDxwnRXEZhOwkLj5o5ENxOYV0JbYu/sjmM0CVLPx6VGwXlGBGImLnUeYIGoEJU7OfMICYnMK OEm0PN0JVMPBwSxgL/FgaxlImFlAXqJ562xmiLXaEg1NHawTGAVmIemehdAxC0nHAkbmVYyi xanFSbnpRkZ6qUWZycXF+Xl6eaklmxiBoXhwy2+DHYwvnzseYhTgYFTi4f0guzNMiDWxrLgy 9xCjBAezkgiv3BugEG9KYmVValF+fFFpTmrxIUZpDhYlcd7VzuvDhATSE0tSs1NTC1KLYLJM HJxSDYztNdfWRW7SLNu0YpfQG0U9w6vMTR+aueKS6udlONxmqT9quPKa6p1LwT6TSg3DD3vU cHU+cypOcd+W083SOM9cripkVeHmWUt+f1aU6Z3Ttz5D5YP2e/n6qpCmr01rrTnfVdR/+srm ZFEc5dvPeOzVJiFT6yg9n7dW917KsT1K1Fn9YdODo0osxRmJhlrMRcWJALYzekFBAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/1TTHSxlLmSK48VWIsp3vSJXvlxg>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-12.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Feb 2016 15:36:44 -0000

AVTCORE and RMCAT,

I have in my role as document shepherd reviewed the changes. They are 
almost all clarifications. There is on added SHOULD NOT in the text. 
This is that one SHOULD NOT turn off the RTP circuit breaker due to 
missing RTCP implementation unless a non-RTP/RTCP based circuit breaker 
is available with reference to the TSVWG circuit breaker.

I don't consider this a major changes, and will proceed with producing 
my publication request and related write-up. The WG will have a week or 
so to react to the changes before I submit the publication request.

Cheers

Magnus Westerlund
AVTCORE chair

Den 2016-02-09 kl. 16:01, skrev internet-drafts@ietf.org:
>
> 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-12.txt
> 	Pages           : 24
> 	Date            : 2016-02-09
>
> 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 the applications, then network congestion will
>     deteriorate the user's multimedia experience.  This acts as a safety
>     measure to prevent starvation of network resources denying other
>     flows from access to the Internet, such measures are essential for an
>     Internet that is heterogeneous and for traffic that is hard to
>     predict in advance.  This document does not propose a congestion
>     control algorithm; instead, it defines a minimal set of RTP circuit-
>     breakers.  Circuit-breakers are conditions under which an RTP sender
>     needs to stop transmitting media data in order to protect the network
>     from excessive congestion.  It is expected that, in the absence of
>     severe congestion, all RTP applications running on best-effort IP
>     networks will be able to run without triggering these circuit
>     breakers.  Any future RTP congestion control specification will be
>     expected to operate within the constraints defined by these circuit
>     breakers.
>
>
> 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-12
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-12
>
>
> 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/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed Feb 10 15:57:29 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E37F1A70E2; Wed, 10 Feb 2016 15:57:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160210235725.3561.25028.idtracker@ietfa.amsl.com>
Date: Wed, 10 Feb 2016 15:57:25 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/XUSZiFjz6yUoNT6mv4hHKeDinNg>
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-13.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 10 Feb 2016 23:57:25 -0000

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-13.txt
	Pages           : 24
	Date            : 2016-02-10

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 the applications, then network congestion will
   deteriorate the user's multimedia experience.  This acts as a safety
   measure to prevent starvation of network resources denying other
   flows from access to the Internet, such measures are essential for an
   Internet that is heterogeneous and for traffic that is hard to
   predict in advance.  This document does not propose a congestion
   control algorithm; instead, it defines a minimal set of RTP circuit-
   breakers.  Circuit-breakers are conditions under which an RTP sender
   needs to stop transmitting media data in order to protect the network
   from excessive congestion.  It is expected that, in the absence of
   severe congestion, all RTP applications running on best-effort IP
   networks will be able to run without triggering these circuit
   breakers.  Any future RTP congestion control specification will be
   expected to operate within the constraints defined by these circuit
   breakers.


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-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-13


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/


From nobody Wed Feb 10 16:07:00 2016
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 283071A86DF for <avt@ietfa.amsl.com>; Wed, 10 Feb 2016 16:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 94wl5BoI_enq for <avt@ietfa.amsl.com>; Wed, 10 Feb 2016 16:06:55 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD3E21A86DD for <avt@ietf.org>; Wed, 10 Feb 2016 16:06:54 -0800 (PST)
Received: from [81.187.2.149] (port=40717 helo=[192.168.0.86]) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1aTema-00056E-Ny for avt@ietf.org; Thu, 11 Feb 2016 00:06:53 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20160210235725.3561.25028.idtracker@ietfa.amsl.com>
Date: Thu, 11 Feb 2016 00:06:50 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DBAC8A5-857E-4D77-B8E4-F8F7C0EA522A@csperkins.org>
References: <20160210235725.3561.25028.idtracker@ietfa.amsl.com>
To: IETF AVTCore WG <avt@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/pPS44upELcTbgbR5z8FHlKDoLRw>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-13.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 11 Feb 2016 00:06:59 -0000

This is a very minor update: it adds a reference to ConEx [RFC7713], as =
a potential future means of signalling congestion:

Index: draft-ietf-avtcore-rtp-circuit-breakers.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- draft-ietf-avtcore-rtp-circuit-breakers.xml	(revision 1099)
+++ draft-ietf-avtcore-rtp-circuit-breakers.xml	(working copy)
@@ -157,7 +157,9 @@
         2) if <xref target=3D"RFC3168">Explicit Congestion Notification=20=

         (ECN)</xref> is supported, the network can signal the presence=20=

         of congestion by marking packets using ECN Congestion =
Experienced=20
-        (CE) marks; or=20
+        (CE) marks (this could potentially be augmented by mechanisms
+        such as ConEX <xref target=3D"RFC7713"/>, or other future =
protocol
+        extensions for network signalling of congestion); or=20
         3) in the extreme case, congestion will cause packet loss that
         can be detected by observing a gap in the received RTP sequence =
numbers. =20
       </t>

Colin


> On 10 Feb 2016, at 23:57, Internet-Drafts@ietf.org wrote:
>=20
>=20
> 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.
>=20
>        Title           : Multimedia Congestion Control: Circuit =
Breakers for Unicast RTP Sessions
>        Authors         : Colin Perkins
>                          Varun Singh
> 	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-13.txt
> 	Pages           : 24
> 	Date            : 2016-02-10
>=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 the applications, then network congestion will
>   deteriorate the user's multimedia experience.  This acts as a safety
>   measure to prevent starvation of network resources denying other
>   flows from access to the Internet, such measures are essential for =
an
>   Internet that is heterogeneous and for traffic that is hard to
>   predict in advance.  This document does not propose a congestion
>   control algorithm; instead, it defines a minimal set of RTP circuit-
>   breakers.  Circuit-breakers are conditions under which an RTP sender
>   needs to stop transmitting media data in order to protect the =
network
>   from excessive congestion.  It is expected that, in the absence of
>   severe congestion, all RTP applications running on best-effort IP
>   networks will be able to run without triggering these circuit
>   breakers.  Any future RTP congestion control specification will be
>   expected to operate within the constraints defined by these circuit
>   breakers.
>=20
>=20
> The IETF datatracker status page for this draft is:
> =
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-13
>=20
> A diff from the previous version is available at:
> =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-circuit-breaker=
s-13
>=20
>=20
> 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.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



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





From nobody Wed Feb 17 05:04:13 2016
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFFF51B39CF for <avt@ietfa.amsl.com>; Wed, 17 Feb 2016 05:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, TVD_SPACE_RATIO=0.001] autolearn=ham
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 MNCVhjBQlR-R for <avt@ietfa.amsl.com>; Wed, 17 Feb 2016 05:04:08 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4FF51B39CC for <avt@ietf.org>; Wed, 17 Feb 2016 05:04:07 -0800 (PST)
X-AuditID: c1b4fb2d-f794c6d000006f31-63-56c46fc52101
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id A1.B3.28465.5CF64C65; Wed, 17 Feb 2016 14:04:05 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.50) with Microsoft SMTP Server id 14.3.248.2; Wed, 17 Feb 2016 14:04:05 +0100
To: IETF AVTCore WG <avt@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <56C46FC3.7050509@ericsson.com>
Date: Wed, 17 Feb 2016 14:04:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyM2K7ge7R/CNhBucWGVu87FnJ7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujK5F35kLrrJWXFgziamB8RlLFyMnh4SAicSyS4tYIWwxiQv3 1rN1MXJxCAkcZpQ4c/gDE4SznFHi7qa1jCBVIgJKEjsmbWMGsdkELCRu/mhkA7GFBbwkzlze wARi8wpoS6xaNgdsA4uAqsSfW6vB4qICMRIXO49A1QhKnJz5BKiGg4NZwF7iwdYykDCzgLxE 89bZYOOFgMY0NHWwTmDkm4WkYxZCxywkHQsYmVcxihanFhfnphsZ66UWZSYXF+fn6eWllmxi BAbUwS2/dXcwrn7teIhRgINRiYd3Q+HhMCHWxLLiytxDjBIczEoivIVpR8KEeFMSK6tSi/Lj i0pzUosPMUpzsCiJ865xXh8mJJCeWJKanZpakFoEk2Xi4JRqYOxtlp6taa4+o2zmatsLt15O ZEsycEqQceoSKot3eTxrItOWtpraeYvYuayKDbrNNq3d6CvP9PytTOZ71VWzVtu9WJT1PGHh 3B9Hv5xRqrtyoi11TtH17Tztt5df4Poo7voy4ZIHR6npcq6+DzsWV+izaOomRWhPLbh/7MPi JD+/nq6bYvMDDyuxFGckGmoxFxUnAgC7aBZGJAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/zcI-ducIAvEqat1NBa1Z-7zm_uc>
Subject: [AVTCORE] Publication Request of draft-ietf-avtcore-rtp-circuit-breakers-13
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 17 Feb 2016 13:04:12 -0000

WG,

I have just requested publication as proposed standard of 
draft-ietf-avtcore-rtp-circuit-breakers-13.

Writeup is available here:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/shepherdwriteup/

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Sun Feb 21 12:52:55 2016
Return-Path: <petithug@acm.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A36971ACDA5; Sun, 21 Feb 2016 12:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.636
X-Spam-Level: 
X-Spam-Status: No, score=-0.636 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_84=0.6, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no
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 j7MuW4SyHZHN; Sun, 21 Feb 2016 12:52:51 -0800 (PST)
Received: from implementers.org (implementers.org [173.246.102.69]) by ietfa.amsl.com (Postfix) with ESMTP id DA48D1ACDA8; Sun, 21 Feb 2016 12:52:50 -0800 (PST)
Received: from [IPv6:2602:ae:177f:9f00:f486:e1a7:6cf7:c359] (unknown [IPv6:2602:ae:177f:9f00:f486:e1a7:6cf7:c359]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 3E779200E3; Sun, 21 Feb 2016 21:52:49 +0100 (CET)
To: Dave Garrett <davemgarrett@gmail.com>, tls@ietf.org
References: <56A8904D.10307@ericsson.com> <CAOgPGoBU+h6cA9RDxBX2m1AR-3-GnC7OYcfDLTpDepX00g73dA@mail.gmail.com> <201602080117.57742.davemgarrett@gmail.com>
From: Marc Petit-Huguenin <petithug@acm.org>
X-Enigmail-Draft-Status: N1110
Message-ID: <56CA239F.6010107@acm.org>
Date: Sun, 21 Feb 2016 13:52:47 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0
MIME-Version: 1.0
In-Reply-To: <201602080117.57742.davemgarrett@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/wCbtIt8gmCVMQwKhEgJ55rximC4>
Cc: avt@ietf.org
Subject: Re: [AVTCORE] [TLS] WG last call of draft-ietf-avtcore-rfc5764-mux-fixes-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 21 Feb 2016 20:52:52 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/07/2016 11:17 PM, Dave Garrett wrote:
> Permanently gobbling up the majority of the codespace feels like
> excessive force here. 

This is not what the RFC-to-be is proposing.  We are just marking the values that can create an issue when used with RFC 5764 as reserved, with a note in the IANA registry that ask to read the RFC-to-be to understand the problem.  If a new proposed ContentType codepoint will never ever be used in the context of RTCWeb, then it can be allocated in the reserved range.

> For TLS 1.3, the first byte will always be one
> of alert(21), handshake(22), or application_data(23), even for custom
> types. The stated type for TLSCiphertext has been frozen to
> application_data(23) with the actual type for the payload now in the
> encrypted fragment. (this is of course assuming we don't eventually
> drop the frozen type & version here, which now sounds unlikely if
> we're having to deal with design flaws like this) Even handshake
> records after the hellos will have an opaque_type of
> application_data(23), with the encrypted fragment.type containing the
> actual handshake(22) designation. All TLS 1.3+ packets will be
> detected with the RFC 5764 Section 5.1.2 algorithm even if new types
> are allocated in the proposed reserved ranges.
> 
> Locking down the <1.2 registry seems fine, however 1.3+ should be
> able to do whatever it needs as its encrypted type is not going to
> get accidentally read & misinterpreted by anything.
> 
> https://tools.ietf.org/html/draft-ietf-tls-tls13-11#section-5.2.2 
> https://tools.ietf.org/html/rfc5764#section-5.1.2 
> https://tools.ietf.org/html/draft-ietf-avtcore-rfc5764-mux-fixes-05#section-4
>
> 
> 
> Dave
> 
> 
> On Monday, February 08, 2016 12:21:02 am Joseph Salowey wrote:
>> This document is relevant to the TLS working because it reserves a
>> large portion of the TLS content type space.  The values 0-19 and
>> 64-255 cannot be used without checking for conflicts with
>> SRTP-DTLS's wacky demultiplexing scheme.   In TLS 1.3 we will move
>> more encrypted content types which should limit the impact this
>> unfortunate design on TLS evolution, but the working group should
>> be aware of this.
>> 
>> 
>> On Wed, Jan 27, 2016 at 1:39 AM, Magnus Westerlund 
>> <magnus.westerlund@ericsson.com> wrote:
>> 
>>> AVTCORE and TLS,
>>> 
>>> TLS WG, you are included in this WG last call, as this document
>>> affects the TLS ContentType IANA registry.
>>> 
>>> This email starts a two week WG last call, that ends on the 10th
>>> of February. The intended status of this document is standards
>>> track (Proposed Standard).
>>> 
>>> The document can be retrieved here: 
>>> https://datatracker.ietf.org/doc/draft-ietf-avtcore-rfc5764-mux-fixes/

- --
>>> 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWyiOZAAoJECnERZXWan7EpAwQALT42q+uWbjk9qfPZmJI4dzU
EKhNuQw+yJZ6Pk0TO5EbLtbLb0U9huWIXfL/qnMhoZKmtyBI05yL08KIIucJQJ74
Y/vTcVuYhminD4Ug8p4ytu9v5RotexQFbomFKqZP3TC0hCISrrWbbg+LU0EEPpZM
jT+D8pYdzAXGEYQvZ8k9xq/rjZfksYLjQOUPLHgoCC1L3wzr3xvswKQ7c0NEoSC8
rDbVxTp4f+q15W3/HG29+wFN6npgapFK49bXPzAR2LYTHO8yw6mHpHMEd3zq9Kd/
HsdOWH2ETqFiLOaszFO+rzQPx+/OsEwZWDTf2tcKLamogCoKfRJKICmFWAvHSf9G
56aiBiwL6kdKZHIcOJ4zQZqG7UdZ1pVy78czPfkjSwB8TD1RMFXNwS6WTgF9RmYy
Ixe1lrvzOdfrL02NvGz2DdEAM7ETS9ujIxbrOUTEg6d7IDJ7FQdT97zHxvCUfjLY
kDd4RtVqIr825+78uJxeXCJ5fZfXOG0VbwpwlC2smyxHUUVwTWQMCJ32EvZynuFo
f7yNMkdSolr3C2Bkt5ELwnKxUtiTqFMZj52rtBzhqAN6iDt289JSvO1e87EORBin
N1ingAw1bEJz1raNF0uA8u7N12QUtAsPrc9hYpmYjxl6I3+d/lFevvmWne/YbWbU
UduqXpPezcNInD7bMDOD
=J64B
-----END PGP SIGNATURE-----


From nobody Wed Feb 24 14:19:43 2016
Return-Path: <ben@nostrum.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A84F21B4066; Wed, 24 Feb 2016 14:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006] autolearn=ham
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 2CSvfq41hgGF; Wed, 24 Feb 2016 14:19:40 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 9B28E1B4057; Wed, 24 Feb 2016 14:19:40 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u1OMJc5D054433 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 24 Feb 2016 16:19:39 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: draft-ietf-avtcore-rtp-circuit-breakers.all@ietf.org, avt@ietf.org
Date: Wed, 24 Feb 2016 16:19:38 -0600
Message-ID: <55B4CAAF-50FB-4111-82EE-3B40B0D9C2F4@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5226)
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/RVAOMdE0El3Ru4KbFHg-zSmT6iU>
Subject: [AVTCORE] AD Evaluation of draft-ietf-avtcore-rtp-circuit-breakers-13
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 24 Feb 2016 22:19:42 -0000

Hi,

This is my AD Evaluation of draft-ietf-avtcore-rtp-circuit-breakers-13. 
While I do have some comments and questions, I don't think anything here 
needs to block IETF last call. Please address these along with any other 
last call feedback.

Thanks!

Ben.


Substantive
===========

-4, third paragraph, sentence starting with "This approach SHOULD NOT be 
used..."

Does this mean that, in addition to the fact that non-RTCP peers 
shouldnâ€™t be on the network in the first place, a circuit-breaker 
implementation shouldnâ€™t talk to them even if they are? That is, even 
if the peer has a "good reason" (in an RFC 2119 sense) to violate that 
SHOULD, circuit-breaker implementations should ostracize it? :-)

-4.2, last paragraph, sentence starting with "In this case"

Does this imply that the SHOULD only applies if the sender has reason to 
believe that the SR or RR packets will be too large? or should the 
sender always behave this way?

How does this relate to the guidance (MAY) in section 8?

- 4.3, 6th paragraph:"Implementations that desire this extra sensitivity 
MAY use the full TCP throughput equation in the RTP circuit breaker. "

Is there potential for the extra sensitivity to do harm (beyond the 
higher calculation complexity)?

-4.4, 2nd to last paragraph, last sentence:

Is there any potential guidance on reasonable lower limits to the time 
period considered "significant"?

- 12.2:

It seems like the following references might should be normative: 
I-D.ietf-tsvwg-circuit-breaker, RFC3168, RFC6679


Editorial
=========

- Abstract
s/"will deteriorate"/"will cause the deterioration of"
-- "This acts as a safety measure..."
What is the antecedent for â€śthisâ€ť? Congestion control? The 
deterioration? (Also, this sentence contains a comma splice)

- 1:
A very short definition of what we mean by "circuit breaker" might be 
useful.

- 3:
It's a little odd to find 2119 keywords imbedded in term definitions. 
You might consider moving those to procedure sections. (OTOH, it may not 
be worth changing this late in the process.)

-4.2, last paragraph:
What would it even mean to maintain a timeout past the end of the 
related stream?

-4.3,

-- paragraph 6:
typo: s/throughout/throughput

-- paragraph 9: "MUST record the value of the fraction
    lost field in the report block"

Does this mean the field _from_ the report block? (That is, you aren't 
_writing_ the value in the report block?)

-9, last paragraph:

Is this paragraph really related to security? It sounds more like an 
operational consideration.






From nobody Wed Feb 24 14:39:12 2016
Return-Path: <ben@nostrum.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B175B1A038E; Wed, 24 Feb 2016 14:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006] autolearn=ham
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 hajGr-SRt5LX; Wed, 24 Feb 2016 14:39:09 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 14CBA1A039E; Wed, 24 Feb 2016 14:39:09 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u1OMd8qi056113 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 24 Feb 2016 16:39:08 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: draft-ietf-avtcore-rtp-circuit-breakers.all@ietf.org, avt@ietf.org
Date: Wed, 24 Feb 2016 16:39:08 -0600
Message-ID: <3D21CCE4-86DB-4F3D-940B-CEE2868401B6@nostrum.com>
In-Reply-To: <55B4CAAF-50FB-4111-82EE-3B40B0D9C2F4@nostrum.com>
References: <55B4CAAF-50FB-4111-82EE-3B40B0D9C2F4@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5226)
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/jrGiwZgPKn9HJeg2KdIxxfJG35Y>
Subject: Re: [AVTCORE] AD Evaluation of draft-ietf-avtcore-rtp-circuit-breakers-13
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 24 Feb 2016 22:39:10 -0000

Hi,

I had one additional question that I forgot to include:

There was a brief thread on the wg list about practical implementation 
experience. Simon started the conversation starting with [1]. Has that 
conversation been resolved, at least to the extent it can?

[1] 
https://mailarchive.ietf.org/arch/msg/avt/3MHdwQzBhpYzTiM5SJeHLnULEbs

Thanks!

Ben.

On 24 Feb 2016, at 16:19, Ben Campbell wrote:

> Hi,
>
> This is my AD Evaluation of 
> draft-ietf-avtcore-rtp-circuit-breakers-13. While I do have some 
> comments and questions, I don't think anything here needs to block 
> IETF last call. Please address these along with any other last call 
> feedback.
>
> Thanks!
>
> Ben.
>
>
> Substantive
> ===========
>
> -4, third paragraph, sentence starting with "This approach SHOULD NOT 
> be used..."
>
> Does this mean that, in addition to the fact that non-RTCP peers 
> shouldnâ€™t be on the network in the first place, a circuit-breaker 
> implementation shouldnâ€™t talk to them even if they are? That is, 
> even if the peer has a "good reason" (in an RFC 2119 sense) to violate 
> that SHOULD, circuit-breaker implementations should ostracize it? :-)
>
> -4.2, last paragraph, sentence starting with "In this case"
>
> Does this imply that the SHOULD only applies if the sender has reason 
> to believe that the SR or RR packets will be too large? or should the 
> sender always behave this way?
>
> How does this relate to the guidance (MAY) in section 8?
>
> - 4.3, 6th paragraph:"Implementations that desire this extra 
> sensitivity MAY use the full TCP throughput equation in the RTP 
> circuit breaker. "
>
> Is there potential for the extra sensitivity to do harm (beyond the 
> higher calculation complexity)?
>
> -4.4, 2nd to last paragraph, last sentence:
>
> Is there any potential guidance on reasonable lower limits to the time 
> period considered "significant"?
>
> - 12.2:
>
> It seems like the following references might should be normative: 
> I-D.ietf-tsvwg-circuit-breaker, RFC3168, RFC6679
>
>
> Editorial
> =========
>
> - Abstract
> s/"will deteriorate"/"will cause the deterioration of"
> -- "This acts as a safety measure..."
> What is the antecedent for â€śthisâ€ť? Congestion control? The 
> deterioration? (Also, this sentence contains a comma splice)
>
> - 1:
> A very short definition of what we mean by "circuit breaker" might be 
> useful.
>
> - 3:
> It's a little odd to find 2119 keywords imbedded in term definitions. 
> You might consider moving those to procedure sections. (OTOH, it may 
> not be worth changing this late in the process.)
>
> -4.2, last paragraph:
> What would it even mean to maintain a timeout past the end of the 
> related stream?
>
> -4.3,
>
> -- paragraph 6:
> typo: s/throughout/throughput
>
> -- paragraph 9: "MUST record the value of the fraction
>    lost field in the report block"
>
> Does this mean the field _from_ the report block? (That is, you aren't 
> _writing_ the value in the report block?)
>
> -9, last paragraph:
>
> Is this paragraph really related to security? It sounds more like an 
> operational consideration.


From nobody Wed Feb 24 15:07:55 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5460E1A1BC9; Wed, 24 Feb 2016 15:07:52 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20160224230752.11392.85461.idtracker@ietfa.amsl.com>
Date: Wed, 24 Feb 2016 15:07:52 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/JFiKw_G5unCMuA5Pkf0hxIDnVbM>
Cc: avtcore-chairs@ietf.org, draft-ietf-avtcore-rtp-circuit-breakers@ietf.org, avt@ietf.org, magnus.westerlund@ericsson.com
Subject: [AVTCORE] Last Call: <draft-ietf-avtcore-rtp-circuit-breakers-13.txt> (Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions) to Proposed Standard
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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: Wed, 24 Feb 2016 23:07:52 -0000

The IESG has received a request from the Audio/Video Transport Core
Maintenance WG (avtcore) to consider the following document:
- 'Multimedia Congestion Control: Circuit Breakers for Unicast RTP
   Sessions'
  <draft-ietf-avtcore-rtp-circuit-breakers-13.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-03-09. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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 the applications, then network congestion will
   deteriorate the user's multimedia experience.  This acts as a safety
   measure to prevent starvation of network resources denying other
   flows from access to the Internet, such measures are essential for an
   Internet that is heterogeneous and for traffic that is hard to
   predict in advance.  This document does not propose a congestion
   control algorithm; instead, it defines a minimal set of RTP circuit-
   breakers.  Circuit-breakers are conditions under which an RTP sender
   needs to stop transmitting media data in order to protect the network
   from excessive congestion.  It is expected that, in the absence of
   severe congestion, all RTP applications running on best-effort IP
   networks will be able to run without triggering these circuit
   breakers.  Any future RTP congestion control specification will be
   expected to operate within the constraints defined by these circuit
   breakers.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Thu Feb 25 15:19:31 2016
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23D911B377F; Thu, 25 Feb 2016 15:19:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 PpnNEFmZ_xaR; Thu, 25 Feb 2016 15:19:22 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [93.93.131.52]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34B2B1B3779; Thu, 25 Feb 2016 15:19:22 -0800 (PST)
Received: from [81.187.2.149] (port=46745 helo=[192.168.0.86]) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1aZ5Bn-00016q-Pm; Thu, 25 Feb 2016 23:19:20 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37E425AB@ESESSMB209.ericsson.se>
Date: Thu, 25 Feb 2016 23:19:15 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBDE14F9-B68C-4471-9E24-0D7EA7821795@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B37E425AB@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/E4K6em1W5KXKlTU8fWxdxDQMRjM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] [MMUSIC] Offer/Answer PT Questions - text proposal
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 25 Feb 2016 23:19:28 -0000

Hi,

> On 25 Feb 2016, at 14:17, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> I put together some text:
>=20
> "The scope of a mapping from a particular dynamic payload type number =
to a codec=20
> (or codec configuration) is for a given RTP media flow direction =
within a session.=20

I think this conflicts with various RTP-related RFCs and drafts, =
although whether this conflict causes practical problems is unclear. RFC =
3551 indicates that the binding between RTP payload type and RTP payload =
format is per RTP session, not per sender within an RTP session:

   mechanisms for defining dynamic payload type bindings have been
   specified in the Session Description Protocol (SDP) and in other
   protocols such as ITU-T Recommendation H.323/H.245.  These mechanisms
   associate the registered name of the encoding/payload format, along
   with any additional required parameters, such as the RTP timestamp
   clock rate and number of channels, with a payload type number.  This
   association is effective only for the duration of the RTP session in
   which the dynamic payload type binding is made.  This association
   applies only to the RTP session for which it is made, thus the
   numbers can be re-used for different encodings in different sessions
   so the number space limitation is avoided.

(note: reuse in different sessions, not different participants within a =
session) and:

   Session participants agree through mechanisms beyond the scope of
   this specification on the set of payload types allowed in a given
   session.=20

which is again, agree the set of PTs for a session, not per participant.

RFC 3550 is unclear, and defers to RFC 3551, but suggests the payload =
type mapping is per RTP session:

   RTP media type: An RTP media type is the collection of payload
      types which can be carried within a single RTP session.  The RTP
      Profile assigns RTP media types to RTP payload types.

draft-ietf-avtcore-multi-media-rtp-session-13 (currently in the RFC =
Editor queue) says, in Section 7:

   Establishing a single RTP session using multiple media types requires
   signalling.  This signalling has to:

   1.  ensure that any participant in the RTP session is aware that this
       is an RTP session with multiple media types;

   2.  ensure that the payload types in use in the RTP session are using
       unique values, with no overlap between the media types;

draft-ietf-rtcweb-rtp-usage-25 says, in section 4.3:

   A single RTP payload type number MUST NOT be assigned to different
   RTP payload formats, or different configurations of the same RTP
   payload format, within a single RTP session (note that the "m=3D" =
lines
   in an SDP bundle group [I-D.ietf-mmusic-sdp-bundle-negotiation] form
   a single RTP session).

Finally, the allowable RTP payload type numbers depend on the RTCP =
packet types used in the session, since use of certain RTCP packet types =
prevents use of some RTP payload types when RTP and RTCP multiplexing is =
used. The allowable RTCP packet types are signalled per RTP session, =
also suggesting that the mapping is per session.=20


> The same dynamic payload type number can be mapped to another codec in =
another RTP=20
> media flow direction within the same session. The mapping MUST NOT =
change to a different
> coded (or coded configuration) for the duration of a session. =
Eventhough not recommended,=20
> for a given direction, multiple dynamic payload type numbers can be =
mapped to the=20
> same codec (or codec configuration).=20
>=20
> Note that a mapping has been created once an endpoint
> has sent and offer or answer, describing the mapping for a given =
direction. Even if the
> offer or answer is rejected or discarded, or if RTP media associated =
with the mapping is never
> sent, the mapping MUST NOT change for the given direction within the =
session.
>=20
> Within an offer or answer, the mapping is for the RTP media flow =
direction towards the offerer/answerer,
> unless the media flow is indicated as 'sendonly' in which case the =
mapping is for the media flow direction
> from the offerer/answerer."
>=20
> Note that the text probably needs some fine tuning, but please take a =
look and see whether you are ok with the approach, and whether you think =
the text covers the issues we've discovered.
>=20
> Regards,
>=20
> Christer
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic



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





From nobody Fri Feb 26 14:02:18 2016
Return-Path: <sperreault@jive.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 176881B315B for <avt@ietfa.amsl.com>; Fri, 26 Feb 2016 14:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=unavailable
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 0_l3FzIzVBfi for <avt@ietfa.amsl.com>; Fri, 26 Feb 2016 14:02:15 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (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 4ADA21B315C for <avt@ietf.org>; Fri, 26 Feb 2016 14:02:15 -0800 (PST)
Received: by mail-qk0-x229.google.com with SMTP id o6so37356595qkc.2 for <avt@ietf.org>; Fri, 26 Feb 2016 14:02:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jive-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=ScW+nh6xlXuTRrZ9ii/NJC7v1LUIr+D6BUfOg+WcqOU=; b=pRAAYg6X8xq4Ydu8JHeSdu/uZGlrjZQCvcaFCPMlbbPDmfQQ3WGEAhRCjNclf7EPpr pacJXdFmw+kdPbdOxABRyWXA/n3+v5xyv0Y53OKwiGpFQvMqnirqUVJq/5X4a0E2o1L4 ARKom1iy4rXz9ktL4vo1WGqyuJ0+SegAYAarTCOcyNzQFMN5QJXpmI44rCpJxsNePZwu dUIU5aHCgve5GE+/ZxcyGeZBpao/aC7fYgN4NMkiat/5yE7x8YEspnKFSOKyPXA/KsiU yZ/xlqHdIGzgs5IRrzikDEx2T8F8EiVKWQQlt0/GJqRhMn4QjxZh2uClJK4g5d4gpPkv 7mmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ScW+nh6xlXuTRrZ9ii/NJC7v1LUIr+D6BUfOg+WcqOU=; b=d0ulslWtg2g/sjiG/FsiqfekiSnxtlOpAgm+grYG7Fsc++KbyyKjokN8m4hemFLjk5 ylLUDfdb8+06JOI6N+WCQqC+F8s+gi2kGCBoThbJufAudWKbTzUFEmC2gBikKvJDBPaV kxq7CzNBqqKMBC4g0Ha4PdloztOvM3t+fySDxb32mUoYyM9MMIplTPxYYz4dU5Dq/8zu cg6RUTZD/6CF2+GxMw/Wp2zpXDkTXu3iZ94u5GXoa9D5tu37BkM1WB9LKXlmy85sPdMI iF3s1rIQ0zPbdNxO6p20zsEcpycUDrqNl6QWwvQZsGFrDtVCP5cC33WG4LIt/N4IN0kx Ki/Q==
X-Gm-Message-State: AD7BkJL8RL0UuzwEsf9o2DVBjcX6nfqwbKHry03mWO6QqecuinhotGCgghb54OjWeBVjaDuE
X-Received: by 10.55.201.219 with SMTP id m88mr4986380qkl.41.1456524134425; Fri, 26 Feb 2016 14:02:14 -0800 (PST)
Received: from Simons-MacBook-Air.local (modemcable002.114-70-69.static.videotron.ca. [69.70.114.2]) by smtp.googlemail.com with ESMTPSA id o128sm6105313qhb.34.2016.02.26.14.02.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 26 Feb 2016 14:02:13 -0800 (PST)
To: Ben Campbell <ben@nostrum.com>, draft-ietf-avtcore-rtp-circuit-breakers.all@ietf.org, avt@ietf.org
References: <55B4CAAF-50FB-4111-82EE-3B40B0D9C2F4@nostrum.com> <3D21CCE4-86DB-4F3D-940B-CEE2868401B6@nostrum.com>
From: Simon Perreault <sperreault@jive.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56D0CB64.2040705@jive.com>
Date: Fri, 26 Feb 2016 17:02:12 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <3D21CCE4-86DB-4F3D-940B-CEE2868401B6@nostrum.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/HxM6N-RMvFM8JcA7RkeyEz51r_Y>
Subject: Re: [AVTCORE] AD Evaluation of draft-ietf-avtcore-rtp-circuit-breakers-13
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 26 Feb 2016 22:02:17 -0000

Le 2016-02-24 17:39, Ben Campbell a Ă©crit :
> There was a brief thread on the wg list about practical implementation
> experience. Simon started the conversation starting with [1]. Has that
> conversation been resolved, at least to the extent it can?

As far as I am concerned:

- The authors added good text about how to handle non-conforming
implementations.

- Even with that text, non-conforming implementations are so common in
practice as to make this whole idea inapplicable to the SIP world in
general. I admit WebRTC might be different and having WebRTC endpoints
implement this algorithm would probably make sense, because they would
be less likely to have to interoperate with broken implementations.

Just my 2 cents.

Simon

