From rohc-bounces@ietf.org Fri Jun 01 08:27:58 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu6EW-0005KF-WF; Fri, 01 Jun 2007 08:27:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hu2mS-0004gZ-KD
	for rohc@ietf.org; Fri, 01 Jun 2007 04:46:44 -0400
Received: from an-out-0708.google.com ([209.85.132.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hu2mR-0001U0-E6
	for rohc@ietf.org; Fri, 01 Jun 2007 04:46:44 -0400
Received: by an-out-0708.google.com with SMTP id c17so165584anc
	for <rohc@ietf.org>; Fri, 01 Jun 2007 01:46:43 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=cGToa/Q3O4VFoa49wmovrz4P4nl9bHDdD2aPBzd6piIqk9Pt2VJ70YrHn6Zcj6VMxM3eKqfk471I65sHkYLRxSL7pVbGBRb1R3rYRAXCVtYY2oPqIX9BL6s0ohd7NKwGENpX6dRwfmFYNd0xLhr+tfzfwzNXP/6Gt4UptHXQE50=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=hsOqgVSFOVlPozabxCyREMkkJ1d6JDquQYrigOC11Pqx233+tKhGIjlqSY7gih3D+QfGKrC1xhCPNDDqsgjZao0IDu/HcB5l7vH3gBlTUf5xJvyyPH5k2OkfB0IC4+qC5r3MJX4IoyNEcO7O9sK6CzoN7JKsNV6CSg1LLAIC4rA=
Received: by 10.100.200.12 with SMTP id x12mr877584anf.1180687598366;
	Fri, 01 Jun 2007 01:46:38 -0700 (PDT)
Received: by 10.100.37.12 with HTTP; Fri, 1 Jun 2007 01:46:38 -0700 (PDT)
Message-ID: <f631f9a80706010146x77bc6b0bw93789d19d2a8f71@mail.gmail.com>
Date: Fri, 1 Jun 2007 14:16:38 +0530
From: zabi <mohamed.zabiulla@gmail.com>
To: rohc@ietf.org
In-Reply-To: <f631f9a80706010145k1936bc1ci3f280b2fa8f3b911@mail.gmail.com>
MIME-Version: 1.0
References: <f631f9a80706010145k1936bc1ci3f280b2fa8f3b911@mail.gmail.com>
X-Spam-Score: 0.9 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-Mailman-Approved-At: Fri, 01 Jun 2007 08:27:55 -0400
Subject: [rohc] Regarding UDPlite on windows
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0497420265=="
Errors-To: rohc-bounces@ietf.org

--===============0497420265==
Content-Type: multipart/alternative; 
	boundary="----=_Part_3466_9683292.1180687598318"

------=_Part_3466_9683292.1180687598318
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dear Sir,

I have inplemented a UDPlite client server on windows.  I would like to test
it on the internet and check as to how far it

is useful compared to traditional udp.

Regards,
Mohamed Zabiulla

------=_Part_3466_9683292.1180687598318
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<span class="gmail_quote"><br></span>
<div>Dear Sir,</div>
<div>&nbsp;</div>
<div>I have inplemented a UDPlite client server on windows.&nbsp; I would like to test it on the internet and check as to how far it</div>
<div>&nbsp;</div>
<div>is useful compared to traditional udp.</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>Mohamed Zabiulla<br clear="all"><br>&nbsp;</div>

------=_Part_3466_9683292.1180687598318--


--===============0497420265==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0497420265==--




From rohc-bounces@ietf.org Fri Jun 01 11:30:38 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu95J-0002Jn-SE; Fri, 01 Jun 2007 11:30:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hu95I-0002GS-98
	for rohc@ietf.org; Fri, 01 Jun 2007 11:30:36 -0400
Received: from mclniron02-ext.bah.com ([156.80.1.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hu95H-0002tb-0o
	for rohc@ietf.org; Fri, 01 Jun 2007 11:30:36 -0400
x-SBRS: None
X-REMOTE-IP: 156.80.7.153
X-IronPort-AV: E=Sophos;i="4.16,373,1175486400"; d="scan'208";a="197637119"
Received: from mclnexbh03.resource.ds.bah.com ([156.80.7.153])
	by mclniron02-int.bah.com with ESMTP; 01 Jun 2007 11:30:34 -0400
Received: from MCLNEXVS05.resource.ds.bah.com ([156.80.7.124]) by
	mclnexbh03.resource.ds.bah.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 1 Jun 2007 11:30:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Feedback on draft-ietf-rohc-hcoipsec-04
Date: Fri, 1 Jun 2007 11:30:36 -0400
Message-ID: <37BDD2FAF2AEAE459C6C70FDC2892E4E01E7837D@MCLNEXVS05.resource.ds.bah.com>
In-Reply-To: <000701c7715a$c9b9f0b0$8700a8c0@jymden3>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Feedback on draft-ietf-rohc-hcoipsec-04
Thread-Index: AcdxW0nHkpwAM3QHRqmy0N4iQxfmIwV3x3sw
References: <000701c7715a$c9b9f0b0$8700a8c0@jymden3>
From: "Ertekin, Emre" <ertekin_emre@bah.com>
To: <rohc@ietf.org>
X-OriginalArrivalTime: 01 Jun 2007 15:30:36.0390 (UTC)
	FILETIME=[CD253860:01C7A461]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Lars-Erik,

Thanks for taking the time to review our drafts!  I agree with all of
your comments.  We incorporated the changes that you proposed, and have
decided to modify all three of our drafts (e.g., Framework, IKEv2
Extensions, and IPsec extensions) to be RoHC specific.

I resubmitted all three of the drafts; they should be available shortly.

Best Regards,
Emre
=20
> *  References: This document is intended to be informational, and I
>     would like to hear how one can argue for normative references
>     in an informative document.
>=20
> * The document should either:
>   - be reformulated to focus on ROHC only, including document title
>       or
>   - take a slightly different perspective as more of a general problem
>     statement, as the solution envisioned is built on ROHC.
>   As it is now, the document gives the impression the solution
>   envisioned will in itself be realized for all HC schemes, which is
>   not the case.
>=20
> * 6.1.1, replace "must be extended" with "may have to be extended"
>=20
> * Reference to ROHC-over-reordering does not give a proper view
>    of the scope of that document, which is mainly a problem analysis.
>    The reference name should also properly match the title, "EXT" is
>    not a good chioce.
>=20
> * ROHCv2 should be referenced as the only really proper HC scheme
>    for HCoIPsec.
>=20
> * 6.1.2, the goal is not to remove HC lower layer dependency, but
>    to facilitate the traditional LL functions by other  means for this
>    scenario .
>=20
> * When discussing the Protocol/Next Header approach, the
>    document talks about this as "a value" and gives the impression
>    this will provide a solution for all HC schemes, while it actually
>    will be a ROHC identifier. Just try to adjust to not give an
>    improper impression. Further, if you see this document as more
>    of a general problem statement (see second bullet above), it
>    should be made clear that the Protocol value solution is just one
>    "potential" solution. Consequences and restrictions with using
>    the protocol field could also be useful to have.
>=20
> That was it, overall the document looks fine!!
> /L-E

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



From rohc-bounces@ietf.org Mon Jun 04 15:50:47 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIZe-00042j-1I; Mon, 04 Jun 2007 15:50:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIZ2-00037N-NI; Mon, 04 Jun 2007 15:50:05 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvIZ2-0002oC-Ck; Mon, 04 Jun 2007 15:50:04 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 3D36A26EA1;
	Mon,  4 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HvIZ0-0002hN-4h; Mon, 04 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HvIZ0-0002hN-4h@stiedprstage1.ietf.org>
Date: Mon, 04 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-ikev2-extensions-hcoipsec-02.txt 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Robust Header Compression Working Group of the IETF.

	Title		: IKEv2 Extensions to Support Robust Header Compression over IPsec (RoHCoIPsec)
	Author(s)	: R. Jasani, et al.
	Filename	: draft-ietf-rohc-ikev2-extensions-hcoipsec-02.txt
	Pages		: 10
	Date		: 2007-6-4
	
When using Robust Header Compression (RoHC [ROHC]) in conjunction
   with IPsec [IPSEC] (i.e.  [RoHCOIPSEC]) a mechanism is needed to
   negotiate RoHC configuration parameters between end-points prior to
   operation.  Internet Key Exchange (IKE) is a mechanism which can be
   leveraged to handle these negotiations.  This document specifies
   extensions to Internet Key Exchange (IKEv2 [IKEV2]) that will allow
   RoHC and its associated configuration parameters to be negotiated for
   IPsec security associations (SAs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ikev2-extensions-hcoipsec-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rohc-ikev2-extensions-hcoipsec-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rohc-ikev2-extensions-hcoipsec-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-6-4123532.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-ikev2-extensions-hcoipsec-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rohc-ikev2-extensions-hcoipsec-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-6-4123532.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From rohc-bounces@ietf.org Mon Jun 04 15:52:17 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIbA-0005zy-1F; Mon, 04 Jun 2007 15:52:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIZV-0003gb-PC; Mon, 04 Jun 2007 15:50:33 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HvIZU-0002fT-F4; Mon, 04 Jun 2007 15:50:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 5DBB72AD00;
	Mon,  4 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HvIZ0-0002hK-48; Mon, 04 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HvIZ0-0002hK-48@stiedprstage1.ietf.org>
Date: Mon, 04 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-hcoipsec-05.txt 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Robust Header Compression Working Group of the IETF.

	Title		: Integration of Robust Header Compression (RoHC) over IPsec Security Associations
	Author(s)	: E. Ertekin, et al.
	Filename	: draft-ietf-rohc-hcoipsec-05.txt
	Pages		: 13
	Date		: 2007-6-4
	
IP Security (IPsec) provides various security services for IP
   traffic.  However, the benefits of IPsec come at the cost of
   increased overhead.  This document outlines a framework for
   integrating Robust Header Compression (RoHC) over IPsec (RoHCoIPsec).
   By compressing the inner headers of IP packets, RoHCoIPsec proposes
   to reduce the amount of overhead associated with the transmission of
   traffic over IPsec Security Associations (SAs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-hcoipsec-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rohc-hcoipsec-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rohc-hcoipsec-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-6-4123333.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-hcoipsec-05.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-rohc-hcoipsec-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-6-4123333.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From rohc-bounces@ietf.org Mon Jun 11 22:03:07 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxvim-0001fe-JS; Mon, 11 Jun 2007 22:03:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxvil-0001fZ-II
	for rohc@ietf.org; Mon, 11 Jun 2007 22:02:59 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxvil-0002z8-0S
	for rohc@ietf.org; Mon, 11 Jun 2007 22:02:59 -0400
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l5C22sw6027133
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 11 Jun 2007 19:02:55 -0700
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l5C22nQ5009415;
	Mon, 11 Jun 2007 19:02:54 -0700 (PDT)
Received: from NAEX09.na.qualcomm.com ([10.46.56.82]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Jun 2007 19:01:39 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Update of ROHCv2 profiles draft
Date: Mon, 11 Jun 2007 19:01:39 -0700
Message-ID: <ECA90F8A96A62E4EB8D9E25E5140F7560423E95C@NAEX09.na.qualcomm.com>
In-Reply-To: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Update of ROHCv2 profiles draft
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQN+Xxug
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
From: "Kapoor, Rohit" <rkapoor@qualcomm.com>
To: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 02:01:39.0418 (UTC)
	FILETIME=[9D664BA0:01C7AC95]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Kristofer, Ghyslain,

Thanks for the updated draft. Pls find few comments below:

1) Regarding use of timer-based compression in pt_1_seq_ts, I had
brought up this issue earlier, but haven't seen any resolution for it in
the current draft. The issue was that timer-based will require 5 bits to
handle a reasonable amount of jitter, but the pt_1_seq_ts packet in the
current draft only has 4 bits. Also, if the number of bits for TS in
pt_1_seq_ts is increased from 4 to 5, it would still be good for the
packet size to stay as 2 octets (so that performance of RoHC v2 for
VoIP-like applications is not worse than that of RFC 3095). For this, we
had also proposed the solution below.

Quoting from earlier email:

"The addition of Timer-Based compression (for which TS will require at
least 5 bits to handle a reasonable amount of jitter) should not cause
the pt_1_seq_ts packet to exceed 2 octets. To allow this packet to fit
within 2 octets, I am providing below a suggestion of what packet
discriminators can look like (if timer-based and pt_0_crc7 are both
added).
=20
pt_0_crc3: "0"
pt_1_rnd: "10" (1 extra bit for use; TS can have 1 extra bit)
pt_1_seq_id: "100" (1 extra bit for use; either MSN or IP-ID can have 1
more bit)
pt_1_seq_ts: "101" (now this has 1 extra bit for TS, making a total of 5
TS bits).
pt_0_crc7: "1100" (this has 1 less bit now; so maybe MSN can be reduced
to 5 bits, which is still very robust).
pt_2_rnd: "1101" (1 fewer bit for use; MSN can be reduced from 7 to 6
bits)
pt_2_seq_ts: "11011" (1 fewer bit for use; MSN can be reduced from 7 to
6 bits)
pt_2_seq_id: "110100" (2 fewer bits for use, 1 of them due to the
addition of pt_2_seq_both; both MSN and IP-ID can be reduced by 1 bit
each)
pt_2_seq_both: "110101"


Note that this is just an example of a solution. Any proposal which
handles this issue would be OK for me.


2) Section 6.8.3.1 says the following:   "The following packet formats
exist **exclusively** for profiles 0x101 and 0x107" and then later also
"The following packet formats exist **exclusively** for profiles
0x102,0x103, 0x104 and 0x108". But, some of the packet formats (such as
pt_1_seq_id) are defined under both of these sentences.

3) ts_stride_value and time_stride_value are defined as:

         ts_stride_value: This parameter is set to a user-selected value
         that is the expected increase in the RTP Timestamp between
         consecutive sequence numbers.  See also Section 6.6.8.

         time_stride_value: This parameter is set to a user-selected
         value that is the expected inter-arrival time between
         consecutive packets for this flow.  See also Section 6.6.9.

Are these intended to be user-selected values?

Thanks,
Rohit

> -----Original Message-----
> From: Kristofer Sandlund (LU/EAB)
[mailto:kristofer.sandlund@ericsson.com]
> Sent: Thursday, May 24, 2007 11:48 PM
> To: rohc@ietf.org
> Cc: Ghyslain Pelletier (LU/EAB)
> Subject: [rohc] Update of ROHCv2 profiles draft
>=20
> Hi all,
>=20
> we have just sent in an update of the profiles draft which
> mostly contains the changes discussed on the list towards the end of
> last year. The draft should be announced within the next couple of
days
> as usual.
> Here is a list of changes since the previous revision.
>=20
> Changes in the FN code (packet formats):
> - Lots of minor typos and smaller bug fixes related to FN syntax
> - Fixes to scaled encoding and MSN handling
> - Style-related cleanup to make the code more consistent
> - Addition of many ENFORCE-statements to make the code more formally
>   correct
> - Added a co_repair format for all profiles which is bitwaise very
>   similar to co_common (so it should be very easy to implement), but
>   has the possibility of sending all LSB-fields as
>   uncompressed (should be seen as an IR-DYN replacement)
> - Repair-specific irregular chain items added in order to make context
>   repair for outer headers, including extension headers, but have LSB
>   encoded fields sent uncompressed
> - Optimized the co_common formats with "meta-discriminators" in order
to
>   reduce the flag overhead
> - Added timer-based compression (this still needs to be added to the
> text
>   where we just have a placeholder section for now)
> - Fixed ESP static chain so encrypted and null-encrypted static chains
> can
>   be discriminated from each other
> - LSB-offsets are made much more consistent throughput the formats
> - Header chain termination for IP-only profile (different static chain
>   items if this is the terminating IP header)
>=20
> Changes to the text:
> - Text on scaled encoding re-written and improved
> - External arguments to the FN code section added
> - Design rationale for the packet formats section added
> - Text on state logic improved
> - Clarifications around the unidirectional/bidirectional operation
> - Added new feedback option for requesting update of control fields
>   (to be used with NACKs)
> - Update of Appendix A (field classifications) which was previously
>   imported from RFC3095 and contained a bunch of errors
> - Removed Appendix A.3
> - CRC algorithm and demo are now in framework, so it is removed from
>   this draft
> - Added section about handling reordering
> - Removal of the IR-DYN packet format from all these profiles
>=20
> The draft still needs some more work in a few areas, but we are
getting
> closer to finalizing this work now, so we would be very grateful
> if you read and comment on this draft so that it contains what you
> expect it to.
>=20
> Thanks to all the people who contributed on the list to the
discussions
> on this draft!
>=20
> /Kristofer & Ghyslain
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

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



From rohc-bounces@ietf.org Tue Jun 12 02:44:17 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy06u-0003kW-0v; Tue, 12 Jun 2007 02:44:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy06t-0003kO-8v
	for rohc@ietf.org; Tue, 12 Jun 2007 02:44:11 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy06r-0006bn-7E
	for rohc@ietf.org; Tue, 12 Jun 2007 02:44:11 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	324D720627; Tue, 12 Jun 2007 08:44:08 +0200 (CEST)
X-AuditID: c1b4fb3c-ac51ebb0000073d5-2e-466e40b8f97e 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	192C220785; Tue, 12 Jun 2007 08:44:08 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 08:44:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Update of ROHCv2 profiles draft
Date: Tue, 12 Jun 2007 08:44:06 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F04168EE7@esealmw105.eemea.ericsson.se>
In-Reply-To: <ECA90F8A96A62E4EB8D9E25E5140F7560423E95C@NAEX09.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Update of ROHCv2 profiles draft
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQN+XxugAAo0aLA=
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
	<ECA90F8A96A62E4EB8D9E25E5140F7560423E95C@NAEX09.na.qualcomm.com>
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: "Kapoor, Rohit" <rkapoor@qualcomm.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 06:44:07.0573 (UTC)
	FILETIME=[13498450:01C7ACBD]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Rohit,

thanks for your comments. My answers inline.

Kapoor, Rohit <mailto:rkapoor@qualcomm.com> wrote on den 12 juni 2007
04:02 :

> Kristofer, Ghyslain,
>=20
> Thanks for the updated draft. Pls find few comments below:
>=20
> 1) Regarding use of timer-based compression in pt_1_seq_ts, I had
> brought up this issue earlier, but haven't seen any
> resolution for it in
> the current draft.

Since we hadn't decided what to do on that last time we discussed it, I
left the following TODO in the draft:

// TODO:
// - PT_0/PT_1 packets? Use "tbc-optimized" or "msn-optimized"

So it was not forgotten, we just preferred to get out a new revision of
the
draft as soon as we could and let us continue the discussion later.

I will give a more detailed answer on this issue later this week or next
week

> The issue was that timer-based will
> require 5 bits to
> handle a reasonable amount of jitter, but the pt_1_seq_ts
> packet in the
> current draft only has 4 bits. Also, if the number of bits for TS in
> pt_1_seq_ts is increased from 4 to 5, it would still be good for the
> packet size to stay as 2 octets (so that performance of RoHC v2 for
> VoIP-like applications is not worse than that of RFC 3095).
> For this, we
> had also proposed the solution below.
>=20
> Quoting from earlier email:
>=20
> "The addition of Timer-Based compression (for which TS will require at
> least 5 bits to handle a reasonable amount of jitter) should not cause
> the pt_1_seq_ts packet to exceed 2 octets. To allow this packet to fit
> within 2 octets, I am providing below a suggestion of what packet
> discriminators can look like (if timer-based and pt_0_crc7 are both
> added).=20
>=20
> pt_0_crc3: "0"
> pt_1_rnd: "10" (1 extra bit for use; TS can have 1 extra bit)
> pt_1_seq_id: "100" (1 extra bit for use; either MSN or IP-ID
> can have 1
> more bit)
> pt_1_seq_ts: "101" (now this has 1 extra bit for TS, making a
> total of 5
> TS bits).
> pt_0_crc7: "1100" (this has 1 less bit now; so maybe MSN can
> be reduced
> to 5 bits, which is still very robust).
> pt_2_rnd: "1101" (1 fewer bit for use; MSN can be reduced from 7 to 6
> bits) pt_2_seq_ts: "11011" (1 fewer bit for use; MSN can be reduced
> from 7 to
> 6 bits)
> pt_2_seq_id: "110100" (2 fewer bits for use, 1 of them due to the
> addition of pt_2_seq_both; both MSN and IP-ID can be reduced by 1 bit
> each) pt_2_seq_both: "110101"
>=20
>=20
> Note that this is just an example of a solution. Any proposal which
> handles this issue would be OK for me.
>=20
>=20
> 2) Section 6.8.3.1 says the following:   "The following packet formats
> exist **exclusively** for profiles 0x101 and 0x107" and then
> later also
> "The following packet formats exist **exclusively** for profiles
> 0x102,0x103, 0x104 and 0x108". But, some of the packet
> formats (such as
> pt_1_seq_id) are defined under both of these sentences.
>=20

Ok, I can agree the text could use some polishing :)
The point of the text is that the RTP-based profiles contain different
fields
then the others, but I could have phrased it better. Will think of
something
for the next revision.

> 3) ts_stride_value and time_stride_value are defined as:
>=20
>          ts_stride_value: This parameter is set to a
> user-selected value
>          that is the expected increase in the RTP Timestamp between
>          consecutive sequence numbers.  See also Section 6.6.8.
>=20
>          time_stride_value: This parameter is set to a user-selected
>          value that is the expected inter-arrival time between
>          consecutive packets for this flow.  See also Section 6.6.9.
>=20
> Are these intended to be user-selected values?

Yes, they are "user-selected" the same way they are that in 3095 in the
sense that they can be set to any value independent of what is in the
packet
stream (of course, there are just a couple of values that would make for
efficient compression). But maybe the word "user" is not the best word
to
use here, since it might be interpreted by some as if it is set up
during
configuration while it is *usually* set by inspecting the flow over
time.

Do you have any suggestion for a better phrasing?

/Kristofer

>=20
> Thanks,
> Rohit
>=20
>> -----Original Message-----
>> From: Kristofer Sandlund (LU/EAB)
> [mailto:kristofer.sandlund@ericsson.com]
>> Sent: Thursday, May 24, 2007 11:48 PM
>> To: rohc@ietf.org
>> Cc: Ghyslain Pelletier (LU/EAB)
>> Subject: [rohc] Update of ROHCv2 profiles draft
>>=20
>> Hi all,
>>=20
>> we have just sent in an update of the profiles draft which
>> mostly contains the changes discussed on the list towards the end of
>> last year. The draft should be announced within the next couple of
>> days as usual. Here is a list of changes since the previous revision.
>>=20
>> Changes in the FN code (packet formats):
>> - Lots of minor typos and smaller bug fixes related to FN syntax
>> - Fixes to scaled encoding and MSN handling
>> - Style-related cleanup to make the code more consistent
>> - Addition of many ENFORCE-statements to make the code more formally
>> correct=20
>> - Added a co_repair format for all profiles which is bitwaise very
>>   similar to co_common (so it should be very easy to implement), but
>>   has the possibility of sending all LSB-fields as
>>   uncompressed (should be seen as an IR-DYN replacement)
>> - Repair-specific irregular chain items added in order to make
>>   context repair for outer headers, including extension headers, but
>>   have LSB encoded fields sent uncompressed
>> - Optimized the co_common formats with
> "meta-discriminators" in order
> to
>>   reduce the flag overhead
>> - Added timer-based compression (this still needs to be added to the
>>   text where we just have a placeholder section for now)
>> - Fixed ESP static chain so encrypted and null-encrypted static
>>   chains can be discriminated from each other
>> - LSB-offsets are made much more consistent throughput the formats
>> - Header chain termination for IP-only profile (different static
>>   chain items if this is the terminating IP header)
>>=20
>> Changes to the text:
>> - Text on scaled encoding re-written and improved
>> - External arguments to the FN code section added
>> - Design rationale for the packet formats section added
>> - Text on state logic improved
>> - Clarifications around the unidirectional/bidirectional operation
>> - Added new feedback option for requesting update of control fields=20
>> (to be used with NACKs)=20
>> - Update of Appendix A (field classifications) which was previously
>>   imported from RFC3095 and contained a bunch of errors
>> - Removed Appendix A.3
>> - CRC algorithm and demo are now in framework, so it is removed from
>> this draft=20
>> - Added section about handling reordering
>> - Removal of the IR-DYN packet format from all these profiles
>>=20
>> The draft still needs some more work in a few areas, but we are
>> getting closer to finalizing this work now, so we would be very
>> grateful=20
>> if you read and comment on this draft so that it contains what you
>> expect it to.=20
>>=20
>> Thanks to all the people who contributed on the list to the
>> discussions on this draft!=20
>>=20
>> /Kristofer & Ghyslain
>>=20
>> _______________________________________________
>> Rohc mailing list
>> Rohc@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rohc

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



From rohc-bounces@ietf.org Wed Jun 13 12:44:42 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyVxa-0002jI-8X; Wed, 13 Jun 2007 12:44:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyVxY-0002it-Lw
	for rohc@ietf.org; Wed, 13 Jun 2007 12:44:40 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyVxY-0002aI-4I
	for rohc@ietf.org; Wed, 13 Jun 2007 12:44:40 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l5DGiaBY017803
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Jun 2007 09:44:36 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l5DGiZBq022425; Wed, 13 Jun 2007 09:44:36 -0700
Received: from NAEX09.na.qualcomm.com ([10.46.56.82]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 09:44:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Update of ROHCv2 profiles draft
Date: Wed, 13 Jun 2007 09:44:34 -0700
Message-ID: <ECA90F8A96A62E4EB8D9E25E5140F7560423EBA2@NAEX09.na.qualcomm.com>
In-Reply-To: <A91F30A632473A47B40C18D2B107CA6F04168EE7@esealmw105.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Update of ROHCv2 profiles draft
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQN+XxugAAo0aLAAR7MQQA==
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
	<ECA90F8A96A62E4EB8D9E25E5140F7560423E95C@NAEX09.na.qualcomm.com>
	<A91F30A632473A47B40C18D2B107CA6F04168EE7@esealmw105.eemea.ericsson.se>
From: "Kapoor, Rohit" <rkapoor@qualcomm.com>
To: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 13 Jun 2007 16:44:35.0850 (UTC)
	FILETIME=[203A0EA0:01C7ADDA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Kristofer,

Thanks for the reply. Pls see some comments below.


> -----Original Message-----
> From: Kristofer Sandlund (LU/EAB)
[mailto:kristofer.sandlund@ericsson.com]
> Sent: Monday, June 11, 2007 11:44 PM
> To: Kapoor, Rohit; rohc@ietf.org
> Cc: Ghyslain Pelletier (LU/EAB)
> Subject: RE: [rohc] Update of ROHCv2 profiles draft
>=20
> Hi Rohit,
>=20
> thanks for your comments. My answers inline.
>=20
> Kapoor, Rohit <mailto:rkapoor@qualcomm.com> wrote on den 12 juni 2007
> 04:02 :
>=20
> > Kristofer, Ghyslain,
> >
> > Thanks for the updated draft. Pls find few comments below:
> >
> > 1) Regarding use of timer-based compression in pt_1_seq_ts, I had
> > brought up this issue earlier, but haven't seen any
> > resolution for it in
> > the current draft.
>=20
> Since we hadn't decided what to do on that last time we discussed it,
I
> left the following TODO in the draft:
>=20
> // TODO:
> // - PT_0/PT_1 packets? Use "tbc-optimized" or "msn-optimized"
>=20
> So it was not forgotten, we just preferred to get out a new revision
of
> the
> draft as soon as we could and let us continue the discussion later.
>=20
> I will give a more detailed answer on this issue later this week or
next
> week

<Rohit> OK, look forward to your answer.

>=20
> > 3) ts_stride_value and time_stride_value are defined as:
> >
> >          ts_stride_value: This parameter is set to a
> > user-selected value
> >          that is the expected increase in the RTP Timestamp between
> >          consecutive sequence numbers.  See also Section 6.6.8.
> >
> >          time_stride_value: This parameter is set to a user-selected
> >          value that is the expected inter-arrival time between
> >          consecutive packets for this flow.  See also Section 6.6.9.
> >
> > Are these intended to be user-selected values?
>=20
> Yes, they are "user-selected" the same way they are that in 3095 in
the
> sense that they can be set to any value independent of what is in the
> packet
> stream (of course, there are just a couple of values that would make
for
> efficient compression). But maybe the word "user" is not the best word
> to
> use here, since it might be interpreted by some as if it is set up
> during
> configuration while it is *usually* set by inspecting the flow over
> time.

<Rohit> How about using RFC 3095-like language?

      TS_STRIDE: Predicted increment/decrement of the RTP Timestamp
      field when it changes.
=20
      TIME_STRIDE: Predicted time interval in milliseconds between
      changes in the RTP Timestamp.


Thanks,
Rohit

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



From rohc-bounces@ietf.org Fri Jun 15 01:05:49 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz40K-0005hZ-J7; Fri, 15 Jun 2007 01:05:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz40J-0005hT-KK
	for rohc@ietf.org; Fri, 15 Jun 2007 01:05:47 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz40I-0002i8-8Y
	for rohc@ietf.org; Fri, 15 Jun 2007 01:05:47 -0400
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l5F55fNw020415
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 14 Jun 2007 22:05:42 -0700
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l5F556x6007155;
	Thu, 14 Jun 2007 22:05:06 -0700 (PDT)
