From rohc-bounces@ietf.org Thu Feb 01 11:31:18 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCeq6-00025t-AH; Thu, 01 Feb 2007 11:31:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCeq5-00025A-F7
	for rohc@ietf.org; Thu, 01 Feb 2007 11:31:09 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCepy-0004EC-M0
	for rohc@ietf.org; Thu, 01 Feb 2007 11:31:09 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	8F69021290; Thu,  1 Feb 2007 17:30:57 +0100 (CET)
X-AuditID: c1b4fb3e-b06d4bb0000007e1-34-45c215c1ce86 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	74E8721173; Thu,  1 Feb 2007 17:30:57 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Feb 2007 17:30:57 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] RE: AD comments on draft-ietf-rohc-tcp-15
Date: Thu, 1 Feb 2007 17:30:55 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC0504556C64@esealmw109.eemea.ericsson.se>
In-Reply-To: <026F8EEDAD2C4342A993203088C1FC0504556156@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] RE: AD comments on draft-ietf-rohc-tcp-15
Thread-Index: AcdFPmdbidqn19EWQ4GnnheDxAd+wgAAIexgADbkT2A=
From: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
To: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>,
	"Lars-Erik Jonsson" <lars-erik@lejonsson.com>
X-OriginalArrivalTime: 01 Feb 2007 16:30:57.0011 (UTC)
	FILETIME=[59A22430:01C7461E]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: Carl Knutsson <calle@effnet.com>, "West, Mark" <mark.a.west@roke.co.uk>,
	Carsten Bormann <cabo@tzi.org>, rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

>> Anyway, I will get back with a text proposal shortly.

Alternative 1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Proposal
- Remove last paragraph of sections 6.4.1 and 6.4.2
- Add in section 3.2 before the last paragraph:
=20
   Header compression algorithms generally make the implicit assumption
   that any checksum present in the protocol header it processes is
   consistent with the fields protected by the checksum. In particular,
   for the IPv4 header and for the MINE header, the purpose of the
   checksum is to protect individual hops from processing a corrupted
   header. As a consequence, it is assumed that a compressor will not
   process a corrupted header. Otherwise, because these checksums are
   compressed away and recalculated in the decompressor
   [REF inferred_ipv4_checksum()][REF inferred_mine_checksum()],
   transparency cannot be guaranteed for a header with an inconsistent
   checksum.=20

Alternative 2:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Proposal (section 6.4.1):
- Replace last paragraph of section 6.4.1 with:

   The purpose of the IPv4 header checksum is to protect individual
   hops from processing a corrupted header. This encoding method
   implicitely assumes that the compressor will not process a
   corrupted header. Otherwise, this encoding method cannot guarantee
   that the checksum as recomputed by the decompressor will be bitwise
   identical to its original value before compression.

- Replace two last paragraphs of section 6.4.2 with:

   The motivations abnd the assumptions for inferring this checksum
   are similar to the ones explained above in Section 6.4.1.

-----Original Message-----
From: Ghyslain Pelletier (LU/EAB)
[mailto:ghyslain.pelletier@ericsson.com]=20
Sent: den 31 januari 2007 15:05
To: Magnus Westerlund (KI/EAB); pelle@cdt.luth.se
Cc: Carl Knutsson; West, Mark; Carsten Bormann; rohc@ietf.org; Lars-Erik
Jonsson
Subject: RE: [rohc] RE: AD comments on draft-ietf-rohc-tcp-15

Hej Magnus,

This could be an acceptable alternative from my perspective, to
formulate it as to what it is an assumption of the compression profile,
somewhere in section 3. However, I have always been under the impression
that that was implicit from the specifications of IPv4 no matter what.

Anyway, I will get back with a text proposal shortly.

///Ghyslain

Magnus Westerlund wrote:
> pelle@cdt.luth.se skrev:
>> Magnus, Kristofer,
>>=20
>> I totally disagree with changing the current wording.
>>=20
>> I totally agree with Carsten and Mark opinion previously expressed
>> on this thread, which arguments were very much in-line with my
>> initial answer.=20
>>=20
>> I think that we should not specify anything in our profiles that
>> would lead to a compressor discarding a packet. Once again, it is
>> not the responsability of header compression to police other
>> protocol/stack behavior.=20
>>=20
>> Wrt to the "transparency issue", header compression has always used
>> the assumption that erroneous IP checksums would never reach the
>> compressor, and Carsten in addition pointed out that this has been
>> discussed and agreed long time ago. Furthermore, as Carsten pointed
>> out, IPv6 folks did not even include a cheksum in the IPv6 header
>> for a reason.=20
>>=20
>> Personally, I would remove the sentence entirely, and I think that
>> would follow all other other RoHC specs very nicely.
>>=20
>> Regards,
>>=20
>> ///Ghyslain
>>=20
>=20
> If it always has been an assumption that erroneous headers will not
> reach the compressor, can you please point out where in the current
> set of document that assumption is documented?
>=20
> In case it is not documented can we please document it. I am fine with
> removing the normative sentence as long as the assumption is correctly
> documented and the possible effects of not fulfilling this assumption.
>=20
>  From my perspective I think it is important that you document the
> cases when transparency is only fulfilled as certain assumptions are
> meet.=20
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------


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

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



From rohc-bounces@ietf.org Thu Feb 01 15:39:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCiiD-0004UE-Ao; Thu, 01 Feb 2007 15:39:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCiiC-0004Sr-BZ
	for rohc@ietf.org; Thu, 01 Feb 2007 15:39:16 -0500
