From rohc-bounces@ietf.org  Mon Jan  5 08:28:01 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D79473A6853;
	Mon,  5 Jan 2009 08:28:01 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB1973A67B4
	for <rohc@core3.amsl.com>; Mon,  5 Jan 2009 08:27:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.329
X-Spam-Level: 
X-Spam-Status: No, score=-2.329 tagged_above=-999 required=5 tests=[AWL=0.270, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SVF2ojSNvJhm for <rohc@core3.amsl.com>;
	Mon,  5 Jan 2009 08:27:15 -0800 (PST)
Received: from mclniron02-ext.bah.com (mclniron02-ext.bah.com [156.80.1.73])
	by core3.amsl.com (Postfix) with ESMTP id AA8913A63D2
	for <rohc@ietf.org>; Mon,  5 Jan 2009 08:27:15 -0800 (PST)
x-SBRS: None
X-REMOTE-IP: 156.80.7.151
X-IronPort-AV: E=Sophos;i="4.36,332,1228107600"; d="scan'208";a="32306410"
Received: from mclnexbh01.resource.ds.bah.com ([156.80.7.151])
	by mclniron02-int.bah.com with ESMTP; 05 Jan 2009 11:27:02 -0500
Received: from MCLNEXVS05.resource.ds.bah.com ([156.80.7.121]) by
	mclnexbh01.resource.ds.bah.com with Microsoft
	SMTPSVC(6.0.3790.3959); Mon, 5 Jan 2009 11:27:02 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 11:27:01 -0500
Message-ID: <37BDD2FAF2AEAE459C6C70FDC2892E4E03CFEBA8@MCLNEXVS05.resource.ds.bah.com>
In-Reply-To: <4933FEE0.6090102@nkiconsulting.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] FW: CDR review ROHCoIPSec
Thread-Index: AclTx1eMy4gqNjq0Tz22Tnfv+Z2j7AAzxSLQ
References: <37BDD2FAF2AEAE459C6C70FDC2892E4E0398FFC0@MCLNEXVS05.resource.ds.bah.com>
	<4933FEE0.6090102@nkiconsulting.com>
From: "Ertekin, Emre [USA]" <ertekin_emre@bah.com>
To: "Robert A. Stangarone Jr." <stangarr@nkiconsulting.com>
X-OriginalArrivalTime: 05 Jan 2009 16:27:02.0319 (UTC)
	FILETIME=[708EFBF0:01C96F52]
Cc: "Christou, Christos \[USA\]" <christou_chris@bah.com>, cabo@tzi.org,
	rohc@ietf.org, Yoav Nir <ynir@checkpoint.com>
Subject: Re: [rohc] FW: CDR review ROHCoIPSec
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

Robert,

I have been updating the document based on the comments that I received
during the WG LC.

Apologies -- I did not adjudicate three of your comments.  Please find
my responses to the three points below.

<snip>

> ------ draft-ietf-rohc-IPsec-extensions-hcoipsec-03 ------

<snip>

> >> 2.2.  Security Association Database (SAD)
> >>
> >> Section 2.1 last paragraph & section 2.2:
> >>
> >> The FEEDBACK_FOR ROHC Channel Parameter should only be populated in
> > the
> >> SAD when a SA in the reverse direction is available. Section 2.2
> needs
> >> clarification regarding the purpose/function of each of the ROHC
SAD
> >> configuration items as they relate to the directional processing
> flow
> >> (inbound and outbound) of a particular SA.
> >>
> 
> Your thoughts on this point?

I don't think that Section 2.1 should contain information about the ROHC
SAD configuration items and how they relate to directional processing of
an SA, since Section 2.1 primarily discusses the SPD.

However, I agree that Section 2.2 should be updated.  This section will
need to be updated anyway now that channel parameters are signaled
between the initiator and the responder.  As you recommended, we can add
a discussion on each channel parameter, and how they are relate to
inbound/outbound SAs.

<snip>

>------ draft-ietf-rohc-ikev2-extensions-hcoipsec-07 ------

<snip>

> >> This document needs to state that the final negotiated set of
> profiles
> >> (as transmitted by the responder if the signaling approach
suggested
> >> above is adopted) MUST NOT contain in invalid combination of RoHCv1
> > and
> >> RoHCv2 profiles. For example, a RoHC channel cannot support both
RFC
> >> 3095 UDP/IP and RFC 5225 UDP/IP.
> >>
> 
> Your thoughts on this?

I think that this point was addressed in a separate email.  Since we are
switching to the signaling-based channel parameter negotiation, I think
that the best approach is to prohibit the initiator/responder to signal
multiple versions of the same profile.  

This way, we can ensure that two different versions of the same profile
will never be active on the same ROHC channel.

> >> For the Notify Message Type field, ROHC_SUPPORTED is specified, but
> >> there is no description of what value in that field indicates
> >> ROHC_SUPPORTED. What value should be used? Some reference to the
> need
> >> for IANA to allocate a IKEv2 Notify message registry would be
> >> informative.
> >>
> 
> Your thoughts on this?

We can add a reference in Section 2.1 of the document that points to the
document's IANA considerations section.  Will this address your comment?


We will be finalizing all three documents over the next couple of days
and should have a new revision out very shortly!  Thanks again for your
comments.

Best Regards,
Emre
 
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www.ietf.org/mailman/listinfo/rohc


From rohc-bounces@ietf.org  Fri Jan  9 14:57:56 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BDA23A6A50;
	Fri,  9 Jan 2009 14:57:56 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 56CB73A6A50
	for <rohc@core3.amsl.com>; Fri,  9 Jan 2009 14:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.876
X-Spam-Level: 
X-Spam-Status: No, score=-1.876 tagged_above=-999 required=5 tests=[AWL=0.722, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9ind3KX9SsGY for <rohc@core3.amsl.com>;
	Fri,  9 Jan 2009 14:57:54 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70])
	by core3.amsl.com (Postfix) with ESMTP id 726C23A6A44
	for <rohc@ietf.org>; Fri,  9 Jan 2009 14:57:54 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1])
	by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KD800DJ87S335@usaga02-in.huawei.com> for
	rohc@ietf.org; Fri, 09 Jan 2009 14:57:40 -0800 (PST)
Received: from X24512z ([10.124.12.66])
	by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KD800GPW7S3S6@usaga02-in.huawei.com> for
	rohc@ietf.org; Fri, 09 Jan 2009 14:57:39 -0800 (PST)
Date: Fri, 09 Jan 2009 16:57:39 -0600
From: Frank Xia <xiayangsong@huawei.com>
To: rohc@ietf.org
Message-id: <003a01c972ad$abd54800$420c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
Cc: Vijay Devarapalli <vijay@wichorus.com>
Subject: [rohc] ROHC over Mobile IPv6
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1635465684=="
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1635465684==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_KxTTxzChE7sDne9q2WdZhw)"

This is a multi-part message in MIME format.

--Boundary_(ID_KxTTxzChE7sDne9q2WdZhw)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi All   

Mobile IPv6 (MIPv6) is widely adopted by 
WiMAX/3GPP/3GPP2.  To improve MIPv6 
performance, IETF mobility community, 
especially MIPSHOP and MEXT WG, 
has been working on tunnel optimization for a while.
The solution was questioned by IESG last November
during MIPSHOP Rechartering.  IESG suggested
ROHC should be considered in this work.

Mobiel IPv6 specifies a protocol which allows 
a mobile  to remain reachable while moving around
the internet. The mobile node is always  identified 
by its home address, regardless of its current point 
of attachment to the Internet.  While situated away 
from its home, the mobile node is also associated 
with a care-of address, which provides information 
about the mobile node's current location.  IPv6 packets 
addressed to the mobile node's home address are 
intercepted by a home agent, and routed to the
mobile node through a bidirectional tunnel. Tunnel
encapuslation could be IPSec, IPv6inIPv6, IPv4inIPv6,
IPv4 in UDP, or others .

Mobile IPv6 uses Binding Update (BU)/Binding 
Acknowledgement(BA) to create/delete tunnel,
and Generic Signaling Messages for other 
purpose communication. 

is it possible to have a  channel  parameters 
negotiation document to facilitate MIPv6 using 
ROHC?

BR
Frank

--Boundary_(ID_KxTTxzChE7sDne9q2WdZhw)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi All&nbsp;&nbsp; </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Mobile IPv6 (MIPv6)&nbsp;is widely adopted by 
</FONT></DIV>
<DIV><FONT face=Arial size=2>WiMAX/3GPP/</FONT><FONT face=Arial 
size=2>3GPP2.&nbsp; To improve MIPv6 </FONT></DIV>
<DIV><FONT face=Arial size=2>performance, IETF </FONT><FONT face=Arial 
size=2>mobility community, </FONT></DIV>
<DIV><FONT face=Arial size=2>especially MIPSHOP and </FONT><FONT face=Arial 
size=2>MEXT WG, </FONT></DIV>
<DIV><FONT face=Arial size=2>has been working on tunnel optimization for a 
while.</FONT></DIV>
<DIV><FONT face=Arial size=2>The solution was questioned by IESG last 
November</FONT></DIV>
<DIV><FONT face=Arial size=2>during MIPSHOP Rechartering.&nbsp; IESG 
suggested</FONT></DIV>
<DIV><FONT face=Arial size=2>ROHC should be considered in this 
work.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Mobiel IPv6 specifies a protocol which allows 
</FONT></DIV>
<DIV><FONT face=Arial size=2>a mobile&nbsp; to remain reachable while moving 
around</FONT></DIV>
<DIV><FONT face=Arial size=2>the internet. </FONT><FONT face=Arial 
size=2>The&nbsp;mobile node is always&nbsp; </FONT><FONT face=Arial 
size=2>identified </FONT></DIV>
<DIV><FONT face=Arial size=2>by its home </FONT><FONT face=Arial size=2>address, 
regardless of its </FONT><FONT face=Arial size=2>current point </FONT></DIV>
<DIV><FONT face=Arial size=2>of attachment</FONT><FONT face=Arial 
size=2>&nbsp;to the Internet.&nbsp; </FONT><FONT face=Arial size=2>While 
situated away </FONT></DIV>
<DIV><FONT face=Arial size=2>from its home,&nbsp;the mobile node </FONT><FONT 
face=Arial size=2>is also associated </FONT></DIV>
<DIV><FONT face=Arial size=2>with a care-of address, which </FONT><FONT 
face=Arial size=2>provides information </FONT></DIV>
<DIV><FONT face=Arial size=2>about the mobile node's current </FONT><FONT 
face=Arial size=2>location.&nbsp; IPv6 packets </FONT></DIV>
<DIV><FONT face=Arial size=2>addressed to the mobile node's </FONT><FONT 
face=Arial size=2>home address are </FONT></DIV>
<DIV><FONT face=Arial size=2>intercepted by a home agent, and routed to 
the</FONT></DIV>
<DIV><FONT face=Arial size=2>mobile node through a bidirectional tunnel. 
Tunnel</FONT></DIV>
<DIV><FONT face=Arial size=2>encapuslation could be IPSec, IPv6inIPv6, 
IPv4inIPv6,</FONT></DIV>
<DIV><FONT face=Arial size=2>IPv4 in UDP, or others&nbsp;.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Mobile IPv6 uses Binding Update (BU)/Binding 
</FONT></DIV>
<DIV><FONT face=Arial size=2>Acknowledgement(BA) to create/delete 
tunnel,</FONT></DIV>
<DIV><FONT face=Arial size=2>and </FONT><FONT face=Arial size=2>Generic 
Signaling Messages for other </FONT></DIV>
<DIV><FONT face=Arial><FONT size=2>purpose communication.</FONT> </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>is it possible to have a&nbsp; channel&nbsp; 
parameters </FONT></DIV>
<DIV><FONT face=Arial size=2>negotiation </FONT><FONT face=Arial size=2>document 
to facilitate MIPv6 using </FONT></DIV>
<DIV><FONT face=Arial size=2>ROHC?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>BR</FONT></DIV>
<DIV><FONT face=Arial size=2>Frank</FONT></DIV></BODY></HTML>

--Boundary_(ID_KxTTxzChE7sDne9q2WdZhw)--

--===============1635465684==
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://www.ietf.org/mailman/listinfo/rohc

--===============1635465684==--


From rohc-bounces@ietf.org  Fri Jan  9 15:17:41 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 412D63A6864;
	Fri,  9 Jan 2009 15:17:41 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C419A28C11D
	for <rohc@core3.amsl.com>; Fri,  9 Jan 2009 15:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5
	tests=[AWL=-0.250, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0ss89Chh0cSl for <rohc@core3.amsl.com>;
	Fri,  9 Jan 2009 15:17:39 -0800 (PST)
Received: from ins1.sd.spawar.navy.mil (ins1.sd.spawar.navy.mil
	[IPv6:2001:480:10:4::2])
	by core3.amsl.com (Postfix) with ESMTP id 9E7F13A67AD
	for <rohc@ietf.org>; Fri,  9 Jan 2009 15:17:38 -0800 (PST)
Received: from pescado.nosc.mil (pescado.nosc.mil [128.49.4.90])
	by ins1.sd.spawar.navy.mil (8.13.1/8.13.1) with ESMTP id n09NCK9x024461
	for <rohc@ietf.org>; Fri, 9 Jan 2009 15:12:20 -0800
Received: from [127.0.0.1] (alderon.sd.spawar.navy.mil
	[128.49.162.148]) by pescado.nosc.mil (Netscape Messaging Server
	4.15) with ESMTP id KD88GJ00.GGR; Fri, 9 Jan 2009 15:12:19 -0800 
Message-ID: <4967D9C6.7020002@nkiconsulting.com>
Date: Fri, 09 Jan 2009 15:12:06 -0800
From: Robert Stangarone <stangarr@nkiconsulting.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Frank Xia <xiayangsong@huawei.com>
References: <003a01c972ad$abd54800$420c7c0a@china.huawei.com>
In-Reply-To: <003a01c972ad$abd54800$420c7c0a@china.huawei.com>
Cc: Vijay Devarapalli <vijay@wichorus.com>, rohc@ietf.org
Subject: Re: [rohc] ROHC over Mobile IPv6
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

Frank,

You might take a look at a the following documents that propose how to
negotiate ROHC Channel Parameters for the use ROHC within an IPsec
tunnel with IKEv2:

Integration of Robust Header Compression (RoHC) over IPsec Security
Associations
http://www.ietf.org/internet-drafts/draft-ietf-rohc-hcoipsec-09.txt

IKEv2 Extensions to Support Robust Header Compression over IPsec(RoHCoIPsec)
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ikev2-extensions-hcoipsec-07.txt

IPsec Extensions to Support Robust Header Compression over IPsec
(RoHCoIPsec)
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ipsec-extensions-hcoipsec-03.txt

Cheers,

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


From rohc-bounces@ietf.org  Fri Jan  9 15:32:20 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17C6F3A684F;
	Fri,  9 Jan 2009 15:32:20 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 156F228C161
	for <rohc@core3.amsl.com>; Fri,  9 Jan 2009 15:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.966
X-Spam-Level: 
X-Spam-Status: No, score=-1.966 tagged_above=-999 required=5 tests=[AWL=0.632, 
	BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RiW4VV1EhR7Z for <rohc@core3.amsl.com>;
	Fri,  9 Jan 2009 15:32:18 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70])
	by core3.amsl.com (Postfix) with ESMTP id 3D3403A67AD
	for <rohc@ietf.org>; Fri,  9 Jan 2009 15:32:18 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1])
	by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KD800DVC9DF35@usaga02-in.huawei.com> for
	rohc@ietf.org; Fri, 09 Jan 2009 15:32:04 -0800 (PST)
Received: from X24512z ([10.124.12.66])
	by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KD800IF39DFK2@usaga02-in.huawei.com> for
	rohc@ietf.org; Fri, 09 Jan 2009 15:32:03 -0800 (PST)
Date: Fri, 09 Jan 2009 17:32:03 -0600
From: Frank Xia <xiayangsong@huawei.com>
To: Robert Stangarone <stangarr@nkiconsulting.com>
Message-id: <001b01c972b2$7a3bbbd0$420c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
References: <003a01c972ad$abd54800$420c7c0a@china.huawei.com>
	<4967D9C6.7020002@nkiconsulting.com>
Cc: Vijay Devarapalli <vijay@wichorus.com>, rohc@ietf.org
Subject: Re: [rohc] ROHC over Mobile IPv6
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

Hi Bob

Thank your reply!
I had a glance at  these documents.

The problem is  that MIPv6 never mandates using
IPSec tunnel when forwarding data packets.
That is, it is possible that there is no any IPSec
SA between tunnel ends.

BR
Frank

----- Original Message ----- 
From: "Robert Stangarone" <stangarr@nkiconsulting.com>
To: "Frank Xia" <xiayangsong@huawei.com>
Cc: "Vijay Devarapalli" <vijay@wichorus.com>; <rohc@ietf.org>
Sent: Friday, January 09, 2009 5:12 PM
Subject: Re: [rohc] ROHC over Mobile IPv6


> Frank,
>
> You might take a look at a the following documents that propose how to
> negotiate ROHC Channel Parameters for the use ROHC within an IPsec
> tunnel with IKEv2:
>
> Integration of Robust Header Compression (RoHC) over IPsec Security
> Associations
> http://www.ietf.org/internet-drafts/draft-ietf-rohc-hcoipsec-09.txt
>
> IKEv2 Extensions to Support Robust Header Compression over 
> IPsec(RoHCoIPsec)
> http://www.ietf.org/internet-drafts/draft-ietf-rohc-ikev2-extensions-hcoipsec-07.txt
>
> IPsec Extensions to Support Robust Header Compression over IPsec
> (RoHCoIPsec)
> http://www.ietf.org/internet-drafts/draft-ietf-rohc-ipsec-extensions-hcoipsec-03.txt
>
> Cheers,
>
> Bob
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc 

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


From rohc-bounces@ietf.org  Mon Jan 12 22:33:28 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4FE483A6851;
	Mon, 12 Jan 2009 22:33:28 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48ED53A68FF
	for <rohc@core3.amsl.com>; Fri,  9 Jan 2009 06:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
	tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C2ABd-wr9iUJ for <rohc@core3.amsl.com>;
	Fri,  9 Jan 2009 06:46:41 -0800 (PST)
Received: from vsnlchnsym02.vsnlxchange.com (VSNLCHNSYM02.vsnlxchange.com
	[59.163.96.19]) by core3.amsl.com (Postfix) with ESMTP id 124793A6783
	for <rohc@ietf.org>; Fri,  9 Jan 2009 06:46:38 -0800 (PST)
Received: from vsnlchnsym02.vsnlxchange.com (unknown [127.0.0.1])
	by vsnlchnsym02.vsnlxchange.com (Symantec Brightmail Gateway) with
	ESMTP id 9F84016D6
	for <rohc@ietf.org>; Fri,  9 Jan 2009 20:15:55 +0530 (IST)
X-AuditID: 0a480a09-a3df3bb000000cb8-8c-49676323c666
Received: from sudipkumarm ([59.160.207.5]) by VSNLCHNFE001.VSNLXCHANGE.COM
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 9 Jan 2009 20:15:55 +0530
From: "Sudip Kumar Mandal" <sudipkumarm@tataelxsi.co.in>
To: <rohc@ietf.org>
Date: Fri, 9 Jan 2009 20:16:18 +0530
Message-ID: <000001c97269$090ed7b0$761b320a@telxsi.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-OriginalArrivalTime: 09 Jan 2009 14:45:55.0343 (UTC)
	FILETIME=[FA02E9F0:01C97268]
X-Brightmail-Tracker: AAAAAQr+oFQ=
X-Mailman-Approved-At: Mon, 12 Jan 2009 22:33:26 -0800
Cc: 'Vidya Akhare' <vizz@tataelxsi.co.in>, abhisheksaurabh@tataelxsi.co.in,
	Gurushant G Kotagi <gurushant@tataelxsi.co.in>
Subject: [rohc] RoHCv2 : Problems in decoding sequentially late packets
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: sudipkumarm@tataelxsi.co.in
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org


Hi,
 I am facing problems in decoding sequentially late packets if link
reordering (between compressor and the decompressor) situation is being
simulated. I am explaining the situation with
an example:


Late packet

Suppose initiallly the encoder has 0x0004 in its window and encoded value of
0x0004 is reached to the
decompressor.Assuming sequential increment of the field encoder then encodes
0x0005 and 0x0006.

Suppose in the link the value 0x0005 and 0x0006 is lost and these value
didn't reach the decoder,
so the decoder still uses 0x0004 as its reference value (assuming successful
decoding of encoded
value of 0x0004).

Now encoder encodes 0x0007 using 0x0004,0x0005,0x0006 having in its
reference window and it will send
0x0003 as its encoded value.
Decompressor receives 0x0003 (sequentially early packet) and it can
reconstruct, the reconstructed value
will be 0x0007 which is offcourse equal to the original value. Decoder will
make its reference value as 0x0007.

Now suppose the encoded value of 0x0005 (sequentially late packet) is
reached to the decompressor. Using
reference value of 0x0004 the encoded value of 0x0005 will be 0x0001.The
decoder has 0x0007 in its reference
and this time the decoded value will be 0x0008 which is not equal to the
original value (0x0005)

I am not finding any clue how to handle sequentially late packets and how to
identify sequentially late packet.
According to RFC 5225 "How the decompressor detects a sequentially late
packet is outside the scope of this specification,
but it can for example use the MSN for this purpose", but as per my
knowledge MSN has to be decoded first then it can be used to
identify sequentially late packet.
So, I would, therefore request you to suggest some idea so that the decoder
can identify sequentially late packet before decoding the
encoded value and it can decode it successfully.



Thanks & Regards
Sudip Kumar Mandal
Tata Elxsi Ltd
Bangalore, India



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www.ietf.org/mailman/listinfo/rohc


From rohc-bounces@ietf.org  Tue Jan 13 00:32:18 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C395C3A68B0;
	Tue, 13 Jan 2009 00:32:18 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DDC93A68B0
	for <rohc@core3.amsl.com>; Tue, 13 Jan 2009 00:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UiKlBzenAeg7 for <rohc@core3.amsl.com>;
	Tue, 13 Jan 2009 00:32:17 -0800 (PST)
Received: from lists.levonline.com (lists.levonline.com [217.70.33.37])
	by core3.amsl.com (Postfix) with ESMTP id 0CA943A683E
	for <rohc@ietf.org>; Tue, 13 Jan 2009 00:32:15 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by lists.levonline.com (Postfix) with ESMTP id 07F2D29C31D;
	Tue, 13 Jan 2009 09:31:40 +0100 (CET)
X-Virus-Scanned: By http://levonline.com - free virus scanning for all
	customers
Received: from lists.levonline.com ([127.0.0.1])
	by localhost (lists.levonline.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vl26bnW0bxOK; Tue, 13 Jan 2009 09:31:36 +0100 (CET)
Received: from truck3.fordonnet.levonline.com (truck3.fordonnet.levonline.com
	[192.168.18.23])
	by lists.levonline.com (Postfix) with ESMTP id 6E8D929C233;
	Tue, 13 Jan 2009 09:31:36 +0100 (CET)
Received: from [192.168.101.51]
	(c-f97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.249]) (authenticated bits=0)
	by truck3.fordonnet.levonline.com (8.12.11.20060308/8.12.11) with ESMTP
	id n0D8VU9O025897
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 13 Jan 2009 09:31:31 +0100
Message-ID: <496C5176.6030105@effnet.com>
Date: Tue, 13 Jan 2009 09:31:50 +0100
From: Carl Knutsson <carl.knutsson@effnet.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
MIME-Version: 1.0
To: sudipkumarm@tataelxsi.co.in
References: <000001c97269$090ed7b0$761b320a@telxsi.com>
In-Reply-To: <000001c97269$090ed7b0$761b320a@telxsi.com>
X-Enigmail-Version: 0.95.0
Cc: 'Vidya Akhare' <vizz@tataelxsi.co.in>, abhisheksaurabh@tataelxsi.co.in,
	rohc@ietf.org, Gurushant G Kotagi <gurushant@tataelxsi.co.in>
Subject: Re: [rohc] RoHCv2 : Problems in decoding sequentially late packets
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

Sudip Kumar Mandal,

There is no need to identify sequentially late packets in this case.
This should be handled by the lsb encoding.

The compressor must take into account the jitter and packet loss over
the link when choosing the ROHC packet type and the number of lsb bits
sent. If reordering is causing an lsb encoded field is decompressed
incorrectly, then you have an incorrect the reording_ratio and/or a to
small sliding window (see section 5.1.2).

/Calle

Sudip Kumar Mandal wrote:
> Hi,
>  I am facing problems in decoding sequentially late packets if link
> reordering (between compressor and the decompressor) situation is being
> simulated. I am explaining the situation with
> an example:
> 
> 
> Late packet
> 
> Suppose initiallly the encoder has 0x0004 in its window and encoded value of
> 0x0004 is reached to the
> decompressor.Assuming sequential increment of the field encoder then encodes
> 0x0005 and 0x0006.
> 
> Suppose in the link the value 0x0005 and 0x0006 is lost and these value
> didn't reach the decoder,
> so the decoder still uses 0x0004 as its reference value (assuming successful
> decoding of encoded
> value of 0x0004).
> 
> Now encoder encodes 0x0007 using 0x0004,0x0005,0x0006 having in its
> reference window and it will send
> 0x0003 as its encoded value.
> Decompressor receives 0x0003 (sequentially early packet) and it can
> reconstruct, the reconstructed value
> will be 0x0007 which is offcourse equal to the original value. Decoder will
> make its reference value as 0x0007.
> 
> Now suppose the encoded value of 0x0005 (sequentially late packet) is
> reached to the decompressor. Using
> reference value of 0x0004 the encoded value of 0x0005 will be 0x0001.The
> decoder has 0x0007 in its reference
> and this time the decoded value will be 0x0008 which is not equal to the
> original value (0x0005)
> 
> I am not finding any clue how to handle sequentially late packets and how to
> identify sequentially late packet.
> According to RFC 5225 "How the decompressor detects a sequentially late
> packet is outside the scope of this specification,
> but it can for example use the MSN for this purpose", but as per my
> knowledge MSN has to be decoded first then it can be used to
> identify sequentially late packet.
> So, I would, therefore request you to suggest some idea so that the decoder
> can identify sequentially late packet before decoding the
> encoded value and it can decode it successfully.
> 
> 
> 
> Thanks & Regards
> Sudip Kumar Mandal
> Tata Elxsi Ltd
> Bangalore, India
> 
> 
> 
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc

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


From rohc-bounces@ietf.org  Tue Jan 13 03:14:30 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CEC73A69BF;
	Tue, 13 Jan 2009 03:14:30 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B2A8F3A69BF
	for <rohc@core3.amsl.com>; Tue, 13 Jan 2009 03:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bdfcywO2qmuV for <rohc@core3.amsl.com>;
	Tue, 13 Jan 2009 03:14:29 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de
	[IPv6:2001:638:708:30c9:209:3dff:fe00:7136])
	by core3.amsl.com (Postfix) with ESMTP id 7C4463A69AC
	for <rohc@ietf.org>; Tue, 13 Jan 2009 03:14:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de
	(smtp-fb3.informatik.uni-bremen.de [134.102.224.120])
	by informatik.uni-bremen.de (8.14.2/8.14.2) with ESMTP id
	n0DBE10n001358; Tue, 13 Jan 2009 12:14:01 +0100 (CET)
Received: from [10.0.1.200] (reingewinn.informatik.uni-bremen.de
	[134.102.218.123])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id
	314CB1704DA; Tue, 13 Jan 2009 12:14:01 +0100 (CET)
Message-Id: <42A3CADC-E7C3-45C8-AA47-563A2AEB7E5A@tzi.org>
From: Carsten Bormann <cabo@tzi.org>
To: Carl Knutsson <carl.knutsson@effnet.com>
In-Reply-To: <496C5176.6030105@effnet.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 13 Jan 2009 12:14:04 +0100
References: <000001c97269$090ed7b0$761b320a@telxsi.com>
	<496C5176.6030105@effnet.com>
X-Mailer: Apple Mail (2.930.3)
Cc: abhisheksaurabh@tataelxsi.co.in, rohc@ietf.org,
	Gurushant G Kotagi <gurushant@tataelxsi.co.in>,
	sudipkumarm@tataelxsi.co.in, 'Vidya Akhare' <vizz@tataelxsi.co.in>,
	Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] RoHCv2 : Problems in decoding sequentially late packets
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

On Jan 13, 2009, at 09:31, Carl Knutsson wrote:

> If reordering is causing an lsb encoded field is decompressed
> incorrectly, then you have an incorrect the reording_ratio and/or a to
> small sliding window (see section 5.1.2).


Well, the whole thing is a probability game.
So, more precisely put: If that happens often enough to result in a  
performance problem, you should use different values and sacrifice  
some compression performance.
If it happens rarely enough that it doesn't result in performance  
degradation, you probably don't care about the occasional mis- 
decompression.
Most of these cases will be caught by the header checksum, and then  
there is often a UDP checksum as well.
(Link layer checksums are not perfect even without decompression,  
either.)

Gruesse, Carsten

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



From rohc-bounces@ietf.org  Mon Feb  2 00:03:07 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4ED683A688F; Mon,  2 Feb 2009 00:03:07 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 491763A6ABA for <rohc@core3.amsl.com>; Fri, 30 Jan 2009 07:55:14 -0800 (PST)
X-Quarantine-ID: <4sXG48rNEw2v>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BANNED, message contains part: multipart/mixed | application/ms-tnef,.tnef,winmail.dat
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
X-Amavis-Modified: Mail body modified (defanged) by core3.amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4sXG48rNEw2v for <rohc@core3.amsl.com>; Fri, 30 Jan 2009 07:55:13 -0800 (PST)
Content-Type: multipart/mixed; boundary="----------=_1233330914-30353-1"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Received: from vsnlchnsym01.vsnlxchange.com (VSNLCHNSYM01.vsnlxchange.com [59.163.96.18]) by core3.amsl.com (Postfix) with ESMTP id 0E83B3A6A47 for <rohc@ietf.org>; Fri, 30 Jan 2009 07:55:10 -0800 (PST)
Received: from vsnlchnsym01.vsnlxchange.com (unknown [127.0.0.1]) by vsnlchnsym01.vsnlxchange.com (Symantec Brightmail Gateway) with ESMTP id ECAF33006 for <rohc@ietf.org>; Fri, 30 Jan 2009 21:21:51 +0530 (IST)
Received: from vamsikrishnan ([59.160.207.5]) by VSNLCHNFE001.VSNLXCHANGE.COM with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 30 Jan 2009 21:21:51 +0530
From: "Vamsikrishna" <vamsikrishna@tataelxsi.co.in>
To: <rohc@ietf.org>
Date: Fri, 30 Jan 2009 21:22:18 +0530
Message-ID: <000201c982f2$bc204de0$1a1b320a@telxsi.com>
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mailman-Approved-At: Mon, 02 Feb 2009 00:03:05 -0800
Subject: [rohc] Reordering for profile 0x0102 and 0x0104: RFC 5225
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: vamsikrishna@tataelxsi.co.in
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format...

------------=_1233330914-30353-1
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

WARNING: contains banned part

------------=_1233330914-30353-1
Content-Type: message/rfc822; x-spam-type=original; name="message"
Content-Disposition: attachment; filename="message"
Content-Transfer-Encoding: 7bit
Content-Description: Original message

Received: from vsnlchnsym01.vsnlxchange.com (VSNLCHNSYM01.vsnlxchange.com [59.163.96.18])
	by core3.amsl.com (Postfix) with ESMTP id 0E83B3A6A47
	for <rohc@ietf.org>; Fri, 30 Jan 2009 07:55:10 -0800 (PST)
Received: from vsnlchnsym01.vsnlxchange.com (unknown [127.0.0.1])
	by vsnlchnsym01.vsnlxchange.com (Symantec Brightmail Gateway) with ESMTP id ECAF33006
	for <rohc@ietf.org>; Fri, 30 Jan 2009 21:21:51 +0530 (IST)
X-AuditID: 0a480a07-a9308bb000000fc1-0c-49832217150b
Received: from vamsikrishnan ([59.160.207.5]) by VSNLCHNFE001.VSNLXCHANGE.COM with Microsoft SMTPSVC(6.0.3790.3959);
	 Fri, 30 Jan 2009 21:21:51 +0530
Reply-To: <vamsikrishna@tataelxsi.co.in>
From: "Vamsikrishna" <vamsikrishna@tataelxsi.co.in>
To: <rohc@ietf.org>
Subject: Reordering for profile 0x0102 and 0x0104: RFC 5225
Date: Fri, 30 Jan 2009 21:22:18 +0530
Message-ID: <000201c982f2$bc204de0$1a1b320a@telxsi.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_01C98320.D5DD6BE0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Importance: Normal
X-MS-TNEF-Correlator: 000000005CD69304AE14FE4D82A16600DD132ABDA4423903
X-OriginalArrivalTime: 30 Jan 2009 15:51:51.0523 (UTC) FILETIME=[AAC0D330:01C982F2]
X-Brightmail-Tracker: AAAAAQPmCRA=

This is a multi-part message in MIME format.

------=_NextPart_000_0003_01C98320.D5DD6BE0
Content-Type: text/plain;
	charset="iso-8859-1"
content-transfer-encoding: 7bit


Dear RoHCers
	
	I have a small confusion whether do we need to give the
support of Reordering for profile 0x0102 and 0x0104 or not?

In RFC 5225, he generally speaks "ROHCv2 profiles, however, 
can handle robustly and efficiently a limited amount of 
reordering after the compression point as part of the 
compression algorithm itself."

Does it mean profiles 0x0102 and 0x0104 can handle reordering?

But RFC 5225 tells to refer RFC 4224 for the impacts of 
out-of-order delivery on profiles based on rfc3095. And in 
Section 3.1 and 3.2 of RFC 4224 Tells to assaign 
interpretation interval offset p to -1 for profiles 0x002 
and 0x004. And more over RFC 4224 says these suggestions are 
applicable for the design of new profiles.
 
If Reordering is not supported for profiles 0x0102 and 0x0104
What is the need of communicating reordering_ratio value in 
Co_Common packet type, because it is already communicated through
IR and Co_Repair packets?

If a channel is configured with UDP(0x0012) or IP(0x0104) profiles
Does the channel has to guarantee us sequence delivary?.

Thanks in Advance

Regards
Vamsi krishna 


 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.

------=_NextPart_000_0003_01C98320.D5DD6BE0
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="winmail.dat"

eJ8+IhQPAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANkHAQAeABUAFgAAAAUALwEB
A5AGAPQHAAAjAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB
AAAAMwAAAFJlb3JkZXJpbmcgZm9yIHByb2ZpbGUgMHgwMTAyIGFuZCAweDAxMDQ6IFJGQyA1MjI1
AAACAXEAAQAAABYAAAAByYLyujefLgLcI9ZANZjf7MnpH2UAAAACAR0MAQAAACIAAABTTVRQOlZB
TVNJS1JJU0hOQUBUQVRBRUxYU0kuQ08uSU4AAAALAAEOAAAAAEAABg4AUM6v8oLJAQIBCg4BAAAA
GAAAAAAAAABc1pMErhT+TYKhZgDdEyq9woAAAAMAFA4BAAAACwAfDgEAAAACAQkQAQAAADMEAAAv
BAAAogYAAExaRnWR7KwZAwAKAHJjcGcxMjUWMgD4C2BuDhAwMzNPAfcCpAPjAgBjaArAc/BldDAg
BxMCgwBQBFXxAgBwcnESERDnCFUHst8Cgw5QEj8TTAKDMwRHE75uNBTIEy8UM30KgAjIILY7CW8O
MDUCgAqBdgiQlHdrC4BkGLB1YwBQHwsDC7YKsQqBAEAgRGXzCsEIAEhDBJAQsB70DJIRIFcgSSAQ
8HZlIGhhIHMAwGwDIAWgboxmdQCQAiAgd2gRMLMjMAXAZG8jECHgbgngyGQgdCOwZ2kh0SNRIR7k
c3VwcAkRIG86ZgfwZQWwBIELgGcgPwIQBcAVYCXgAxAh4DB4ujAPQDIh8B2gJ3Q0JdBhBcBub3Q/
HuUe80lhA6BSRkMgDkAOMCy7IaAh4GcJ8ASQIkF5IhAacB+QawQhIXAiUk+tH/B2J9AnBXMqgW8j
0O0h0HIqgB7kYwOREPAdoOsnUQNgYiLAdCtBJ/IBEU8N4AiQAjAvMiBsB3Bp6nQkIWEEYHUCMCXS
HuR7CXAmN2EBgBQBI1EicW2/FWAHkCLTJZALgAVAYQQgvwqxJcMzEi3FM2kHQGcFsDEwsGhtIDCw
ESBsZpQuIh7lYh7VRG8Hkf0wsCAHgAORLJYnfyiALirzJicpC0J1BUAqBiRAN1BubAQgJFEJcGYU
ASoCNH8qUCiAJsI1IyFwB3AKsGPnNzAxaAhgdC0l4EFwJkJ3I5A3UCSRcitQM+I5dmIXNHAkISLx
chDQMzA5/DUuEWAoAQuALbUGYEBw+SLiMy4fYCfyRdAn0CXiYz8FOAEgIFQ+FjRwc/ULcGcLkGMf
US21SJERUL80MQSQM4EBkEWDSaN2B0DfJdED0BEwJvAkQi0fYCbJ/znTJ8Ee5Cf1KHBEZARgCXDv
JdAtcT7oSEB5PkEjMBEg+SIQdWcq0C8QIuEEIArA/TVGYSWAMIAuIAJgIeA/if8BAACQSHAl0iQA
B+AslkdC9i4e5C21SSX7BAAowlBh3yWDJCFMHie8HuRXEPAFQN9WkTMSJAMl4TNRbTEwUhHvRYAm
kSvhMghfKxBFgUdD30rhClBEuCvhCFBfCFBbQJcCIEdDQFFrS2F0eSuA9SqAYgWQYSLAXcFaEwdA
uQlwYWQrUFsoJCJoA2D1UIBoKXVSJ+NeoSYQCrD2aSbhX5NzKQwl8CIAEOH+biQAAyBWkSKCSGAI
cCQhgwPwI1AgVURQKEzi9Q4gKSiSSWfDKGFoQFQX8yknCzBzYg9AAUBIQGqh/x9wOKIzE2YFEPA+
Q0iSK+F/ZvAKwABwMMAh4CLAIhBlcnEKUG5jIeBCEwrAef4/VNBJYTgCFKFp2RcBHvWdKIBULmEr
sUTBQWRK4LduUSkaJhBnCxEgNVYxAIkAkCBrBRBzaG4iAF9wiHUaSXEttRrBAHcQAAMACVkDAAAA
CwAAgAggBgAAAAAAwAAAAAAAAEYAAAAAA4UAAAAAAAADAAKACCAGAAAAAADAAAAAAAAARgAAAAAQ
hQAAAAAAAAMAB4AIIAYAAAAAAMAAAAAAAABGAAAAAFKFAAB9bgEAHgAJgAggBgAAAAAAwAAAAAAA
AEYAAAAAVIUAAAEAAAAEAAAAOS4wAAsAEYAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAAAwAS
gAggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALABuACCAGAAAAAADAAAAAAAAARgAAAAAOhQAA
AAAAAAMAHIAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAegAggBgAAAAAAwAAAAAAAAEYA
AAAAGIUAAAAAAAACAfgPAQAAABAAAABc1pMErhT+TYKhZgDdEyq9AgH6DwEAAAAQAAAAXNaTBK4U
/k2CoWYA3RMqvQIB+w8BAAAAUQAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABtc3BzdC5kbGwAAAAA
AE5JVEH5v7gBAKoAN9luAAAARDpcdmFtc2kgbWFpbCdzXG1haWxib3gucHN0AAAAAAMA/g8FAAAA
AwANNP03AAACAX8AAQAAADEAAAAwMDAwMDAwMDVDRDY5MzA0QUUxNEZFNEQ4MkExNjYwMEREMTMy
QUJEQTQ0MjM5MDMAAAAAAwAGEMrlcS0DAAcQjAMAAAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAGUA
AABERUFSUk9IQ0VSU0lIQVZFQVNNQUxMQ09ORlVTSU9OV0hFVEhFUkRPV0VORUVEVE9HSVZFVEhF
U1VQUE9SVE9GUkVPUkRFUklOR0ZPUlBST0ZJTEUwWDAxMDJBTkQwWDAxMDRPAAAAAFcJ

------=_NextPart_000_0003_01C98320.D5DD6BE0--


------------=_1233330914-30353-1
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://www.ietf.org/mailman/listinfo/rohc

------------=_1233330914-30353-1--

From rohc-bounces@ietf.org  Mon Feb  2 02:01:35 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F8C93A68CF; Mon,  2 Feb 2009 02:01:35 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 933593A689F for <rohc@core3.amsl.com>; Mon,  2 Feb 2009 02:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gl7UmOWbaNBG for <rohc@core3.amsl.com>; Mon,  2 Feb 2009 02:01:32 -0800 (PST)
Received: from lists.levonline.com (lists.levonline.com [217.70.33.37]) by core3.amsl.com (Postfix) with ESMTP id 7AD013A6896 for <rohc@ietf.org>; Mon,  2 Feb 2009 02:01:31 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by lists.levonline.com (Postfix) with ESMTP id 2EEA229C07B; Mon,  2 Feb 2009 11:00:49 +0100 (CET)
X-Virus-Scanned: By http://levonline.com - free virus scanning for all customers
Received: from lists.levonline.com ([127.0.0.1]) by localhost (lists.levonline.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6W78Ve+Mgpu; Mon,  2 Feb 2009 11:00:48 +0100 (CET)
Received: from truck1.fordonnet.levonline.com (truck1.fordonnet.levonline.com [192.168.18.21]) by lists.levonline.com (Postfix) with ESMTP id ECE9329C061; Mon,  2 Feb 2009 11:00:47 +0100 (CET)
Received: from [192.168.101.51] (c-f97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.124.249]) (authenticated bits=0) by truck1.fordonnet.levonline.com (8.12.11.20060308/8.12.11) with ESMTP id n12A0bDe006751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Feb 2009 11:00:45 +0100
Message-ID: <4986C45C.6060407@effnet.com>
Date: Mon, 02 Feb 2009 11:01:00 +0100
From: Carl Knutsson <carl.knutsson@effnet.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: vamsikrishna@tataelxsi.co.in
References: <000201c982f2$bc204de0$1a1b320a@telxsi.com>
In-Reply-To: <000201c982f2$bc204de0$1a1b320a@telxsi.com>
X-Enigmail-Version: 0.95.0
Cc: rohc@ietf.org
Subject: Re: [rohc] Reordering for profile 0x0102 and 0x0104: RFC 5225
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

Vamsi krishna,

Vamsikrishna wrote:
> 
> Dear RoHCers
> 	
> 	I have a small confusion whether do we need to give the
> support of Reordering for profile 0x0102 and 0x0104 or not?
> 
> In RFC 5225, he generally speaks "ROHCv2 profiles, however, 
> can handle robustly and efficiently a limited amount of 
> reordering after the compression point as part of the 
> compression algorithm itself."
> 
> Does it mean profiles 0x0102 and 0x0104 can handle reordering?
> 
I think you will find the answer in RFC5225 section 4.3. "Operational
Characteristics of ROHCv2 Profiles". Note that the text you are refering
to is in section "Improvements of ROHCv2 over RFC 3095 Profiles" and is
a general description of differences between RFC3095 and RFC5225.

Other recommended reading would be section 5.1.1. "Optimistic Approach"
and section 5.1.2. "Tradeoff between Robustness to Losses and to
Reordering".

> But RFC 5225 tells to refer RFC 4224 for the impacts of 
> out-of-order delivery on profiles based on rfc3095. And in 
> Section 3.1 and 3.2 of RFC 4224 Tells to assaign 
> interpretation interval offset p to -1 for profiles 0x002 
> and 0x004. And more over RFC 4224 says these suggestions are 
> applicable for the design of new profiles.
>  
> If Reordering is not supported for profiles 0x0102 and 0x0104
> What is the need of communicating reordering_ratio value in 
> Co_Common packet type, because it is already communicated through
> IR and Co_Repair packets?
> 
It was a design decision. We have several other fields that are present
in several different packet types: TOS, TTL for example. I can think of
more than one reason to have reordering_ratio in co_common. For example
a cheap way of changing reordering_ratio etc.

> If a channel is configured with UDP(0x0012) or IP(0x0104) profiles
> Does the channel has to guarantee us sequence delivary?.
> 
see RFC5225 section 4.3.


Best regards,

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

From rohc-bounces@ietf.org  Mon Feb  2 10:45:02 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C18963A6B2B; Mon,  2 Feb 2009 10:45:02 -0800 (PST)
X-Original-To: rohc@ietf.org
Delivered-To: rohc@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id BC8B43A6B2B; Mon,  2 Feb 2009 10:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090202184501.BC8B43A6B2B@core3.amsl.com>
Date: Mon,  2 Feb 2009 10:45:01 -0800 (PST)
Cc: rohc@ietf.org
Subject: [rohc] I-D Action:draft-ietf-rohc-hcoipsec-10.txt
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
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-10.txt
	Pages           : 13
	Date            : 2009-02-02

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-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-rohc-hcoipsec-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-02103843.I-D@ietf.org>


--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://www.ietf.org/mailman/listinfo/rohc

--NextPart--

From rohc-bounces@ietf.org  Mon Feb  2 10:45:04 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC0D03A6BE0; Mon,  2 Feb 2009 10:45:04 -0800 (PST)
X-Original-To: rohc@ietf.org
Delivered-To: rohc@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id C46A93A6BAC; Mon,  2 Feb 2009 10:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090202184501.C46A93A6BAC@core3.amsl.com>
Date: Mon,  2 Feb 2009 10:45:01 -0800 (PST)
Cc: rohc@ietf.org
Subject: [rohc] I-D Action:draft-ietf-rohc-ikev2-extensions-hcoipsec-08.txt
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
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)       : E. Ertekin, et al.
	Filename        : draft-ietf-rohc-ikev2-extensions-hcoipsec-08.txt
	Pages           : 10
	Date            : 2009-02-02

In order to integrate ROHC with IPsec [ROHCOIPSEC], a mechanism is
needed to signal ROHC channel parameters between end-points.
Internet Key Exchange (IKE) is a mechanism which can be leveraged to
exchange these parameters.  This document specifies extensions to
IKEv2 [IKEV2] that will allow ROHC and its associated channel
parameters to be signaled for IPsec security associations (SAs).

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-rohc-ikev2-extensions-hcoipsec-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-02103859.I-D@ietf.org>


--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://www.ietf.org/mailman/listinfo/rohc

--NextPart--

From rohc-bounces@ietf.org  Mon Feb  2 10:45:05 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F10FB3A6BE4; Mon,  2 Feb 2009 10:45:04 -0800 (PST)
X-Original-To: rohc@ietf.org
Delivered-To: rohc@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id C84B83A6BC5; Mon,  2 Feb 2009 10:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090202184501.C84B83A6BC5@core3.amsl.com>
Date: Mon,  2 Feb 2009 10:45:01 -0800 (PST)
Cc: rohc@ietf.org
Subject: [rohc] I-D Action:draft-ietf-rohc-ipsec-extensions-hcoipsec-04.txt
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
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           : IPsec Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)
	Author(s)       : E. Ertekin, et al.
	Filename        : draft-ietf-rohc-ipsec-extensions-hcoipsec-04.txt
	Pages           : 10
	Date            : 2009-02-02

Integrating ROHC with IPsec (ROHCoIPsec) offers the combined benefits
of IP security services and efficient bandwidth utilization.
However, in order to integrate ROHC with IPsec, extensions to the SPD
and SAD are required.  This document describes the IPsec extensions
required to support ROHCoIPsec.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-rohc-ipsec-extensions-hcoipsec-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-02-02103917.I-D@ietf.org>


--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://www.ietf.org/mailman/listinfo/rohc

--NextPart--