Received: from NAEX15.na.qualcomm.com ([10.47.5.244]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 22:05:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Jun 2007 22:05:04 -0700
Message-ID: <C2E0B39A89E6BE4FAFA874758D621CF4011CDD70@NAEX15.na.qualcomm.com>
In-Reply-To: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on ROHCv2 profiles draft 
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQQKjVVg
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
From: "Jin, Haipeng" <haipengj@qualcomm.com>
To: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 15 Jun 2007 05:05:06.0332 (UTC)
	FILETIME=[BD4555C0:01C7AF0A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
Subject: [rohc] Comments on ROHCv2 profiles draft 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi, Kristofer and Ghyslain,

Great effort in updating the profile draft!

I have the following comments:
1. Decompressor state:
I remember we had some discussion on the state diagram in section 5.3.1.
It is not possible to transit from NC to FC directly. The main reason is
that IR-DYN carries CRC-8 but does not verify the entire context so a
CRC-7 packet such as co-common or p0-crc7 is needed as an intermediate
step. Now that IR-DYN is removed, I would propose to change the stage
diagram to allow direct transition from NC to FC with CRC-8
verification. I still don't see how the two-step upward transition helps
to make the decompression process more robust. Actually, it may make
things worse in some cases, for example, if the compressor sends a
couple of IRs, followed by a couple of p0-crc7 and then a number of crc3
packets. If the p0-crc7 packets are erases and the decompressor stays in
IC, all the subsequent crc3 packets will be dropped even without
decompression attempt when those packets can actually be decompressed
successfully. This is even worse if the compressor is working in
non-feedback mode.

Another question I have regards decompressor state is: in section
5.3.1.3, the text says "The decompressor moves back to the IC state if
it assumes context damage, and back to the NC state if it assumes static
context damage." about downward transition, this is not consistent with
the diagram. So what is the real intend here? Are you thinking to allow
direct transition back from FC to NC?

2. IP-ID behavior

The new profile only allows sequential behavior to inner IP-ID. For all
outer headers, IP-IDs are assumed to be either constant or random. This
means that in two-level IP headers (e.g. MIP) case which may be a common
use case in wireless networks, the compressor may not be able to
compress the packet as efficiently as in RFC3095. It would be great if
you can add an sequential indicator for the outer header to handle at
least this case.

3. Packet formats

I have similar concerns as Rohit on the packet formats and bit number
allocations and will try to follow your response on the existing thread.

That is for now.=20

Best Regards,
Haipeng
=20


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



From rohc-bounces@ietf.org Fri Jun 15 04:25:42 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz77g-00005s-UD; Fri, 15 Jun 2007 04:25:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz77g-00005n-Jj
	for rohc@ietf.org; Fri, 15 Jun 2007 04:25:36 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz77f-0001G2-Q3
	for rohc@ietf.org; Fri, 15 Jun 2007 04:25:36 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	293CA211A1; Fri, 15 Jun 2007 10:25:35 +0200 (CEST)
X-AuditID: c1b4fb3e-b1036bb0000007e1-ff-46724cffbdf2
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1009F207BF; Fri, 15 Jun 2007 10:25:35 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Jun 2007 10:25:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Jun 2007 10:25:33 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F041B8CBA@esealmw105.eemea.ericsson.se>
In-Reply-To: <C2E0B39A89E6BE4FAFA874758D621CF4011CDD70@NAEX15.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on ROHCv2 profiles draft 
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQQKjVVgABhcy+A=
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
	<C2E0B39A89E6BE4FAFA874758D621CF4011CDD70@NAEX15.na.qualcomm.com>
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: "Jin, Haipeng" <haipengj@qualcomm.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 15 Jun 2007 08:25:34.0296 (UTC)
	FILETIME=[BE7EFD80:01C7AF26]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
Subject: [rohc] RE: Comments on ROHCv2 profiles draft 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Haipeng,

comments inline as usual.

Jin, Haipeng <mailto:haipengj@qualcomm.com> wrote on den 15 juni 2007
07:05 :

> Hi, Kristofer and Ghyslain,
>=20
> Great effort in updating the profile draft!
>=20
> I have the following comments:
> 1. Decompressor state:
> I remember we had some discussion on the state diagram in
> section 5.3.1.
> It is not possible to transit from NC to FC directly. The
> main reason is
> that IR-DYN carries CRC-8 but does not verify the entire context so a
> CRC-7 packet such as co-common or p0-crc7 is needed as an intermediate
> step. Now that IR-DYN is removed, I would propose to change the stage
> diagram to allow direct transition from NC to FC with CRC-8
> verification.

The IR packet has the same potential issue as the IR-DYN packet, i.e.
that it may omit control fields from the packet and these do not get
verified by the CRC-8. Therefore, I think the 2-step transition is still
a valid choice.=20
The alternative is still to try to beef up the IR
by either adding an extra CRC or mandating the presence of control
fields
etc, but I think that's going to be a lot more "patch-work" (and more
overhead) than having a 2-step transition which is simple. And the cost
is quite minimal since you're not going to be in NC state very often.

I would have liked to change the coverage of the existing CRC-8 for
the IR, but since that is defined by the framework, that's not an
option,
unfortunately.

Anyway, note that section 5 is informative, so if an implementation
wants to do something else such as a one-step approach, that would not
be illegal, although it is not the main recommendation of this spec

> I still don't see how the two-step upward
> transition helps
> to make the decompression process more robust. Actually, it may make
> things worse in some cases, for example, if the compressor sends a
> couple of IRs, followed by a couple of p0-crc7 and then a
> number of crc3
> packets. If the p0-crc7 packets are erases and the
> decompressor stays in
> IC, all the subsequent crc3 packets will be dropped even without
> decompression attempt when those packets can actually be decompressed
> successfully. This is even worse if the compressor is working in
> non-feedback mode.=20

As stated above, there's a larger chance of things going wrong with
the one-step approach. And since we're using the optimistic approach,
the chance of losing all pt-0-crc7 (as in your example above) that you
send should be very small, otherwise the compressor has chosen a bad=20
optimistic approach value.

>=20
> Another question I have regards decompressor state is: in section
> 5.3.1.3, the text says "The decompressor moves back to the IC state if
> it assumes context damage, and back to the NC state if it
> assumes static
> context damage." about downward transition, this is not
> consistent with
> the diagram. So what is the real intend here? Are you
> thinking to allow
> direct transition back from FC to NC?

Agreed, the text and the picture are inconsistent. I would probably
prefer adding an extra arrow to the picture, but I think the other
option is also viable. What's you opinion?

>=20
> 2. IP-ID behavior
>=20
> The new profile only allows sequential behavior to inner
> IP-ID. For all
> outer headers, IP-IDs are assumed to be either constant or
> random. This
> means that in two-level IP headers (e.g. MIP) case which may
> be a common
> use case in wireless networks, the compressor may not be able to
> compress the packet as efficiently as in RFC3095. It would be great if
> you can add an sequential indicator for the outer header to handle at
> least this case.=20

Here, I refer to the motivations in the now-expired requirements draft
that this WG agreed on for ROHCv2, see section 2.6 of this one:
http://tools.ietf.org/html/draft-ietf-rohc-rfc3095bis-improvements-03

So I would be very much against changing this since that adds a lot
of complexity and it gives a very minimal gain and only for a very
small subset of tunneled packets.

>=20
> 3. Packet formats
>=20
> I have similar concerns as Rohit on the packet formats and bit number
> allocations and will try to follow your response on the
> existing thread.

Ok, since that's a bit more complex issue, I will get back to that when
I have had more time to prepare a comprehensive answer and re-read all
the old discussions we had last year.

BR,
   Kristofer

>=20
> That is for now.
>=20
> Best Regards,
> Haipeng

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



From rohc-bounces@ietf.org Fri Jun 15 09:51:59 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzCDW-0005Oz-2I; Fri, 15 Jun 2007 09:51:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzCDV-0005Ou-I5
	for rohc@ietf.org; Fri, 15 Jun 2007 09:51:57 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzCDU-0000V2-3Y
	for rohc@ietf.org; Fri, 15 Jun 2007 09:51:57 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l5FDpmwN000624
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 15 Jun 2007 06:51:48 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l5FDpl20005899; Fri, 15 Jun 2007 06:51:47 -0700
Received: from NAEX09.na.qualcomm.com ([10.46.56.82]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Jun 2007 06:51:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [rohc] RE: Comments on ROHCv2 profiles draft 
Date: Fri, 15 Jun 2007 06:51:47 -0700
Message-ID: <ECA90F8A96A62E4EB8D9E25E5140F75604267CA5@NAEX09.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on ROHCv2 profiles draft 
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQQKjVVgABhcy+AAC5nGQA==
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se><C2E0B39A89E6BE4FAFA874758D621CF4011CDD70@NAEX15.na.qualcomm.com>
	<A91F30A632473A47B40C18D2B107CA6F041B8CBA@esealmw105.eemea.ericsson.se>
From: "Kapoor, Rohit" <rkapoor@qualcomm.com>
To: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>,
	"Jin, Haipeng" <haipengj@qualcomm.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 15 Jun 2007 13:51:47.0679 (UTC)
	FILETIME=[512436F0:01C7AF54]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0461357329=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0461357329==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7AF54.50D24F6A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7AF54.50D24F6A
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



<Kristofer> Anyway, note that section 5 is informative, so if an =
implementation
wants to do something else such as a one-step approach, that would not
be illegal, although it is not the main recommendation of this spec


Since Section 5 is informative, I am assuming that the decompressor =
state transition (i.e., NC -> IC -> FC) is also informative. Also, there =
is no requirement on the compressor to send packets according to this =
transition of the decompressor.

As an example, say the decompressor implemements a 2-state transition as =
above. Say, the compressor sends a few IRs followed by a UO-0. The IRs =
will cause the decompressor to transition from NC to IC, but the UO-O =
will be received when the decompressor is in IC, and will cause a =
failure.

If most decompressor implementations follow the recommended 2-step state =
transition diagram but there is no requirement (or recommendation) on =
the compressor to send a CRC-7 packet after sending IRs, isn't this =
broken?

Thanks,
Rohit

------_=_NextPart_001_01C7AF54.50D24F6A
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: [rohc] RE: Comments on ROHCv2 profiles draft </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>

<P><FONT SIZE=3D2>&lt;Kristofer&gt; Anyway, note that section 5 is =
informative, so if an implementation<BR>
wants to do something else such as a one-step approach, that would =
not<BR>
be illegal, although it is not the main recommendation of this spec<BR>
<BR>
<BR>
Since Section 5 is informative, I am assuming that the decompressor =
state transition (i.e., NC -&gt; IC -&gt; FC) is also informative. Also, =
there is no requirement on the compressor to send packets according to =
this transition of the decompressor.<BR>
<BR>
As an example, say the decompressor implemements a 2-state transition as =
above. Say, the compressor sends a few IRs followed by a UO-0. The IRs =
will cause the decompressor to transition from NC to IC, but the UO-O =
will be received when the decompressor is in IC, and will cause a =
failure.<BR>
<BR>
If most decompressor implementations follow the recommended 2-step state =
transition diagram but there is no requirement (or recommendation) on =
the compressor to send a CRC-7 packet after sending IRs, isn't this =
broken?<BR>
<BR>
Thanks,<BR>
Rohit</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7AF54.50D24F6A--


--===============0461357329==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0461357329==--




From rohc-bounces@ietf.org Fri Jun 15 14:03:52 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzG9G-0006WS-TQ; Fri, 15 Jun 2007 14:03:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzG9D-0006TK-Me; Fri, 15 Jun 2007 14:03:47 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HzG9C-0000vU-9a; Fri, 15 Jun 2007 14:03:47 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l5FI3jIe001846; 
	Fri, 15 Jun 2007 11:03:45 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l5FI3jxf001845;
	Fri, 15 Jun 2007 11:03:45 -0700
Date: Fri, 15 Jun 2007 11:03:45 -0700
Message-Id: <200706151803.l5FI3jxf001845@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: rohc@ietf.org, rfc-editor@rfc-editor.org
Subject: [rohc] RFC 4896 on Signaling Compression (SigComp) Corrections and
	Clarifications
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4896

        Title:      Signaling Compression (SigComp) Corrections and 
                    Clarifications 
        Author:     A. Surtees, M. West,
                    A.B. Roach
        Status:     Standards Track
        Date:       June 2007
        Mailbox:    abigail.surtees@roke.co.uk, 
                    mark.a.west@roke.co.uk, 
                    adam@estacado.net
        Pages:      28
        Characters: 58435
        Updates:    RFC3320, RFC3321, RFC3485
        See-Also:   

        I-D Tag:    draft-ietf-rohc-sigcomp-impl-guide-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4896.txt

This document describes common misinterpretations and some
ambiguities in the Signaling Compression Protocol (SigComp), and
offers guidance to developers to resolve any resultant problems.
SigComp defines a scheme for compressing messages generated by
application protocols such as the Session Initiation Protocol (SIP).
This document updates the following RFCs: RFC 3320, RFC 3321, and RFC
3485.  [STANDARDS TRACK]

This document is a product of the Robust Header Compression
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



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



From rohc-bounces@ietf.org Mon Jun 18 08:07:44 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0G1H-00088W-2m; Mon, 18 Jun 2007 08:07:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0G1F-00088K-N2
	for rohc@ietf.org; Mon, 18 Jun 2007 08:07:41 -0400
Received: from av11-1-sn2.hy.skanova.net ([81.228.8.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0G1E-0001Kb-Dw
	for rohc@ietf.org; Mon, 18 Jun 2007 08:07:41 -0400
Received: by av11-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 9356838059; Mon, 18 Jun 2007 14:07:39 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av11-1-sn2.hy.skanova.net (Postfix) with ESMTP id 793B938056
	for <rohc@ietf.org>; Mon, 18 Jun 2007 14:07:39 +0200 (CEST)
Received: from jymden3 (90-227-154-194-no14.tbcn.telia.com [90.227.154.194])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with SMTP id 57DD337E59
	for <rohc@ietf.org>; Mon, 18 Jun 2007 14:07:39 +0200 (CEST)
Message-ID: <007701c7b1a1$480a6400$8700a8c0@jymden3>
From: "Lars-Erik Jonsson" <larsman@home.se>
To: <rohc@ietf.org>
Date: Mon, 18 Jun 2007 14:07:45 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [rohc] New milestone dates (and adjusted milestones) for ROHC
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

ROHCers,

Please review the updated list of still not completed WG milestones.

BR
/L-E


Aug 2007  RObust Header Compression over IPsec (RoHCoIPsec)
                  submitted to IESG for publication as Informational
Oct 2007  Revised ROHC IP/UDP/RTP profiles submitted to IESG
                  for publication as Proposed Standard
Oct 2007  IKEv2 extensions for RoHCoIPsec submitted to IESG for
                  publication as Proposed Standard
Oct 2007  IPsec Extensions for RoHCoIPsec with RObust Header
                 Compression Protocol Number Registration submitted to
                 IESG for publication as Proposed Standard
Nov 2007  Recharter of WG to develop additional profiles if needed,
                 or possible additional compression schemes. Consideration
                 of concluding the working group.




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



From rohc-bounces@ietf.org Mon Jun 18 21:09:44 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0SE2-0007zB-4G; Mon, 18 Jun 2007 21:09:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0SE1-0007z6-BJ
	for rohc@ietf.org; Mon, 18 Jun 2007 21:09:41 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0SE0-0000aO-OD
	for rohc@ietf.org; Mon, 18 Jun 2007 21:09:41 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l5J19akO032679
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 18 Jun 2007 18:09:37 -0700
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l5J19XaW021508; Mon, 18 Jun 2007 18:09:36 -0700
Received: from NAEX15.na.qualcomm.com ([10.47.5.244]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Jun 2007 18:09:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] RE: Comments on ROHCv2 profiles draft 
Date: Mon, 18 Jun 2007 18:09:32 -0700
Message-ID: <C2E0B39A89E6BE4FAFA874758D621CF4012380FF@NAEX15.na.qualcomm.com>
In-Reply-To: <A91F30A632473A47B40C18D2B107CA6F041B8CBA@esealmw105.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] RE: Comments on ROHCv2 profiles draft 
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQQKjVVgABhcy+AAiTYXUA==
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se><C2E0B39A89E6BE4FAFA874758D621CF4011CDD70@NAEX15.na.qualcomm.com>
	<A91F30A632473A47B40C18D2B107CA6F041B8CBA@esealmw105.eemea.ericsson.se>
From: "Jin, Haipeng" <haipengj@qualcomm.com>
To: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 19 Jun 2007 01:09:33.0284 (UTC)
	FILETIME=[7EF85A40:01C7B20E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi, Kristofer,

Thanks for your reply, please see more comments following yours.

-----Original Message-----
From: Kristofer Sandlund (LU/EAB)
[mailto:kristofer.sandlund@ericsson.com]=20
Sent: Friday, June 15, 2007 1:26 AM
To: Jin, Haipeng; rohc@ietf.org
Cc: Ghyslain Pelletier (LU/EAB)
Subject: [rohc] RE: Comments on ROHCv2 profiles draft=20

Hi Haipeng,

comments inline as usual.

Jin, Haipeng <mailto:haipengj@qualcomm.com> wrote on den 15 juni 2007
07:05 :

> Hi, Kristofer and Ghyslain,
>=20
> Great effort in updating the profile draft!
>=20
> I have the following comments:
> 1. Decompressor state:
> I remember we had some discussion on the state diagram in
> section 5.3.1.
> It is not possible to transit from NC to FC directly. The
> main reason is
> that IR-DYN carries CRC-8 but does not verify the entire context so a
> CRC-7 packet such as co-common or p0-crc7 is needed as an intermediate
> step. Now that IR-DYN is removed, I would propose to change the stage
> diagram to allow direct transition from NC to FC with CRC-8
> verification.

The IR packet has the same potential issue as the IR-DYN packet, i.e.
that it may omit control fields from the packet and these do not get
verified by the CRC-8. Therefore, I think the 2-step transition is still
a valid choice.=20
The alternative is still to try to beef up the IR
by either adding an extra CRC or mandating the presence of control
fields
etc, but I think that's going to be a lot more "patch-work" (and more
overhead) than having a 2-step transition which is simple. And the cost
is quite minimal since you're not going to be in NC state very often.

I would have liked to change the coverage of the existing CRC-8 for
the IR, but since that is defined by the framework, that's not an
option,
unfortunately.

[Haipeng] The framework only says the coverage of CRC-8 for IR is
profile-dependent and recommends what is the minimal that need to be
covered. If you think there are fields that need to be covered in
RTP/UDP/... profiles, wouldn't it be great to list them out and have a
discussion here and maybe make the coverage mandatory in these profiles?

Anyway, note that section 5 is informative, so if an implementation
wants to do something else such as a one-step approach, that would not
be illegal, although it is not the main recommendation of this spec

[Haipeng] The problem is that the text gives the impression that only
two-step transition is allowed. For example, if no CRC7 is received
in-between crc8 and crc3 packets, the decompressor will not attempt
decompression on those crc3 packets. If both options are allowed, then
it would be great if the text can be clarified to convey the idea. I
understand that it might be hard to express all possibilities in the
diagram before making it appear messy, maybe an alternative is to make
the diagram simpler. Instead of showing all transition possibilities
which are not currently done as you pointed out, the diagram can show
only the three available states and general transition connections. The
text can be enhanced to capture all the conditions. =20

> I still don't see how the two-step upward
> transition helps
> to make the decompression process more robust. Actually, it may make
> things worse in some cases, for example, if the compressor sends a
> couple of IRs, followed by a couple of p0-crc7 and then a
> number of crc3
> packets. If the p0-crc7 packets are erases and the
> decompressor stays in
> IC, all the subsequent crc3 packets will be dropped even without
> decompression attempt when those packets can actually be decompressed
> successfully. This is even worse if the compressor is working in
> non-feedback mode.=20

As stated above, there's a larger chance of things going wrong with
the one-step approach. And since we're using the optimistic approach,
the chance of losing all pt-0-crc7 (as in your example above) that you
send should be very small, otherwise the compressor has chosen a bad=20
optimistic approach value.

[Haipeng] The reason I gave this example is because in the past email
threads, similar examples (IR re-ordering followed by crc3 packets) were
used to show why two-step transition is needed. I agree that if the
compressor can choose a good OAA value, then neither that example nor my
example will be a concern. One-step approach won't have problem either.

>=20
> Another question I have regards decompressor state is: in section
> 5.3.1.3, the text says "The decompressor moves back to the IC state if
> it assumes context damage, and back to the NC state if it
> assumes static
> context damage." about downward transition, this is not
> consistent with
> the diagram. So what is the real intend here? Are you
> thinking to allow
> direct transition back from FC to NC?

Agreed, the text and the picture are inconsistent. I would probably
prefer adding an extra arrow to the picture, but I think the other
option is also viable. What's you opinion?

[Haipeng] RFC3095 only discussed two-step downward transition, " Only
when decompression of several packets sent in the FO state fails in the
"Static Context" state will the decompressor go all the way back to the
"No Context" state.". I don't see much problem allowing transition back
from FC to NC, but it would be great if there are some general
guidelines on what might be the criteria for the decompressor to
determine whether to go from FC to IC or from FC to NC. Do you have some
scenarios in mind?

>=20
> 2. IP-ID behavior
>=20
> The new profile only allows sequential behavior to inner
> IP-ID. For all
> outer headers, IP-IDs are assumed to be either constant or
> random. This
> means that in two-level IP headers (e.g. MIP) case which may
> be a common
> use case in wireless networks, the compressor may not be able to
> compress the packet as efficiently as in RFC3095. It would be great if
> you can add an sequential indicator for the outer header to handle at
> least this case.=20

Here, I refer to the motivations in the now-expired requirements draft
that this WG agreed on for ROHCv2, see section 2.6 of this one:
http://tools.ietf.org/html/draft-ietf-rohc-rfc3095bis-improvements-03

So I would be very much against changing this since that adds a lot
of complexity and it gives a very minimal gain and only for a very
small subset of tunneled packets.

[Haipeng] I would be careful in saying that tunneled packets belong to a
very small subset. MIP is a mobility management mechanism that is used
widely. Tunnel packets with two levels of headers are common if CCoA
mode of operation is used and it is important for ROHC to handle them
efficiently.

[Haipeng] In addition, the text in the expired requirements draft says
that it is unrealistic that the outer IP-ID can be compressed
sequentially. This is not true either. There are actually
implementations where the tunneling endpoints set outer IP-ID to the
same as inner IP-ID sequentially to allow efficient compression using
3095. If the same stacks are used for updated profile, the IP-ID will
not be compressed efficiently.


Best Regards,
Haipeng

>=20
> 3. Packet formats
>=20
> I have similar concerns as Rohit on the packet formats and bit number
> allocations and will try to follow your response on the
> existing thread.

Ok, since that's a bit more complex issue, I will get back to that when
I have had more time to prepare a comprehensive answer and re-read all
the old discussions we had last year.

BR,
   Kristofer

>=20
> That is for now.
>=20
> Best Regards,
> Haipeng

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

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



From rohc-bounces@ietf.org Tue Jun 19 02:16:44 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0X18-0004R2-Rg; Tue, 19 Jun 2007 02:16:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0X18-0004Ov-4W
	for rohc@ietf.org; Tue, 19 Jun 2007 02:16:42 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0X16-0003Gc-Fq
	for rohc@ietf.org; Tue, 19 Jun 2007 02:16:42 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	864D62071E; Tue, 19 Jun 2007 08:16:35 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-c3-467774c31aa4
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	645762067D; Tue, 19 Jun 2007 08:16:35 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 08:16:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] RE: Comments on ROHCv2 profiles draft 
Date: Tue, 19 Jun 2007 08:16:34 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F042123FE@esealmw105.eemea.ericsson.se>
In-Reply-To: <ECA90F8A96A62E4EB8D9E25E5140F75604267CA5@NAEX09.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] RE: Comments on ROHCv2 profiles draft 
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQQKjVVgABhcy+AAC5nGQAC5i5Nw
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se><C2E0B39A89E6BE4FAFA874758D621CF4011CDD70@NAEX15.na.qualcomm.com>
	<A91F30A632473A47B40C18D2B107CA6F041B8CBA@esealmw105.eemea.ericsson.se>
	<ECA90F8A96A62E4EB8D9E25E5140F75604267CA5@NAEX09.na.qualcomm.com>
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: "Kapoor, Rohit" <rkapoor@qualcomm.com>,
	"Jin, Haipeng" <haipengj@qualcomm.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 19 Jun 2007 06:16:34.0991 (UTC)
	FILETIME=[6329C3F0:01C7B239]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Rohit,

you are right, there is probably some text missing from section 6 which
makes some normative statements about this, it must have fallen out of
the draft at some point :)
If we stick with the two-step approach for the next revision, I think
we should fix that. Thanks for pointing it out.
See also separate mail about the states which I will send in a couple
of minutes time.