Received: from deliverator8.gatech.edu ([130.207.165.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCii8-0003bX-0w
	for rohc@ietf.org; Thu, 01 Feb 2007 15:39:16 -0500
Received: from deliverator8.gatech.edu (localhost [127.0.0.1])
	by localhost (Postfix) with SMTP id 7400DA21
	for <rohc@ietf.org>; Thu,  1 Feb 2007 15:39:09 -0500 (EST)
	(envelope-from christian@gatech.edu)
Received: from mailprx1.gatech.edu (mailprx1.prism.gatech.edu [130.207.171.15])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client CN "smtp.mail.gatech.edu", Issuer "RSA Data Security,
	Inc." (verified OK))
	by deliverator8.gatech.edu (Postfix) with ESMTP id 74C74A25
	for <rohc@ietf.org>; Thu,  1 Feb 2007 15:23:50 -0500 (EST)
	(envelope-from christian@gatech.edu)
Received: from Christian2 (lawn-128-61-112-174.lawn.gatech.edu
	[128.61.112.174]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	(sasl: method=LOGIN, username=cmenkens3@mailprx1.gatech.edu, sender=n/a)
	by mailprx1.gatech.edu (Postfix) with ESMTP id 14E5A26CF
	for <rohc@ietf.org>; Thu,  1 Feb 2007 15:23:50 -0500 (EST)
	(envelope-from christian@gatech.edu)
From: "Christian M Menkens" <christian@gatech.edu>
To: <rohc@ietf.org>
Date: Thu, 1 Feb 2007 15:23:48 -0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcdGO3HwCIgPc6EASIy7UDNj8ByGGAAA1r4w
Message-Id: <20070201202350.14E5A26CF@mailprx1.gatech.edu>
X-GT-Spam-Rating: (7%)
X-GT-Spam-Details: The following antispam rules were triggered by this message:
	Rule        Score Description
	HTML_70_90  0.100 Message is 70-90% HTML
X-GT-AVAS-Version: 5.3.0.289146, Antispam-Engine: 2.5.0.283055,
	Antispam-Data: 2007.2.1.122433
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Subject: [rohc] Published SIP (with and without SigComp) traffic/network
	traces?
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0723538537=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0723538537==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0047_01C74614.F91D0F70"

This is a multi-part message in MIME format.

------=_NextPart_000_0047_01C74614.F91D0F70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

Does anybody know if there are any traces of real world / larger deployments
of SIP/IMS systems available? We would need some traces do analyse them. It
would be amazing if we could get our hand on traffic with and without the
use of SigComp or other compression mechanisms.

 

Best,

 

Christian

 

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

Christian M. Menkens
Georgia Institute of Technology
 <mailto:404-547-1953christian@gatech.edu> christian@gatech.edu

 


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

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.E-MailFormatvorlage17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.E-MailFormatvorlage19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DDE-AT link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Does anybody know if there are any traces of =
real
world / larger deployments of SIP/IMS systems available? We would need =
some
traces do analyse them. It would be amazing if we could get our hand on =
traffic
with and without the use of SigComp or other compression =
mechanisms.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Best,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Christian<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana'>--------------------------=
--------------------------</span></font><span
lang=3DEN-GB><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana'>Christian
M. Menkens<br>
<strong><b><font face=3DVerdana><span =
style=3D'font-family:Verdana'>Georgia Institute
of Technology</span></font></b></strong><br>
</span></font><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'><a =
href=3D"mailto:404-547-1953christian@gatech.edu"><span
lang=3DEN-GB>christian@gatech.edu</span></a></span></font><span =
lang=3DEN-GB><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0047_01C74614.F91D0F70--



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

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

--===============0723538537==--





From rohc-bounces@ietf.org Fri Feb 02 05:37:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCvn7-00041X-BF; Fri, 02 Feb 2007 05:37:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCvn6-0003rh-Hn
	for rohc@ietf.org; Fri, 02 Feb 2007 05:37:12 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCvmv-0000M0-0h
	for rohc@ietf.org; Fri, 02 Feb 2007 05:37:10 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7F10E21240; Fri,  2 Feb 2007 11:37:00 +0100 (CET)
X-AuditID: c1b4fb3e-aeed1bb0000007e1-8e-45c3144c678b 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6ECFB211D1; Fri,  2 Feb 2007 11:37:00 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Feb 2007 11:37:00 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Feb 2007 11:36:59 +0100
Message-ID: <45C3144B.6090106@ericsson.com>
Date: Fri, 02 Feb 2007 11:36:59 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
Subject: Re: [rohc] RE: AD comments on draft-ietf-rohc-tcp-15
References: <026F8EEDAD2C4342A993203088C1FC0504556C64@esealmw109.eemea.ericsson.se>
In-Reply-To: <026F8EEDAD2C4342A993203088C1FC0504556C64@esealmw109.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Feb 2007 10:36:59.0849 (UTC)
	FILETIME=[11B62390:01C746B6]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Carl Knutsson <calle@effnet.com>,
	Lars-Erik Jonsson <lars-erik@lejonsson.com>, "West,
	Mark" <mark.a.west@roke.co.uk>, rohc@ietf.org,
	Carsten Bormann <cabo@tzi.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Ghyslain Pelletier (LU/EAB) skrev:
>>> Anyway, I will get back with a text proposal shortly.
> 
> Alternative 1:
> ==============
> Proposal
> - Remove last paragraph of sections 6.4.1 and 6.4.2
> - Add in section 3.2 before the last paragraph:
>  
>    Header compression algorithms generally make the implicit assumption
>    that any checksum present in the protocol header it processes is
>    consistent with the fields protected by the checksum. In particular,
>    for the IPv4 header and for the MINE header, the purpose of the
>    checksum is to protect individual hops from processing a corrupted
>    header. As a consequence, it is assumed that a compressor will not
>    process a corrupted header. Otherwise, because these checksums are
>    compressed away and recalculated in the decompressor
>    [REF inferred_ipv4_checksum()][REF inferred_mine_checksum()],
>    transparency cannot be guaranteed for a header with an inconsistent
>    checksum. 
> 
> Alternative 2:
> ==============
> Proposal (section 6.4.1):
> - Replace last paragraph of section 6.4.1 with:
> 
>    The purpose of the IPv4 header checksum is to protect individual
>    hops from processing a corrupted header. This encoding method
>    implicitely assumes that the compressor will not process a
>    corrupted header. Otherwise, this encoding method cannot guarantee
>    that the checksum as recomputed by the decompressor will be bitwise
>    identical to its original value before compression.
> 
> - Replace two last paragraphs of section 6.4.2 with:
> 
>    The motivations abnd the assumptions for inferring this checksum
>    are similar to the ones explained above in Section 6.4.1.
> 

If the two inffered header checksums are the only two cases when this 
can occur I personally would prefer alternative 2.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From rohc-bounces@ietf.org Fri Feb 02 09:56:26 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCzpy-00011e-Rj; Fri, 02 Feb 2007 09:56:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCzpx-000106-Mo
	for rohc@ietf.org; Fri, 02 Feb 2007 09:56:25 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCzpo-0001ss-38
	for rohc@ietf.org; Fri, 02 Feb 2007 09:56:25 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	76B4620133; Fri,  2 Feb 2007 15:56:13 +0100 (CET)
X-AuditID: c1b4fb3e-b16d6bb0000007e1-b3-45c3510d97dd 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	561BB213AE; Fri,  2 Feb 2007 15:56:13 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Feb 2007 15:56:13 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] RE: AD comments on draft-ietf-rohc-tcp-15
Date: Fri, 2 Feb 2007 15:56:10 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC05045956DD@esealmw109.eemea.ericsson.se>
In-Reply-To: <45C3144B.6090106@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] RE: AD comments on draft-ietf-rohc-tcp-15
Thread-Index: AcdGthLXAzzrF/vrSzmqvJh55FNnVwAI43wg
From: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
To: "Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 02 Feb 2007 14:56:13.0203 (UTC)
	FILETIME=[483B9E30:01C746DA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: Carl Knutsson <calle@effnet.com>,
	Lars-Erik Jonsson <lars-erik@lejonsson.com>, "West,
	Mark" <mark.a.west@roke.co.uk>, rohc@ietf.org,
	Carsten Bormann <cabo@tzi.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Magnus,

I have updated the RoHC-TCP draft in the CVS after your comments:
http://www.dmn.tzi.org/cgi-bin/cvsweb.cgi/fn/
I will submit an updated version.

///Ghyslain

Magnus Westerlund wrote:
> Ghyslain Pelletier (LU/EAB) skrev:
>>>> Anyway, I will get back with a text proposal shortly.
>>=20
>> Alternative 1:
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Proposal
>> - Remove last paragraph of sections 6.4.1 and 6.4.2
>> - Add in section 3.2 before the last paragraph:
>>=20
>>    Header compression algorithms generally make the implicit
>>    assumption that any checksum present in the protocol header it
>>    processes is consistent with the fields protected by the
>>    checksum. In particular, for the IPv4 header and for the MINE
>>    header, the purpose of the checksum is to protect individual hops
>>    from processing a corrupted header. As a consequence, it is
>>    assumed that a compressor will not process a corrupted header.
>>    Otherwise, because these checksums are compressed away and
>>    recalculated in the decompressor [REF
>>    inferred_ipv4_checksum()][REF inferred_mine_checksum()],
>> transparency cannot be guaranteed for a header with an inconsistent=20
>> checksum. =20
>>=20
>> Alternative 2:
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Proposal (section 6.4.1):
>> - Replace last paragraph of section 6.4.1 with:
>>=20
>>    The purpose of the IPv4 header checksum is to protect individual
>>    hops from processing a corrupted header. This encoding method
>>    implicitely assumes that the compressor will not process a
>>    corrupted header. Otherwise, this encoding method cannot guarantee
>>    that the checksum as recomputed by the decompressor will be
>>    bitwise identical to its original value before compression.
>>=20
>> - Replace two last paragraphs of section 6.4.2 with:
>>=20
>>    The motivations abnd the assumptions for inferring this checksum
>>    are similar to the ones explained above in Section 6.4.1.
>>=20
>=20
> If the two inffered header checksums are the only two cases when this
> can occur I personally would prefer alternative 2.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------


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



From rohc-bounces@ietf.org Fri Feb 02 15:50:47 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HD5Mt-0003QU-9J; Fri, 02 Feb 2007 15:50:47 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HD5Mf-0002ny-D8; Fri, 02 Feb 2007 15:50:33 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HD5Mf-0002wR-1v; Fri, 02 Feb 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id AF52A2AD1E;
	Fri,  2 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HD5MA-0002Nz-EN; Fri, 02 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HD5MA-0002Nz-EN@stiedprstage1.ietf.org>
Date: Fri, 02 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-tcp-16.txt 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

--NextPart

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

	Title		: RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)
	Author(s)	: G. Pelletier, et al.
	Filename	: draft-ietf-rohc-tcp-16.txt
	Pages		: 93
	Date		: 2007-2-2
	
This document specifies a ROHC (Robust Header Compression) profile
   for compression of TCP/IP packets.  The profile, called ROHC-TCP,
   provides efficient and robust compression of TCP headers, including
   frequently used TCP options such as SACK (Selective Acknowledgments)
   and Timestamps.

   ROHC-TCP works well when used over links with significant error rates
   and long round-trip times.  For many bandwidth-limited links where
   header compression is essential, such characteristics are common.

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

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

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

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

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

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-tcp-16.txt

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

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


--OtherAccess--

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

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

--NextPart--




From rohc-bounces@ietf.org Mon Feb 05 10:40:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE5x5-0004SZ-Tr; Mon, 05 Feb 2007 10:40:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE5x2-0004Me-KF; Mon, 05 Feb 2007 10:40:16 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HE5x2-0003OW-E2; Mon, 05 Feb 2007 10:40:16 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 4851E26ECF;
	Mon,  5 Feb 2007 15:40:16 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HE5x2-00062o-63; Mon, 05 Feb 2007 10:40:16 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1HE5x2-00062o-63@stiedprstage1.ietf.org>
Date: Mon, 05 Feb 2007 10:40:16 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: rohc@ietf.org
Subject: [rohc] Last Call: draft-ietf-rohc-tcp (RObust Header Compression 
 (ROHC): A Profile for TCP/IP (ROHC-TCP)) to Proposed Standard 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

The IESG has received a request from the Robust Header Compression WG 
(rohc) to consider the following document:

- 'RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP) '
   <draft-ietf-rohc-tcp-16.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-02-19. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-rohc-tcp-16.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=8269&rfc_flag=0


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



From rohc-bounces@ietf.org Mon Feb 12 12:10:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGegu-00043h-Hk; Mon, 12 Feb 2007 12:10:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGegs-0003xo-Nv
	for rohc@ietf.org; Mon, 12 Feb 2007 12:10:10 -0500
Received: from rsys002x.roke.co.uk ([193.118.201.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGegq-0004mS-Q3
	for rohc@ietf.org; Mon, 12 Feb 2007 12:10:10 -0500
Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85])
	by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id l1CH73Jr016410;
	Mon, 12 Feb 2007 17:07:03 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Feb 2007 17:07:03 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C5019A8ED4@rsys005a.comm.ad.roke.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Second WG last-call for SIP/SigComp - dedicated review
Thread-Index: Acc7ubK+qZq7pwsvTbS6t9+rsbbkJwS7RhmQ
References: <A632AD91CF90F24A87C42F6B96ADE5C50171886A@rsys005a.comm.ad.roke.co.uk>
	<45B0A4AC.5040803@ericsson.com>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
X-MailScanner-roke-co-uk: Found to be clean
X-MailScanner-roke-co-uk-SpamCheck: 
X-MailScanner-From: abigail.surtees@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: da41e01217ab11ad82db577473e913ae
Cc: lars-erik@lejonsson.com, rohc@ietf.org
Subject: [rohc] RE: Second WG last-call for SIP/SigComp - dedicated review
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Gonzalo,

Apologies for the delayed response.  Comments in-line:=20
>=20
> yes, abstracts should not have normative language. However,=20
> you are right pointing out that the second 'must' should be=20
> normative. I have moved that text from the Introduction to a=20
> new section right after the Terminology section and I have=20
> made that 'must' a normative MUST.
>=20
> Of course, specifications should be followed once they are published.=20
> Therefore, legacy implementations will, obviously, not be=20
> compliant with this document. That is why the document=20
> contains a Backwards Compatibility section explaining the situation.
>=20
> Regarding implementations confirming to other specs, the=20
> section on Provate Agreements covers that.
>=20
OK

> we do not use normative language because support for RFC 3485=20
> is already normatively mandated in RFC 3485, and support for=20
> RFC 3586 is already normatively mandated in RFC 3486. We=20
> point to those RFCs, but do not repeat the normative=20
> statements here (this is common practice when writing RFCs).
>=20

OK

> > Section 3.1:
> > I know the 'reason' part here but I think it should be written more=20
> > clearly (I think if you were new to it you'd have to read=20
> it several=20
> > times).  Add another sentence to explain the example.  Also, the=20
> > SigComp user guide refers to 'circular buffer' not 'ring=20
> buffer' so it=20
> > may be worth using 'circular buffer' here (ring buffer isn't used=20
> > anywhere else).
>=20
> I have replaced 'ring buffer' with 'circular buffer'.
>=20
OK.

> I will be happy to add the clarifying sentence you request if=20
> you provide me with it.
>=20
"For example, the
   condition set by [RFC3320] for SigComp over UDP means: C + 2*B + R +
   2*S + 128 < DMS (each term is described below).  On the other hand,
   8KB additional memory should not cause any problem for an endpoint
   that already implements SIP, SigComp, and applications that use SIP
   as DMS is memory only temporarily needed during decompression of a
   SigComp message (the memory can be reclaimed when the message has
   been decompressed)."

Rephrased slightly to:

"For example, the
condition set by [RFC3320] for SigComp over UDP means: C + 2*B + R +
2*S + 128 < DMS (each term is described below), so if DMS is too small
then at least one of C, B, R and S will be severely restricted.  On the
other hand, DMS is memory which is only during decompression of a
SigComp message (after which it can be reclaimed); therefore, a
requirement of 8Kb should not cause any problem for an endpoint that
already implements SIP, SigComp, and applications that use SIP."

>=20
> > Section 3.2:
>=20
> I have performed the following change:
>=20
> OLD:
> Reason: a non-zero SMS allows an endpoint to upload a state in the
> first SIP message sent to a remote endpoint without the uncertainty of
> whether or not it can be created in the remote endpoint.
>          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>=20
> NEW:
> Reason: a non-zero SMS allows an endpoint to upload a state in the
> first SIP message sent to a remote endpoint without the uncertainty of
> whether the remote endpoint will have enough memory to store such a
>          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>=20
> state.
> ^^^^^^
>=20
OK

> > Section 3.5:
> > Add a statement that because the static dictionary is=20
> mandatory it does
> > not need to be advertised (last point in this email discussion
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg04463.html).
>=20
> I have added:
>=20
> "Note that, since support for the static SIP/SDP dictionary is
> mandatory, it does not need to be advertised."
>=20
OK

> > Section 8.2
> > Re: Use of IP address and port/connection for the remote application
> > identifier for legacy systems.  If a client fails (losing=20
> all SIP state
> > including SigComp compartment) and re-REGISTERS with the same IP
> > address, how can the SIP stack tell that the old=20
> compartment is invalid.
> > I realise that the answer is probably that this circumstance is
> > relatively unlikely and that NACK would recover the situation, but I
> > think this should be made clearer.
>=20
> Implementors are made aware of this type of problem related to legacy=20
> systems in the section about Backwards Compatibility.

Hmm, ok.  This one isn't explicitly listed, but the lack of NACK is and
it's when NACK isn't present that the problem would be more major.
>=20
> > Section 8.3=20
> > I think this section should be combined with section 8.4.  The
> > definition of when compartments should be opened and closed=20
> needs to be
> > stronger.  In this section, section 8.4 and section 12,=20
> there are strong
> > echoes of the fact that it used to be possible to have different
> > compartment lifetimes.
> > I think there should be standards language (probably=20
> SHOULDs) stating
> > when compartments should be opened and closed.  i.e.=20
> compartments SHOULD
> > last the lifetime of the registration, but leaving the=20
> possibility for
> > early closure and NACK recovery in extreme cases (e.g. overload
> > conditions).
>=20
> I have combined Sections 8.3 and 8.4, as you suggest.

(now 9.3) OK

>=20
> The document already contains normative language regarding when one=20
> should open and close compartments. Regarding the MAY strength on=20
> compartment closure, we need to leave the door open for=20
> implementations=20
> to keep states after the registration expires.
>=20
> With respect to your overload example, the document already says that=20
> implementations SHOULD NOT close the compartments before the=20
> registration expires. Note that we do not use MUST NOT.

OK
>=20
> > Section 8.3 (Paragraph about keeping state beyond the end of a
> > compartment):
> > This paragraph still refers to compartments lasting the length of a
> > dialog or transaction!
> > How useful is the technique described in this paragraph, now that a
> > compartment lifetime is a registration?=20
>=20
> I have removed the text talking about dialogs and=20
> transactions. Per my=20
> comment above, we do not need to force implementations to close their=20
> compartments when the registration expires. If they want to=20
> do it, they=20
> can do it, but if they don't, they do not harm anyone by not=20
> closing the=20
> compartment.
>=20
OK
>=20
> > Section 8.4
> > See comment on section 8.3 about strengthening compartment=20
> definition.
> > I also think the security implications of opening a compartment on
> > receipt of a REGISTER should be mentioned.  Compartments=20
> and state can
> > only be created if the application says so, but, particularly if the
> > decompressing node is a proxy, the non-2xx response may=20
> take a while to
> > be generated.
>=20
> Non-2xx responses for REGISTER requests are generated immediately.

But, if the response is not generated at the proxy, then surely it's
going to take some time for the response to come back from the server?

> > Section 8.4
> > "However, applications MAY also choose to keep these
> >    compartments open for a longer period of time, as discussed
> >    previously."
> > Does the 'as discussed previously refer to the 'paragraph=20
> about keeping
> > state beyond the end of a compartment'?  If so, then i) I'm not sure
> > it's that useful and ii) the wording implies something=20
> different.  If
> > not, then what does it refer to?
>=20
> it refers to the text you point to and, per my comments=20
> above, I believe=20
> it is indeed a useful feature.
>=20
OK
>=20
> > Section 8.5
> > I was surprised to see this section (but maybe I missed=20
> it's discussion
> > on the list).  I can understand softening the 'SHOULD' in=20
> RFC3486, but I
> > don't think it should be a 'SHOULD NOT' - it depends on the=20
> stateless
> > algorithm in use and the size of the message being=20
> compressed.  With a
> > stateless algorithm that has short bytecode and a large=20
> message (e.g.
> > INVITE) it is possible to still achieve non-trivial=20
> compression gain.
>=20
> Theoretically, you are right. Practically, no one intends to do that.=20
> Note that revision 03 of this draft covered every single scenario you=20
> could eventually implement. The conclusion was that the spec needs to=20
> focus on realistic scenarios only; this way, it becomes a=20
> simpler spec.=20

In general, regarding the simpler spec, I agree with you.  However, in
this particular instance, I don't see the need to restrict the
implementer in this way.  Granted, it is a SHOULD NOT rather than a MUST
NOT, but if the implementer can implement a stateless algorithm that
achieves compression (at least for some messages) why should we
recommend that they shouldn't do that?  Also, how do you know that in
practice no-one intends to do that?

Having looked at where the quoted text appears in RFC 3486, it is not
related to stateless compression or compression without a compartment.
So I'm still not sure why this paragraph is in this document.

If there is really a need for a statement (which I don't think there
is), then I think it should be no more than:

"RFC 3486 [RFC 3486] states that:

      "If the next-hop URI contains the parameter comp=3Dsigcomp, the
      client SHOULD compress the request using SigComp"

Although this states that messages SHOULD be compressed, it should be
noted that in some cases compressing a message may actually result in
message expansion.  Therefore where comp=3Dsigcomp is specified, it is =
up
to the implementation to work out whether or not to compress a message.
This decision may use available information such as compartment
availability, and uncompressed and compressed message lengths.

Note that it is always possible to use the 'well-known shim header'
mentioned in section 5."


> That is why revision 04 is much simpler than 03.
>=20
> > Section 12:
> > I think section 12 should either be part of section 8 or=20
> become section
> > 9 (preferably the former) because it is an example of compartment
> > creation and deletion.
>=20
> This is of course a matter of taste, but, as it is the case in many=20
> other RFCs, we have chosen to place the examples at the end=20
> of the document.

OK, fair enough.
>=20
> > As mentioned above several sentences have echoes of the=20
> possibility of
> > having variable compartment lifetime:
> >=20
> > "This compartment will be valid, at least, for the
> >    duration of the registration."
> > Remove the 'at least'
> >=20
> > "The compartment opened by the outbound proxy will be valid,
> >    at least, for the duration of the registration."
> > Remove the 'at least'
>=20
> The 'at least' is there because implementations may choose to=20
> extend the=20
> lifetime of the compartment, per my comments above.
>=20
> > "Since this URI's SIP/SigComp identifier 'Outbound-id'=20
> matches that of
> >    the compartment created before, this compartment is used=20
> to compress
> >    the INVITE request."
> > What other compartment could be used?
>=20
> The node may have SigComp relationships with other nodes at the same=20
> time (e.g., an outbound proxy from other operator for reliability).
>=20
> > Nits:
> >=20
>=20
> > Section 4: final note:
> >=20
> > Refers to 'a SigComp structured TCP connection' - I think the word
> > structured is unnecessary and mildly confusing in this note.
> > Alternatively make it 'SigComp-structured'
>=20
> Fixed.

Two occurences, only one is fixed.
>=20
> >=20
> > Section 7:=20
> > Phraseology 'failure occurred to' and 'loss occurred to'=20
> feel slightly
> > clumsy.
> > Rephrase to:
> > 'failure occurred on' and 'If the response was lost, ...'
>=20
> Fixed.
There's a second 'to' relating back to the failure occurring which
should also be an 'on'.

"or on the response to that message"

>=20
> >=20
> > "Outgoing responses: the remote application identifier is=20
> the same as
> > the previously-received request that initiated the transaction the
> > response belongs to."
> > ->
> > "Outgoing responses: the remote application identifier is=20
> the same as
> > that of the previously-received request that initiated the=20
> transaction
> > to which the response belongs."
>=20
> Fixed.

Cut and paste error - during the fix the '>' have crept into the draft!

>=20
> > comparment -> compartment (1 instance in section 8.3 and 1=20
> in section
> > 11)
>=20
> Fixed.

Still one instance of comparment in section 12.
=20
> >=20
> > Section 8.4: last paragraph
> > "If following the previous rules" -> "If, following the=20
> rules above, "
>=20
> Fixed.

Missing 'the'

Section 13: first paragrpaph under figure 1:

"'outbound's proxy" -> "outbound proxy's"

Section 13: page 15, paragraph 4:

"   The registrar also constructs the route future outgoing requests
   (from the user agent) and places it in a Service-Route header field
   in a 200 (OK) response (3). "

->

"   The registrar also constructs the route future outgoing requests
   (from the user agent) will follow and places it in a Service-Route
header field
                         ^^^^^^^^^^^^
   in a 200 (OK) response (3). "

>=20
> I uploaded a working version of revision 05, which includes all the=20
> changes above, to:
> http://users.piuha.net/gonzalo/temp/draft-ietf-rohc-sigcomp-sip-05.txt
>=20
> Let me know if you are OK with this version so that I can submit it.
>=20
> Cheers,
>=20
> Gonzalo
>=20

Best regards,

Abbie

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



From rohc-bounces@ietf.org Thu Feb 15 06:16:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHeb6-0001kX-5z; Thu, 15 Feb 2007 06:16:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHeb4-0001kP-NS
	for rohc@ietf.org; Thu, 15 Feb 2007 06:16:18 -0500
Received: from gws04.hcl.in ([203.105.186.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHeb2-0005Fc-HD
	for rohc@ietf.org; Thu, 15 Feb 2007 06:16:18 -0500
Received: from gws04.hcl.in (gws04 [10.249.64.135])
	by localhost.hcl.in (Postfix) with ESMTP id A888C360049
	for <rohc@ietf.org>; Thu, 15 Feb 2007 16:46:07 +0530 (IST)
Received: from chn-egw02-out.corp.hcl.in (unknown [10.249.64.38])by 
	gws04.hcl.in (Postfix) with ESMTP id 75A49360025for <rohc@ietf.org>;
	Thu, 15 Feb 2007 16:46:07 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.15]) by 
	chn-egw02-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.1830);
	Thu, 15 Feb 2007 16:46:07 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 Feb 2007 16:44:46 +0530
