Re: [rtcweb] RTCWeb Data Stream and RTP Synchronization - new I.-D.

Harald Alvestrand <harald@alvestrand.no> Tue, 31 July 2012 16:03 UTC

Return-Path: <harald@alvestrand.no>
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 CBF3621F863F for <rtcweb@ietfa.amsl.com>; Tue, 31 Jul 2012 09:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.324
X-Spam-Level:
X-Spam-Status: No, score=-110.324 tagged_above=-999 required=5 tests=[AWL=0.274, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 IVkuSU7AHI1z for <rtcweb@ietfa.amsl.com>; Tue, 31 Jul 2012 09:03:33 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 42A8321F8620 for <rtcweb@ietf.org>; Tue, 31 Jul 2012 09:03:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id A913839E127 for <rtcweb@ietf.org>; Tue, 31 Jul 2012 18:03:24 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aeXfMF0d8Bt2 for <rtcweb@ietf.org>; Tue, 31 Jul 2012 18:03:23 +0200 (CEST)
Received: from [IPv6:2001:df8:0:80:221:6aff:fe8f:cf14] (unknown [IPv6:2001:df8:0:80:221:6aff:fe8f:cf14]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 01E7539E031 for <rtcweb@ietf.org>; Tue, 31 Jul 2012 18:03:22 +0200 (CEST)
Message-ID: <501801DB.3030600@alvestrand.no>
Date: Tue, 31 Jul 2012 09:03:39 -0700
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAC8DBE4E9704C41BCB290C2F3CC921A1627CACC@nasanexd01h.na.qualcomm.com>
In-Reply-To: <CAC8DBE4E9704C41BCB290C2F3CC921A1627CACC@nasanexd01h.na.qualcomm.com>
Content-Type: multipart/alternative; boundary="------------010001060305010105000709"
Subject: Re: [rtcweb] RTCWeb Data Stream and RTP Synchronization - new I.-D.
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: Tue, 31 Jul 2012 16:03:36 -0000

On 07/30/2012 12:11 PM, Mandyam, Giridhar wrote:
>
> Hello,
>
> Please note the internet draft recently uploaded:http://tools.ietf.org/html/draft-mandyam-rtcweb-data-synch-00  entitled "RTCWeb Data Stream and RTP Synchronization."   All comments, suggestions, requests for clarification, corrections are welcome.
>   
Hello - I scanned your draft quickly, and I see a lot of talk about 
signaling that synchronization between data tracks and RTP tracks is 
requested, but nothing about how you intended to represent timestamps in 
SCTP.

Could you clarify what timestamps you intended to synchronize?

                  Harald

> Thanks,
> -Giri Mandyam, Qualcomm Innovation Center
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb