Re: [AVT] draft-schierl-avt-rtp-multi-session-transmission-00.txt

Colin Perkins <csp@csperkins.org> Sun, 16 November 2008 20:35 UTC

Return-Path: <avt-bounces@ietf.org>
X-Original-To: avt-archive@optimus.ietf.org
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 337263A69B9; Sun, 16 Nov 2008 12:35:50 -0800 (PST)
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2EE903A697B for <avt@core3.amsl.com>; Sun, 16 Nov 2008 12:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.103
X-Spam-Level:
X-Spam-Status: No, score=-6.103 tagged_above=-999 required=5 tests=[AWL=0.496, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NT8KclANqbbF for <avt@core3.amsl.com>; Sun, 16 Nov 2008 12:35:47 -0800 (PST)
Received: from mr1.dcs.gla.ac.uk (mr1.dcs.gla.ac.uk [130.209.249.184]) by core3.amsl.com (Postfix) with ESMTP id 20B483A684A for <avt@ietf.org>; Sun, 16 Nov 2008 12:35:47 -0800 (PST)
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:63126 helo=[192.168.0.4]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1L1noj-0001DS-Rr; Sun, 16 Nov 2008 20:01:58 +0000
In-Reply-To: <44C96BEE548AC8429828A3762315034701492BE5@vaebe101.NOE.Nokia.com>
References: <026F8EEDAD2C4342A993203088C1FC0508BF251C@esealmw109.eemea.ericsson.se><44C96BEE548AC8429828A376231503470149232D@vaebe101.NOE.Nokia.com><ybuy6znjw82.fsf@jesup.eng.wgate.com><44C96BEE548AC8429828A3762315034701492B47@vaebe101.NOE.Nokia.com> <ybuk5b3r95k.fsf@jesup.eng.wgate.com> <44C96BEE548AC8429828A3762315034701492BE5@vaebe101.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <29D0A231-7B79-4CF8-906C-8A4657F90D1F@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
Date: Sun, 16 Nov 2008 20:01:57 +0000
To: Ye-Kui.Wang@nokia.com
X-Mailer: Apple Mail (2.753.1)
Cc: rjesup@wgate.com, ingemar.s.johansson@ericsson.com, avt@ietf.org
Subject: Re: [AVT] draft-schierl-avt-rtp-multi-session-transmission-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

Err, no. Things like decoding order number go into an RTP payload  
header, as part of a payload format, not into a header extension.

Colin


On 16 Nov 2008, at 16:46, <Ye-Kui.Wang@nokia.com> wrote:
> Thanks for the clarification, which is important. According to  
> this, it
> appears that if the RTP header extenstion contains Decoder Order  
> Number
> information, then there is no problem, as this information not related
> to anything in the RTP header. A good thing is that this solution is
> really generic!
>
> BR, YK
>
>> -----Original Message-----
>> From: ext Randell Jesup [mailto:rjesup@wgate.com]
>> Sent: 16 November, 2008 17:19
>> To: Wang Ye-Kui (Nokia-NRC/Tampere)
>> Cc: ingemar.s.johansson@ericsson.com; avt@ietf.org
>> Subject: Re: [AVT]
>> draft-schierl-avt-rtp-multi-session-transmission-00.txt
>>
>> <Ye-Kui.Wang@nokia.com> writes:
>>>>>> My question is ..how serious is the identified problem ?.
>>>>>> My gut feeling is that a receiver that implements e.g decoding
>>>>>> of G.718 content will likely update the RTP stack to recognize
>>>>>> header extensions if header extensions are used to carry e.g
>>>>>> the NTP timestamp related to the RTP timetstamp in the RTP  
>>>>>> header.
>>>>
>>>> What if an intermediary deletes the header extension?  (SBC, B2BUA,
>>>> raw message store, etc).
>>>
>>> What are the (good) reasons for an intermediary to delete header
>>> extensions? Isn't so that if there is something an
>> intermediary does not
>>> understand, it'd better not to touch the something?
>>
>> True - but if you modify the main package, passing through the header
>> extension becomes tricky.  For example, a B2BUA may leave the payload
>> alone, but almost always rewrites the RTP header, and may
>> generate it's own
>> (or modify passed-through) RTCP packets.  If the header extension
>> references the header (sequence or timestamps), you could be
>> broken.  Or if
>> the header extension references the SSRC, or data carried in the RTCP
>> stream (like NTP time), you could also be broken, and there's no  
>> way to
>> know if you don't understand (and comply with) the extension.
>>
>> I mention things like this because Asterisk does those
>> actions, I think.
>>
>> -- 
>> Randell Jesup, Worldgate (developers of the Ojo videophone),
>> ex-Amiga OS team
>> rjesup@wgate.com
>> "The fetters imposed on liberty at home have ever been forged
>> out of the weapons
>> provided for defence against real, pretended, or imaginary
>> dangers from abroad."
>> 		- James Madison, 4th US president (1751-1836)
>>
>>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



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



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt