
From carl.knutsson@effnet.com  Tue Jun 16 06:14:39 2009
Return-Path: <carl.knutsson@effnet.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 655813A689E for <rohc@core3.amsl.com>; Tue, 16 Jun 2009 06:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 SRKwjRoi0awS for <rohc@core3.amsl.com>; Tue, 16 Jun 2009 06:14:38 -0700 (PDT)
Received: from lists.levonline.com (lists.levonline.com [217.70.33.37]) by core3.amsl.com (Postfix) with ESMTP id 686623A6A2E for <Rohc@ietf.org>; Tue, 16 Jun 2009 06:14:34 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by lists.levonline.com (Postfix) with ESMTP id 7DDF429C531; Tue, 16 Jun 2009 14:50:31 +0200 (CEST)
X-Virus-Scanned: By http://levonline.com - free virus scanning for all customers
Received: from lists.levonline.com ([127.0.0.1]) by localhost (lists.levonline.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQ5rDpFJ0IoK; Tue, 16 Jun 2009 14:50:27 +0200 (CEST)
Received: from truck2.fordonnet.levonline.com (gw-uu-virtual.levonline.com [217.70.32.2]) by lists.levonline.com (Postfix) with ESMTP id 3DA5929C506; Tue, 16 Jun 2009 14:50:27 +0200 (CEST)
Received: from [192.168.101.28] (c-6a0471d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.4.106]) (authenticated bits=0) by truck2.fordonnet.levonline.com (8.12.11.20060308/8.12.11) with ESMTP id n5GCoPgm029744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 14:50:26 +0200
Message-ID: <4A379691.3070009@effnet.com>
Date: Tue, 16 Jun 2009 14:56:49 +0200
From: Carl Knutsson <carl.knutsson@effnet.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: Manoranjan Sahu <manoranjansahu@tataelxsi.co.in>
References: <4A377339.5000805@tataelxsi.co.in>
In-Reply-To: <4A377339.5000805@tataelxsi.co.in>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: lars-erik@lejonsson.com, gurushant@tataelxsi.co.in, Rohc@ietf.org, ghyslain.pelletier@ericsson.com
Subject: Re: [rohc] IPID in Extension3
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: Tue, 16 Jun 2009 13:14:39 -0000

Manoranjan Sahu,

I don't have a personal support agreement with you, so I guess your
intention was to send this email to the rohc list. If not, please send
this kind of questions to the rohc list in the future.

I believe this question can be found in the RFC if you read it
carefully. Have you for example studied the RFC4815 section 8.2? RFC4815
 updates RFC3095 (see top of RFC3095).

Also, this question have been asked before on the list. The least
minimum effort before sending a question to list (or RFC authors) should
be to read the RFCs and search the list archives.

Read the thread that start with this message:
http://www.ietf.org/mail-archive/web/rohc/current/msg01675.html

By the way, we will achieve exactly the same compression efficiency by
sending it offset encoded compared to sending it uncompressed.



Best regards,

Carl Knutsson
ROHC WG chair

Manoranjan Sahu wrote:
> Hi,
>    Thanking you for your Previous responses to questions related to ROHC ,
>    I have a doubt regarding Ext3 in RFC 3095.
>    *IPID in Ext3 is compressed(Offset IPID) or Uncompressed(Original
> IPID) ? *
>    if your answer is compressed IPID then please clarify why is that so
> as per my understanding
>    in RFC 3095 Extension3 format has 16 bit IPID field ,hence  we can
> send  full IPID
>   through  Ext3 ,there is no reason why we should compress that IPID as
> we will achieve
>   nothing .
>    Please reply soon .
>    Thanking you & With Regards,
>    Manoranjan Sahu
> 
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended
> recipient, you should not disseminate, distribute or copy this e-mail.
> Please notify the sender immediately and destroy
> all copies of this message and any attachments contained in it.
> 
> 


From nikhil@erg.abdn.ac.uk  Wed Jun 17 13:57:24 2009
Return-Path: <nikhil@erg.abdn.ac.uk>
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 0EFF73A6C84 for <rohc@core3.amsl.com>; Wed, 17 Jun 2009 13:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level: 
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_05=-1.11, HTML_MESSAGE=0.001]
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 OyxCX7xzwLaZ for <rohc@core3.amsl.com>; Wed, 17 Jun 2009 13:57:23 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 0E4673A6808 for <rohc@ietf.org>; Wed, 17 Jun 2009 13:57:22 -0700 (PDT)
Received: from nikhillaptop (nikhil.erg.abdn.ac.uk [139.133.204.171]) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n5HKvTwp029588 for <rohc@ietf.org>; Wed, 17 Jun 2009 21:57:29 +0100 (BST)
From: "Nikhil Ninan" <nikhil@erg.abdn.ac.uk>
To: <rohc@ietf.org>
Date: Wed, 17 Jun 2009 21:57:18 +0100
Message-ID: <001b01c9ef8e$36c42af0$a44c80d0$@abdn.ac.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C9EF96.988892F0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnvjjOX1G1GQ26kQn+1qxvvIcoBGw==
Content-Language: en-gb
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: nikhil@erg.abdn.ac.uk
Subject: [rohc] rohc implementation
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: Wed, 17 Jun 2009 20:57:24 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01C9EF96.988892F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all,

                 I have just got into the field of header compression. I
wanted some info on RoHC freeware implementation available at the moment
that can be used for non profit research and also white papers/tutorials
that can help getting my head around RoHC.

Cheers

Nikhil


------=_NextPart_000_001C_01C9EF96.988892F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span lang=3DEN-GB>Hello all,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
lang=3DEN-GB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
I have just got into the field of header compression. I wanted some info =
on
RoHC freeware implementation available at the moment that can be used =
for non
profit research and also white papers/tutorials that can help getting my =
head
around RoHC.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>Cheers<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB>Nikhil<o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_001C_01C9EF96.988892F0--