/Kristofer

Kapoor, Rohit <mailto:rkapoor@qualcomm.com> wrote on den 15 juni 2007
15:52 :

> <Kristofer> Anyway, note that section 5 is informative, so if
> an implementation
> wants to do something else such as a one-step approach, that would not
> be illegal, although it is not the main recommendation of this spec
>=20
>=20
> Since Section 5 is informative, I am assuming that the
> decompressor state transition (i.e., NC -> IC -> FC) is also
> informative. Also, there is no requirement on the compressor
> to send packets according to this transition of the decompressor.
>=20
> As an example, say the decompressor implemements a 2-state
> transition as above. Say, the compressor sends a few IRs
> followed by a UO-0. The IRs will cause the decompressor to
> transition from NC to IC, but the UO-O will be received when
> the decompressor is in IC, and will cause a failure.
>=20
> If most decompressor implementations follow the recommended
> 2-step state transition diagram but there is no requirement
> (or recommendation) on the compressor to send a CRC-7 packet
> after sending IRs, isn't this broken?
>=20
> Thanks,
> Rohit

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



From rohc-bounces@ietf.org Tue Jun 19 02:48:37 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0XW1-0001j4-Fe; Tue, 19 Jun 2007 02:48:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0XVz-0001iv-J6
	for rohc@ietf.org; Tue, 19 Jun 2007 02:48:35 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0XVy-0001xJ-Dt
	for rohc@ietf.org; Tue, 19 Jun 2007 02:48:35 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A57F420090; Tue, 19 Jun 2007 08:48:33 +0200 (CEST)
X-AuditID: c1b4fb3e-b0835bb0000007e1-52-46777c41984c
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	86F48201A3; Tue, 19 Jun 2007 08:48:33 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 08:48:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] RE: Comments on ROHCv2 profiles draft 
Date: Tue, 19 Jun 2007 08:48:31 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F04212435@esealmw105.eemea.ericsson.se>
In-Reply-To: <C2E0B39A89E6BE4FAFA874758D621CF4012380FF@NAEX15.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] RE: Comments on ROHCv2 profiles draft 
Thread-Index: AceemKzW4kh3p+4+SgCvFk/ihGdinQQKjVVgABhcy+AAiTYXUAA7vAHQ
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se><C2E0B39A89E6BE4FAFA874758D621CF4011CDD70@NAEX15.na.qualcomm.com>
	<A91F30A632473A47B40C18D2B107CA6F041B8CBA@esealmw105.eemea.ericsson.se>
	<C2E0B39A89E6BE4FAFA874758D621CF4012380FF@NAEX15.na.qualcomm.com>
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: "Jin, Haipeng" <haipengj@qualcomm.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 19 Jun 2007 06:48:33.0376 (UTC)
	FILETIME=[DA9C1600:01C7B23D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Haipeng,

thanks for the feedback, more comments inline.

Jin, Haipeng <mailto:haipengj@qualcomm.com> wrote on den 19 juni 2007
03:10 :

> Hi, Kristofer,
>=20
> Thanks for your reply, please see more comments following yours.
>=20
> -----Original Message-----
> From: Kristofer Sandlund (LU/EAB)
> [mailto:kristofer.sandlund@ericsson.com]
> Sent: Friday, June 15, 2007 1:26 AM
> To: Jin, Haipeng; rohc@ietf.org
> Cc: Ghyslain Pelletier (LU/EAB)
> Subject: [rohc] RE: Comments on ROHCv2 profiles draft
>=20
> Hi Haipeng,
>=20
> comments inline as usual.
>=20
> Jin, Haipeng <mailto:haipengj@qualcomm.com> wrote on den 15 juni 2007
> 07:05 :=20
>=20
>> Hi, Kristofer and Ghyslain,
>>=20
>> Great effort in updating the profile draft!
>>=20
>> I have the following comments:
>> 1. Decompressor state:
>> I remember we had some discussion on the state diagram in
>> section 5.3.1.
>> It is not possible to transit from NC to FC directly. The
>> main reason is
>> that IR-DYN carries CRC-8 but does not verify the entire context so a
>> CRC-7 packet such as co-common or p0-crc7 is needed as an
>> intermediate step. Now that IR-DYN is removed, I would propose to
>> change the stage diagram to allow direct transition from NC to FC
>> with CRC-8 verification.
>=20
> The IR packet has the same potential issue as the IR-DYN packet, i.e.
> that it may omit control fields from the packet and these do not get
> verified by the CRC-8. Therefore, I think the 2-step
> transition is still
> a valid choice.
> The alternative is still to try to beef up the IR
> by either adding an extra CRC or mandating the presence of control
> fields etc, but I think that's going to be a lot more "patch-work"
> (and more overhead) than having a 2-step transition which is simple.
> And the cost
> is quite minimal since you're not going to be in NC state very often.
>=20
> I would have liked to change the coverage of the existing CRC-8 for
> the IR, but since that is defined by the framework, that's not an
> option, unfortunately.
>=20
> [Haipeng] The framework only says the coverage of CRC-8 for IR is
> profile-dependent and recommends what is the minimal that need to be
> covered. If you think there are fields that need to be covered in
> RTP/UDP/... profiles, wouldn't it be great to list them out and have a
> discussion here and maybe make the coverage mandatory in
> these profiles?

When I read up on the old discussions we had on this, I found my old
email from last year
http://www1.ietf.org/mail-archive/web/rohc/current/msg04569.html=20
which proposed alternatives for how to handle IR and state transitions,
and the only reply I got on that was from Lars-Erik who supported the
two-step approach which is why this draft version still uses the
two-step
logic.

Could you check that one and give your opinions?

Btw, you're absolutely right that the IR CRC-8 coverage is=20
profile-dependent.
I don't know where I got the other idea from, so that possibility is
also listed in the referenced mail above :)

>=20
> Anyway, note that section 5 is informative, so if an implementation
> wants to do something else such as a one-step approach, that would not
> be illegal, although it is not the main recommendation of this spec
>=20
> [Haipeng] The problem is that the text gives the impression that only
> two-step transition is allowed. For example, if no CRC7 is received
> in-between crc8 and crc3 packets, the decompressor will not attempt
> decompression on those crc3 packets.
> If both options are allowed, then
> it would be great if the text can be clarified to convey the idea. I
> understand that it might be hard to express all possibilities in the
> diagram before making it appear messy, maybe an alternative is to make
> the diagram simpler. Instead of showing all transition possibilities
> which are not currently done as you pointed out, the diagram can show
> only the three available states and general transition
> connections. The
> text can be enhanced to capture all the conditions.

Yes, as Rohit pointed out, there is something missing here w.r.t. the
two-step transition. I'm not exactly sure on what's the best way to
fix this, but probably add some normative rules in section 6.

>=20
>> I still don't see how the two-step upward
>> transition helps
>> to make the decompression process more robust. Actually, it may make
>> things worse in some cases, for example, if the compressor sends a
>> couple of IRs, followed by a couple of p0-crc7 and then a
>> number of crc3
>> packets. If the p0-crc7 packets are erases and the
>> decompressor stays in
>> IC, all the subsequent crc3 packets will be dropped even without
>> decompression attempt when those packets can actually be decompressed
>> successfully. This is even worse if the compressor is working in
>> non-feedback mode.
>=20
> As stated above, there's a larger chance of things going wrong with
> the one-step approach. And since we're using the optimistic approach,
> the chance of losing all pt-0-crc7 (as in your example above) that you
> send should be very small, otherwise the compressor has chosen a bad
> optimistic approach value.=20
>=20
> [Haipeng] The reason I gave this example is because in the past email
> threads, similar examples (IR re-ordering followed by crc3
> packets) were
> used to show why two-step transition is needed. I agree that if the
> compressor can choose a good OAA value, then neither that
> example nor my
> example will be a concern. One-step approach won't have
> problem either.
>=20
>>=20
>> Another question I have regards decompressor state is: in section
>> 5.3.1.3, the text says "The decompressor moves back to the IC state
>> if it assumes context damage, and back to the NC state if it
>> assumes static
>> context damage." about downward transition, this is not
>> consistent with
>> the diagram. So what is the real intend here? Are you
>> thinking to allow
>> direct transition back from FC to NC?
>=20
> Agreed, the text and the picture are inconsistent. I would probably
> prefer adding an extra arrow to the picture, but I think the other
> option is also viable. What's you opinion?
>=20
> [Haipeng] RFC3095 only discussed two-step downward transition, " Only
> when decompression of several packets sent in the FO state
> fails in the
> "Static Context" state will the decompressor go all the way
> back to the
> "No Context" state.". I don't see much problem allowing
> transition back
> from FC to NC, but it would be great if there are some general
> guidelines on what might be the criteria for the decompressor to
> determine whether to go from FC to IC or from FC to NC. Do
> you have some
> scenarios in mind?

I prefer to leave it up to the decompressor to drop back to NC state
whenever it wants to, as long it has reason to suspect that it might
have lost synch of the static context. For example, if the decompressor
receives an IR packet with a bad CRC-8 followed by a CRC-3 packet,
it might guess that it doesn't have sufficient static context and drop
directly to NC.
I'm not saying it should do that always, but since all the downwards
transitions have to be based on some form of guessing by the
decompressor,
I think it is fine for the spec to say that it may be extra conservative
if it wants to.
But like I said, I can agree to either of the solutions.

Regarding more guidelines, do you think that section 5.3.2 is
insufficient
(we refer to that from the picture w.r.t. transitions)?
I think that has quite good guidelines for how to detect context damage,
but if you think it is insufficient, please give a text proposals that
we can discuss further.

>=20
>>=20
>> 2. IP-ID behavior
>>=20
>> The new profile only allows sequential behavior to inner
>> IP-ID. For all
>> outer headers, IP-IDs are assumed to be either constant or
>> random. This
>> means that in two-level IP headers (e.g. MIP) case which may
>> be a common
>> use case in wireless networks, the compressor may not be able to
>> compress the packet as efficiently as in RFC3095. It would be great
>> if you can add an sequential indicator for the outer header to
>> handle at least this case.
>=20
> Here, I refer to the motivations in the now-expired requirements draft
> that this WG agreed on for ROHCv2, see section 2.6 of this one:
> http://tools.ietf.org/html/draft-ietf-rohc-rfc3095bis-improvements-03
>=20
> So I would be very much against changing this since that adds a lot
> of complexity and it gives a very minimal gain and only for a very
> small subset of tunneled packets.
>=20
> [Haipeng] I would be careful in saying that tunneled packets
> belong to a
> very small subset. MIP is a mobility management mechanism that is used
> widely. Tunnel packets with two levels of headers are common if CCoA
> mode of operation is used and it is important for ROHC to handle them
> efficiently.=20
>=20
> [Haipeng] In addition, the text in the expired requirements draft says
> that it is unrealistic that the outer IP-ID can be compressed
> sequentially. This is not true either. There are actually
> implementations where the tunneling endpoints set outer IP-ID to the
> same as inner IP-ID sequentially to allow efficient compression using
> 3095. If the same stacks are used for updated profile, the IP-ID will
> not be compressed efficiently.