From rohc-bounces@ietf.org  Mon Feb  2 10:54:13 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D36803A69DD; Mon,  2 Feb 2009 10:54:13 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 55FCC3A69DD for <rohc@core3.amsl.com>; Mon,  2 Feb 2009 10:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.378
X-Spam-Level: 
X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5 tests=[AWL=0.221,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5UWbYipv+QAw for <rohc@core3.amsl.com>; Mon,  2 Feb 2009 10:53:41 -0800 (PST)
Received: from mclniron01-ext.bah.com (mclniron01-ext.bah.com [156.80.1.71]) by core3.amsl.com (Postfix) with ESMTP id 6D30E3A67B5 for <rohc@ietf.org>; Mon,  2 Feb 2009 10:53:41 -0800 (PST)
x-SBRS: None
X-REMOTE-IP: 156.80.7.152
X-IronPort-AV: E=Sophos;i="4.37,366,1231131600";  d="scan'208";a="349433"
Received: from bahmail.bah.com (HELO mclnexbh02.resource.ds.bah.com) ([156.80.7.152]) by mclniron01-int.bah.com with ESMTP; 02 Feb 2009 13:53:22 -0500
Received: from MCLNEXVS05.resource.ds.bah.com ([156.80.7.121]) by mclnexbh02.resource.ds.bah.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Feb 2009 13:53:22 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 2 Feb 2009 13:53:20 -0500
Message-ID: <37BDD2FAF2AEAE459C6C70FDC2892E4E03F79404@MCLNEXVS05.resource.ds.bah.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Updated ROHCoIPsec I-Ds
Thread-Index: AcmFZ4QjsOnTOyz1SpKXPeS5mIE93g==
From: "Ertekin, Emre [USA]" <ertekin_emre@bah.com>
To: "rohc" <rohc@ietf.org>
X-OriginalArrivalTime: 02 Feb 2009 18:53:22.0193 (UTC) FILETIME=[85567010:01C98567]
Cc: Yoav Nir <ynir@checkpoint.com>
Subject: [rohc] Updated ROHCoIPsec I-Ds
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

Hi All, 

We have revised the three ROHCoIPsec internet-drafts based on comments
we received during the WGLC.  The updated drafts can be found at:

http://www.ietf.org/internet-drafts/draft-ietf-rohc-hcoipsec-10.txt
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ikev2-extensions-hco
ipsec-08.txt
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ipsec-extensions-hco
ipsec-04.txt

-------------------------

The following summarizes major changes to each draft:

(1)  draft-ietf-rohc-hcoipsec-10.txt:
	-- Clarified Section 5.2 to indicate that ROHCoIPsec poses
challenges for devices inspecting ESP-NULL encrypted packets
	-- Added a paragraph to Section 6.1; the paragraph references
RFC 3759 (to help describe ROHCoIPsec operation)

(2)  draft-ietf-rohc-ikev2-extensions-hcoipsec-08:
	-- Updated text throughout the draft to reflect a
signaling-based approach for initialization of ROHC channel parameters
	-- Updated the format of the ROHC_SUPPORTED Notify message; the
contents of this message are now expressed through "ROHC Attribute
Types"
	-- Added the capability to signal an ICV length for the
integrity algorithm used in conjunction with ROHC
	-- Included text in the IANA considerations section that
requests allocations for "ROHC Attribute Types" within the IKEv2
Parameters registry
	
(3)  draft-ietf-rohc-ipsec-extensions-hcoipsec-04:
	-- Clarified that the ROHC Data Item exists for both inbound and
outbound SAs, and the channel parameters associated with
inbound/outbound SAs
	-- Updated the Security considerations section: deleted text
which recommended that the strength of the integrity check used with
ROHC should be at least the same strength as the integrity-check used
with IPsec; furthermore, indicated that the use of padding to mitigate
traffic flow analysis reduces the efficiency gains offered by header
compression

--------------------------

Thanks to Yoav and Bob who served as CDRs during the WGLC.  Thanks also
to the wider ROHC working group for their review of these documents.  

Please let me know if you have any questions.

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

From rohc-bounces@ietf.org  Tue Feb  3 09:24:33 2009
Return-Path: <rohc-bounces@ietf.org>
X-Original-To: rohc-archive@megatron.ietf.org
Delivered-To: ietfarch-rohc-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B426F3A6B17; Tue,  3 Feb 2009 09:24:33 -0800 (PST)
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66EA13A6B17 for <rohc@core3.amsl.com>; Tue,  3 Feb 2009 09:24:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j7T6yhPMhG3b for <rohc@core3.amsl.com>; Tue,  3 Feb 2009 09:24:32 -0800 (PST)
Received: from bear.ext.ti.com (bear.ext.ti.com [192.94.94.41]) by core3.amsl.com (Postfix) with ESMTP id A483B3A68ED for <rohc@ietf.org>; Tue,  3 Feb 2009 09:24:32 -0800 (PST)
Received: from dlep95.itg.ti.com ([157.170.170.107]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id n13HO8Ut025149 for <rohc@ietf.org>; Tue, 3 Feb 2009 11:24:13 -0600
Received: from dlee75.ent.ti.com (localhost [127.0.0.1]) by dlep95.itg.ti.com (8.13.8/8.13.8) with ESMTP id n13HO8s5006417 for <rohc@ietf.org>; Tue, 3 Feb 2009 11:24:08 -0600 (CST)
Received: from dlee04.ent.ti.com ([157.170.170.9]) by dlee75.ent.ti.com ([157.170.170.72]) with mapi; Tue, 3 Feb 2009 11:24:08 -0600
From: "Smith, Stephen" <smsmith@ti.com>
To: "rohc@ietf.org" <rohc@ietf.org>
Date: Tue, 3 Feb 2009 11:24:06 -0600
Thread-Topic: packet traces availability?
Thread-Index: Ack8IwvTDn/qn8+GQvuwO3xfC3hZ+hJ/y+eg
Message-ID: <23D0CDE7C386D144A4F26EB0F427F8C021EC808A@dlee04.ent.ti.com>
References: <Pine.GSO.4.58.0811011359590.18326@brother.ludd.ltu.se>
In-Reply-To: <Pine.GSO.4.58.0811011359590.18326@brother.ludd.ltu.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: [rohc] packet traces availability?
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org

All,

Sorry for spamming the list, but I have seen several references (for example, the 2001 bake off slides) to the availability of ROHC packet traces to aid in testing.  Does anyone have any information?  I googled through this list, didn't see anything offhand, but could have missed it.

If none are available, what is the general consensus on interop testing during development?

Any help would be appreciated.

Thanks,
Stephen

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

Return-Path: <bsarkar@starentnetworks.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1C113A6B52 for <rohc@core3.amsl.com>; Tue,  3 Feb 2009 20:54:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hbxa7i86pFAQ for <rohc@core3.amsl.com>; Tue,  3 Feb 2009 20:54:06 -0800 (PST)
Received: from mx0.starentnetworks.com (mx0.starentnetworks.com [12.38.223.203]) by core3.amsl.com (Postfix) with ESMTP id D82353A6B51 for <rohc@ietf.org>; Tue,  3 Feb 2009 20:54:05 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx0.starentnetworks.com (Postfix) with ESMTP id E0F4C90257; Tue,  3 Feb 2009 23:53:42 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1]) by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11973-10; Tue, 3 Feb 2009 23:53:41 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com [10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP; Tue,  3 Feb 2009 23:53:41 -0500 (EST)
Received: from exchindia3.starentnetworks.com ([10.6.7.5]) by exchtewks1.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Feb 2009 23:53:41 -0500
Received: from [10.6.7.67] ([10.6.7.67]) by exchindia3.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 4 Feb 2009 10:23:36 +0530
Message-ID: <49891F4A.5070304@starentnetworks.com>
Date: Wed, 04 Feb 2009 10:23:30 +0530
From: Sarkar Biplab <bsarkar@starentnetworks.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: "Smith, Stephen" <smsmith@ti.com>
References: <Pine.GSO.4.58.0811011359590.18326@brother.ludd.ltu.se> <23D0CDE7C386D144A4F26EB0F427F8C021EC808A@dlee04.ent.ti.com>
In-Reply-To: <23D0CDE7C386D144A4F26EB0F427F8C021EC808A@dlee04.ent.ti.com>
X-Enigmail-Version: 0.95.7
OpenPGP: url=http://pgp.mit.edu:11371/pks/lookup?search=0x6D543EEE&op=index
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig150B9F327B885289727A4D01"
X-OriginalArrivalTime: 04 Feb 2009 04:53:36.0004 (UTC) FILETIME=[89A7A440:01C98684]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
Cc: "rohc@ietf.org" <rohc@ietf.org>
Subject: Re: [rohc] packet traces availability?
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 04:54:07 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig150B9F327B885289727A4D01
Content-Type: multipart/alternative;
 boundary="------------040501000307040505040003"

This is a multi-part message in MIME format.
--------------040501000307040505040003
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Stephen,

A stateless packet tracer can understand but not distinguish all the
ROHC packets. There are some proprietary implementations of the same.
But I haven't seen an open source implementation yet.

Thanks
Biplab


Smith, Stephen wrote:
> All,
>
> Sorry for spamming the list, but I have seen several references (for ex=
ample, the 2001 bake off slides) to the availability of ROHC packet trace=
s to aid in testing.  Does anyone have any information?  I googled throug=
h this list, didn't see anything offhand, but could have missed it.
>
> If none are available, what is the general consensus on interop testing=
 during development?
>
> Any help would be appreciated.
>
> Thanks,
> Stephen
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc
>  =20


--------------040501000307040505040003
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content=3D"text/html;charset=3DISO-8859-1" http-equiv=3D"Content-=
Type">
</head>
<body bgcolor=3D"#ffffff" text=3D"#000066">
Hello Stephen,<br>
<br>
A stateless packet tracer can understand but not distinguish all the
ROHC packets. There are some proprietary implementations of the same.
But I haven't seen an open source implementation yet.<br>
<br>
Thanks<br>
Biplab<br>
<br>
<br>
Smith, Stephen wrote:
<blockquote
 cite=3D"mid:23D0CDE7C386D144A4F26EB0F427F8C021EC808A@dlee04.ent.ti.com"
 type=3D"cite">
  <pre wrap=3D"">All,

Sorry for spamming the list, but I have seen several references (for exam=
ple, the 2001 bake off slides) to the availability of ROHC packet traces =
to aid in testing.  Does anyone have any information?  I googled through =
this list, didn't see anything offhand, but could have missed it.

If none are available, what is the general consensus on interop testing d=
uring development?

Any help would be appreciated.

Thanks,
Stephen

_______________________________________________
Rohc mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Rohc@ietf.org">Rohc@=
ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/rohc">https://www.ietf.org/mailman/listinfo/rohc</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------040501000307040505040003--

--------------enig150B9F327B885289727A4D01
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJiR9M3rQBTW1UPu4RAoH6AKC4gh4FFc4aORBKA7Dn0w/bWiGZAACfcvFE
K0HLa+rOsHHD1mUTGukJMzU=
=Mida
-----END PGP SIGNATURE-----

--------------enig150B9F327B885289727A4D01--


Return-Path: <pradeep.shambhu@gmail.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E823028C1B0 for <rohc@core3.amsl.com>; Wed,  4 Feb 2009 05:10:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sq0QHoTRX+ll for <rohc@core3.amsl.com>; Wed,  4 Feb 2009 05:10:25 -0800 (PST)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id D310228C232 for <rohc@ietf.org>; Wed,  4 Feb 2009 05:10:24 -0800 (PST)
Received: by qw-out-2122.google.com with SMTP id 3so977826qwe.31 for <rohc@ietf.org>; Wed, 04 Feb 2009 05:10:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=XMao0EhydNNKw++NFewaEB+P+ASzxpzi0ZBJDzsOPQI=; b=bsZvC9UgKjcgtPwcLR0bDgQpdGOlBAGbYWv+5qCZvP7zm+sm3tLLUHZxnx5HGOVkSS 5kC1DG8TLycx+UZJ7i4GmxLb2KNR6HmdRI3UcksUe6swMvZ+uPm4RmUwNoWP5FOMo/iW XpIqblajV2p1m/6TMj0Gy14ZFuBmBGOt+jJpA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=AvkwJN6zeyJpR6CDW5YtWeLdZzRj3/djWWinMRxlFE9bCJPC5kQB+3N+hy2oCUWs2u pDk8Ef+2axkUYTKweZcrQ98xk/euPyBYcEFrGU9Bf7CAixLR5ct8AhQFKD5QsSyuxmyJ +assbU4O7bgL7nyvlnUHPf7r5UTqAYmRU7ASg=
MIME-Version: 1.0
Received: by 10.214.184.14 with SMTP id h14mr7970593qaf.178.1233753003267;  Wed, 04 Feb 2009 05:10:03 -0800 (PST)
Date: Wed, 4 Feb 2009 18:40:03 +0530
Message-ID: <aa02215c0902040510o32edcdeet67efc12a1f2a6518@mail.gmail.com>
From: pradeep shambhu <pradeep.shambhu@gmail.com>
To: rohc@ietf.org
Content-Type: multipart/alternative; boundary=0015175cdeb2801975046217813f
Subject: [rohc] Two-way matching operation in ROHC-FN(4887)
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 13:10:26 -0000

--0015175cdeb2801975046217813f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

What is two way matching process in ROHC-FN & in what way it is similar to
unification process?



With Regards,
Pradeep Shambhu
Kyocera Wireless India
9986484414



On Wed, Feb 4, 2009 at 1:30 AM, <rohc-request@ietf.org> wrote:

> Send Rohc mailing list submissions to
>        rohc@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://www.ietf.org/mailman/listinfo/rohc
> or, via email, send a message with subject or body 'help' to
>        rohc-request@ietf.org
>
> You can reach the person managing the list at
>        rohc-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Rohc digest..."
>
>
> Today's Topics:
>
>   1. packet traces availability? (Smith, Stephen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 3 Feb 2009 11:24:06 -0600
> From: "Smith, Stephen" <smsmith@ti.com>
> Subject: [rohc] packet traces availability?
> To: "rohc@ietf.org" <rohc@ietf.org>
> Message-ID:
>        <23D0CDE7C386D144A4F26EB0F427F8C021EC808A@dlee04.ent.ti.com>
> Content-Type: text/plain; charset="us-ascii"
>
> All,
>
> Sorry for spamming the list, but I have seen several references (for
> example, the 2001 bake off slides) to the availability of ROHC packet traces
> to aid in testing.  Does anyone have any information?  I googled through
> this list, didn't see anything offhand, but could have missed it.
>
> If none are available, what is the general consensus on interop testing
> during development?
>
> Any help would be appreciated.
>
> Thanks,
> Stephen
>
>
>
> ------------------------------
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc
>
>
> End of Rohc Digest, Vol 58, Issue 2
> ***********************************
>

--0015175cdeb2801975046217813f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

What is two way matching process in ROHC-FN &amp; in what way it is similar=
 to unification process?<br><br><br><br clear=3D"all">With Regards,<br>Prad=
eep Shambhu<br>Kyocera Wireless India<br>9986484414<br><br>
<br><br><div class=3D"gmail_quote">On Wed, Feb 4, 2009 at 1:30 AM,  <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:rohc-request@ietf.org">rohc-request@ietf.o=
rg</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"bord=
er-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-l=
eft: 1ex;">
Send Rohc mailing list submissions to<br>
 &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:rohc@ietf.org">rohc@ietf.org<=
/a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
 &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"https://www.ietf.org/mailman/listinf=
o/rohc" target=3D"_blank">https://www.ietf.org/mailman/listinfo/rohc</a><br=
>
or, via email, send a message with subject or body &#39;help&#39; to<br>
 &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:rohc-request@ietf.org">rohc-r=
equest@ietf.org</a><br>
<br>
You can reach the person managing the list at<br>
 &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:rohc-owner@ietf.org">rohc-own=
er@ietf.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of Rohc digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
 &nbsp; 1. packet traces availability? (Smith, Stephen)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 3 Feb 2009 11:24:06 -0600<br>
From: &quot;Smith, Stephen&quot; &lt;<a href=3D"mailto:smsmith@ti.com">smsm=
ith@ti.com</a>&gt;<br>
Subject: [rohc] packet traces availability?<br>
To: &quot;<a href=3D"mailto:rohc@ietf.org">rohc@ietf.org</a>&quot; &lt;<a h=
ref=3D"mailto:rohc@ietf.org">rohc@ietf.org</a>&gt;<br>
Message-ID:<br>
 &nbsp; &nbsp; &nbsp; &nbsp;&lt;<a href=3D"mailto:23D0CDE7C386D144A4F26EB0F=
427F8C021EC808A@dlee04.ent.ti.com">23D0CDE7C386D144A4F26EB0F427F8C021EC808A=
@dlee04.ent.ti.com</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br>
<br>
All,<br>
<br>
Sorry for spamming the list, but I have seen several references (for exampl=
e, the 2001 bake off slides) to the availability of ROHC packet traces to a=
id in testing. &nbsp;Does anyone have any information? &nbsp;I googled thro=
ugh this list, didn&#39;t see anything offhand, but could have missed it.<b=
r>

<br>
If none are available, what is the general consensus on interop testing dur=
ing development?<br>
<br>
Any help would be appreciated.<br>
<br>
Thanks,<br>
Stephen<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Rohc mailing list<br>
<a href=3D"mailto:Rohc@ietf.org">Rohc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/rohc" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/rohc</a><br>
<br>
<br>
End of Rohc Digest, Vol 58, Issue 2<br>
***********************************<br>
</blockquote></div><br>

--0015175cdeb2801975046217813f--


Return-Path: <mihirjm@gmail.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0B273A6BD3 for <rohc@core3.amsl.com>; Wed, 25 Feb 2009 19:41:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tof9YSgjZ7e3 for <rohc@core3.amsl.com>; Wed, 25 Feb 2009 19:41:06 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id 0D4C03A6BCC for <rohc@ietf.org>; Wed, 25 Feb 2009 19:41:06 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 27so387259wfd.31 for <rohc@ietf.org>; Wed, 25 Feb 2009 19:41:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=WmstgGFkVyu1hZAz7tE8x0a3XE7AKp6X5uYZquJG14M=; b=hwuVEIL82+e9+wCsPiKY7VZiQ+xIikcJwLDIdFhYNLscBubeiJOUwDyOIdk+IISTX9 y7xjlH+ELKJ0sx+TmaOAxa2avqzQflCLhL2SJNR37sGyf27bWFe/H7scO9u5ZwqfcVto yBh7C5rLmtzFN6Mle+IXOYfHeIi5fNqPWS4co=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=KFQ5Kc6gH1hycFx8kwGwfB+OcPkjyOPlTxEpMrHEwdz8tWA7OPxp84E2usu2Uh77IZ fQggGgzqbyo4AvLe1ftdUAAD4Uc0d+whaxf3opDPMijfCXF4FrDXpPEzvIbmT5MzOFmJ xdXsS45ceCA0AEMFo6fvcZe1+vbxwpHpYqQ5o=
MIME-Version: 1.0
Received: by 10.142.76.15 with SMTP id y15mr415312wfa.263.1235619687112; Wed,  25 Feb 2009 19:41:27 -0800 (PST)
Date: Thu, 26 Feb 2009 11:41:27 +0800
Message-ID: <86c08c690902251941o30b5c809m455e8c1344275370@mail.gmail.com>
From: Mihir Mehta <mihirjm@gmail.com>
To: rohc@ietf.org
Content-Type: multipart/alternative; boundary=001636e1fd018720f40463ca20d4
Subject: [rohc] Calculating TS_Stride value
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 03:41:06 -0000

--001636e1fd018720f40463ca20d4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dear All,

Could anyone help me to know how to calculate the TS_Stride value by looking
at the RTP TS field.

In most cases, it is assumed to be 160 assuming that the audio sampling rate
is 8khz and and 1 voice frame 'may' cover 20ms. There could be a possibility
that the voice frame may cover less than 20ms. In that case what would be
the best way to calculate the TS_Stride value?

Further,assuming that the sampling rate is also unknown, in that case how
can one caculate the TS_Stride value?

Could someone kindly help me?

Thanks in advance
Mihir

--001636e1fd018720f40463ca20d4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear All,<div><br></div><div><br></div><div>Could anyone help me to know ho=
w to calculate the TS_Stride value by looking at the RTP TS field.</div><di=
v><br></div><div>In most cases, it is assumed to be 160 assuming that the a=
udio sampling rate is 8khz and and 1 voice frame &#39;may&#39; cover 20ms. =
There could be a possibility that the voice frame may cover less than 20ms.=
 In that case what would be the best way to calculate the TS_Stride value?<=
/div>
<div><br></div><div>Further,assuming that the sampling rate is also unknown=
, in that case how can one caculate the TS_Stride value?</div><div><br></di=
v><div>Could someone kindly help me?</div><div><br></div><div>Thanks in adv=
ance</div>
<div>Mihir</div>

--001636e1fd018720f40463ca20d4--


Return-Path: <gcpradeep@tataelxsi.co.in>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B70C3A67F7 for <rohc@core3.amsl.com>; Thu, 26 Feb 2009 05:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.398
X-Spam-Level: *
X-Spam-Status: No, score=1.398 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYmdOxLIZNcx for <rohc@core3.amsl.com>; Thu, 26 Feb 2009 05:07:30 -0800 (PST)
Received: from vsnlchnsym02.vsnlxchange.com (VSNLCHNSYM02.vsnlxchange.com [59.163.96.19]) by core3.amsl.com (Postfix) with ESMTP id 26CA93A6B2F for <rohc@ietf.org>; Thu, 26 Feb 2009 05:07:30 -0800 (PST)
Received: from vsnlchnsym02.vsnlxchange.com (unknown [127.0.0.1]) by vsnlchnsym02.vsnlxchange.com (Symantec Brightmail Gateway) with ESMTP id EF85D1A78 for <rohc@ietf.org>; Thu, 26 Feb 2009 18:37:17 +0530 (IST)
X-AuditID: 0a480a09-a39a5bb000005f33-d5-49a69404a9b5
Received: from gcpradeep ([59.160.207.5]) by VSNLCHNFE001.VSNLXCHANGE.COM with Microsoft SMTPSVC(6.0.3790.3959); Thu, 26 Feb 2009 18:36:32 +0530
From: "Chaitanya Pradeep" <gcpradeep@tataelxsi.co.in>
To: <rohc@ietf.org>
Date: Thu, 26 Feb 2009 18:37:05 +0530
Message-ID: <000501c99813$1fdabfc0$cd1a320a@telxsi.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C99841.3992FBC0"
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: High
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-OriginalArrivalTime: 26 Feb 2009 13:06:32.0463 (UTC) FILETIME=[0BAFA1F0:01C99813]
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Thu, 26 Feb 2009 05:19:22 -0800
Subject: [rohc] Query regarding V2 Profile Classification (Profile 0x104)
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gcpradeep@tataelxsi.co.in
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 13:10:31 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C99841.3992FBC0
Content-Type: text/plain;
	charset="iso-8859-1"
content-transfer-encoding: 7bit

Dear RoHC ers,

     I am facing ambiguity regarding (Profile 0x104) classification in RoHC
V2 Profiles.

     1. On what basis we will choose Profile 0x104 in Version-2 Profiles?

         Because, as mentioned in RFC 5225, all the Profiles present
         in Rohc Version-2 support arbitrary number of IP Levels. So how do
we differentiate between Profile0x104 and
         rest of Profiles (i.e, like Profile0x101 , Profile0x102 ,
Profile0x103 etc) in V2 to classify which Profile the
         Packet stream belongs to?

     2. Is the interpretation correct?

          a) Profile 0x104 is chosen when the Input packet contains only IP
headers and not ended by any RTP/UDP/ESP/TCP headers. (or)
          b) Profile 0x104 is chosen only when no other V2 profile is