From jiwoongl@qualcomm.com  Thu Jun 18 20:41:11 2009
Return-Path: <jiwoongl@qualcomm.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 4BD1F3A67CC for <rohc@core3.amsl.com>; Thu, 18 Jun 2009 20:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.489
X-Spam-Level: 
X-Spam-Status: No, score=-101.489 tagged_above=-999 required=5 tests=[AWL=1.109, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 2eM3xGDK4wlp for <rohc@core3.amsl.com>; Thu, 18 Jun 2009 20:41:06 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 992963A677C for <rohc@ietf.org>; Thu, 18 Jun 2009 20:41:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=jiwoongl@qualcomm.com; q=dns/txt; s=qcdkim; t=1245382879; x=1276918879; h=from:to:date:subject:thread-topic:thread-index: message-id:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Lee,=20Jiwoong"=20<jiwoongl@qualcomm.com>|To: =20"rohc@ietf.org"=20<rohc@ietf.org>|Date:=20Thu,=2018=20 Jun=202009=2020:41:17=20-0700|Subject:=20Comments=20on=20 RFC=204997|Thread-Topic:=20Comments=20on=20RFC=204997 |Thread-Index:=20Acnwj808uuYCoHxJRyiVHSvj1BZPVA=3D=3D |Message-ID:=20<29F0770B56D6A94794A647432F9A9EF0685CDB33D 5@NALASEXMB14.na.qualcomm.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20multipart/alternative=3B=0D=0A=09boundar y=3D"_000_29F0770B56D6A94794A647432F9A9EF0685CDB33D5NALAS EXMB14na_"|MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfe e=3Bi=3D"5300,2777,5650"=3B=20a=3D"19639429"; bh=u7VokF/TqoZqxqo7MmOW7NxjQdaOOfwRjVzeWoIu0EU=; b=pSrnYtxU1KO++yeUIBn9xUadRXdY0qHILDrWGLc0r3Te08hPeWSN8N9Y KzzwI78BYENqhfYkshieHHN3pIZQZ/S8abs4jWlNlXs6S+qGEjqCAEIqv 3jdOSvUNCqWnL3Ql3YAlRBAQDNtbhcGkSMc9Rw76vn+ICmwZAf2M1YQNI A=;
X-IronPort-AV: E=McAfee;i="5300,2777,5650"; a="19639429"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Jun 2009 20:41:19 -0700
Received: from msgtransport02.qualcomm.com (msgtransport02.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n5J3fJ4F006659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rohc@ietf.org>; Thu, 18 Jun 2009 20:41:19 -0700
Received: from nasanexhub06.na.qualcomm.com (nasanexhub06.na.qualcomm.com [129.46.134.254]) by msgtransport02.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n5J3fIP7015937 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rohc@ietf.org>; Thu, 18 Jun 2009 20:41:18 -0700
Received: from nalasexhub04.na.qualcomm.com (10.47.130.55) by nasanexhub06.na.qualcomm.com (129.46.134.254) with Microsoft SMTP Server (TLS) id 8.1.358.0; Thu, 18 Jun 2009 20:41:18 -0700
Received: from NALASEXMB14.na.qualcomm.com ([10.47.5.251]) by nalasexhub04.na.qualcomm.com ([10.47.130.55]) with mapi; Thu, 18 Jun 2009 20:41:18 -0700
From: "Lee, Jiwoong" <jiwoongl@qualcomm.com>
To: "rohc@ietf.org" <rohc@ietf.org>
Date: Thu, 18 Jun 2009 20:41:17 -0700
Thread-Topic: Comments on RFC 4997
Thread-Index: Acnwj808uuYCoHxJRyiVHSvj1BZPVA==
Message-ID: <29F0770B56D6A94794A647432F9A9EF0685CDB33D5@NALASEXMB14.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_29F0770B56D6A94794A647432F9A9EF0685CDB33D5NALASEXMB14na_"
MIME-Version: 1.0
Subject: [rohc] Comments on RFC 4997
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, 19 Jun 2009 03:43:31 -0000

--_000_29F0770B56D6A94794A647432F9A9EF0685CDB33D5NALASEXMB14na_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear ROHC WG,

I hope this comment was not discussed before. At least my quick search did =
not find the related thread.

These are some questions and comments about RFC 4997.


1.       Definition of Single quotes



According to pp 26 of the same document,  a discriminator is defined
     discriminator     =3D:=3D   '01101';
as equivalent to
     discriminator     =3D:=3D   compressed_value(5, 13);

In pp 36 the last paragraph, COMPRESSED format3 was defined with
field_4 =3D:=3D '1010';            // set ULENGTH to zero

Here unless one do not impose different interpretation of the single
quotes for the /field/ and the /discriminator/, wouldn't it be better
to change this into the following?
field_4 =3D:=3D '1010';            // set ULENGTH to 4



2.       Possible error in the Worked Example



I suspected in Appendix B.7 pp. 56 "COMPRESSED flags_set" format,

abc_flag_bits =3D:=3D uncompressed_value(3, 7) [0];

shoud be corrected to

abc_flag_bits =3D:=3D irregular(3) [3];



Accordingly, subsequent examples till Appendix B.8 should be corrected.





3.       Encoding function naming issue.



To my impression, the ROHC documents are using the notion and the term "com=
pression" to mean both of compression and encoding, as if they are the same=
. I believe it is not.



To single out a case, the same document is defining encoding functions

"uncompressed_value( ., . )" and "compressed_value( ., .)"



These functions are indeed for inference functions. That is, it says "the f=
ield value can be computed by using other explicit field values".  Above na=
ming does not carry this descriptive understanding at all. I understand the=
 author's original idea of that naming - which is possibly derived from the=
 fact that the associated field is/is not defined in UNCOMPRESSED/COMPRESSE=
D format, or so, which is less crucial in catching the notion of "inference=
" encoding.





I will appreciate your inputs.

Many thanks,



Jwoong









--_000_29F0770B56D6A94794A647432F9A9EF0685CDB33D5NALASEXMB14na_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:229115931;
	mso-list-type:hybrid;
	mso-list-template-ids:-1908662984 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Dear ROHC WG,<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>I hope this comment was not discussed before. At least=
 my
quick search did not find the related thread.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>These are some questions and comments about RFC 4997.<=
o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Definition of Single quotes<o:p></o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>According to pp 26 of the same document, &nbsp;=
a
discriminator is defined<br>
&nbsp;&nbsp;&nbsp;&nbsp; discriminator&nbsp;&nbsp;&nbsp;&nbsp; =3D:=3D&nbsp=
;&nbsp;
'01101';<br>
as equivalent to<br>
&nbsp;&nbsp;&nbsp;&nbsp; discriminator&nbsp;&nbsp;&nbsp;&nbsp; =3D:=3D&nbsp=
;&nbsp;
compressed_value(5, 13);<br>
<br>
In pp 36 the last paragraph, COMPRESSED format3 was defined with<br>
field_4 =3D:=3D
'1010';&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /=
/
set ULENGTH to zero<br>
<br>
Here unless one do not impose different interpretation of the single<br>
quotes for the /field/ and the /discriminator/, wouldn&#8217;t it be better=
<br>
to change this into the following?<br>
field_4 =3D:=3D
'1010';&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /=
/
set ULENGTH to 4<o:p></o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Possible error in the Worked Example <o:p></o:p></p=
>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>I suspected in Appendix B.7 pp. 56 &#8220;COMPR=
ESSED
flags_set&#8221; format, <o:p></o:p></p>

<p class=3DMsoListParagraph>abc_flag_bits =3D:=3D uncompressed_value(3, 7) =
[0];<o:p></o:p></p>

<p class=3DMsoListParagraph>shoud be corrected to<o:p></o:p></p>

<p class=3DMsoListParagraph>abc_flag_bits =3D:=3D irregular(3) [3];<o:p></o=
:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>Accordingly, subsequent examples till Appendix =
B.8
should be corrected.<o:p></o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Encoding function naming issue.<o:p></o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>To my impression, the ROHC documents are using =
the
notion and the term &#8220;compression&#8221; to mean both of compression a=
nd
encoding, as if they are the same. I believe it is not.<o:p></o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>To single out a case, the same document is defi=
ning
encoding functions <o:p></o:p></p>

<p class=3DMsoListParagraph>&#8220;uncompressed_value( ., . )&#8221; and &#=
8220;compressed_value(
., .)&#8221;<o:p></o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>These functions are indeed for inference functi=
ons. That
is, it says &#8220;the field value can be computed by using other explicit
field values&#8221;. &nbsp;Above naming does not carry this descriptive
understanding at all. I understand the author&#8217;s original idea of that
naming &#8211; which is possibly derived from the fact that the associated
field is/is not defined in UNCOMPRESSED/COMPRESSED format, or so, which is =
less
crucial in catching the notion of &#8220;inference&#8221; encoding.<o:p></o=
:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>&nbsp;<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'>I will appreciate you=
r
inputs. <o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'>Many thanks,<o:p></o:=
p></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'>Jwoong<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph><o:p>&nbsp;</o:p></p>

<p class=3DMsoListParagraph>&nbsp;<o:p></o:p></p>

</div>

</body>

</html>

--_000_29F0770B56D6A94794A647432F9A9EF0685CDB33D5NALASEXMB14na_--

From klaus.warnke@acticom.de  Fri Jun 19 02:20:27 2009
Return-Path: <klaus.warnke@acticom.de>
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 171193A69E1 for <rohc@core3.amsl.com>; Fri, 19 Jun 2009 02:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 WJ-MX+tkSgXS for <rohc@core3.amsl.com>; Fri, 19 Jun 2009 02:20:25 -0700 (PDT)
Received: from mail.acticom-networks.com (mail.acticom-networks.com [87.106.254.214]) by core3.amsl.com (Postfix) with ESMTP id 9FE973A6A10 for <rohc@ietf.org>; Fri, 19 Jun 2009 02:20:25 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.acticom-networks.com (Postfix) with ESMTP id 158F51C00435; Fri, 19 Jun 2009 11:20:37 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at acticom-networks.com
Received: from mail.acticom-networks.com ([127.0.0.1]) by localhost (mail.acticom-networks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Osw9RMbunx3Q; Fri, 19 Jun 2009 11:20:30 +0200 (CEST)
Received: from godfather.bln.acticom.de (mail.oosoft.net [212.99.204.33]) by mail.acticom-networks.com (Postfix) with ESMTP id 3A6011C0042E; Fri, 19 Jun 2009 11:20:30 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by godfather.bln.acticom.de (Postfix) with ESMTP id AC574F3ADA; Fri, 19 Jun 2009 11:20:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at bln.acticom.de
Received: from godfather.bln.acticom.de ([127.0.0.1]) by localhost (godfather.bln.acticom.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cn6IWtQ4awDL; Fri, 19 Jun 2009 11:20:27 +0200 (CEST)
Received: from [192.168.33.27] (tornado.bln.acticom.de [192.168.33.27]) by godfather.bln.acticom.de (Postfix) with ESMTP id 26610F3AD5; Fri, 19 Jun 2009 11:20:27 +0200 (CEST)
Message-ID: <4A3B585B.5000409@acticom.de>
Date: Fri, 19 Jun 2009 11:20:27 +0200
From: Klaus Warnke <klaus.warnke@acticom.de>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Lee, Jiwoong" <jiwoongl@qualcomm.com>
References: <29F0770B56D6A94794A647432F9A9EF0685CDB33D5@NALASEXMB14.na.qualcomm.com>
In-Reply-To: <29F0770B56D6A94794A647432F9A9EF0685CDB33D5@NALASEXMB14.na.qualcomm.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "rohc@ietf.org" <rohc@ietf.org>
Subject: Re: [rohc] Comments on RFC 4997
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, 19 Jun 2009 09:20:27 -0000

Hi Lee,

from my point of view the definitions are correct.

A compressed value is a value that exist in a compressed format only.

The discriminator is used to distinguish the packets to choose
the correct format for decompression. Therefore this field does
not appear in a uncompressed format.

 > field_4 =:= '1010'; // set ULENGTH to zero

If a compressed packet start with '1010' the COMPRESSED format3
could be used. But the field_4 does not appear in a UNCOMPRESSED
format, so the ULENGTH is zero.

 > abc_flag_bits =:= uncompressed_value(3, 7) [0];

eg_header
{
UNCOMPRESSED {
abc_flag_bits [ 3 ];
}

COMPRESSED flags_set {
abc_flag_bits =:= uncompressed_value(3, 7) [ 0 ];
}
}

To compress a eg_header into the flags_set format, the
abs_flag_bits field in the uncompressed eg_header with the length
3 must have the value 7. If not, the flags_set format can not be
used, an other format must (irregular, for example). But the
value 7 itself does not appear in the flags_set format itself,
therefore the CLENTH is zero. It is compressed away.

The '[3]' in the UNCOMPRESSED format says, that this field is in
this format three bits in length. You can see this also in every
COMPRESSED format definiton:

abc_flag_bits =:= irregular(3) [ 3 ];
abc_flag_bits =:= uncompressed_value(3, 7) [ 0 ];
abc_flag_bits =:= static [ 0 ];

In irregular the field is send as it is with 3bits. For
uncompressed_value see above. In static, the value in the
eg_header must be the same as saved in the context. To
decompressed such format, a value in the context must exist.

The fn defines a two way mapping between uncompressed and
compressed format. You can use the eg_header UNCOMPRESSED ->
COMPRESSED flags_set mapping, if all definitions could be
fulfilled. Maybe more than one works for compression.
And vice versa.

This is how I understand the fn.

br
Klaus Warnke

Lee, Jiwoong wrote:
>
> Dear ROHC WG,
>
> I hope this comment was not discussed before. At least my quick search 
> did not find the related thread.
>
> These are some questions and comments about RFC 4997.
>
> 1. Definition of Single quotes
>
> According to pp 26 of the same document, a discriminator is defined
> discriminator =:= '01101';
> as equivalent to
> discriminator =:= compressed_value(5, 13);
>
> In pp 36 the last paragraph, COMPRESSED format3 was defined with
> field_4 =:= '1010'; // set ULENGTH to zero
>
> Here unless one do not impose different interpretation of the single
> quotes for the /field/ and the /discriminator/, wouldn’t it be better
> to change this into the following?
> field_4 =:= '1010'; // set ULENGTH to 4
>
> 2. Possible error in the Worked Example
>
> I suspected in Appendix B.7 pp. 56 “COMPRESSED flags_set” format,
>
> abc_flag_bits =:= uncompressed_value(3, 7) [0];
>
> shoud be corrected to
>
> abc_flag_bits =:= irregular(3) [3];
>
> Accordingly, subsequent examples till Appendix B.8 should be corrected.
>
> 3. Encoding function naming issue.
>
> To my impression, the ROHC documents are using the notion and the term 
> “compression” to mean both of compression and encoding, as if they are 
> the same. I believe it is not.
>
> To single out a case, the same document is defining encoding functions
>
> “uncompressed_value( ., . )” and “compressed_value( ., .)”
>
> These functions are indeed for inference functions. That is, it says 
> “the field value can be computed by using other explicit field 
> values”. Above naming does not carry this descriptive understanding at 
> all. I understand the author’s original idea of that naming – which is 
> possibly derived from the fact that the associated field is/is not 
> defined in UNCOMPRESSED/COMPRESSED format, or so, which is less 
> crucial in catching the notion of “inference” encoding.
>
> I will appreciate your inputs.
>
> Many thanks,
>
> Jwoong
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc
>   


-- 
Klaus Warnke                klaus.warnke@acticom.de
http://www.acticom.de
Tel +49-30-4303.2510        Fax +49-30-4303.2519
* --------------------------------------------------------- *
acticom GmbH
Am Borsigturm 42, 13507 Berlin, Germany
Managing Directors:  Olaf Kehrer, Gerrit Schulte
Commercial Register: Berlin-Charlottenburg HRB 73245
VAT-ID DE205131766
* --------------------------------------------------------- *
This email and the information it contains may be
privileged and/or confidential. It is for the intended
addressee(s) only. The unauthorised use, disclosure or
copying of this email, or any information contained,
is prohibited. If you are not an intended recipient,
please notify the sender immediately and delete this email.


From raffles@gluft.com  Fri Jun 19 12:36:26 2009
Return-Path: <raffles@gluft.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 0C3D53A6C19 for <rohc@core3.amsl.com>; Fri, 19 Jun 2009 12:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 invmk4z4ks99 for <rohc@core3.amsl.com>; Fri, 19 Jun 2009 12:36:24 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by core3.amsl.com (Postfix) with ESMTP id 8C3003A6BD5 for <rohc@ietf.org>; Fri, 19 Jun 2009 12:36:24 -0700 (PDT)
Received: from [192.168.1.64] (93-97-78-217.zone5.bethere.co.uk [93.97.78.217]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0MKv1o-1MHjsy1iFh-000jGe; Fri, 19 Jun 2009 21:36:29 +0200
Message-ID: <4A3BE8CF.1020803@gluft.com>
Date: Fri, 19 Jun 2009 20:36:47 +0100
From: Raffles <raffles@gluft.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Klaus Warnke <klaus.warnke@acticom.de>
References: <29F0770B56D6A94794A647432F9A9EF0685CDB33D5@NALASEXMB14.na.qualcomm.com> <4A3B585B.5000409@acticom.de>
In-Reply-To: <4A3B585B.5000409@acticom.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V01U2FsdGVkX19gezbXxAnB92cjdWHNTtYMDPXvZbAs2Hj9461 H1Nv+63ee7h4DSi0xOOgWoENqG/mv9rUMFbPiD1JYyrhguHdGU JOAy6ODVdJhgwVyRl1ufDcf+qos/JFC
Cc: "rohc@ietf.org" <rohc@ietf.org>, "Lee, Jiwoong" <jiwoongl@qualcomm.com>
Subject: Re: [rohc] Comments on RFC 4997
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, 19 Jun 2009 19:36:26 -0000

Hi Klaus, Lee, All,

Thanks Klaus for replying to this. All your answers are correct as far 
as I can see. Thank you for taking the time to respond.

Lee, does this explain things for you?  It seems to me that you have 
perhaps got confused between  ULENGTH and CLENGTH. Feel free to ask 
further questions if you still have doubts.

Regards

Raffles (RFC 4997 Editor)

Klaus Warnke wrote:
> Hi Lee,
>
> from my point of view the definitions are correct.
>
> A compressed value is a value that exist in a compressed format only.
>
> The discriminator is used to distinguish the packets to choose
> the correct format for decompression. Therefore this field does
> not appear in a uncompressed format.
>
> > field_4 =:= '1010'; // set ULENGTH to zero
>
> If a compressed packet start with '1010' the COMPRESSED format3
> could be used. But the field_4 does not appear in a UNCOMPRESSED
> format, so the ULENGTH is zero.
>
> > abc_flag_bits =:= uncompressed_value(3, 7) [0];
>
> eg_header
> {
> UNCOMPRESSED {
> abc_flag_bits [ 3 ];
> }
>
> COMPRESSED flags_set {
> abc_flag_bits =:= uncompressed_value(3, 7) [ 0 ];
> }
> }
>
> To compress a eg_header into the flags_set format, the
> abs_flag_bits field in the uncompressed eg_header with the length
> 3 must have the value 7. If not, the flags_set format can not be
> used, an other format must (irregular, for example). But the
> value 7 itself does not appear in the flags_set format itself,
> therefore the CLENTH is zero. It is compressed away.
>
> The '[3]' in the UNCOMPRESSED format says, that this field is in
> this format three bits in length. You can see this also in every
> COMPRESSED format definiton:
>
> abc_flag_bits =:= irregular(3) [ 3 ];
> abc_flag_bits =:= uncompressed_value(3, 7) [ 0 ];
> abc_flag_bits =:= static [ 0 ];
>
> In irregular the field is send as it is with 3bits. For
> uncompressed_value see above. In static, the value in the
> eg_header must be the same as saved in the context. To
> decompressed such format, a value in the context must exist.
>
> The fn defines a two way mapping between uncompressed and
> compressed format. You can use the eg_header UNCOMPRESSED ->
> COMPRESSED flags_set mapping, if all definitions could be
> fulfilled. Maybe more than one works for compression.
> And vice versa.
>
> This is how I understand the fn.
>
> br
> Klaus Warnke
>
> Lee, Jiwoong wrote:
>>
>> Dear ROHC WG,
>>
>> I hope this comment was not discussed before. At least my quick 
>> search did not find the related thread.
>>
>> These are some questions and comments about RFC 4997.
>>
>> 1. Definition of Single quotes
>>
>> According to pp 26 of the same document, a discriminator is defined
>> discriminator =:= '01101';
>> as equivalent to
>> discriminator =:= compressed_value(5, 13);
>>
>> In pp 36 the last paragraph, COMPRESSED format3 was defined with
>> field_4 =:= '1010'; // set ULENGTH to zero
>>
>> Here unless one do not impose different interpretation of the single
>> quotes for the /field/ and the /discriminator/, wouldn’t it be better
>> to change this into the following?
>> field_4 =:= '1010'; // set ULENGTH to 4
>>
>> 2. Possible error in the Worked Example
>>
>> I suspected in Appendix B.7 pp. 56 “COMPRESSED flags_set” format,
>>
>> abc_flag_bits =:= uncompressed_value(3, 7) [0];
>>
>> shoud be corrected to
>>
>> abc_flag_bits =:= irregular(3) [3];
>>
>> Accordingly, subsequent examples till Appendix B.8 should be corrected.
>>
>> 3. Encoding function naming issue.
>>
>> To my impression, the ROHC documents are using the notion and the 
>> term “compression” to mean both of compression and encoding, as if 
>> they are the same. I believe it is not.
>>
>> To single out a case, the same document is defining encoding functions
>>
>> “uncompressed_value( ., . )” and “compressed_value( ., .)”
>>
>> These functions are indeed for inference functions. That is, it says 
>> “the field value can be computed by using other explicit field 
>> values”. Above naming does not carry this descriptive understanding 
>> at all. I understand the author’s original idea of that naming – 
>> which is possibly derived from the fact that the associated field 
>> is/is not defined in UNCOMPRESSED/COMPRESSED format, or so, which is 
>> less crucial in catching the notion of “inference” encoding.
>>
>> I will appreciate your inputs.
>>
>> Many thanks,
>>
>> Jwoong
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Rohc mailing list
>> Rohc@ietf.org
>> https://www.ietf.org/mailman/listinfo/rohc
>>   
>
>

-- 
Raffles (Robert Finking)
m: 0789 463 9887
e: raffles@gluft.com
w: gluft.com

         O                  O
 OOOOOO  O  O    O OOOOOO OOOOO
 O    O  O  O    O OOOOO    O
 OOOOOO  O  OOOOOO O        O
 OOOOOO
      we  care  about  software

-----------------------------------------------------------------
Gluft Ltd. Registered No.: 6795336
The information contained in this e-mail and any attachments is
proprietary to Gluft Ltd and must not be passed to any third
party without permission. This communication is for information
only and shall not create or change any contractual relationship.
Please consider the environment before printing this email.
-----------------------------------------------------------------


From jiwoongl@qualcomm.com  Fri Jun 19 15:21:02 2009
Return-Path: <jiwoongl@qualcomm.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 7F3123A6A59 for <rohc@core3.amsl.com>; Fri, 19 Jun 2009 15:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.229
X-Spam-Level: 
X-Spam-Status: No, score=-104.229 tagged_above=-999 required=5 tests=[AWL=2.370, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 NemHWTf4TEEv for <rohc@core3.amsl.com>; Fri, 19 Jun 2009 15:21:01 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 3158C3A6C34 for <rohc@ietf.org>; Fri, 19 Jun 2009 15:21:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=jiwoongl@qualcomm.com; q=dns/txt; s=qcdkim; t=1245450075; x=1276986075; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Lee,=20Jiwoong"=20<jiwoongl@qualcomm.com>|To: =20Raffles=20<raffles@gluft.com>,=20Klaus=20Warnke=20<kla us.warnke@acticom.de>|CC:=20"rohc@ietf.org"=20<rohc@ietf. org>|Date:=20Fri,=2019=20Jun=202009=2015:21:13=20-0700 |Subject:=20RE:=20[rohc]=20Comments=20on=20RFC=204997 |Thread-Topic:=20[rohc]=20Comments=20on=20RFC=204997 |Thread-Index:=20AcnxFUWBQ3eJ6ndnTSiup9iDRAlfHwAFpEkg |Message-ID:=20<29F0770B56D6A94794A647432F9A9EF0685CDB341 A@NALASEXMB14.na.qualcomm.com>|References:=20<29F0770B56D 6A94794A647432F9A9EF0685CDB33D5@NALASEXMB14.na.qualcomm.c om>=0D=0A=20<4A3B585B.5000409@acticom.de>=20<4A3BE8CF.102 0803@gluft.com>|In-Reply-To:=20<4A3BE8CF.1020803@gluft.co m>|Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5651"=3B=20a=3D"19655166"; bh=yDMW+o8lTTk90vfeRqzhgzSGRKx2oKa5PjJwsmXOL78=; b=DAOnLuXUvskLbeP5clAtDbHB+XzOeqjbgDbvqGkL7NxHclNpM5H0weuv 9BasP5gV/nyH0Z1bLEhUI1O7R6v2sGkabXzKnvBg6IUeQcwArI1tQCYXq Bka322m6FIqsE9+GuiNmf7ARdecD5TByYGXBqAWFNQg1U8V+ZzdM3uI2O E=;
X-IronPort-AV: E=McAfee;i="5300,2777,5651"; a="19655166"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jun 2009 15:21:14 -0700
Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com [129.46.61.156]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n5JMLEF7028476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Jun 2009 15:21:14 -0700
Received: from nasanexhub02.na.qualcomm.com (nasanexhub02.na.qualcomm.com [10.46.143.120]) by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n5JMLD0t028781 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 19 Jun 2009 15:21:13 -0700
Received: from nalasexhub04.na.qualcomm.com (10.47.130.55) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.1.358.0; Fri, 19 Jun 2009 15:21:13 -0700
Received: from NALASEXMB14.na.qualcomm.com ([10.47.5.251]) by nalasexhub04.na.qualcomm.com ([10.47.130.55]) with mapi; Fri, 19 Jun 2009 15:21:13 -0700
From: "Lee, Jiwoong" <jiwoongl@qualcomm.com>
To: Raffles <raffles@gluft.com>, Klaus Warnke <klaus.warnke@acticom.de>
Date: Fri, 19 Jun 2009 15:21:13 -0700
Thread-Topic: [rohc] Comments on RFC 4997
Thread-Index: AcnxFUWBQ3eJ6ndnTSiup9iDRAlfHwAFpEkg
Message-ID: <29F0770B56D6A94794A647432F9A9EF0685CDB341A@NALASEXMB14.na.qualcomm.com>
References: <29F0770B56D6A94794A647432F9A9EF0685CDB33D5@NALASEXMB14.na.qualcomm.com> <4A3B585B.5000409@acticom.de> <4A3BE8CF.1020803@gluft.com>
In-Reply-To: <4A3BE8CF.1020803@gluft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rohc@ietf.org" <rohc@ietf.org>
Subject: Re: [rohc] Comments on RFC 4997
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, 19 Jun 2009 22:21:02 -0000

Dear all,

Indeed, that was the case. Thank you for the clarification, Klaus.

Regards,
Jiwoong


-----Original Message-----
From: Raffles [mailto:raffles@gluft.com]=20
Sent: Friday, June 19, 2009 12:37 PM
To: Klaus Warnke
Cc: Lee, Jiwoong; rohc@ietf.org
Subject: Re: [rohc] Comments on RFC 4997

Hi Klaus, Lee, All,

Thanks Klaus for replying to this. All your answers are correct as far=20
as I can see. Thank you for taking the time to respond.

Lee, does this explain things for you?  It seems to me that you have=20
perhaps got confused between  ULENGTH and CLENGTH. Feel free to ask=20
further questions if you still have doubts.

Regards

Raffles (RFC 4997 Editor)

Klaus Warnke wrote:
> Hi Lee,
>
> from my point of view the definitions are correct.
>
> A compressed value is a value that exist in a compressed format only.
>
> The discriminator is used to distinguish the packets to choose
> the correct format for decompression. Therefore this field does
> not appear in a uncompressed format.
>
> > field_4 =3D:=3D '1010'; // set ULENGTH to zero
>
> If a compressed packet start with '1010' the COMPRESSED format3
> could be used. But the field_4 does not appear in a UNCOMPRESSED
> format, so the ULENGTH is zero.
>
> > abc_flag_bits =3D:=3D uncompressed_value(3, 7) [0];
>
> eg_header
> {
> UNCOMPRESSED {
> abc_flag_bits [ 3 ];
> }
>
> COMPRESSED flags_set {
> abc_flag_bits =3D:=3D uncompressed_value(3, 7) [ 0 ];
> }
> }
>
> To compress a eg_header into the flags_set format, the
> abs_flag_bits field in the uncompressed eg_header with the length
> 3 must have the value 7. If not, the flags_set format can not be
> used, an other format must (irregular, for example). But the
> value 7 itself does not appear in the flags_set format itself,
> therefore the CLENTH is zero. It is compressed away.
>
> The '[3]' in the UNCOMPRESSED format says, that this field is in
> this format three bits in length. You can see this also in every
> COMPRESSED format definiton:
>
> abc_flag_bits =3D:=3D irregular(3) [ 3 ];
> abc_flag_bits =3D:=3D uncompressed_value(3, 7) [ 0 ];
> abc_flag_bits =3D:=3D static [ 0 ];
>
> In irregular the field is send as it is with 3bits. For
> uncompressed_value see above. In static, the value in the
> eg_header must be the same as saved in the context. To
> decompressed such format, a value in the context must exist.
>
> The fn defines a two way mapping between uncompressed and
> compressed format. You can use the eg_header UNCOMPRESSED ->
> COMPRESSED flags_set mapping, if all definitions could be
> fulfilled. Maybe more than one works for compression.
> And vice versa.
>
> This is how I understand the fn.
>
> br
> Klaus Warnke
>
> Lee, Jiwoong wrote:
>>
>> Dear ROHC WG,
>>
>> I hope this comment was not discussed before. At least my quick=20
>> search did not find the related thread.
>>
>> These are some questions and comments about RFC 4997.
>>
>> 1. Definition of Single quotes
>>
>> According to pp 26 of the same document, a discriminator is defined
>> discriminator =3D:=3D '01101';
>> as equivalent to
>> discriminator =3D:=3D compressed_value(5, 13);
>>
>> In pp 36 the last paragraph, COMPRESSED format3 was defined with
>> field_4 =3D:=3D '1010'; // set ULENGTH to zero
>>
>> Here unless one do not impose different interpretation of the single
>> quotes for the /field/ and the /discriminator/, wouldn't it be better
>> to change this into the following?
>> field_4 =3D:=3D '1010'; // set ULENGTH to 4
>>
>> 2. Possible error in the Worked Example
>>
>> I suspected in Appendix B.7 pp. 56 "COMPRESSED flags_set" format,
>>
>> abc_flag_bits =3D:=3D uncompressed_value(3, 7) [0];
>>
>> shoud be corrected to
>>
>> abc_flag_bits =3D:=3D irregular(3) [3];
>>
>> Accordingly, subsequent examples till Appendix B.8 should be corrected.
>>
>> 3. Encoding function naming issue.
>>
>> To my impression, the ROHC documents are using the notion and the=20
>> term "compression" to mean both of compression and encoding, as if=20
>> they are the same. I believe it is not.
>>
>> To single out a case, the same document is defining encoding functions
>>
>> "uncompressed_value( ., . )" and "compressed_value( ., .)"
>>
>> These functions are indeed for inference functions. That is, it says=20
>> "the field value can be computed by using other explicit field=20
>> values". Above naming does not carry this descriptive understanding=20
>> at all. I understand the author's original idea of that naming -=20
>> which is possibly derived from the fact that the associated field=20
>> is/is not defined in UNCOMPRESSED/COMPRESSED format, or so, which is=20
>> less crucial in catching the notion of "inference" encoding.
>>
>> I will appreciate your inputs.
>>
>> Many thanks,
>>
>> Jwoong
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Rohc mailing list
>> Rohc@ietf.org
>> https://www.ietf.org/mailman/listinfo/rohc
>>  =20
>
>

--=20
Raffles (Robert Finking)
m: 0789 463 9887
e: raffles@gluft.com
w: gluft.com

         O                  O
 OOOOOO  O  O    O OOOOOO OOOOO
 O    O  O  O    O OOOOO    O
 OOOOOO  O  OOOOOO O        O
 OOOOOO
      we  care  about  software

-----------------------------------------------------------------
Gluft Ltd. Registered No.: 6795336
The information contained in this e-mail and any attachments is
proprietary to Gluft Ltd and must not be passed to any third
party without permission. This communication is for information
only and shall not create or change any contractual relationship.
Please consider the environment before printing this email.
-----------------------------------------------------------------


From Karthik.Balaguru@lntinfotech.com  Thu Jun 25 05:54:42 2009
Return-Path: <Karthik.Balaguru@lntinfotech.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 E67DD3A6B04 for <rohc@core3.amsl.com>; Thu, 25 Jun 2009 05:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.489
X-Spam-Level: 
X-Spam-Status: No, score=-5.489 tagged_above=-999 required=5 tests=[AWL=1.110,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 pQxN7hS5mmi6 for <rohc@core3.amsl.com>; Thu, 25 Jun 2009 05:54:42 -0700 (PDT)
Received: from mail96.messagelabs.com (mail96.messagelabs.com [216.82.254.19]) by core3.amsl.com (Postfix) with SMTP id 1A34B3A6D92 for <rohc@ietf.org>; Thu, 25 Jun 2009 05:53:44 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Karthik.Balaguru@lntinfotech.com
X-Msg-Ref: server-13.tower-96.messagelabs.com!1245934302!39142218!1
X-StarScan-Version: 6.0.0; banners=lntinfotech.com,-,-
X-Originating-IP: [203.101.96.4]
Received: (qmail 25542 invoked from network); 25 Jun 2009 12:51:43 -0000
Received: from bangaloresmtp.lntinfotech.com (HELO bangaloresmtp.lntinfotech.com) (203.101.96.4) by server-13.tower-96.messagelabs.com with SMTP; 25 Jun 2009 12:51:43 -0000
Received: from Bangalore.lntinfotech.com ([172.28.0.3]) by bangaloresmtp.lntinfotech.com (Lotus Domino Release 7.0.3) with ESMTP id 2009062518233028-98701 ; Thu, 25 Jun 2009 18:23:30 +0530 
To: rohc@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF4774DF8E.E95CB052-ON652575E0.0033DFE9-652575E0.0046A641@lntinfotech.com>
From: Karthik Balaguru <Karthik.Balaguru@lntinfotech.com>
Date: Thu, 25 Jun 2009 18:21:40 +0530
X-MIMETrack: Serialize by Router on BANGALORE/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/25/2009 06:21:41 PM, Serialize complete at 06/25/2009 06:21:41 PM, Itemize by SMTP Server on BangaloreSMTP/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/25/2009 06:23:30 PM, Serialize by Router on BangaloreSMTP/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/25/2009 06:23:31 PM, Serialize complete at 06/25/2009 06:23:31 PM
Content-Type: multipart/alternative; boundary="=_alternative 0046A632652575E0_="
Subject: [rohc] Support of ROHC Piggyback Feedback in LTE
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: Thu, 25 Jun 2009 12:54:43 -0000

This is a multipart message in MIME format.
--=_alternative 0046A632652575E0_=
Content-Type: text/plain; charset="US-ASCII"

Hi,

Need clarifications on ROHC Piggyback feedback support in LTE.

LTE standrad states that PDCP Control Packet (Feedback) shall not be 
ciphered (Reference - 3GPP TS 36.323 V8.5.0, Section 5.5.4 ) and PDCP data 

packets shall be ciphered by configured algorithm (Reference - Section 
5.2.1, 5.2.2 ) . 
In case of Piggyback feedback packet, DataPacket will be attatched at the 
end of feedback packet.  (RFC 3095 - Page no 43,44 & Section 5.2.2)
1. In LTE PDCP, If the Data Packet should be ciphered for these piggyback 
packets , then how will the Peer entity generate COUNT input for ciphering 
algorithm as PDCP-SN is not available ?
2. In LTE PDCP, Can the data Packet be sent without ciphering in Piggyback 
Feedback packets ?

Further reference w.r.t RFC 3095 - Page no 44
d) To allow piggybacking, 5), it is possible to deduce the length of 
feedback information by examining the first few octets of the
    feedback.  This allows the decompressor to pass piggybacked feedback 
information to the associated same-side compressor
    without understanding its format.  The length information decouples 
the decompressor from the compressor in the sense that
    the decompressor can process the compressed header immediately without 
waiting for the compressor to hand it back after parsing
    the feedback information.

Kindly clarify regarding the support of RoHC piggyback Feedback in LTE ?

Thx in advans,
Karthik Balaguru

______________________________________________________________________
--=_alternative 0046A632652575E0_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="Trebuchet MS">Hi,</font>
<br>
<br><font size=2 face="Trebuchet MS">Need clarifications on ROHC Piggyback
feedback support in LTE.</font>
<br>
<br><font size=2 face="Trebuchet MS">LTE standrad states that PDCP Control
Packet (Feedback) shall not be ciphered (Reference - 3GPP TS 36.323 V8.5.0,
Section 5.5.4 ) and PDCP data </font>
<br><font size=2 face="Trebuchet MS">packets shall be ciphered by configured
algorithm (Reference - Section 5.2.1, 5.2.2 ) . </font>
<br><font size=2 face="Trebuchet MS">In case of Piggyback feedback packet,
DataPacket will be attatched at the end of feedback packet. &nbsp;(RFC
3095 - Page no 43,44 &amp; Section 5.2.2)</font>
<br><font size=2 face="Trebuchet MS">1. In LTE PDCP, If the Data Packet
should be ciphered for these piggyback packets , then how will the Peer
entity generate COUNT input for ciphering algorithm as PDCP-SN is not available
?</font>
<br><font size=2 face="Trebuchet MS">2. In LTE PDCP, Can the data Packet
be sent without ciphering in Piggyback Feedback packets ?</font>
<br>
<br><font size=2 face="Trebuchet MS">Further reference w.r.t RFC 3095 -
Page no 44</font>
<br><font size=2 face="Trebuchet MS">d) To allow piggybacking, 5), it is
possible to deduce the length of feedback information by examining the
first few octets of the</font>
<br><font size=2 face="Trebuchet MS">&nbsp; &nbsp; feedback. &nbsp;This
allows the decompressor to pass piggybacked feedback information to the
associated same-side compressor</font>
<br><font size=2 face="Trebuchet MS">&nbsp; &nbsp; without understanding
its format. &nbsp;The length information decouples the decompressor from
the compressor in the sense that</font>
<br><font size=2 face="Trebuchet MS">&nbsp; &nbsp; the decompressor can
process the compressed header immediately without waiting for the compressor
to hand it back after parsing</font>
<br><font size=2 face="Trebuchet MS">&nbsp; &nbsp; the feedback information.</font>
<br>
<br><font size=2 face="Trebuchet MS">Kindly clarify regarding the support
of RoHC piggyback Feedback in LTE ?</font>
<br>
<br><font size=2 face="Trebuchet MS">Thx in advans,</font>
<br><font size=2 face="Trebuchet MS">Karthik Balaguru</font>

<BR>
______________________________________________________________________<BR>

--=_alternative 0046A632652575E0_=--

From lei.zhu@huawei.com  Thu Jun 25 07:32:12 2009
Return-Path: <lei.zhu@huawei.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 3DEED3A68DC for <rohc@core3.amsl.com>; Thu, 25 Jun 2009 07:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.802
X-Spam-Level: 
X-Spam-Status: No, score=-0.802 tagged_above=-999 required=5 tests=[AWL=0.308,  BAYES_05=-1.11]
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 0-f1o3Ns7RRB for <rohc@core3.amsl.com>; Thu, 25 Jun 2009 07:32:11 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 547253A682B for <rohc@ietf.org>; Thu, 25 Jun 2009 07:32:11 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLS00BU7TL11N@szxga03-in.huawei.com> for rohc@ietf.org; Thu, 25 Jun 2009 22:29:25 +0800 (CST)
Received: from huawei.com ([172.17.1.31]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLS00BKBTL1CO@szxga03-in.huawei.com> for rohc@ietf.org; Thu, 25 Jun 2009 22:29:25 +0800 (CST)
Received: from [172.24.1.6] (Forwarded-For: [208.71.39.153]) by szxmc03-in.huawei.com (mshttpd); Thu, 25 Jun 2009 22:29:25 +0800
Date: Thu, 25 Jun 2009 22:29:25 +0800
From: zhulei 41317 <lei.zhu@huawei.com>
To: rohc@ietf.org
Message-id: <fdcff22318f6.18f6fdcff223@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
X-Mailman-Approved-At: Thu, 25 Jun 2009 23:46:29 -0700
Cc: lei.zhu@huawei.com
Subject: [rohc] New draft posted to Rohc
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: Thu, 25 Jun 2009 14:32:12 -0000

Hi Rohc folks:

To summarise extensions to SIP signalling for signalling compressing dictionary, an initial I-D was posted to IETF. I supposed some of you have already gotten the content of this new I-D from link below.

http://tools.ietf.org/html/draft-lei-rohc-sigcomp-static-dictionary-00

I supposed some time in Stockholm meeting could be used to present or discuss it online. Therefore, please take a look on this draft and comment it. Thank you!

Best regards,
Lei Zhu

 

******************************************************************************************
 This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained here in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email
 immediately and delete it!
 *****************************************************************************************

From oferg@radvision.com  Fri Jun 26 01:11:10 2009
Return-Path: <oferg@radvision.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 ECD213A68EE for <rohc@core3.amsl.com>; Fri, 26 Jun 2009 01:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 dDipgbmiHh0C for <rohc@core3.amsl.com>; Fri, 26 Jun 2009 01:11:09 -0700 (PDT)
Received: from eframer.radvision.com (rvil-eframer.RADVISION.com [80.74.106.104]) by core3.amsl.com (Postfix) with ESMTP id 7D73D3A6849 for <rohc@ietf.org>; Fri, 26 Jun 2009 01:11:09 -0700 (PDT)
Received: (from root@localhost) by eframer.radvision.com (8.13.4/8.12.9) id n5Q8K6YC023276 for rohc@ietf.org; Fri, 26 Jun 2009 11:20:06 +0300
Received: from rvil-mail1.RADVISION.com (rvil-mail1.radvision.com [172.20.2.100]) by eframer.radvision.com (8.13.4/8.12.9) with ESMTP id n5Q8JWCs023262;  Fri, 26 Jun 2009 11:19:32 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9F635.6EDF2725"
Date: Fri, 26 Jun 2009 11:07:36 +0300
Message-ID: <FE127977CE269045BBA7EC732F399FD93D526A@rvil-mail1.RADVISION.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] New draft posted to Rohc
thread-index: Acn2KeRH6MVNWXHMQ/u5Y62z0ktsUQAC0ZYN
References: <fdcff22318f6.18f6fdcff223@huawei.com>
From: "Ofer Goren" <oferg@radvision.com>
To: "zhulei 41317" <lei.zhu@huawei.com>, <rohc@ietf.org>
Subject: Re: [rohc] New draft posted to Rohc
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, 26 Jun 2009 08:11:11 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9F635.6EDF2725
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Lei.
=20
You referred to the IMS additions as well, but IMS p-headers were not =
included in this new dictionary. Is there a plan to add them as well?
=20
Ofer

________________________________

From: rohc-bounces@ietf.org on behalf of zhulei 41317
Sent: Thu 6/25/2009 17:29
To: rohc@ietf.org
Cc: lei.zhu@huawei.com
Subject: [rohc] New draft posted to Rohc



Hi Rohc folks:

To summarise extensions to SIP signalling for signalling compressing =
dictionary, an initial I-D was posted to IETF. I supposed some of you =
have already gotten the content of this new I-D from link below.

http://tools.ietf.org/html/draft-lei-rohc-sigcomp-static-dictionary-00

I supposed some time in Stockholm meeting could be used to present or =
discuss it online. Therefore, please take a look on this draft and =
comment it. Thank you!

Best regards,
Lei Zhu



*************************************************************************=
*****************
 This email and its attachments contain confidential information from =
HUAWEI, which is intended only for the person or entity whose address is =
listed above. Any use of the information contained here in any way =
(including, but not limited to, total or partial disclosure, =
reproduction, or dissemination) by persons other than the intended =
recipient(s) is prohibited. If you receive this email in error, please =
notify the sender by phone or email
 immediately and delete it!
 =
*************************************************************************=
****************
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www.ietf.org/mailman/listinfo/rohc



------_=_NextPart_001_01C9F635.6EDF2725
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>[rohc] New draft posted to Rohc</TITLE>=0A=
<META content=3D"text/html; charset=3Dunicode" http-equiv=3DContent-Type>=0A=
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr id=3DidOWAReplyText77162>=0A=
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3DArial>Hi =
Lei.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>You referred to the IMS =
additions as well, but IMS&nbsp;p-headers were not included in this new =
dictionary. Is there a plan to add them as well?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2 face=3DArial>Ofer</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT size=3D2 face=3DTahoma><B>From:</B> rohc-bounces@ietf.org on =
behalf of zhulei 41317<BR><B>Sent:</B> Thu 6/25/2009 17:29<BR><B>To:</B> =
rohc@ietf.org<BR><B>Cc:</B> lei.zhu@huawei.com<BR><B>Subject:</B> [rohc] =
New draft posted to Rohc<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi Rohc folks:<BR><BR>To summarise extensions to SIP =
signalling for signalling compressing dictionary, an initial I-D was =
posted to IETF. I supposed some of you have already gotten the content =
of this new I-D from link below.<BR><BR><A =
href=3D"http://tools.ietf.org/html/draft-lei-rohc-sigcomp-static-dictiona=
ry-00">http://tools.ietf.org/html/draft-lei-rohc-sigcomp-static-dictionar=
y-00</A><BR><BR>I supposed some time in Stockholm meeting could be used =
to present or discuss it online. Therefore, please take a look on this =
draft and comment it. Thank you!<BR><BR>Best regards,<BR>Lei =
Zhu<BR><BR><BR><BR>******************************************************=
************************************<BR>&nbsp;This email and its =
attachments contain confidential information from HUAWEI, which is =
intended only for the person or entity whose address is listed above. =
Any use of the information contained here in any way (including, but not =
limited to, total or partial disclosure, reproduction, or dissemination) =
by persons other than the intended recipient(s) is prohibited. If you =
receive this email in error, please notify the sender by phone or =
email<BR>&nbsp;immediately and delete =
it!<BR>&nbsp;************************************************************=
*****************************<BR>________________________________________=
_______<BR>Rohc mailing list<BR>Rohc@ietf.org<BR><A =
href=3D"https://www.ietf.org/mailman/listinfo/rohc">https://www.ietf.org/=
mailman/listinfo/rohc</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C9F635.6EDF2725--

From pelle@cdt.luth.se  Fri Jun 26 11:52:18 2009
Return-Path: <pelle@cdt.luth.se>
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 32FCA3A6989 for <rohc@core3.amsl.com>; Fri, 26 Jun 2009 11:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 Um1R-WiMclw5 for <rohc@core3.amsl.com>; Fri, 26 Jun 2009 11:52:17 -0700 (PDT)
Received: from mxi.ltu.se (mxi.ltu.se [130.240.42.23]) by core3.amsl.com (Postfix) with ESMTP id 4A7233A67AA for <rohc@ietf.org>; Fri, 26 Jun 2009 11:52:06 -0700 (PDT)
Received: from sm.luth.se (lisa.sm.luth.se [130.240.3.1]) by mxi.ltu.se (8.13.1/8.13.1) with ESMTP id n5QITZJx023134; Fri, 26 Jun 2009 20:29:35 +0200
Received: from localhost (localhost [127.0.0.1]) by sm.luth.se (8.13.8/8.13.8) with ESMTP id n5QITH7U019420; Fri, 26 Jun 2009 20:29:35 +0200 (MEST)
Received: from bas10-montrealak-1128582994.dsl.bell.ca (bas10-montrealak-1128582994.dsl.bell.ca [67.68.207.82])  by www.sm.luth.se (IMP) with HTTP  for <pelle@mailhost.sm.luth.se>; Fri, 26 Jun 2009 20:29:17 +0200
Message-ID: <1246040957.4a45137dcf34e@www.sm.luth.se>
Date: Fri, 26 Jun 2009 20:29:17 +0200
From: pelle@cdt.luth.se
To: Karthik Balaguru <Karthik.Balaguru@lntinfotech.com>
References: <OF4774DF8E.E95CB052-ON652575E0.0033DFE9-652575E0.0046A641@lntinfotech.com>
In-Reply-To: <OF4774DF8E.E95CB052-ON652575E0.0033DFE9-652575E0.0046A641@lntinfotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.1
X-Originating-IP: 67.68.207.82
Cc: rohc@ietf.org
Subject: Re: [rohc] Support of ROHC Piggyback Feedback in LTE
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, 26 Jun 2009 18:52:18 -0000

Hello,

Kind reminder - please note that this mailing list is for questions concerning 
IETF specifications handled by the ROHC WG.

Questions related to 3GPP specifications may not receive any answers, and 
should be directed to the group responsible for those specifications.

Wrt to the total length of the entire feedback information, my understanding is 
that it is derived by inspecting the first two octets of each feedback element 
in the ROHC packet.

Cheers,

///Ghyslain

PS: Regarding your 3GPP specific questions, let's hope the following can 
provide you with some useful guidance. For further questions, please turn to 
the proper forum. The following is my understanding of the LTE specs.

For Rel-8 PDCP LTE as per TS36.323v860, if header compression is configured for 
the DRB by RRC at RB setup the following applies: the PDCP Data PDUs carry the 
entire ROHC packet (i.e. piggybacked feedback, if any, and the ROHC header and 
payload) in the data part of the PDCP PDU (see subclause 6.2.3 and 6.2.4 in 
particular); the PDCP Control PDU carries only interspersed ROHC feedback 
packets (see subclause 5.5.4 and 6.2.5 in particular).

Ciphering in Rel-8 LTE PDCP is not applicable to PDCP Control PDUs (there is no 
associated PDCP SN), but ciphering is always applied to PDCP Data PDUs for DRBs 
(thus always covering both the piggybacked feedback, if any, and the rest of 
the ROHC packet). The compressor in the PDCP entity first assemble the ROHC 
packet (including any piggyback feedback from the decompressor), then PDCP 
ciphers the result as the data part of the PDCP PDU with the COUNT associated 
to the original, uncompressed SDU.

ROHC is not applicable to SRBs.


Quoting Karthik Balaguru <Karthik.Balaguru@lntinfotech.com>:

> Hi,
> 
> Need clarifications on ROHC Piggyback feedback support in LTE.
> 
> LTE standrad states that PDCP Control Packet (Feedback) shall not be 
> ciphered (Reference - 3GPP TS 36.323 V8.5.0, Section 5.5.4 ) and PDCP data 
> 
> packets shall be ciphered by configured algorithm (Reference - Section 
> 5.2.1, 5.2.2 ) . 
> In case of Piggyback feedback packet, DataPacket will be attatched at the 
> end of feedback packet.  (RFC 3095 - Page no 43,44 & Section 5.2.2)
> 1. In LTE PDCP, If the Data Packet should be ciphered for these piggyback 
> packets , then how will the Peer entity generate COUNT input for ciphering 
> algorithm as PDCP-SN is not available ?
> 2. In LTE PDCP, Can the data Packet be sent without ciphering in Piggyback 
> Feedback packets ?
> 
> Further reference w.r.t RFC 3095 - Page no 44
> d) To allow piggybacking, 5), it is possible to deduce the length of 
> feedback information by examining the first few octets of the
>     feedback.  This allows the decompressor to pass piggybacked feedback 
> information to the associated same-side compressor
>     without understanding its format.  The length information decouples 
> the decompressor from the compressor in the sense that
>     the decompressor can process the compressed header immediately without 
> waiting for the compressor to hand it back after parsing
>     the feedback information.
> 
> Kindly clarify regarding the support of RoHC piggyback Feedback in LTE ?
> 
> Thx in advans,
> Karthik Balaguru
> 
> ______________________________________________________________________





From lei.zhu@huawei.com  Fri Jun 26 05:59:46 2009
Return-Path: <lei.zhu@huawei.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 4D2563A6809 for <rohc@core3.amsl.com>; Fri, 26 Jun 2009 05:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.649
X-Spam-Level: 
X-Spam-Status: No, score=-0.649 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 xsBPV47HNp-8 for <rohc@core3.amsl.com>; Fri, 26 Jun 2009 05:59:45 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 586C13A67A7 for <rohc@ietf.org>; Fri, 26 Jun 2009 05:59:45 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU002J6K1XWH@szxga01-in.huawei.com> for rohc@ietf.org; Fri, 26 Jun 2009 20:58:45 +0800 (CST)
Received: from huawei.com ([172.17.1.31]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLU007GHK1XHL@szxga01-in.huawei.com> for rohc@ietf.org; Fri, 26 Jun 2009 20:58:45 +0800 (CST)
Received: from [172.24.1.6] (Forwarded-For: [208.71.39.153]) by szxmc03-in.huawei.com (mshttpd); Fri, 26 Jun 2009 20:58:45 +0800
Date: Fri, 26 Jun 2009 20:58:45 +0800
From: zhulei 41317 <lei.zhu@huawei.com>
In-reply-to: <FE127977CE269045BBA7EC732F399FD93D526A@rvil-mail1.RADVISION.com>
To: Ofer Goren <oferg@radvision.com>
Message-id: <f4dbf4172f52.2f52f4dbf417@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
References: <fdcff22318f6.18f6fdcff223@huawei.com> <FE127977CE269045BBA7EC732F399FD93D526A@rvil-mail1.RADVISION.com>
X-Mailman-Approved-At: Sun, 28 Jun 2009 23:45:20 -0700
Cc: rohc@ietf.org
Subject: [rohc] Re :RE:  New draft posted to Rohc
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, 26 Jun 2009 12:59:46 -0000

Hi Ofer,

Regarding your input on this draft.

Section 3.1 "How these extra strings selected" the concepts how to pick up those SIP protocol extension. 

The strings are selected from SIP extension defined in SIP and SIPPING WG in recent years. Some drafting in queue or review processes are also looked at. It seems that ims P-headers in RFC4457 must be included in the new dictionary. There could be more necessary strings.

In addition, the strings defined for SDP extensions are also considered to be included in further versions of this draft. Thank you!

Best regards,
Lei


> Hi Lei.
> 
> You referred to the IMS additions as well, but IMS p-headers were 
> not included in this new dictionary. Is there a plan to add them 
> as well?
> 
> Ofer
> 
> ________________________________
> 
> From: rohc-bounces@ietf.org on behalf of zhulei 41317
> Sent: Thu 6/25/2009 17:29
> To: rohc@ietf.org
> Cc: lei.zhu@huawei.com
> Subject: [rohc] New draft posted to Rohc
> 
> 
> 
> Hi Rohc folks:
> 
> To summarise extensions to SIP signalling for signalling 
> compressing dictionary, an initial I-D was posted to IETF. I 
> supposed some of you have already gotten the content of this new I-
> D from link below.
> 
> http://tools.ietf.org/html/draft-lei-rohc-sigcomp-static-
> dictionary-00
> 
> I supposed some time in Stockholm meeting could be used to present 
> or discuss it online. Therefore, please take a look on this draft 
> and comment it. Thank you!
> 
> Best regards,
> Lei Zhu
> 
> 
> 
> ******************************************************************************************
> This email and its attachments contain confidential information 
> from HUAWEI, which is intended only for the person or entity whose 
> address is listed above. Any use of the information contained here 
> in any way (including, but not limited to, total or partial 
> disclosure, reproduction, or dissemination) by persons other than 
> the intended recipient(s) is prohibited. If you receive this email 
> in error, please notify the sender by phone or email
> immediately and delete it!
> 
> *****************************************************************************************_______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc
> 
> 
> 

From Karthik.Balaguru@lntinfotech.com  Mon Jun 29 07:18:36 2009
Return-Path: <Karthik.Balaguru@lntinfotech.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 64B9F3A6999; Mon, 29 Jun 2009 07:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.043
X-Spam-Level: 
X-Spam-Status: No, score=-6.043 tagged_above=-999 required=5 tests=[AWL=0.555,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 vvFQSVX6gtXo; Mon, 29 Jun 2009 07:18:29 -0700 (PDT)
Received: from mail142.messagelabs.com (mail142.messagelabs.com [216.82.249.99]) by core3.amsl.com (Postfix) with SMTP id 024963A6B3A; Mon, 29 Jun 2009 07:18:28 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Karthik.Balaguru@lntinfotech.com
X-Msg-Ref: server-14.tower-142.messagelabs.com!1246285116!33785523!5
X-StarScan-Version: 6.0.0; banners=lntinfotech.com,-,-
X-Originating-IP: [203.101.96.4]
Received: (qmail 27145 invoked from network); 29 Jun 2009 14:18:40 -0000
Received: from bangaloresmtp.lntinfotech.com (HELO bangaloresmtp.lntinfotech.com) (203.101.96.4) by server-14.tower-142.messagelabs.com with SMTP; 29 Jun 2009 14:18:40 -0000
Received: from Bangalore.lntinfotech.com ([172.28.0.3]) by bangaloresmtp.lntinfotech.com (Lotus Domino Release 7.0.3) with ESMTP id 2009062919502172-109863 ; Mon, 29 Jun 2009 19:50:21 +0530 
In-Reply-To: <1246040957.4a45137dcf34e@www.sm.luth.se>
To: pelle@cdt.luth.se
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OFE667A92C.01DDCDB7-ON652575E4.004AE5FE-652575E4.004E9A1C@lntinfotech.com>
From: Karthik Balaguru <Karthik.Balaguru@lntinfotech.com>
Date: Mon, 29 Jun 2009 19:48:32 +0530
X-MIMETrack: Serialize by Router on BANGALORE/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/29/2009 07:48:35 PM, Serialize complete at 06/29/2009 07:48:35 PM, Itemize by SMTP Server on BangaloreSMTP/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/29/2009 07:50:21 PM, Serialize by Router on BangaloreSMTP/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/29/2009 07:50:27 PM, Serialize complete at 06/29/2009 07:50:27 PM
Content-Type: multipart/alternative; boundary="=_alternative 004E9A19652575E4_="
Cc: rohc@ietf.org, rohc-bounces@ietf.org
Subject: Re: [rohc] Support of ROHC Piggyback Feedback in LTE
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: Mon, 29 Jun 2009 14:18:36 -0000

This is a multipart message in MIME format.
--=_alternative 004E9A19652575E4_=
Content-Type: text/plain; charset="US-ASCII"

Hi Pelle,

Thanks for your clarifications.

I will be forwarding the 3GPP specific queries to 3GPP LTE Forum.

PS :
Based on your reply, i assume that Piggyback packet is a 'Compressed 
packet'  each associated with one PDCP SDU.

The query/dilemma was due to the 2 statements from Section 5.5.4 from 
TS36.323v850 that has been mentioned below :-
" The header compression protocol generates two types of output packets:
-     compressed packets, each associated with one PDCP SDU
-     standalone packets not associated with a PDCP SDU, i.e. interspersed 
ROHC feedback packets "

As the LTE PDCP standard does not explicitly talk about the piggyback 
packet , i think , 
the term 'Compressed packet' in the section 5.5.4 TS36.323v850 mentioned 
above refers 
to  ' Rohc Feedback Packet and Rohc Compressed header (Piggybacked) '. It 
does not refer to 'Rohc Compressed header' alone.

Thanks for your reply,

Regards,
Karthik Balaguru





pelle@cdt.luth.se 
Sent by: rohc-bounces@ietf.org
06/26/2009 11:59 PM

To
Karthik Balaguru <Karthik.Balaguru@lntinfotech.com>
cc
rohc@ietf.org
Subject
Re: [rohc] Support of ROHC Piggyback Feedback in LTE






Hello,

Kind reminder - please note that this mailing list is for questions 
concerning 
IETF specifications handled by the ROHC WG.

Questions related to 3GPP specifications may not receive any answers, and 
should be directed to the group responsible for those specifications.

Wrt to the total length of the entire feedback information, my 
understanding is 
that it is derived by inspecting the first two octets of each feedback 
element 
in the ROHC packet.

Cheers,

///Ghyslain

PS: Regarding your 3GPP specific questions, let's hope the following can 
provide you with some useful guidance. For further questions, please turn 
to 
the proper forum. The following is my understanding of the LTE specs.

For Rel-8 PDCP LTE as per TS36.323v860, if header compression is 
configured for 
the DRB by RRC at RB setup the following applies: the PDCP Data PDUs carry 
the 
entire ROHC packet (i.e. piggybacked feedback, if any, and the ROHC header 
and 
payload) in the data part of the PDCP PDU (see subclause 6.2.3 and 6.2.4 
in 
particular); the PDCP Control PDU carries only interspersed ROHC feedback 
packets (see subclause 5.5.4 and 6.2.5 in particular).

Ciphering in Rel-8 LTE PDCP is not applicable to PDCP Control PDUs (there 
is no 
associated PDCP SN), but ciphering is always applied to PDCP Data PDUs for 
DRBs 
(thus always covering both the piggybacked feedback, if any, and the rest 
of 
the ROHC packet). The compressor in the PDCP entity first assemble the 
ROHC 
packet (including any piggyback feedback from the decompressor), then PDCP 

ciphers the result as the data part of the PDCP PDU with the COUNT 
associated 
to the original, uncompressed SDU.

ROHC is not applicable to SRBs.


Quoting Karthik Balaguru <Karthik.Balaguru@lntinfotech.com>:

> Hi,
> 
> Need clarifications on ROHC Piggyback feedback support in LTE.
> 
> LTE standrad states that PDCP Control Packet (Feedback) shall not be 
> ciphered (Reference - 3GPP TS 36.323 V8.5.0, Section 5.5.4 ) and PDCP 
data 
> 
> packets shall be ciphered by configured algorithm (Reference - Section 
> 5.2.1, 5.2.2 ) . 
> In case of Piggyback feedback packet, DataPacket will be attatched at 
the 
> end of feedback packet.  (RFC 3095 - Page no 43,44 & Section 5.2.2)
> 1. In LTE PDCP, If the Data Packet should be ciphered for these 
piggyback 
> packets , then how will the Peer entity generate COUNT input for 
ciphering 
> algorithm as PDCP-SN is not available ?
> 2. In LTE PDCP, Can the data Packet be sent without ciphering in 
Piggyback 
> Feedback packets ?
> 
> Further reference w.r.t RFC 3095 - Page no 44
> d) To allow piggybacking, 5), it is possible to deduce the length of 
> feedback information by examining the first few octets of the
>     feedback.  This allows the decompressor to pass piggybacked feedback 

> information to the associated same-side compressor
>     without understanding its format.  The length information decouples 
> the decompressor from the compressor in the sense that
>     the decompressor can process the compressed header immediately 
without 
> waiting for the compressor to hand it back after parsing
>     the feedback information.
> 
> Kindly clarify regarding the support of RoHC piggyback Feedback in LTE ?
> 
> Thx in advans,
> Karthik Balaguru
> 
> ______________________________________________________________________




_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www.ietf.org/mailman/listinfo/rohc

______________________________________________________________________



______________________________________________________________________
--=_alternative 004E9A19652575E4_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="Trebuchet MS">Hi Pelle,</font>
<br>
<br><font size=2 face="Trebuchet MS">Thanks for your clarifications.</font>
<br>
<br><font size=2 face="Trebuchet MS">I will be forwarding the 3GPP specific
queries to 3GPP LTE Forum.</font>
<br>
<br><font size=2 face="Trebuchet MS">PS :</font>
<br><font size=2 face="Trebuchet MS">Based on your reply, i assume that
Piggyback packet is a 'Compressed packet' &nbsp;each associated with one
PDCP SDU.</font>
<br>
<br><font size=2 face="Trebuchet MS">The query/dilemma was due to the 2
statements from Section 5.5.4 from TS36.323v850 that has been mentioned
below :-</font>
<br><font size=2 face="Trebuchet MS">&quot; The header compression protocol
generates <b><i>two types of output packets:</i></b></font>
<br><font size=2 face="Trebuchet MS">- &nbsp; &nbsp;<i> <b>compressed packets</i></b>,
each associated with one PDCP SDU</font>
<br><font size=2 face="Trebuchet MS">- &nbsp; &nbsp; standalone packets
not associated with a PDCP SDU, i.e. <b><i>interspersed ROHC feedback packets</i></b>
&quot;</font>
<br>
<br><font size=2 face="Trebuchet MS">As the LTE PDCP standard does not
explicitly talk about the piggyback packet , i think , </font>
<br><font size=2 face="Trebuchet MS">the term 'Compressed packet' in the
section 5.5.4 TS36.323v850 mentioned above refers </font>
<br><font size=2 face="Trebuchet MS">to &nbsp;' Rohc Feedback Packet and
Rohc Compressed header (Piggybacked) '. It does not refer to 'Rohc Compressed
header' alone.</font>
<br>
<br><font size=2 face="Trebuchet MS">Thanks for your reply,</font>
<br>
<br><font size=2 face="Trebuchet MS">Regards,</font>
<br><font size=2 face="Trebuchet MS">Karthik Balaguru</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="Trebuchet MS"><b>pelle@cdt.luth.se</b>
</font>
<br><font size=1 face="Trebuchet MS">Sent by: rohc-bounces@ietf.org</font>
<p><font size=1 face="Trebuchet MS">06/26/2009 11:59 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="Trebuchet MS">To</font></div>
<td><font size=1 face="Trebuchet MS">Karthik Balaguru &lt;Karthik.Balaguru@lntinfotech.com&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="Trebuchet MS">cc</font></div>
<td><font size=1 face="Trebuchet MS">rohc@ietf.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="Trebuchet MS">Subject</font></div>
<td><font size=1 face="Trebuchet MS">Re: [rohc] Support of ROHC Piggyback
Feedback in LTE</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hello,<br>
<br>
Kind reminder - please note that this mailing list is for questions concerning
<br>
IETF specifications handled by the ROHC WG.<br>
<br>
Questions related to 3GPP specifications may not receive any answers, and
<br>
should be directed to the group responsible for those specifications.<br>
<br>
Wrt to the total length of the entire feedback information, my understanding
is <br>
that it is derived by inspecting the first two octets of each feedback
element <br>
in the ROHC packet.<br>
<br>
Cheers,<br>
<br>
///Ghyslain<br>
<br>
PS: Regarding your 3GPP specific questions, let's hope the following can
<br>
provide you with some useful guidance. For further questions, please turn
to <br>
the proper forum. The following is my understanding of the LTE specs.<br>
<br>
For Rel-8 PDCP LTE as per TS36.323v860, if header compression is configured
for <br>
the DRB by RRC at RB setup the following applies: the PDCP Data PDUs carry
the <br>
entire ROHC packet (i.e. piggybacked feedback, if any, and the ROHC header
and <br>
payload) in the data part of the PDCP PDU (see subclause 6.2.3 and 6.2.4
in <br>
particular); the PDCP Control PDU carries only interspersed ROHC feedback
<br>
packets (see subclause 5.5.4 and 6.2.5 in particular).<br>
<br>
Ciphering in Rel-8 LTE PDCP is not applicable to PDCP Control PDUs (there
is no <br>
associated PDCP SN), but ciphering is always applied to PDCP Data PDUs
for DRBs <br>
(thus always covering both the piggybacked feedback, if any, and the rest
of <br>
the ROHC packet). The compressor in the PDCP entity first assemble the
ROHC <br>
packet (including any piggyback feedback from the decompressor), then PDCP
<br>
ciphers the result as the data part of the PDCP PDU with the COUNT associated
<br>
to the original, uncompressed SDU.<br>
<br>
ROHC is not applicable to SRBs.<br>
<br>
<br>
Quoting Karthik Balaguru &lt;Karthik.Balaguru@lntinfotech.com&gt;:<br>
<br>
&gt; Hi,<br>
&gt; <br>
&gt; Need clarifications on ROHC Piggyback feedback support in LTE.<br>
&gt; <br>
&gt; LTE standrad states that PDCP Control Packet (Feedback) shall not
be <br>
&gt; ciphered (Reference - 3GPP TS 36.323 V8.5.0, Section 5.5.4 ) and PDCP
data <br>
&gt; <br>
&gt; packets shall be ciphered by configured algorithm (Reference - Section
<br>
&gt; 5.2.1, 5.2.2 ) . <br>
&gt; In case of Piggyback feedback packet, DataPacket will be attatched
at the <br>
&gt; end of feedback packet. &nbsp;(RFC 3095 - Page no 43,44 &amp; Section
5.2.2)<br>
&gt; 1. In LTE PDCP, If the Data Packet should be ciphered for these piggyback
<br>
&gt; packets , then how will the Peer entity generate COUNT input for ciphering
<br>
&gt; algorithm as PDCP-SN is not available ?<br>
&gt; 2. In LTE PDCP, Can the data Packet be sent without ciphering in Piggyback
<br>
&gt; Feedback packets ?<br>
&gt; <br>
&gt; Further reference w.r.t RFC 3095 - Page no 44<br>
&gt; d) To allow piggybacking, 5), it is possible to deduce the length
of <br>
&gt; feedback information by examining the first few octets of the<br>
&gt; &nbsp; &nbsp; feedback. &nbsp;This allows the decompressor to pass
piggybacked feedback <br>
&gt; information to the associated same-side compressor<br>
&gt; &nbsp; &nbsp; without understanding its format. &nbsp;The length information
decouples <br>
&gt; the decompressor from the compressor in the sense that<br>
&gt; &nbsp; &nbsp; the decompressor can process the compressed header immediately
without <br>
&gt; waiting for the compressor to hand it back after parsing<br>
&gt; &nbsp; &nbsp; the feedback information.<br>
&gt; <br>
&gt; Kindly clarify regarding the support of RoHC piggyback Feedback in
LTE ?<br>
&gt; <br>
&gt; Thx in advans,<br>
&gt; Karthik Balaguru<br>
&gt; <br>
&gt; ______________________________________________________________________<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Rohc mailing list<br>
Rohc@ietf.org<br>
https://www.ietf.org/mailman/listinfo/rohc<br>
<br>
______________________________________________________________________<br>
</font></tt>
<br>

<BR>
______________________________________________________________________<BR>

--=_alternative 004E9A19652575E4_=--
