IETF Logo Mail Archive

Re: [AVT] Some comments to subsection 8.1.1 in draft-ietf-avt-rtp-svc-08

<Ye-Kui.Wang@nokia.com> Thu, 27 March 2008 22:12 UTC

Return-Path: <avt-bounces@ietf.org>
X-Original-To: ietfarch-avt-archive@core3.amsl.com
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8025628C92A; Thu, 27 Mar 2008 15:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.862
X-Spam-Level:
X-Spam-Status: No, score=-100.862 tagged_above=-999 required=5 tests=[AWL=-0.424, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 E--uL2sTJFJl; Thu, 27 Mar 2008 15:12:45 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2CC428C705; Thu, 27 Mar 2008 15:12:45 -0700 (PDT)
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 95CD528C8CA for <avt@core3.amsl.com>; Thu, 27 Mar 2008 15:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 FD-Q6Zx9tEWn for <avt@core3.amsl.com>; Thu, 27 Mar 2008 15:12:43 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id D756228C705 for <avt@ietf.org>; Thu, 27 Mar 2008 15:12:43 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m2RMCDpW017462; Thu, 27 Mar 2008 17:12:26 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 28 Mar 2008 00:10:14 +0200
Received: from vaebe101.NOE.Nokia.com ([10.160.244.11]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 28 Mar 2008 00:10:14 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 28 Mar 2008 00:10:09 +0200
Message-ID: <44C96BEE548AC8429828A3762315034769505B@vaebe101.NOE.Nokia.com>
In-Reply-To: <679BE374-4583-46BB-A72A-DF2C8BFE7802@csperkins.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [AVT] Some comments to subsection 8.1.1 in draft-ietf-avt-rtp-svc-08
Thread-Index: AciQVRWAQmMKzNrxS32e1Jdm1uuuCAAAXejw
References: <70765B7ABD04E845863F69CAC91A5ADB01B0DAA4@Xms1.etsihq.org><12919642-CFC2-492C-9FC0-E1381B30CBFA@csperkins.org><1FEB9B9F2EC38343955D02B2AE86AACB7656DF@lan-ex-02.panasonic.de><50365D40-4B93-4B00-A68D-10BF08468D6D@csperkins.org><1FEB9B9F2EC38343955D02B2AE86AACB7FD805@lan-ex-02.panasonic.de> <8BD6448C-729E-4565-990F-8602B931ABE1@csperkins.org> <44C96BEE548AC8429828A3762315034769505A@vaebe101.NOE.Nokia.com> <679BE374-4583-46BB-A72A-DF2C8BFE7802@csperkins.org>
From: Ye-Kui.Wang@nokia.com
To: csp@csperkins.org
X-OriginalArrivalTime: 27 Mar 2008 22:10:14.0299 (UTC) FILETIME=[5504C6B0:01C89057]
X-Nokia-AV: Clean
Cc: avt@ietf.org
Subject: Re: [AVT] Some comments to subsection 8.1.1 in draft-ietf-avt-rtp-svc-08
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-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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

 

>> 1. In the following copied text, NTP timestamps of NAL units or 
>> operation point representations are mentioned. However, NAL 
>units are 
>> not directly assoicated with NTP timestamps, which are only directly 
>> assoicated with RTCP SRs. The NTP timestamp for each NAL 
>unit must be 
>> defined.
>
>The RTCP SR packets define the mapping between the two 
>timelines, allowing you to directly derive the NTP timestamps 
>from the RTP timestamps in each session. This is the standard 
>RFC 3550 semantics:  
>nothing specific to this format needs to be defined.
>

By defining I meant adding something saying that the NTP timestamp is
derived for each packet (according to RFC 3550) and each NAL unit's NTP
timestamp is equal to the NTP timestamp of the packet the NAL unit is
carried in. This makes the description better, and I think it is aligned
with what you said above. 

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

v2.31.3 | Report a Bug | By Email | System Status