Sure, there are tunnels that use such a mechanism, but however you cut
it,
tunneled packets are a subset of all packets, and tunnels with the
behavior
you describe are a subset of tunnels which means this is a minority
of packets that are affected. And the cost of 0-2 bytes in those cases=20
seems small enough to avoid trying to optimize.

The outer-IPID mechanism of 3095 has really been despised by
implementers
due to its strange and over-complex logic and it would require quite a
large change in the current v2 packet formats to get that back.

So I think you will need very strong motivations to get that change into
the spec, especially with previous WG consensus of not doing this (also,
ROHC-TCP already follows the IPID logic used in v2).=20

/Kristofer

>=20
>=20
> Best Regards,
> Haipeng
>=20
>>=20
>> 3. Packet formats
>>=20
>> I have similar concerns as Rohit on the packet formats and bit number
>> allocations and will try to follow your response on the
>> existing thread.
>=20
> Ok, since that's a bit more complex issue, I will get back to
> that when
> I have had more time to prepare a comprehensive answer and re-read all
> the old discussions we had last year.
>=20
> BR,
>    Kristofer
>=20
>>=20
>> That is for now.
>>=20
>> Best Regards,
>> Haipeng
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

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



From rohc-bounces@ietf.org Wed Jun 20 02:50:31 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0u1N-0001TZ-UT; Wed, 20 Jun 2007 02:50:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0u1N-0001TU-N5
	for rohc@ietf.org; Wed, 20 Jun 2007 02:50:29 -0400
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0u1M-0002iL-9y
	for rohc@ietf.org; Wed, 20 Jun 2007 02:50:29 -0400
Received: from [192.168.101.51] ([192.168.101.51]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id l5K6oPAR028537
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 20 Jun 2007 08:50:27 +0200
Message-ID: <4678CE34.20200@effnet.com>
Date: Wed, 20 Jun 2007 08:50:28 +0200
From: Carl Knutsson <carl.knutsson@effnet.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061217)
MIME-Version: 1.0
To: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
In-Reply-To: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: rohc@ietf.org,
	"Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
Subject: [rohc] More comments on ROHCv2 profiles draft
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Kristofer, Ghyslain,

I found a small issue in the feedback section. copy-and-paste? I believe a more
detailed description of the msn decompression in the feedback packet would improve
the draft.

Section 6.9.2.1:
	"carrying a REJECT option MUST also carry a CRC option."

There are no CRC options in ROCHv2 and crc8 is always included in feedback-2 packets.

In Section 6.9.1, it would be nice with a more detailed description how the
compressor should decompress the msn in feedback packets. There are some more
places in the draft that describes the msn in feedback, but it does not cover the
details on how to decompress/compress the field other than that it is lsb-encoded.

Best regards,
Carl Knutsson

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



From rohc-bounces@ietf.org Wed Jun 20 10:45:12 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11Qh-0007nW-Bb; Wed, 20 Jun 2007 10:45:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11Qg-0007mo-8I
	for rohc@ietf.org; Wed, 20 Jun 2007 10:45:06 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11Qe-0006GK-Ip
	for rohc@ietf.org; Wed, 20 Jun 2007 10:45:06 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	87336211E1
	for <rohc@ietf.org>; Wed, 20 Jun 2007 16:45:03 +0200 (CEST)
X-AuditID: c1b4fb3e-b2038bb0000007e1-6c-46793d6f698a
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6E920201DB
	for <rohc@ietf.org>; Wed, 20 Jun 2007 16:45:03 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 16:45:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Jun 2007 16:45:02 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC05052DF7CA@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RoHCv2 and current mail discussions
Thread-Index: AcezSZVuoRKlqW9LQZWGfDaQPlFEog==
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: <rohc@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 14:45:03.0043 (UTC)
	FILETIME=[95CAD130:01C7B349]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Subject: [rohc] RoHCv2 and current mail discussions
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

RoHCers,

Thanks for the recent discussions and feedback on the draft.
I would like to find a way to resolve those at this point.

I see two main issues being discussed:

1) Number of TBC and MSN bits in PT-0
   This has implications on packet formats and robustness

2) Two-step transition
   This has implications on robustness of updating the control fields

I wil try to summarize these issues in two subsequent mails.

But first I'd like to point out that one of the issues is related to =
Timer-Based Compression (TBC ...) and I'd like to point out that I still =
do not think that there is a compelling case for including support for =
TBC in RoHCv2: the gain is at most one octet for OA number of packets =
after a "silence period", where the TS to SN function need to be =
adjusted. IMO, this is a very small gain in light of the additional =
complexity.

I'd like to put some perspective on all this.

Please keep in mind that the main objectives of RoHCv2 are:
A) increased robustness to packet reordering;
B) similar performance as RFC3095 under similar conditions,
   for the "steady-state" part;
C) simpler to implement, simpler logic;

Basically, parts of A) is achieved in RoHCv2 by:
A.1) configurable LSB interpretation interval for MSN
A.2) special care to how control fields are updated
    (see next mail about 2-step transition)

In essence, B) is achieved by defining a PT0 that is identical to UO-0.

And finally, C) is partly achieved by using the operational logic of =
RoHC-TCP as the base, and augment it to handle reordering better. In =
addition, other simplifications have been made (list compression, etc.). =
Orignally, we felt that TBC was falling into this category (I still do =
actually).

BUT, if TBC does not impact other features that have higher priority in =
the objectives of RoHCv2, then I might not mind that much that TBC gets =
included.

In other words, we have no requirement or objective to optimize for =
specific events or link technology. We do it when it comes at no costs =
to other more important "features".

And from my perspective, TBC is not more important IMO than robustness =
against reordering.

Therefore, I would argue that we should either not include support for =
TBC, or include support for TBC but keep the packet formats as they are =
in the current draft intact, i.e. Keep 6 MSN bits in PT0-CRC7 and keep 4 =
bits for TS (TBC), as I think that robustness is more important.

There are other aspects to this question, which I address in the next =
email.

Cheers,=20

///Ghyslain

 --
 Ghyslain Pelletier, Dipl. Ing.
 Senior Research Engineer
 Wireless IP Optimizations
 Ericsson Research, Corporate Unit

 Ericsson AB, Laboratoriegr=E4nd 11
 Box 920, S-97128 Lule=E5, SWEDEN
 Phone : +46 (0)  8 404 29 43
 Mobile: +46 (0) 70 264 83 14
 Ghyslain.Pelletier at ericsson.com
 http://www.ericsson.com

--------------------------------------------
 The opinions expressed in this message are
 my personal opinions.
 These opinions are not necessarily those of
 my employer, unless stated otherwise.
--------------------------------------------

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



From rohc-bounces@ietf.org Wed Jun 20 10:58:13 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11dN-0000RW-Lk; Wed, 20 Jun 2007 10:58:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11dM-0000RR-RZ
	for rohc@ietf.org; Wed, 20 Jun 2007 10:58:12 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11dJ-0003do-9E
	for rohc@ietf.org; Wed, 20 Jun 2007 10:58:12 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C75E0211E2
	for <rohc@ietf.org>; Wed, 20 Jun 2007 16:58:08 +0200 (CEST)
X-AuditID: c1b4fb3e-af032bb0000007e1-97-46794080a811
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	AF99D2018B
	for <rohc@ietf.org>; Wed, 20 Jun 2007 16:58:08 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 16:58:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Jun 2007 16:58:07 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC05052DF7F3@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RoHCv2 issue #1: Number of TBC and MSN bits
Thread-Index: AcezS2l5w4pmkVXUQuCg9vH49fS7Mg==
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: <rohc@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 14:58:08.0543 (UTC)
	FILETIME=[69FC9AF0:01C7B34B]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: [rohc] RoHCv2 issue #1: Number of TBC and MSN bits
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

RoHCers,

Trying to summarize the issues in order to move forward.

Issue #1: Number of TBC and MSN bits
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
The issue here seems to be that there are only a certain number of bits =
available for MSN and TBC in PT1 packet types. These bits should be =
split between those two fields in the best manner.

Currently, we have the following formats:
1) useful against moderate # consecutive losses, very small reordering =
depth:
  - PT0-CRC3: MSN(4 bits), size(1 octet)
  - PT1     : MSN(4 bits), size(2 octets)
2) useful against higher # consecutive losses, higher reordering depth
  - PT0-CRC7: MSN(6 bits), size(2 octets)  =20
  - PT2     : MSN(7 bits), size(3 octet)

Note that PT0-CRC7 is also useful (when sending a PT0 type is possible) =
to efficiently verify the updating of control fields by an IR header. =
This makes updating of control fields more robust (see next mail).

Gains of TBC:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
With respect to the gains of TBC, my understanding is that:

1) the compression gain it is limited in practice to at most one octet =
for a number "OA" of packets after a silence period, where the TS to SN =
function need to be adjusted. This is because the current PT2 (3 octets) =
can be used, while the alternative would be to modify PT1 (2 octets).

IMO, this is a very small gain, and we need to consider how relevant it =
is compared to what would be lost in terms of robustness.=20

2) one aspect is the amount of jitter that TBC can tolerate depending on =
the number of TS TBC bits.

Looking at last year's discussions, there is a mail arguing in favor of =
having 5 bits of TS in PT1:
http://www1.ietf.org/mail-archive/web/rohc/current/msg04579.html

This would require reshuffling the discriminators and taking one MSN bit =
from PT0-CRC7.

>From what I understand, 4 bits of TBC TS provides a tolerance to jitter =
of +-100ms; this seems quite sufficient for real-time media such as =
VoIP, because the end-user/jitterbuffer most likely not be capable of =
handling a larger variation in arrival time. Wrt large jitter in =
practice, my understanding is that even with a slow HARQ etc, 100 ms is =
a lot. So it is unclear to me that handling more jitter than this is =
needed in fact.

Hence, I think that we should stop trying to optimize for one octet here =
and there for cases where compression is not in "steady-state", and =
instead focus on robustness against reordering. In that case, I would =
argue in favor of keeping the current packet formats in the draft as =
they are, i.e. 4 bits of TS TBC is enough and less a priority than to =
have 6 bits MSN in PT0-CRC7

Cheers,

///Ghyslain

 --
 Ghyslain Pelletier, Dipl. Ing.
 Senior Research Engineer
 Wireless IP Optimizations
 Ericsson Research, Corporate Unit

 Ericsson AB, Laboratoriegr=E4nd 11
 Box 920, S-97128 Lule=E5, SWEDEN
 Phone : +46 (0)  8 404 29 43
 Mobile: +46 (0) 70 264 83 14
 Ghyslain.Pelletier at ericsson.com
 http://www.ericsson.com

--------------------------------------------
 The opinions expressed in this message are
 my personal opinions.
 These opinions are not necessarily those of
 my employer, unless stated otherwise.
--------------------------------------------


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



From rohc-bounces@ietf.org Wed Jun 20 11:09:41 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11oT-00022g-NR; Wed, 20 Jun 2007 11:09:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11oS-00022K-3f
	for rohc@ietf.org; Wed, 20 Jun 2007 11:09:40 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11oQ-0007Cg-H0
	for rohc@ietf.org; Wed, 20 Jun 2007 11:09:40 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	01A55205DB
	for <rohc@ietf.org>; Wed, 20 Jun 2007 17:09:38 +0200 (CEST)
X-AuditID: c1b4fb3c-b0e80bb0000007e1-1e-46794331ae3b
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	D72D320066
	for <rohc@ietf.org>; Wed, 20 Jun 2007 17:09:37 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 17:09:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Jun 2007 17:09:37 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC05052DF80A@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RoHCv2 issue #2: Two-step transition
Thread-Index: AcezTQRxjK9TDAsRQvKWBcSCQGiTEQ==
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: <rohc@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 15:09:37.0716 (UTC)
	FILETIME=[04C40F40:01C7B34D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Subject: [rohc] RoHCv2 issue #2: Two-step transition
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

RoHCers,

Trying to bring this discussion to some conclusion.

It seems that in this case the issue is to motivate the two-step =
transition.

Well, the idea was originally to remove any possible error cases in case =
an IR updates at least one control field to a different value, when =
reordering is possible. Error cases are possible because control fields =
are not used to "decompress" the IR header.

Because we do not want to make mandatory to always send the control =
fields in the IR, and because there is no room for a 3-bit CRC in the IR =
to cover those fields, then the approach where the usage of the updated =
control fields is CRC-7 verified prior to allowing decompression of =
CRC-3 headers was proposed.

However, it's been argued on the mailing list that it might be too =
strict to mandate the decompressor to successfully verify a header with =
a CRC-7, before being allowed to attempt decompression of a header with =
a CRC-3.=20

(Note that the co_common and co_repair headers do not either mandate =
that control fields are sent, however they contain a CRC3 over the =
context values for the control fields, hence these headers can both =
update these fields and verify them, although they may not use their =
value by CRC-7 verification. Therefore this issue applies only to the IR =
header.)

So, here is my proposal:

1) We could change the state machine to a "one-step" state machine, =
whereas
   when the compressor uses IR but do not modify any of the control =