supported by the compressor entity other than Profile 0x104.

  Pls share your valuble thoughts regarding the same.

Thanks,
Pradeep.















The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.

------=_NextPart_000_0006_01C99841.3992FBC0
Content-Type: text/html;
	charset="iso-8859-1"
content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-1=
">


<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D883285312-26022009>Dear RoHC=
 
ers,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp; I am facing ambiguity 
regarding (Profile 0x104)&nbsp;classification in RoHC V2 
Profiles.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp; 1. On what basis we will=
 
choose Profile 0x104&nbsp;in Version-2 Profiles?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;Because, as&nbsp;mentioned in RFC 5225,&nbsp;all the Profiles present=
 
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 in 
Rohc Version-2 support arbitrary number of IP Levels. So how do we different=
iate 
between Profile0x104 and </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 rest 
of Profiles (i.e, like Profile0x101 , Profile0x102 , Profile0x103 etc) in V2=
 to 
classify which Profile the</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D883285312-26022009>&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Packet stream belongs 
to?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.&nbsp;Is the 
interpretation correct?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;a) 
Profile 0x104 is chosen when the Input packet contains only IP headers and n=
ot 
ended by any RTP/UDP/ESP/TCP headers. (or)</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D883285312-26022009>&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Profile 0x104 is chosen only 
when&nbsp;no other V2 profile is supported by the compressor entity other th=
an 
Profile 0x104.&nbsp;</SPAN></FONT><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D883285312-26022009>&nbsp; 
Pls&nbsp;share your valuble thoughts regarding the same.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>Pradeep.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN 
class=3D883285312-26022009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D883285312-26022009>&nbsp;&nbs=
p;&nbsp; 
</SPAN></FONT></DIV><p>The information contained in this electronic message=
 and any attachments to this message are intended for the exclusive use of t=