Message-ID: <66E8AEE9980BB44CA5FCAD39EBA56AC6944811@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Doubt regarding DMS and UDVM memory size
Thread-Index: AcdQ8oA/dHMkaxmhSGqsqkKOBqVEYA==
From: "Gangadharan G, TLS-Chennai" <Gangadharang@hcl.in>
To: <rohc@ietf.org>
X-OriginalArrivalTime: 15 Feb 2007 11:16:07.0056 (UTC) 
	FILETIME=[B0204100:01C750F2]
X-imss-version: 2.046
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-17.4436 TC:1F TRN:63 TV:3.6.1039(14998.003)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:2 C:2 M:2 S:2 R:2 (0.0000 0.0000)
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
Subject: [rohc] Doubt regarding DMS and UDVM memory size
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1916706519=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1916706519==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C750F2.80A93DE4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C750F2.80A93DE4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi All,

=20

As per RFC 3320, UDVM memory size is calculated from the DMS and Message
size and also based on transport type.

i.e., For UDP, udvm_memory_size =3D DMS - sigcomp_message_size

      For TCP, udvm_memory_size =3D DMS / 2

=20

As the DMS value is constant (for particular session/application),
udvm_memory_size varies on each message.

=20

How the bytecode has to handle this variance with the BYTE_COPY_RIGHT
value?

