[rohc] TS encoding for RFC 3095
Jer-ming Lin <csiejer@gmail.com> Fri, 01 October 2010 08:33 UTC
Return-Path: <csiejer@gmail.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id EE1093A6BD9 for <rohc@core3.amsl.com>;
Fri, 1 Oct 2010 01:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.452
X-Spam-Level:
X-Spam-Status: No, score=-0.452 tagged_above=-999 required=5 tests=[AWL=-0.658,
BAYES_00=-2.599, DEAR_SOMETHING=1.605, J_CHICKENPOX_27=0.6,
J_CHICKENPOX_28=0.6]
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 NWX0f8xhkt-s for
<rohc@core3.amsl.com>; Fri, 1 Oct 2010 01:33:38 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com
[209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 45EC83A69F9 for
<rohc@ietf.org>; Fri, 1 Oct 2010 01:33:37 -0700 (PDT)
Received: by pwi3 with SMTP id 3so939483pwi.31 for <rohc@ietf.org>;
Fri, 01 Oct 2010 01:34:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:received:date:message-id
:subject:from:to:content-type:content-transfer-encoding;
bh=PMOd8dG3vy1Kj6EFPnLI6BrOTC7292XiCOJ60kTiEXA=;
b=HEbSa/2zTqMzM0nnwZhqVpVOqJ9w1bWT2ZkwuuLtXhC+PqwS/ndF+NU1TGnKCkZjWQ
niKlflHrnCCMUG0PA1XZNSxOVAfh7VZembfKEUTb2J9qmTcyy+GQrqZ4zfE2mkQxlhTN
F0VKHUaF/aOI0btiS+UUpBqFgmbGuWryvyP9c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=mime-version:date:message-id:subject:from:to:content-type
:content-transfer-encoding;
b=GhUQeHw18rdxv91EUU0AsqxSbUktyYVzS5Vy9GscIAIcdzvU0WiacT1FjWLaA1qsFn
CngRVqFLiedd25JJrgGmY5/+xa+yzI1OeZFdvYw/7hqoNk8OtF7H5frfZZZ7BRL93g8C
whATUm8S4oUXd2UhJcPCKonVe3/DMdMIlKslA=
MIME-Version: 1.0
Received: by 10.142.69.9 with SMTP id r9mr4432111wfa.147.1285922064376;
Fri, 01 Oct 2010 01:34:24 -0700 (PDT)
Received: by 10.142.158.5 with HTTP; Fri, 1 Oct 2010 01:34:24 -0700 (PDT)
Date: Fri, 1 Oct 2010 16:34:24 +0800
Message-ID: <AANLkTi=zkpwC2nfeTGnDR=4FU3sWSu8pS_d8_bws0jiw@mail.gmail.com>
From: Jer-ming Lin <csiejer@gmail.com>
To: rohc@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: [rohc] TS encoding for RFC 3095
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 01 Oct 2010 08:33:39 -0000
Hi ROHCers, I have a questions about compressing TS(unscaled and scaled). Would you please give me your advice and clarify me. 1) Does compressor use the transmitted unscaled TS to be its TS reference when compressing scaled TS at the step 2 of RFC 4815's 4.4.3. Or compressor needs to re-construct the reference of scaled TS. Thanks in advance, Jer-ming Lin 2010/2/4 Jer-ming Lin <cs202050@csie.ncu.edu.tw>tw>: > Dear Sir, > > Quoting Carl Knutsson <carl.knutsson@effnet.com>om>: >>> >>> .. >>> TS_STRIDE and the relationship of delta_TS. Is that right? >> >> No, the compressor must first establish the TS_STRIDE by sending it >> as-is together with unscaled TS. From those two values, TS_SCALED and >> TS_OFFSET can be derived and used for later for compression. >> > > After establishing the TS_STRIDE and TS_OFFSET, the compressor sends > scaled TS bits or no TS bits if scaled TS has the relationship of > "delta_TS=delta_SN*default-slope(TS)." > > For performance issue, if the scaled TS(derived from unscaled > TS/TS_STRIDE) also have the relationship of delta_TS in consecutive > IR/IR-DYN/UOR-ext3 packets. Can the compressor send no-TS bits directly > after the establishing packets? The RFC did not mention this. I think this > can reduce the compressed header size since no-TS bits are sent. > > > For example, > > SN, TS, TS_STRIDE, scaled TS, Type, transmit TS bits, > 1, 26189, 280, 93, IR, 32 > 2, 26469, 280, 94, IR, 32 > 3, 26749, 280, 95, IR, 32 > 4, 27029, 280, 96, UO-0, 0 > > The first, sencond, third construct the TS_STRIDE and the relationship of > delta_TS. The forth cand send no-TS bits. > > Sincerely yours, > Jer-ming > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > _______________________________________________ > Rohc mailing list > Rohc@ietf.org > https://www.ietf.org/mailman/listinfo/rohc >
- [rohc] TS encoding for RFC 3095 Jer-ming Lin