fields
   it may send a header with a CRC-3 directly after, and

2) We could add in a normative section text similar to the following:

  "The compressor should not use a CO format with a CRC-3 immediately =
after having
  sent an IR header that updates at least one control field to a =
different value;
  the compressor SHOULD use a CO format with a CRC-7, and subject it to =
the
  optimistic approach it implements."

The consequence of 1) is that the decompressor may attempt decompression =
of a CRC-3 header whenever it likes, while the consequence of 2) is that =
a compressor will send a CRC-7 after updating the control fields with =
the IR header to ensure that the control fields are properly updated =
(unless it knows better, i.e. If it does not do that, the decompressor =
will still attempt decompression of the CRC-3 header)

Yet, in means in practice that we still strongly recommend (SHOULD) that =
a CRC-7 follows an IR header, but compression won't break if it is not =
the case and if reordering isn't an issue. IMO, increased robustness =
against reordering for control fields at such a low cost is quite good =
actually. I think that this porposal should be acceptable to everyone? =
It's flexible, can be made robust and it is not broken. Agreed?

Cheers,

///Ghyslain

 --
 Ghyslain Pelletier, Dipl. Ing.
 Senior Research Engineer
 Wireless IP Optimizations
 Ericsson Research, Corporate Unit

 Ericsson AB, Laboratoriegr=E4nd 11
 Box 920, S-97128 Lule=E5, SWEDEN
 Phone : +46 (0)  8 404 29 43
 Mobile: +46 (0) 70 264 83 14
 Ghyslain.Pelletier at ericsson.com
 http://www.ericsson.com

--------------------------------------------
 The opinions expressed in this message are
 my personal opinions.
 These opinions are not necessarily those of
 my employer, unless stated otherwise.
--------------------------------------------


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



From rohc-bounces@ietf.org Thu Jun 21 04:47:28 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1IK7-0006ih-5G; Thu, 21 Jun 2007 04:47:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1IK5-0006ia-67
	for rohc@ietf.org; Thu, 21 Jun 2007 04:47:25 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1IK2-0005DH-W8
	for rohc@ietf.org; Thu, 21 Jun 2007 04:47:25 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	67DC420813; Thu, 21 Jun 2007 10:47:22 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-37-467a3b1a8ecb
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	49931203E9; Thu, 21 Jun 2007 10:47:22 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 10:47:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] RoHCv2 and current mail discussions
Date: Thu, 21 Jun 2007 10:47:21 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC05052DFBF5@esealmw109.eemea.ericsson.se>
In-Reply-To: <ECA90F8A96A62E4EB8D9E25E5140F75604267CB1@NAEX09.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] RoHCv2 and current mail discussions
Thread-Index: AcezSZVuoRKlqW9LQZWGfDaQPlFEogAAq1QrACLGTTA=
References: <026F8EEDAD2C4342A993203088C1FC05052DF7CA@esealmw109.eemea.ericsson.se>
	<ECA90F8A96A62E4EB8D9E25E5140F75604267CB1@NAEX09.na.qualcomm.com>
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: "Kapoor, Rohit" <rkapoor@qualcomm.com>
X-OriginalArrivalTime: 21 Jun 2007 08:47:21.0929 (UTC)
	FILETIME=[C8627390:01C7B3E0]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7c1a129dc3801d79d40c5ca8dee767eb
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Rohit!

As I think that you meant your answer to reach also the RoHC mailing =
list, I will reply with cc to the list as well!

Kristofer and myself did not have time to tackle the remaining issues =
with RoHCv2 since last year, but at this point I am interested in moving =
the work as fast as we can, so we can produce another update soon and =
send the draft to working group last call. Your help is appreciated!

See comments inline.

///Ghyslain=20

Kapoor, Rohit wrote:
> Ghyslain,
>=20
> I think both robustness and TBC are important and the right balance
> needs to be found. A couple of points below:=20

What I read here is a mix of two different things: one is a property of =
the compression algorithm, the other is a specific encoding method to =
optimize a specific case.

My understanding wrt RoHCv2 (requirements) has always been that we need =
to maintain at least the same robustness properties as for RFC3095, and =
in addition to improve this robustness to handle better the case where =
there is reordering. Robustness is something that needs to be addressed =
in all aspects of the protocol, because the consequence of failing with =
robustness is protocol-induced packet losses.

Wrt to specific encoding methods, unless these address robustness (such =
as CRC or wlsb) then their use is related to compression efficiency. In =
this respect, what I believe is important is to look at the most =
frequently occuring case (what I refer to "steady-state", or "second =
order" compression) because this is where a gain in efficiency has the =
most impact.

Specific cases where one or two octets can be saved for a very few =
number of packets can be interesting, as long as these optimizations do =
not conflict with other more important properties, such as robutstness.

This is because we need to work with the general assumption that we can =
expect links where RoHC is applied to have the capability to handle 1, =
2, 3 octets of variation in size above the minimal PT0 size. This also =
because of the fact that there is from time to time a need to use PT1 =
and PT2, purely because e.g. of the change patterns of the flow.

So, in this respect, I agree with you that both robustness and =
compression efficiency are important, but I would argue that not all =
aspects of compression efficiency have the same importance, and what is =
addressed by TBC does not weight as much as robustness properties IMO.

I would like to know what others think about this.
=20
> 1) As far as robustness goes, even 5 bits provides a robustness of 32
> dropped packets, or if reordering (say 1/4 of INTERVAL) has to be
> supported, then 24 dropped packets and up to 8 reordering. 6 bits
> provides robustness of 16 reordering and up to 48 dropped packets. In
> most systems, I would argue that any service is unlikely to work at
> all if one had drops > 24. In fact, so much consecutive drops will
> likely lead to radio link failure, so why try to handle such packet
> loss at all? So, I am arguing that 5 bits is already very robust and
> 6 bits is overkill.       =20

I think the main issue here is not the number of consecutive losses, but =
the reordering depth that is possible.
=20
> 2) Also, I think we should be clear when mentioning the gains of TBC.

I agree. IMO the gains should be discussed without any link-layer =
dependency, i.e. We should use a definition of the gain that cannot =
change depending on what link layer we use as exemple. The gains should =
be in "absolute" terms, otherwise we create ourselves a moving target in =
the discussions and we will never reach consensus this way. RoHCv2 is =
not designed to be specific to one single link technology, so I think =
that discussing gains in this way can be agreed?

> To say that TBC gains only one octet is not the complete story.

I interpret this as to that you agree that the absolute gain, i.e. The =
difference of the compressed header size with and without the use of =
TBC, is as described in my earlier mail?

> Typically, airlinks are configured to support certain transport block
> formats, and if say your upper-layer packet does not fit in one, then
> the next bigger one could be somewhat larger. So, the impact of 1
> byte larger header may be much more than that. As an example, in the
> DO Rev A standard deployed in the US, Korea and other countries, the
> impact of 1 extra byte could be as much as 32 extra bytes over the
> air. Similar arguments also hold for 3GPP standards such as HSDPA
> (depending upon how airlink is configured).        =20

I heard this argument before.

I copy-paste at the end of this mail an extract from the HSDPA MAC-HS =
specifications. It comes from Annex A: "HS-DSCH Transport Block Size =
Table for FDD" in 25.321.
ftp://ftp.3gpp.org/specs/archive/25_series/25.321/25321-740.zip

The table lists transport block sizes allowed in the in MAC-hsstandard, =
which lists the lower range of allowed sizes over the air. This clearly =
shows that for small frames, there is a spacing of 12 bits between each =
of the transport formats. This I interpret as meaning that adding one =
extra byte of ROHC header will at the worst case result in a padding of =
12 bits.

Therefore, I would argue that your statement does not hold, at least =
with respect to HSDPA.

If your argument is that your statement is true based on how the link is =
configured, then I would assume that a proper configuration would be =
uses. However, this means that the configuration of the link has a also =
general problem with PT1 and PT2, isn't it so? IMU, these links will be =
configured to provide efficient means to carry PT1 and PT2 when those =
needs to be sent anyway. Or at least they should.
=20
> As far as required jitter handing by TBC goes, pls keep in mind that
> on the airlink, the jitter is caused not only by the H-ARQ process.
> Some packets could even see a MAC-layer ARQ (which is like a
> higher-layer ARQ functionality). Thus, jitter could be higher than
> that produced only by H-ARQ.   =20

In 3GPP, that higher-layer ARQ is RLC ("mac-layer ARQ"). My =
understanding is that this outer ARQ is not meant for real-time services =
and that RLC AM will not be used for real-time services (I believe this =
is because the jitter/delay it can introduce goes beyond what the =
application can tolerate anyway).

> I think supporting 5 bits for TBC is much more important than
> supporting 6 bits for MSN, since 5 bits for MSN are already providing
> a lot of robustness (up to 24 consecutive drops and 8 reordering,
> with reordering =3D 1/4 INTERVAL).  =20

I would like to hear others in the working group on this, with technical =
arguments in favor of TBC. I think we can all agree that the absolute =
gain is very small, and that TBC is additional complexity.


I would personally favor not supporting it, and moving forward to =
resolve the other issues instead.

Cheers,

///Ghyslain

nr #bits=20
 1   137=20
 2   149=20
 3   161=20
 4   173=20
 5   185=20
 6   197=20
 7   209=20
 8   221=20
 9   233=20
10   245=20
11   257=20
12   269=20
13   281=20
14   293=20
15   305=20
16   317=20
17   329=20
18   341=20
19   353=20
20   365=20
21   377=20
22   389=20
23   401=20
24   413=20
25   425=20
26   437=20
27   449=20
28   461=20
29   473=20
30   485=20
31   497=20
32   509=20
33   521=20

=20
> Thanks,
> Rohit
>=20
>=20
> -----Original Message-----
> From: Ghyslain Pelletier (LU/EAB)
> [mailto:ghyslain.pelletier@ericsson.com]=20
> Sent: Wed 6/20/2007 7:45 AM
> To: rohc@ietf.org
> Subject: [rohc] RoHCv2 and current mail discussions
>=20
> RoHCers,
>=20
> Thanks for the recent discussions and feedback on the draft.
> I would like to find a way to resolve those at this point.
>=20
> I see two main issues being discussed:
>=20
> 1) Number of TBC and MSN bits in PT-0
>    This has implications on packet formats and robustness
>=20
> 2) Two-step transition
>    This has implications on robustness of updating the control fields
>=20
> I wil try to summarize these issues in two subsequent mails.
>=20
> But first I'd like to point out that one of the issues is related to
> Timer-Based Compression (TBC ...) and I'd like to point out that I
> still do not think that there is a compelling case for including
> support for TBC in RoHCv2: the gain is at most one octet for OA
> number of packets after a "silence period", where the TS to SN
> function need to be adjusted. IMO, this is a very small gain in light
> of the additional complexity.     =20
>=20
> I'd like to put some perspective on all this.
>=20
> Please keep in mind that the main objectives of RoHCv2 are:
> A) increased robustness to packet reordering;
> B) similar performance as RFC3095 under similar conditions,
>    for the "steady-state" part;
> C) simpler to implement, simpler logic;
>=20
> Basically, parts of A) is achieved in RoHCv2 by:
> A.1) configurable LSB interpretation interval for MSN
> A.2) special care to how control fields are updated
>     (see next mail about 2-step transition)
>=20
> In essence, B) is achieved by defining a PT0 that is identical to
> UO-0.=20
>=20
> And finally, C) is partly achieved by using the operational logic of
> RoHC-TCP as the base, and augment it to handle reordering better. In
> addition, other simplifications have been made (list compression,
> etc.). Orignally, we felt that TBC was falling into this category (I
> still do actually).   =20
>=20
> BUT, if TBC does not impact other features that have higher priority
> in the objectives of RoHCv2, then I might not mind that much that TBC
> gets included. =20
>=20
> In other words, we have no requirement or objective to optimize for
> specific events or link technology. We do it when it comes at no
> costs to other more important "features". =20
>=20
> And from my perspective, TBC is not more important IMO than
> robustness against reordering.=20
>=20
> Therefore, I would argue that we should either not include support
> for TBC, or include support for TBC but keep the packet formats as
> they are in the current draft intact, i.e. Keep 6 MSN bits in
> PT0-CRC7 and keep 4 bits for TS (TBC), as I think that robustness is
> more important.   =20
>=20
> There are other aspects to this question, which I address in the next
> email.=20
>=20
> Cheers,
>=20
> ///Ghyslain
>=20
>  --
>  Ghyslain Pelletier, Dipl. Ing.
>  Senior Research Engineer
>  Wireless IP Optimizations
>  Ericsson Research, Corporate Unit
>=20
>  Ericsson AB, Laboratoriegr=E4nd 11
>  Box 920, S-97128 Lule=E5, SWEDEN
>  Phone : +46 (0)  8 404 29 43
>  Mobile: +46 (0) 70 264 83 14
>  Ghyslain.Pelletier at ericsson.com
>  http://www.ericsson.com
>=20
> --------------------------------------------
>  The opinions expressed in this message are
>  my personal opinions.
>  These opinions are not necessarily those of
>  my employer, unless stated otherwise.
> --------------------------------------------
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc


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