=20

For example, In SIP/SIGCOMP the DMS value is 8192. The udvm_memory_size
will be around 7500 (less than 8192).

                    The BYTE_COPY_RIGHT has been hard-coded as 8192 in
the User guide and in other sample bytecode.

                    Is it correct way?

=20

Do others handle the variance of udvm_memory_size in the BYTE_COPY_RIGHT
or hard-code the BYTE_COPY_RIGHT value?

=20

As mentioned in the RFC 3320, the first two byte of the UDVM memory is
its size.=20

                     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     |       UDVM_memory_size          | 0 - 1

                     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

=20

Can we use this value for the BYTE_COPY_RIGHT?

=20

Also, Is it mandatory for the SIGCOMP library to calculate the
udvm_memory_size as per the above formula?

=20

Also please let me know if I am ignorant of any detail.

=20

Note: Please ignore if any Disclaimer is present.

=20

Thanks,

Gangadharan.



DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its=
 affiliates. Any views or opinions presented in=20
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of=20
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have=20
received this email in error please delete it and notify the sender=
 immediately. Before opening any mail and=20
attachments please check them for viruses and defect.

---------------------------------------------------------------------------=
--------------------------------------------
------_=_NextPart_001_01C750F2.80A93DE4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Hi All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>As per RFC 3320, UDVM memory size is calculated from the=
 DMS
