[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[rohc] Signalling compression parameters (access len.) and arrange problem

To: rohc at ietf.org
Subject: [rohc] Signalling compression parameters (access len.) and arrange problem
From: Zhu Lei <lei.zhu at huawei.com>
Date: Thu, 13 Aug 2009 19:52:42 +0800
Delivered-to: rohc at core3.amsl.com
List-archive: <http://www.ietf.org/mail-archive/web/rohc>
List-help: <mailto:rohc-request@ietf.org?subject=help>
List-id: Robust Header Compression <rohc.ietf.org>
List-post: <mailto:rohc@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
Thread-index: AcocDJCWDhALqcuGTByVylZJp11zKw==

Hi Rohc and Signalling compressing folks,

May I ask questions which result in some problems with me when I wrote some text with reading RFC3485 (Static Dictionary for Signaling Compression (SigComp)).

1) RFC3485 stated that "minimum_access_length 6". But I can pick up some strings with value only containing 3 or 4 len. If it is a bug in RFC3485 or I missed some considerations of length?

2) If I am correct, your arrangements to list value of strings in dictionary is that you put strings with pri 1 at the buttom. In addition, the second element is arrange is to list by recognize the firt charactor of strings from 0->9 and a->z also from buttom to top.

Best regards,

Lei Zhu

Prev by Date: Re: [rohc] STATIC-NACK and mode transition
Next by Date: [rohc] REJECT and SN-NOT-VALID
Previous by thread: Re: [rohc] STATIC-NACK and mode transition
Next by thread: [rohc] REJECT and SN-NOT-VALID
Index(es):
- Date
- Thread