Re: [rtcweb] draft-jesup-rtp-congestion-reqs-00.txt: Requirements for RTP congestion control

"James M. Polk" <jmpolk@cisco.com> Mon, 05 March 2012 07:01 UTC

Return-Path: <jmpolk@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E866D21F8594 for <rtcweb@ietfa.amsl.com>; Sun, 4 Mar 2012 23:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.598
X-Spam-Level:
X-Spam-Status: No, score=-109.598 tagged_above=-999 required=5 tests=[AWL=0.774, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K6zNkwcj6cGD for <rtcweb@ietfa.amsl.com>; Sun, 4 Mar 2012 23:01:30 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA9F21F8593 for <rtcweb@ietf.org>; Sun, 4 Mar 2012 23:01:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=3317; q=dns/txt; s=iport; t=1330930890; x=1332140490; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version:content-transfer-encoding; bh=05+t2zBY2mgUk93T0Vz9lJgPpVuExydpnOHRR+b0CSw=; b=mRidMFoB+u3mZM0/b8RZoYrKSaP1nLcxVGsDFtmk0qaYvLw8t75A+VwY q1hjSSrfLq+CFKjY5STvDi5+wA7QT8T/uSvUPKqynOSkEds3I9UGQh0bU F09mlZqPlOJajqowzb4nurV3xm5ZSinLnEFQVm3SzSSz/mvCtZRNiVR3l Q=;
X-IronPort-AV: E=Sophos;i="4.73,532,1325462400"; d="scan'208";a="31907363"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 05 Mar 2012 07:01:29 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2571SVT030459; Mon, 5 Mar 2012 07:01:28 GMT
Message-Id: <201203050701.q2571SVT030459@mtv-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 05 Mar 2012 01:01:27 -0600
To: Harald Alvestrand <harald@alvestrand.no>, "James M. Polk" <jmpolk@cisco.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <4F544FEF.6060702@alvestrand.no>
References: <4F53E513.40002@alvestrand.no> <201203042216.q24MGfal019061@mtv-core-2.cisco.com> <4F544FEF.6060702@alvestrand.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] draft-jesup-rtp-congestion-reqs-00.txt: Requirements for RTP congestion control
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 07:01:31 -0000

At 11:32 PM 3/4/2012, Harald Alvestrand wrote:
>On 03/04/2012 11:16 PM, James M. Polk wrote:
>>Harald
>>
>>Which of these two is expected to be the conflict with rtp-congestion hour?
>Thanks for the pointer to the conflict - I'll pass along to the ICCRG chairs.
>>
>>TUESDAY, March 27, 2012
>>
>>1500-1520  Beverage and Snack Break I - Hall Maillot A
>>1520-1700  Afternoon Session II
>>252A                    IRTF    iccrg Internet 
>>Congestion Control Research Group
>>Maillot                 RAI     avtext Audio/Video Transport Extensions WG
>>253                     RAI     vipr 
>>Verification Involving PSTN Reachability WG
>>
>>1710-1810  Afternoon Session III
>>252A                    IRTF    iccrg Internet 
>>Congestion Control Research Group
>>252B                    RAI     sipcore Session Initiation Protocol Core WG
>>
>>I vote for Session II, but that's just one voice.
>I think so too. I don't know of RTCWEB related material in either session.

fair - but you know there are a LOT of SIP heads in RTCWEB...

James



>>Since most of us aren't part of the ICCRG 
>>mailing list, can you ask and pass along which 
>>session the rtp-congestion hour long discussion will be in? Thanks
>
>Will do.
>
>>
>>BTW - there already is no TSV conflict during either timeslot.
>>
>>James
>>
>>At 03:56 PM 3/4/2012, Harald Alvestrand wrote:
>>>For the WG's interest.
>>>This (among other inputs) will be discussed in 
>>>the IRTF ICCRG WG on Tuesday in Paris.
>>>
>>>Â Â Â Â Â Â Â Â Â Â Â Â Â  Harald
>>>
>>>-------- Original Message --------
>>>Subject: New Version Notification for draft-jesup-rtp-congestion-reqs-00.txt
>>>Date: Sun, 04 Mar 2012 06:19:29 -0800
>>>From: <mailto:internet-drafts@ietf.org>internet-drafts@ietf.org
>>>To: <mailto:harald@alvestrand.no>harald@alvestrand.no
>>>CC: <mailto:randell-ietf@jesup.org>randell-ietf@jesup.org
>>>
>>>
>>>
>>>A new version of I-D, 
>>>draft-jesup-rtp-congestion-reqs-00.txt has 
>>>been successfully submitted by Harald 
>>>Alvestrand and posted to the IETF repository.
>>>
>>>Filename:        draft-jesup-rtp-congestion-reqs
>>>Revision:        00
>>>Title:           Congestion Control Requirements For Real Time Media
>>>Creation date:   2012-03-04
>>>WG ID:           Individual Submission
>>>Number of pages: 7
>>>
>>>Abstract:
>>>    Congestion control is needed for all data transported across the
>>>    Internet, in order to promote fair usage and prevent congestion
>>>    collapse.  The requirements for interactive, point-to-point real time
>>>    multimedia, which needs by low-delay, semi-reliable data delivery,
>>>    are different from the requirements for bulk transfer like FTP or
>>>    bursty transfers like Web pages, and the TCP algorithms are not
>>>    suitable for this traffic.
>>>
>>>    This document attempts to describe a set of requirements that can be
>>>    used to evaluate other congestion control mechanisms in order to
>>>    figure out their fitness for this purpose.
>>>
>>>
>>>
>>>
>>>
>>>
>>>The IETF Secretariat
>>>
>>>
>>>_______________________________________________
>>>rtcweb mailing list
>>>rtcweb@ietf.orghttps://www.ietf.org/mailman/listinfo/rtcweb
>>