[rohc] RTP TS reset/wraparound (UOR-2 extension 3 TSC=0)
zbyszek <z50742850@gmail.com> Mon, 21 October 2013 09:12 UTC
Return-Path: <z50742850@gmail.com>
X-Original-To: rohc@ietfa.amsl.com
Delivered-To: rohc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC6C511E814D for <rohc@ietfa.amsl.com>; Mon, 21 Oct 2013 02:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.418
X-Spam-Level:
X-Spam-Status: No, score=-0.418 tagged_above=-999 required=5 tests=[AWL=2.181, BAYES_00=-2.599]
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 AbSCHIuL5Otg for <rohc@ietfa.amsl.com>; Mon, 21 Oct 2013 02:12:24 -0700 (PDT)
Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDB311E84D0 for <rohc@ietf.org>; Mon, 21 Oct 2013 02:12:03 -0700 (PDT)
Received: from tom.nabble.com ([192.168.236.105]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from <z50742850@gmail.com>) id 1VYBWs-0003s7-NS for rohc@ietf.org; Mon, 21 Oct 2013 02:12:02 -0700
Date: Mon, 21 Oct 2013 02:12:02 -0700
From: zbyszek <z50742850@gmail.com>
To: rohc@ietf.org
Message-ID: <1382346722668-389279.post@n7.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 21 Oct 2013 03:41:44 -0700
Subject: [rohc] RTP TS reset/wraparound (UOR-2 extension 3 TSC=0)
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Oct 2013 09:15:19 -0000
Hi, How compressor should send TS (UOR-2 extension 3 TSC=0) when TS=0xA0 (there was gap: RTP TS has been reseted -> so behaviour is like in TS wraparound?). RFC4815 says that: /4.1. Encoding Used for Compressed TS Bits ... If a compressed packet carries an Extension 3 and field(Tsc)=0, the compressed packet must thus always carry unscaled TS bits. For TS values sent in Extension 3, W-LSB encoded values are sent using the self-describing variable- length format (RFC 3095-Section 4.5.6), and this applies to both scaled and unscaled values./ for TS=0xA0 SDVL (RFC 3095-Section 4.5.6) says that TS should be allocated in 14-bit (2 octets) My question is: when compressor will send unscaled TS on 14-bit if decompressor will be able to decode it properly when there was reset/wraparound of TS? or compressor should sent TS on 32-bit or use IR-DYN packet? (scenario: UOR-2 extension 3 TSC=0, TS=0xA0) Br Zbyszek -- View this message in context: http://ietf.10.n7.nabble.com/RTP-TS-reset-wraparound-UOR-2-extension-3-TSC-0-tp389279.html Sent from the IETF - Rohc mailing list archive at Nabble.com.