and Message size and also based on transport=
 type.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>i.e., For UDP, udvm_memory_size =3D DMS &#8211;=
 sigcomp_message_size<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For TCP, udvm_memory_size=
 =3D
DMS / 2<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>As the DMS value is constant (for particular
session/application), udvm_memory_size varies on each=
 message.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>How the bytecode has to handle this variance with the
BYTE_COPY_RIGHT value?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>For example, In SIP/SIGCOMP the DMS value is 8192. The=
 udvm_memory_size
will be around 7500 (less than 8192).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The BYTE_COPY_RIGHT has been hard-coded as 8192 in the User guide and in=
 other sample
bytecode.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Is it correct way?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Do others handle the variance of udvm_memory_size in the
BYTE_COPY_RIGHT or hard-code the BYTE_COPY_RIGHT=
 value?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>As mentioned in the RFC 3320, the first two byte of the=
 UDVM
memory is its size. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
UDVM_memory_size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;| 0=
 - 1<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Can we use this value for the=
 BYTE_COPY_RIGHT?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Also, Is it mandatory for the SIGCOMP library to=
 calculate
the udvm_memory_size as per the above formula?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Also please let me know if I am ignorant of any=
 detail.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Note: Please ignore if any Disclaimer is=
 present.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10.0pt;
font-family:Arial'>Gangadharan.<o:p></o:p></span></font></p>