From rohc-bounces@ietf.org Tue Jun 26 05:02:59 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I36ws-0000Xl-DI; Tue, 26 Jun 2007 05:02:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I36wq-0000Wy-L5
	for rohc@ietf.org; Tue, 26 Jun 2007 05:02:56 -0400
Received: from [194.237.235.30] (helo=effnet.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I36wo-0005Ii-7J
	for rohc@ietf.org; Tue, 26 Jun 2007 05:02:56 -0400
Received: from [192.168.101.51] ([192.168.101.51]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id l5Q929AR001420
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 26 Jun 2007 11:02:17 +0200
Message-ID: <4680D625.2030405@effnet.com>
Date: Tue, 26 Jun 2007 11:02:29 +0200
From: Carl Knutsson <carl.knutsson@effnet.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061217)
MIME-Version: 1.0
To: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
Subject: Re: [rohc] RoHCv2 and current mail discussions
References: <026F8EEDAD2C4342A993203088C1FC05052DF7CA@esealmw109.eemea.ericsson.se>	<ECA90F8A96A62E4EB8D9E25E5140F75604267CB1@NAEX09.na.qualcomm.com>
	<026F8EEDAD2C4342A993203088C1FC05052DFBF5@esealmw109.eemea.ericsson.se>
In-Reply-To: <026F8EEDAD2C4342A993203088C1FC05052DFBF5@esealmw109.eemea.ericsson.se>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by effnet.com id
	l5Q929AR001420
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 142a000676f5977e1797396caab8b611
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Rohit, Ghyslian, rohcers

I have one inline comment about loss, reordering and msn bits.

//Carl Knutsson

Ghyslain Pelletier (LU/EAB) wrote:
> Hi Rohit!
>=20
> As I think that you meant your answer to reach also the RoHC mailing li=
st, I will reply with cc to the list as well!
>=20
> Kristofer and myself did not have time to tackle the remaining issues w=
ith RoHCv2 since last year, but at this point I am interested in moving t=
he work as fast as we can, so we can produce another update soon and send=
 the draft to working group last call. Your help is appreciated!
>=20
> See comments inline.
>=20
> ///Ghyslain=20
>=20
> Kapoor, Rohit wrote:
>> Ghyslain,
>>
>> I think both robustness and TBC are important and the right balance
>> needs to be found. A couple of points below:=20
>=20
> What I read here is a mix of two different things: one is a property of=
 the compression algorithm, the other is a specific encoding method to op=
timize a specific case.
>=20
> My understanding wrt RoHCv2 (requirements) has always been that we need=
 to maintain at least the same robustness properties as for RFC3095, and =
in addition to improve this robustness to handle better the case where th=
ere is reordering. Robustness is something that needs to be addressed in =
all aspects of the protocol, because the consequence of failing with robu=
stness is protocol-induced packet losses.
>=20
> Wrt to specific encoding methods, unless these address robustness (such=
 as CRC or wlsb) then their use is related to compression efficiency. In =
this respect, what I believe is important is to look at the most frequent=
ly occuring case (what I refer to "steady-state", or "second order" compr=
ession) because this is where a gain in efficiency has the most impact.
>=20
> Specific cases where one or two octets can be saved for a very few numb=
er of packets can be interesting, as long as these optimizations do not c=
onflict with other more important properties, such as robutstness.
>=20
> This is because we need to work with the general assumption that we can=
 expect links where RoHC is applied to have the capability to handle 1, 2=
, 3 octets of variation in size above the minimal PT0 size. This also bec=
ause of the fact that there is from time to time a need to use PT1 and PT=
2, purely because e.g. of the change patterns of the flow.
>=20
> So, in this respect, I agree with you that both robustness and compress=
ion efficiency are important, but I would argue that not all aspects of c=
ompression efficiency have the same importance, and what is addressed by =
TBC does not weight as much as robustness properties IMO.
>=20
> I would like to know what others think about this.
> =20
>> 1) As far as robustness goes, even 5 bits provides a robustness of 32
>> dropped packets, or if reordering (say 1/4 of INTERVAL) has to be
>> supported, then 24 dropped packets and up to 8 reordering. 6 bits
>> provides robustness of 16 reordering and up to 48 dropped packets. In
>> most systems, I would argue that any service is unlikely to work at
>> all if one had drops > 24. In fact, so much consecutive drops will
>> likely lead to radio link failure, so why try to handle such packet
>> loss at all? So, I am arguing that 5 bits is already very robust and
>> 6 bits is overkill.       =20

A clarification about loss and reordering. The configuration above (5 bit=
s msn)
cannot handle 8 reordered and 24 dropped packets. It can handle a negativ=
e msn
difference of 7 or a positive msn difference of 24. Meaning it can either=
 handle
24 lost OR 8 reordered packets, but not combined. Reordered packets after=
/before a
loss sequence may add to the msn difference.

How many reordered packet the configuration support depends on the decomp=
ressor's
ability to update the context correctly for "late" reordered packets. It =
is
possible to create scenarios with loss bursts of 8 packet and reordering =
of 8
packets that gives a much larger msn difference. With this in mind, 6 bit=
s of msn
may not be overkill for some link layer or for compressors without feedba=
ck channels.

>=20
> I think the main issue here is not the number of consecutive losses, bu=
t the reordering depth that is possible.
> =20
>> 2) Also, I think we should be clear when mentioning the gains of TBC.
>=20
> I agree. IMO the gains should be discussed without any link-layer depen=
dency, i.e. We should use a definition of the gain that cannot change dep=
ending on what link layer we use as exemple. The gains should be in "abso=
lute" terms, otherwise we create ourselves a moving target in the discuss=
ions and we will never reach consensus this way. RoHCv2 is not designed t=
o be specific to one single link technology, so I think that discussing g=
ains in this way can be agreed?
>=20
>> To say that TBC gains only one octet is not the complete story.
>=20
> I interpret this as to that you agree that the absolute gain, i.e. The =
difference of the compressed header size with and without the use of TBC,=
 is as described in my earlier mail?
>=20
>> Typically, airlinks are configured to support certain transport block
>> formats, and if say your upper-layer packet does not fit in one, then
>> the next bigger one could be somewhat larger. So, the impact of 1
>> byte larger header may be much more than that. As an example, in the
>> DO Rev A standard deployed in the US, Korea and other countries, the
>> impact of 1 extra byte could be as much as 32 extra bytes over the
>> air. Similar arguments also hold for 3GPP standards such as HSDPA
>> (depending upon how airlink is configured).        =20
>=20
> I heard this argument before.
>=20
> I copy-paste at the end of this mail an extract from the HSDPA MAC-HS s=
pecifications. It comes from Annex A: "HS-DSCH Transport Block Size Table=
 for FDD" in 25.321.
> ftp://ftp.3gpp.org/specs/archive/25_series/25.321/25321-740.zip
>=20
> The table lists transport block sizes allowed in the in MAC-hsstandard,=
 which lists the lower range of allowed sizes over the air. This clearly =
shows that for small frames, there is a spacing of 12 bits between each o=
f the transport formats. This I interpret as meaning that adding one extr=
a byte of ROHC header will at the worst case result in a padding of 12 bi=
ts.
>=20
> Therefore, I would argue that your statement does not hold, at least wi=
th respect to HSDPA.
>=20
> If your argument is that your statement is true based on how the link i=
s configured, then I would assume that a proper configuration would be us=
es. However, this means that the configuration of the link has a also gen=
eral problem with PT1 and PT2, isn't it so? IMU, these links will be conf=
igured to provide efficient means to carry PT1 and PT2 when those needs t=
o be sent anyway. Or at least they should.
> =20
>> As far as required jitter handing by TBC goes, pls keep in mind that
>> on the airlink, the jitter is caused not only by the H-ARQ process.
>> Some packets could even see a MAC-layer ARQ (which is like a
>> higher-layer ARQ functionality). Thus, jitter could be higher than
>> that produced only by H-ARQ.   =20
>=20
> In 3GPP, that higher-layer ARQ is RLC ("mac-layer ARQ"). My understandi=
ng is that this outer ARQ is not meant for real-time services and that RL=
C AM will not be used for real-time services (I believe this is because t=
he jitter/delay it can introduce goes beyond what the application can tol=
erate anyway).
>=20
>> I think supporting 5 bits for TBC is much more important than
>> supporting 6 bits for MSN, since 5 bits for MSN are already providing
>> a lot of robustness (up to 24 consecutive drops and 8 reordering,
>> with reordering =3D 1/4 INTERVAL).  =20
>=20
> I would like to hear others in the working group on this, with technica=
l arguments in favor of TBC. I think we can all agree that the absolute g=
ain is very small, and that TBC is additional complexity.
>=20
>=20
> I would personally favor not supporting it, and moving forward to resol=
ve the other issues instead.
>=20
> Cheers,
>=20
> ///Ghyslain
>=20
> nr #bits=20
>  1   137=20
>  2   149=20
>  3   161=20
>  4   173=20
>  5   185=20
>  6   197=20
>  7   209=20
>  8   221=20
>  9   233=20
> 10   245=20
> 11   257=20
> 12   269=20
> 13   281=20
> 14   293=20
> 15   305=20
> 16   317=20
> 17   329=20
> 18   341=20
> 19   353=20
> 20   365=20
> 21   377=20
> 22   389=20
> 23   401=20
> 24   413=20
> 25   425=20
> 26   437=20
> 27   449=20
> 28   461=20
> 29   473=20
> 30   485=20
> 31   497=20
> 32   509=20
> 33   521=20
>=20
> =20
>> Thanks,
>> Rohit
>>
>>
>> -----Original Message-----
>> From: Ghyslain Pelletier (LU/EAB)
>> [mailto:ghyslain.pelletier@ericsson.com]=20
>> Sent: Wed 6/20/2007 7:45 AM
>> To: rohc@ietf.org
>> Subject: [rohc] RoHCv2 and current mail discussions
>>
>> RoHCers,
>>
>> Thanks for the recent discussions and feedback on the draft.
>> I would like to find a way to resolve those at this point.
>>
>> I see two main issues being discussed:
>>
>> 1) Number of TBC and MSN bits in PT-0
>>    This has implications on packet formats and robustness
>>
>> 2) Two-step transition
>>    This has implications on robustness of updating the control fields
>>
>> I wil try to summarize these issues in two subsequent mails.
>>
>> But first I'd like to point out that one of the issues is related to
>> Timer-Based Compression (TBC ...) and I'd like to point out that I
>> still do not think that there is a compelling case for including
>> support for TBC in RoHCv2: the gain is at most one octet for OA
>> number of packets after a "silence period", where the TS to SN
>> function need to be adjusted. IMO, this is a very small gain in light
>> of the additional complexity.     =20
>>
>> I'd like to put some perspective on all this.
>>
>> Please keep in mind that the main objectives of RoHCv2 are:
>> A) increased robustness to packet reordering;
>> B) similar performance as RFC3095 under similar conditions,
>>    for the "steady-state" part;
>> C) simpler to implement, simpler logic;
>>
>> Basically, parts of A) is achieved in RoHCv2 by:
>> A.1) configurable LSB interpretation interval for MSN
>> A.2) special care to how control fields are updated
>>     (see next mail about 2-step transition)
>>
>> In essence, B) is achieved by defining a PT0 that is identical to
>> UO-0.=20
>>
>> And finally, C) is partly achieved by using the operational logic of
>> RoHC-TCP as the base, and augment it to handle reordering better. In
>> addition, other simplifications have been made (list compression,
>> etc.). Orignally, we felt that TBC was falling into this category (I
>> still do actually).   =20
>>
>> BUT, if TBC does not impact other features that have higher priority
>> in the objectives of RoHCv2, then I might not mind that much that TBC
>> gets included. =20
>>
>> In other words, we have no requirement or objective to optimize for
>> specific events or link technology. We do it when it comes at no
>> costs to other more important "features". =20
>>
>> And from my perspective, TBC is not more important IMO than
>> robustness against reordering.=20
>>
>> Therefore, I would argue that we should either not include support
>> for TBC, or include support for TBC but keep the packet formats as
>> they are in the current draft intact, i.e. Keep 6 MSN bits in
>> PT0-CRC7 and keep 4 bits for TS (TBC), as I think that robustness is
>> more important.   =20
>>
>> There are other aspects to this question, which I address in the next
>> email.=20
>>
>> Cheers,
>>
>> ///Ghyslain
>>
>>  --
>>  Ghyslain Pelletier, Dipl. Ing.
>>  Senior Research Engineer
>>  Wireless IP Optimizations
>>  Ericsson Research, Corporate Unit
>>
>>  Ericsson AB, Laboratoriegr=E4nd 11
>>  Box 920, S-97128 Lule=E5, SWEDEN
>>  Phone : +46 (0)  8 404 29 43
>>  Mobile: +46 (0) 70 264 83 14
>>  Ghyslain.Pelletier at ericsson.com
>>  http://www.ericsson.com
>>
>> --------------------------------------------
>>  The opinions expressed in this message are
>>  my personal opinions.
>>  These opinions are not necessarily those of
>>  my employer, unless stated otherwise.
>> --------------------------------------------
>>
>> _______________________________________________
>> Rohc mailing list
>> Rohc@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rohc
>=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc


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