he addressee(s) and may contain proprietary, confidential or privileged info=
rmation. If you are not the intended recipient, you should not disseminate,=
 distribute or copy this e-mail. Please notify the sender immediately and de=
stroy all copies of this message and any attachments contained in it.</p>
</BODY></HTML>

------=_NextPart_000_0006_01C99841.3992FBC0--



Return-Path: <stangarr@nkiconsulting.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 731403A6BF6 for <rohc@core3.amsl.com>; Thu, 26 Feb 2009 07:13:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4G4vujop2Q0 for <rohc@core3.amsl.com>; Thu, 26 Feb 2009 07:13:11 -0800 (PST)
Received: from ins2.sd.spawar.navy.mil (ins2.sd.spawar.navy.mil [IPv6:2001:480:10:4::3]) by core3.amsl.com (Postfix) with ESMTP id F10EF3A6A4C for <rohc@ietf.org>; Thu, 26 Feb 2009 07:13:09 -0800 (PST)
Received: from pescado.nosc.mil (pescado.nosc.mil [128.49.4.90]) by ins2.sd.spawar.navy.mil (8.13.1/8.13.1) with ESMTP id n1QFDS9V015640 for <rohc@ietf.org>; Thu, 26 Feb 2009 07:13:28 -0800
Received: from [128.49.162.148] (alderon.sd.spawar.navy.mil [128.49.162.148]) by pescado.nosc.mil (Netscape Messaging Server 4.15) with ESMTP id KFOIAG00.IZ4; Thu, 26 Feb 2009 07:13:28 -0800 
Message-ID: <49A6B190.2090000@nkiconsulting.com>
Date: Thu, 26 Feb 2009 07:13:20 -0800
From: Robert Stangarone <stangarr@nkiconsulting.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: gcpradeep@tataelxsi.co.in, rohc@ietf.org
Content-Type: multipart/mixed; boundary="------------080001050801010102000308"
Cc: stangarr@nkiconsulting.com
Subject: [rohc] [Fwd: Query regarding V2 Profile Classification (Profile 0x104)]
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 15:13:12 -0000

This is a multi-part message in MIME format.
--------------080001050801010102000308
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Pradeep,

Re 1):

In the case of the decompressor, the IR packet explicitly binds the 
Context ID to a Profile and Context, and that is how the ROHC 
decompressor determines which Profile the Packet stream belongs to.

In the case of the compressor, I'd think that any incoming packets that 
matched an available Profile would be compared to the existing 
Context(s) to determine if the packets were related to an existing 
Compressed flow in order to determine what action to take, such as 
creating a new Context, or updating an existing one.

Re 2):

I'd say that you would use Profile 0x0104 as the last choice of your 
ROHC Profiles.

This would allow you to use any other supported Profiles first, and 
benefit from the resulting compression.

Profile 0x0104 would only be used after it was found that none of the 
other non-IP headers were present to be compressed.

Bob

-------- Original Message --------
Subject: 	Query regarding V2 Profile Classification (Profile 0x104)
Date: 	Thu, 26 Feb 2009 18:35:19 +0530
From: 	Chaitanya Pradeep <gcpradeep@tataelxsi.co.in>
Reply-To: 	gcpradeep@tataelxsi.co.in
To: 	<ietf@ietf.org>



Dear RoHC ers,

      I am facing ambiguity regarding (Profile 0x104) classification in
RoHC V2 Profiles.

      1. On what basis we will choose Profile 0x104 in Version-2 Profiles?

          Because, as mentioned in RFC 5225, all the Profiles present
          in Rohc Version-2 support arbitrary number of IP Levels. So how
do we differentiate between Profile0x104 and
          rest of Profiles (i.e, like Profile0x101 , Profile0x102 ,
Profile0x103 etc) in V2 to classify which Profile the
          Packet stream belongs to?

      2. Is the interpretation correct?

           a) Profile 0x104 is chosen when the Input packet contains only
IP headers and not ended by any RTP/UDP/ESP/TCP headers. (or)
           b) Profile 0x104 is chosen only when no other V2 profile is
supported by the compressor entity other than Profile 0x104.

   Pls share your valuble thoughts regarding the same.

Thanks,
Pradeep.















The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments contained in it.


--------------080001050801010102000308
Content-Type: text/plain;
 name="Attached Message Part"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Attached Message Part"

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


--------------080001050801010102000308--


Return-Path: <bsarkar@starentnetworks.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B39CA28C2F7 for <rohc@core3.amsl.com>; Fri, 27 Feb 2009 02:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8wZzCjBHa+R for <rohc@core3.amsl.com>; Fri, 27 Feb 2009 02:10:30 -0800 (PST)
Received: from mx0.starentnetworks.com (mx0.starentnetworks.com [12.38.223.203]) by core3.amsl.com (Postfix) with ESMTP id 07CA228C300 for <rohc@ietf.org>; Fri, 27 Feb 2009 02:10:30 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx0.starentnetworks.com (Postfix) with ESMTP id BF52890032; Fri, 27 Feb 2009 05:10:46 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1]) by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23571-14; Fri, 27 Feb 2009 05:10:46 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com [10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP; Fri, 27 Feb 2009 05:10:46 -0500 (EST)
Received: from exchindia3.starentnetworks.com ([10.6.7.5]) by exchtewks1.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Feb 2009 05:10:46 -0500
Received: from [10.6.7.67] ([10.6.7.67]) by exchindia3.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 27 Feb 2009 15:40:36 +0530
Message-ID: <49A7BC14.4070009@starentnetworks.com>
Date: Fri, 27 Feb 2009 15:40:28 +0530
From: Sarkar Biplab <bsarkar@starentnetworks.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Mihir Mehta <mihirjm@gmail.com>
References: <86c08c690902251941o30b5c809m455e8c1344275370@mail.gmail.com>
In-Reply-To: <86c08c690902251941o30b5c809m455e8c1344275370@mail.gmail.com>
X-Enigmail-Version: 0.95.7
OpenPGP: url=http://pgp.mit.edu:11371/pks/lookup?search=0x6D543EEE&op=index
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0E8C34D0D2761338FCD2B4D3"
X-OriginalArrivalTime: 27 Feb 2009 10:10:36.0512 (UTC) FILETIME=[A2431600:01C998C3]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
Cc: rohc@ietf.org
Subject: Re: [rohc] Calculating TS_Stride value
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2009 10:10:31 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0E8C34D0D2761338FCD2B4D3
Content-Type: multipart/alternative;
 boundary="------------080205040305050709080507"

This is a multi-part message in MIME format.
--------------080205040305050709080507
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Mihir,

You can use  statistical approach to calculate TS_Stride.

Thanks
Biplab


Mihir Mehta wrote:
> Dear All,
>
>
> Could anyone help me to know how to calculate the TS_Stride value by
> looking at the RTP TS field.
>
> In most cases, it is assumed to be 160 assuming that the audio
> sampling rate is 8khz and and 1 voice frame 'may' cover 20ms. There
> could be a possibility that the voice frame may cover less than 20ms.
> In that case what would be the best way to calculate the TS_Stride valu=
e?
>
> Further,assuming that the sampling rate is also unknown, in that case
> how can one caculate the TS_Stride value?
>
> Could someone kindly help me?
>
> Thanks in advance
> Mihir
> -----------------------------------------------------------------------=
-
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc
>  =20


--------------080205040305050709080507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content=3D"text/html;charset=3DISO-8859-1" http-equiv=3D"Content-=
Type">
</head>
<body bgcolor=3D"#ffffff" text=3D"#000066">
Hello Mihir,<br>
<br>
You can use&nbsp; statistical approach to calculate TS_Stride. <br>
<br>
Thanks<br>
Biplab<br>
<br>
<br>
Mihir Mehta wrote:
<blockquote
 cite=3D"mid:86c08c690902251941o30b5c809m455e8c1344275370@mail.gmail.com"=

 type=3D"cite">Dear All,
  <div><br>
  </div>
  <div><br>
  </div>
  <div>Could anyone help me to know how to calculate the TS_Stride
value by looking at the RTP TS field.</div>
  <div><br>
  </div>
  <div>In most cases, it is assumed to be 160 assuming that the audio
sampling rate is 8khz and and 1 voice frame 'may' cover 20ms. There
could be a possibility that the voice frame may cover less than 20ms.
In that case what would be the best way to calculate the TS_Stride
value?</div>
  <div><br>
  </div>
  <div>Further,assuming that the sampling rate is also unknown, in that
case how can one caculate the TS_Stride value?</div>
  <div><br>
  </div>
  <div>Could someone kindly help me?</div>
  <div><br>
  </div>
  <div>Thanks in advance</div>
  <div>Mihir</div>
  <pre wrap=3D"">
<hr size=3D"4" width=3D"90%">
_______________________________________________
Rohc mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Rohc@ietf.org">Rohc@=
ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/rohc">https://www.ietf.org/mailman/listinfo/rohc</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------080205040305050709080507--

--------------enig0E8C34D0D2761338FCD2B4D3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJp7wY3rQBTW1UPu4RAoI5AJ4s3ucVFgpTmv4sQDLGCoOtroTkMgCgtF/m
LT0fSYBT/q/Rb6lFdmrJy9g=
=xH9j
-----END PGP SIGNATURE-----

--------------enig0E8C34D0D2761338FCD2B4D3--