</div>

</body>

</html>

<table><tr><td bgcolor=3D#ffffff><font color=3D#000000>DISCLAIMER:<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
<br>
The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only.<br>
It shall not attach any liability on the originator or HCL or its=
 affiliates. Any views or opinions presented in <br>
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates.<br>
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of <br>
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have <br>
received this email in error please delete it and notify the sender=
 immediately. Before opening any mail and <br>
attachments please check them for viruses and defect.<br>
<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
</font></td></tr></table>
------_=_NextPart_001_01C750F2.80A93DE4--


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

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

--===============1916706519==--




From rohc-bounces@ietf.org Thu Feb 15 07:40:18 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHfuI-0002JY-Hb; Thu, 15 Feb 2007 07:40:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHfuH-0002JS-W6
	for rohc@ietf.org; Thu, 15 Feb 2007 07:40:13 -0500
Received: from smtp.iptel.org ([213.192.59.67] helo=mail.iptel.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHfuG-0007qV-Hn
	for rohc@ietf.org; Thu, 15 Feb 2007 07:40:13 -0500
Received: from shell.iptel.org (shell.iptel.org [213.192.59.74])
	by mail.iptel.org (Postfix) with SMTP id 55B7D20A2E3;
	Thu, 15 Feb 2007 13:39:55 +0100 (CET)
Received: by shell.iptel.org (sSMTP sendmail emulation);
	Thu, 15 Feb 2007 13:39:34 +0100
Date: Thu, 15 Feb 2007 13:39:34 +0100
From: cco <cristian.constantin@iptel.org>
To: "Gangadharan G, TLS-Chennai" <Gangadharang@hcl.in>
Subject: Re: [rohc] Doubt regarding DMS and UDVM memory size
Message-ID: <20070215123934.GA22004@shell>
References: <66E8AEE9980BB44CA5FCAD39EBA56AC6944811@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <66E8AEE9980BB44CA5FCAD39EBA56AC6944811@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

On Thu, Feb 15, 2007 at 04:44:46PM +0530, Gangadharan G, TLS-Chennai wrote:
> 
> Hi All,
> 
>  
> 
> As per RFC 3320, UDVM memory size is calculated from the DMS and Message
> size and also based on transport type.
> 
> i.e., For UDP, udvm_memory_size = DMS - sigcomp_message_size
> 
>       For TCP, udvm_memory_size = DMS / 2
> 
>  
> 
> As the DMS value is constant (for particular session/application),
> udvm_memory_size varies on each message.
> 
>  
> 
> How the bytecode has to handle this variance with the BYTE_COPY_RIGHT
> value?

cristian: in such a way that all the addresses btw. BYTE_COPY_LEFT and 
BYTE_COPY_RIGHT are valid addresses in the virtual (machine) memory.

> 
>  
> 
> For example, In SIP/SIGCOMP the DMS value is 8192. The udvm_memory_size
> will be around 7500 (less than 8192).
> 
>                     The BYTE_COPY_RIGHT has been hard-coded as 8192 in
> the User guide and in other sample bytecode.
> 
>                     Is it correct way?

cristian: for the examples given there it works. for any other specific
purposes, it may not be correct.

> 
>  
> 
> Do others handle the variance of udvm_memory_size in the BYTE_COPY_RIGHT
> or hard-code the BYTE_COPY_RIGHT value?
> 
>  
> 
> As mentioned in the RFC 3320, the first two byte of the UDVM memory is
> its size. 
> 
>                      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>                      |       UDVM_memory_size          | 0 - 1
> 
>                      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>  
> 
> Can we use this value for the BYTE_COPY_RIGHT?

cristian: it depends on the layout of the virtual machine memory that
you are using. in any case UDVM_memory_size must be computed in
accordance with the formula above.

> 
>  
> 
> Also, Is it mandatory for the SIGCOMP library to calculate the
> udvm_memory_size as per the above formula?

cristian: yes, since the behaviour should be predictable
(i.e. the bytecode sent by the remote endpoint should be able
to compute how much virtual machine memory is left to be used as a 
"decompression buffer")

bye now!
cristian

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



From rohc-bounces@ietf.org Fri Feb 16 12:44:14 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI77t-0003RC-3N; Fri, 16 Feb 2007 12:44:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI77o-0003P3-Jl; Fri, 16 Feb 2007 12:44:00 -0500
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HI77n-0000kq-84; Fri, 16 Feb 2007 12:44:00 -0500
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l1GHhwDg006173; 
	Fri, 16 Feb 2007 09:43:58 -0800
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l1GHhwGM006172;
	Fri, 16 Feb 2007 09:43:58 -0800
Date: Fri, 16 Feb 2007 09:43:58 -0800
Message-Id: <200702161743.l1GHhwGM006172@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: rohc@ietf.org, rfc-editor@rfc-editor.org
Subject: [rohc] RFC 4815 on RObust Header Compression (ROHC): Corrections
	and Clarifications to RFC 3095
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org


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

        
        RFC 4815

        Title:      RObust Header Compression (ROHC): Corrections 
                    and Clarifications to RFC 3095 
        Author:     L-E. Jonsson, K. Sandlund,
                    G. Pelletier, P. Kremer
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    lars-erik.jonsson@ericsson.com, 
                    kristofer.sandlund@ericsson.com, 
                    ghyslain.pelletier@ericsson.com,  
                    peter.kremer@ericsson.com
        Pages:      33
        Characters: 74819
        Updates:    RFC3095, RFC3241, RFC3843, RFC4019, RFC4362
        See-Also:   

        I-D Tag:    draft-ietf-rohc-rtp-impl-guide-22.txt

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

RFC 3095 defines the RObust Header Compression (ROHC) framework and
profiles for IP (Internet Protocol), UDP (User Datagram Protocol),
RTP (Real-Time Transport Protocol), and ESP (Encapsulating Security
Payload).  Some parts of the specification are unclear or contain
errors that may lead to misinterpretations that may impair
interoperability between different implementations.  This document
provides corrections, additions, and clarifications to RFC 3095; this
document thus updates RFC 3095.  In addition, other clarifications
related to RFC 3241 (ROHC over PPP), RFC 3843 (ROHC IP profile) and
RFC 4109 (ROHC UDP-Lite profiles) are also provided.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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

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

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

help: ways_to_get_rfcs. For example:

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

        help: ways_to_get_rfcs

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

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


The RFC Editor Team
USC/Information Sciences Institute

...



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



From rohc-bounces@ietf.org Fri Feb 23 12:12:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKdy9-0002ki-2S; Fri, 23 Feb 2007 12:12:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKdy6-0002k8-KN; Fri, 23 Feb 2007 12:12:26 -0500
Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKdy5-0006Va-AZ; Fri, 23 Feb 2007 12:12:26 -0500
Received: from [172.17.2.61] (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.13.8/8.13.8) with ESMTP id l1NHCJxJ061652
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 23 Feb 2007 11:12:19 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <45DF2074.90909@nostrum.com>
Date: Fri, 23 Feb 2007 11:12:20 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: "'rohc@ietf.org'" <rohc@ietf.org>
References: <45477421.2080305@nostrum.com>
In-Reply-To: <45477421.2080305@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: SIP WG <sip@ietf.org>, Keith Drage <drage@lucent.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: [rohc] Comments: draft-ietf-rohc-sigcomp-sip-04
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

The sigcomp-sip revisions look good. I have a couple of small comments 
on the new text that should be easy to resolve:

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

Section 8.3:
>    To indicate that such state will continue
>    to be available, the SigComp endpoint can inform its peer SigComp
>    endpoint by announcing the (partial) state ID in the returned SigComp
>    parameters at the end of the registration, dialog, or transaction
>    that was supposed to limit the lifetime of the SigComp state.

I think this is left-over language from the time that dialogs and 
transactions could have associated compartments. I suggest:

   To indicate that such state will continue  
   to be available, the SigComp endpoint can inform its peer SigComp
   endpoint by announcing the (partial) state ID in the returned SigComp
   parameters upon termination of the registration.


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

Nit; Section 8.4:

> Section 9 provides network administrators with recommendations so that 
> they configure they networks properly.

...should be:

    Section 9 provides network administrators with recommendations so
    that they can configure their networks properly.


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

Aside from these two small corrections, I think the document is ready 
for publication. I still believe that it would be improved by the 
addition of an example SIP message (instead of mere excerpts), and I am 
re-including my suggestion from a previous review below. However, I 
think the document serves its purpose even without the example, and see 
no reason to hinder its progress simply because it lacks such an example.

   REGISTER sip:example.net SIP/2.0
   Via: SIP/2.0/UDP 192.0.2.247:2078;branch=z9hG4bK-et736vsjirav;
        rport;sigcomp-id="urn:uuid:2e5fdc76-00be-4314-8202-1116fa82a473"
   From: "Joe User" <sip:2145550500@example.net>;tag=6to4gh7t5j
   To: "Bob User" <sip:2145550501@example.net>
   Call-ID: 3c26700c1adb-lu1lz5ri5orr
   CSeq: 215196 REGISTER
   Max-Forwards: 70
   Contact: <sip:2145550500@192.0.2.247:2078;
            sigcomp-id=urn%3auuid%3a2e5fdc76-00be-4314-8202-1116fa82a473>;
            q=1.0; expires=3600;
            +sip.instance="<urn:uuid:2e5fdc76-00be-4314-8202-1116fa82a473>"
   Content-Length: 0

/a

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



From rohc-bounces@ietf.org Mon Feb 26 15:51:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmoX-0006Mh-3u; Mon, 26 Feb 2007 15:51:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmnk-000490-N0; Mon, 26 Feb 2007 15:50:28 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLmnY-0005yt-E7; Mon, 26 Feb 2007 15:50:28 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 798023299C;
	Mon, 26 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HLmnL-00050I-Bm; Mon, 26 Feb 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HLmnL-00050I-Bm@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-ikev2-extensions-hcoipsec-01.txt 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

--NextPart

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


--OtherAccess--

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

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

--NextPart--




From rohc-bounces@ietf.org Mon Feb 26 15:51:29 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmoW-0006ML-Kq; Mon, 26 Feb 2007 15:51:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmnk-00048y-M7; Mon, 26 Feb 2007 15:50:28 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLmnY-0005ys-Dt; Mon, 26 Feb 2007 15:50:28 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 73D7632987;
	Mon, 26 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HLmnL-00050F-B6; Mon, 26 Feb 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HLmnL-00050F-B6@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-hcoipsec-04.txt 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

--NextPart

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

	Title		: Integration of Header Compression over IPsec Security Associations
	Author(s)	: E. Ertekin, et al.
	Filename	: draft-ietf-rohc-hcoipsec-04.txt
	Pages		: 14
	Date		: 2007-2-26
	
IP Security (IPsec) [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 Header Compression (HC) over IPsec (HCoIPsec).  By
   compressing the inner headers of IP packets, HCoIPsec 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-04.txt

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

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

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

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

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

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

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

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

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

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

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

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


--OtherAccess--

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

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

--NextPart--




From rohc-bounces@ietf.org Mon Feb 26 19:39:35 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLqNT-0006aV-Rr; Mon, 26 Feb 2007 19:39:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLqLz-0005kL-My; Mon, 26 Feb 2007 19:38:03 -0500
Received: from deliverator7.gatech.edu ([130.207.165.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLqLv-0006xa-8f; Mon, 26 Feb 2007 19:38:03 -0500
Received: from deliverator7.gatech.edu (localhost [127.0.0.1])
	by localhost (Postfix) with SMTP id 7A34A1A88;
	Mon, 26 Feb 2007 19:37:58 -0500 (EST)
	(envelope-from christian@gatech.edu)
Received: from mailprx4.gatech.edu (mailprx4.prism.gatech.edu [130.207.171.18])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client CN "smtp.mail.gatech.edu", Issuer "RSA Data Security,
	Inc." (verified OK))
	by deliverator7.gatech.edu (Postfix) with ESMTP id 083451AE1;
	Mon, 26 Feb 2007 19:37:13 -0500 (EST)
	(envelope-from christian@gatech.edu)
Received: from Christian2 (r82h200.res.gatech.edu [128.61.82.200])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	(sasl: method=LOGIN, username=cmenkens3@mailprx4.gatech.edu, sender=n/a)
	by mailprx4.gatech.edu (Postfix) with ESMTP
	id 33BBA215F; Mon, 26 Feb 2007 19:37:12 -0500 (EST)
	(envelope-from christian@gatech.edu)
From: "Christian M Menkens" <christian@gatech.edu>
To: <simple@ietf.org>
Date: Mon, 26 Feb 2007 19:37:11 -0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcdaB2q23rNZKLHMS2m2lTP7TqZCgw==
Message-Id: <20070227003712.33BBA215F@mailprx4.gatech.edu>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f2728948111f2edaaf8980b5b9de55af
Cc: rohc@ietf.org, sip-implementors@cs.columbia.edu
Subject: [rohc] SIMPLE - Presence Dictionary compression
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1417995266=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1417995266==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_07B8_01C759DD.8375AC00"

This is a multi-part message in MIME format.

------=_NextPart_000_07B8_01C759DD.8375AC00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am currently working on evaluating SigComp for out IMS lab at our
university and I saw that Miguel A. Garcia developed a new dictionary for
Presence traffic. This looks really interesting and I am wondering if there
is some compression/decompression software (test UA and sigcomp
implementation etc) out there that can compress SIP traffic with that
dictionary already.
 
I already talked to developers from OpenSigComp and they said it will
probably be part of a future implementation but for now I would need to
implement it myself. 
 
Our project team would like to put more effort into analysing typical
traffic and compression rates and I think there is not enough time to
implement everything.
 
I thought maybe someone is already working on that?
 
Best,
 
Christian

 

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

Christian M. Menkens
Georgia Institute of Technology

251 10th Street, NW, G404
Atlanta, Georgia
30318
Phone: 404-206-3586
Mobile: 404-547-1953
 <mailto:404-547-1953christian@gatech.edu> christian@gatech.edu
 <mailto:christian@menkens.at> christian@menkens.at
 <http://www.christianmenkens.at/> www.christianmenkens.at

 


------=_NextPart_000_07B8_01C759DD.8375AC00
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.E-MailFormatvorlage17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DDE-AT link=3Dblue vlink=3Dpurple>

<div class=3DSection1><pre><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>I am currently working on evaluating SigComp =
for out IMS lab at our university and I saw that Miguel A. Garcia =
developed a new dictionary for Presence traffic. This looks really =
interesting and I am wondering if there is some =
compression/decompression software (test UA and sigcomp implementation =
etc) out there that can compress SIP traffic with that dictionary =
already.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>I already talked to developers from =
OpenSigComp and they said it will probably be part of a future =
implementation but for now I would need to implement it myself. =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>Our project team would like to put more =
effort into analysing typical traffic and compression rates and I think =
there is not enough time to implement =
everything.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>I thought maybe someone is already working on =
that?<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>Best,<o:p></o:p></span></font></pre><pre><font=

size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>Christian<o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana'>--------------------------=
--------------------------</span></font><span
lang=3DEN-GB><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana'>Christian
M. Menkens<br>
<strong><b><font face=3DVerdana><span =
style=3D'font-family:Verdana'>Georgia Institute
of Technology</span></font></b></strong><br>
<br>
<st1:Street w:st=3D"on"><st1:address w:st=3D"on">251 10th Street, =
NW</st1:address></st1:Street>,
G404<br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Atlanta</st1:City>, =
<st1:country-region
 w:st=3D"on">Georgia</st1:country-region></st1:place><br>
30318<br>
Phone: 404-206-3586<br>
<st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Mobile</st1:place></st1:City>:
404-547-1953<br>
</span></font><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'><a =
href=3D"mailto:404-547-1953christian@gatech.edu"><span
lang=3DEN-GB>christian@gatech.edu</span></a></span></font><font size=3D2
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana'><br>
</span></font><a href=3D"mailto:christian@menkens.at"
title=3D"mailto:christian@menkens.at"><font size=3D2 =
face=3DVerdana><span lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana'><span
title=3D"mailto:christian@menkens.at">christian@menkens.at</span></span><=
/font></a><span
lang=3DEN-GB><br>
</span><a href=3D"http://www.christianmenkens.at/"
title=3D"http://www.christianmenkens.at"><font size=3D2 =
face=3DVerdana><span
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:Verdana'><span
title=3D"http://www.christianmenkens.at">www.christianmenkens.at</span></=
span></font></a><span
lang=3DEN-GB><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_07B8_01C759DD.8375AC00--



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

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

--===============1417995266==--





