Re: [AVT] Additional requirement in Congestion control for the "draft-kristensen-avt-rtp-h264-rcdo-00"
"Tom Kristensen" <2mkristensen@gmail.com> Mon, 23 July 2007 22:36 UTC
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID6W4-0006lm-1P; Mon, 23 Jul 2007 18:36:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID6W2-0006lf-Kx for avt@ietf.org; Mon, 23 Jul 2007 18:36:34 -0400
Received: from nz-out-0506.google.com ([64.233.162.225]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID6W1-0005kh-Fu for avt@ietf.org; Mon, 23 Jul 2007 18:36:34 -0400
Received: by nz-out-0506.google.com with SMTP id n1so1221496nzf for <avt@ietf.org>; Mon, 23 Jul 2007 15:36:32 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pyM+GpwLQGfgMpXHMyqkeqVQCLtLGfbCBqzW+X9PFExsLkgIFKYYBRqyto1tq/pYEJ2dQ7nuYDnzYsMW64jP8sOL2XNtGHZwGlPS4KWCyIkNB1NmP8mscCKzY562P4Zues4kTmXUZeYatfg1U8sjECHf76UOZoIrASXKEPJX2NQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jXnkaECc7Mq72eW6d7s6+RV1lvhtRNPgtqDzCstu81NdwXNIC2coc5giFDhEMrb892+YFAuTuK3eXH919MGt2DUDBsx93mFTbB4T4RXJvUhm/gpA+fKlBUgSa3iPWK8nQTBNzrvVdAvyoIgyZ/cglClC8qXvylZPlCMyk8s1uiM=
Received: by 10.114.199.1 with SMTP id w1mr3444923waf.1185230191788; Mon, 23 Jul 2007 15:36:31 -0700 (PDT)
Received: by 10.114.145.6 with HTTP; Mon, 23 Jul 2007 15:36:31 -0700 (PDT)
Message-ID: <7e4b541c0707231536s2ff21497p5c5a23a0f6806048@mail.gmail.com>
Date: Tue, 24 Jul 2007 00:36:31 +0200
From: Tom Kristensen <2mkristensen@gmail.com>
To: "steve.norreys@bt.com" <steve.norreys@bt.com>
Subject: Re: [AVT] Additional requirement in Congestion control for the "draft-kristensen-avt-rtp-h264-rcdo-00"
In-Reply-To: <20B524BAC1567F48AE039F74BD294D19EDC48B@E03MVB1-UKBR.domain1.systemhost.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20B524BAC1567F48AE039F74BD294D19EDC48B@E03MVB1-UKBR.domain1.systemhost.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org
On 24/07/07, steve.norreys@bt.com <steve.norreys@bt.com> wrote: > Hi > > I just skimmed the draft-kristensen-avt-rtp-h264-rcdo-00 > draft and section 6 that deals with congestion control puzzled me somewhat. > The reference to the main congestion control in RFC3550 in the first > sentence is fine but I don't understand the relationship to the rest of the > paragraph. As the media in a sip sense has been 'offered and answered' > therefore congestion techniques will not apply to this 'session' as > congestion control traditionally only applies to the setup of new > 'sessions'. The text in section 6 is stolen from the draft "How to Write an RTP Payload Format" (draft-ietf-avt-rtp-howto-01) - where the text is proposed as an initial text for this section in the template provided. However, an RTP payload format specification is not written solely for SIP applications - so other scenarios apply as well. > The packet loss could be as a result of congestion and could be used as a > indicator to apply congestion control at this entity that is suffering the > packet loss but this is not the only indication of congestion. Presumably > one of the entities monitoring the packet loss is the UE which I hope is not > under congestion but could still be suffering from packet loss does it then > report this loss to the entity sending the higher resolution video. I think > that some clarification of what the additional requirement to monitor packet > loss is needed. Thanks for the input, it's possible to expand and elaborate the text in the H264-RCDO RTP payload format draft. -- Tom -- # TANDBERG R&D ## http://www.tandberg.com _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Additional requirement in Congestion contro… steve.norreys
- Re: [AVT] Additional requirement in Congestion co… Tom Kristensen
- Re: [AVT] Additional requirement in Congestion co… Magnus Westerlund