From rohc-bounces@ietf.org Wed Aug 01 06:49:34 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGBll-0002W0-DD; Wed, 01 Aug 2007 06:49:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGBlk-0002UG-NN
	for rohc@ietf.org; Wed, 01 Aug 2007 06:49:32 -0400
Received: from spark.hss.co.in ([203.145.155.21] helo=tapal.aricent.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGBli-0002L4-Pq
	for rohc@ietf.org; Wed, 01 Aug 2007 06:49:32 -0400
Received: from tapal.aricent.com (localhost [127.0.0.1])
	by tapal.aricent.com (8.13.8/8.13.8) with ESMTP id l71Ai8el005866
	for <rohc@ietf.org>; Wed, 1 Aug 2007 16:14:08 +0530
Received: from pragati.bgh.aricent.com (pragati.bgh.aricent.com 
	[10.203.193.22])by tapal.aricent.com (8.13.8/8.13.8) with ESMTP id 
	l71Ai7N7005853;Wed, 1 Aug 2007 16:14:08 +0530
In-Reply-To: <A632AD91CF90F24A87C42F6B96ADE5C51C4A60@rsys005a.comm.ad.roke.co.uk>
To: "West, Mark" <mark.a.west@roke.co.uk>
Subject: Re: [rohc] RE: State acknowledgement.
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF8B85C8FF.AD784342-ON6525732A.003A5A8A-6525732A.003BEE9C@flextronicssoftware.com>
From: Ranjith.V@aricent.com
Date: Wed, 1 Aug 2007 16:14:34 +0530
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5.5|November 
	30, 2005) at08/01/2007 04:13:40 PM,Serialize complete at 08/01/2007 
	04:13:40 PM
X-imss-version: 2.047
X-imss-result: Passed
X-imss-scanInfo: M:B L:N SM:2
X-imss-tmaseResult: TT:1 TS:-20.0772 TC:1F TRN:75 TV:3.6.1039(15332.002)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:2 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 4.9 (++++)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
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>
Content-Type: multipart/mixed; boundary="===============0027386897=="
Errors-To: rohc-bounces@ietf.org

This is a multipart message in MIME format.
--===============0027386897==
Content-Type: multipart/alternative;
	boundary="=_alternative 003BEE966525732A_="

This is a multipart message in MIME format.
--=_alternative 003BEE966525732A_=
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: base64

SGkgV2VzdCwNCg0KVGhhbmsgeW91IGZvciB5b3VyIHJlc3BvbnNlLg0KDQpOb3cgSSBhbSB3b25k
ZXJpbmcgYWJvdXQgIHNlbGVjdGluZyB0aGUgIHR5cGUgb2YgdGhlIENvbXByZXNzaW9uIGFsZ29y
aXRobSANCnRvIHVzZSAgaW4gU2lnQ29tcC4NCg0KRnJvbSBzb21lIHdoaXRlcGFwZXJzIEkgY2Ft
ZSB0byBrbm93IHRoYXQgTFpTIGlzIGJldHRlciB0aGFuIERFRkxBVEUgLiBpLmUgDQogREVGTEFU
RSBjb25zdW1lcyBtb3JlIENQVSB0aW1lIHRoYW4gTFpTLiBERUZMQVRFIGdpdmVzIGJpdCBiZXR0
ZXIgDQpjb21wcmVzc2lvbiByYXRpbyB0aGFuIExaUy4NCg0KSSB3YW50IHRvIHVzZSBMWlMuIElz
IHRoZXJlIGFueSB0aGlyZCBwYXJ0eSBsaWJyYXJ5ICBhdmFpbGFibGUgZm9yIExaUyANCmNvbXBy
ZXNzaW9uLiAoIHdpdGggTm8gSVBSIGlzc3VlcyBhbmQgZnJlZSBvZiBjb3N0IDotKSkpICkNCg0K
UGxlYXNlIGNsYXJpZnkgdGhpcy4gDQoNCg0KVGhhbmtzIGFuZCBSZWdhcmRzDQpSYW5qaXRoIFJl
ZGR5LiBWDQpFeHRuOiA5MTM0DQpMb2NhdGlvbiA6IEY0LTEyMg0KDQoNCg0KIldlc3QsIE1hcmsi
IDxtYXJrLmEud2VzdEByb2tlLmNvLnVrPiANCjA3LzI3LzIwMDcgMDI6MDggUE0NCg0KDQpUbw0K
UmFuaml0aCBSZWRkeSBWL0JMUi9IU1NASFNTDQpjYw0Kcm9oY0BpZXRmLm9yZw0KU3ViamVjdA0K
W3JvaGNdIFJFOiBTdGF0ZSBhY2tub3dsZWRnZW1lbnQuDQoNCg0KDQoNCg0KDQogDQpIaSBSYW5q
aXRoLA0KIA0KSXQncyB1cCB0byB5b3UgdG8gY29uc3RydWN0IHRoZSBmZWVkYmFjayBzdHJpbmcu
ICBJdCBjYW4gYmUgd2hhdGV2ZXIgeW91IA0Kd2FudCAtLSB0aGUgZXhhbXBsZSBpbiBSRkMgMzMy
MSBpcywgaWYgSSByZW1lbWJlciBjb3JyZWN0bHksIHVzaW5nIHRoZSANCnN0YXRlIGhhc2gsIGJ1
dCBpdCBkb2Vzbid0IGhhdmUgdG8gYmUgdGhhdC4NCiANCkluIHlvdXIgZXhhbXBsZSwgY29tcHJl
c3NvciBBIHdvdWxkIGtub3cgdGhlIFNNUyBhdCBCIChpdCBoYXMgdG8ga25vdyB0aGlzIA0KZm9y
IHRoZSBzZWN1cmUgcmVmZXJlbmNlIHByaW5jaXBsZSB0byB3b3JrKSBhbmQgc28ga25vd3Mgd2hp
Y2ggc3RhdGVzIHdpbGwgDQpiZSBjcmVhdGVkIChhbmQgd2hpY2ggd2lsbCBiZSBkZWxldGVkKS4g
IEEgY2FuIHdvcmsgdGhpcyBvdXQgZnJvbSB0aGUgDQpzdGF0ZS1jcmVhdGlvbiBydWxlcy4NCiAN
CkNoZWVycywNCiANCk1hcmsuDQogDQpQUyAtLSB5b3VyIGRpc2NsYWltZXIgc3RhdGVzIHRoYXQg
dGhpcyBpcyBwcm9wcmlldGFyeSBpbmZvcm1hdGlvbiwgd2hpY2ggDQpkb2Vzbid0IHJlYWxseSBm
aXQgd2l0aCB0aGlzIGJlaW5nIGEgcHVibGljIG1haWxpbmcgbGlzdC4uLg0KIA0KIA0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFJhbmppdGguVkBhcmljZW50LmNvbSBbbWFpbHRv
OlJhbmppdGguVkBhcmljZW50LmNvbV0NClNlbnQ6IDI3IEp1bHkgMjAwNyAwNzo0Nw0KVG86IFdl
c3QsIE1hcmsNCkNjOiByb2hjQGlldGYub3JnDQpTdWJqZWN0OiBTdGF0ZSBhY2tub3dsZWRnZW1l
bnQuDQoNCg0KDQpIaSBXZXN0LCANCg0KSWYgYSBDb21wcmVzc29yIEEgcmVxdWVzdHMgRGVjb21w
cmVzc29yIEIgdG8gY3JlYXRlIGEgIEJ5dGVjb2RlIHN0YXRlLCANCkR5bmFtaWMgc3RhdGUgYW5k
IGEgIFVTRCBzdGF0ZSB0aGVuIGhvdyBkZWNvbXByZXNzb3IgQiBhY2tub3dsZWRnZXMgb2YgDQp0
aGVzZSBzdGF0ZXMgdG8gQS4gDQoNCkkga25vdyBhYm91dCAgZmVlZGJhY2sgbWVjaGFuaXNhbSAu
IE15IGRvdWJ0IGlzIGFib3V0ICB3aGF0IHdpbGwgYmUgdGhlIA0KZmVlZGJhY2sgc3RyaW5nLi4u
PyANCg0KU3VwcG9zZSBkZWNvbXByZXNzb3IgQiBoYXZlIGVub3VnaHMgU01TIHRvIGNyZWF0ZSBC
eXRlY29kZSBzdGF0ZSwgRHluYW1pYyANCnN0YXRlIGFuZCBpdCBpcyBub3QgZm9yIFVTRCBzdGF0
ZSB0aGVuIGhvdyBpdCBpbmZvcm1zIGFib3V0IHNhdmVkIHN0YXRlcyANCmFuZCB1bnNhdmVkIHN0
YXRlcyB0byBjb21wcmVzc29yIEEuLi4/IA0KDQoNCg0KVGhhbmtzIGFuZCBSZWdhcmRzDQpSYW5q
aXRoIFJlZGR5LiBWDQpFeHRuOiA5MTM0DQpMb2NhdGlvbiA6IEY0LTEyMg0KDQoqKioqKioqKioq
KioqKioqKioqKioqKiAgQXJpY2VudC0gQ29uZmlkZW50aWFsICAgKioqKioqKioqKioqKioqKioq
KioqKiogDQoiRElTQ0xBSU1FUjogVGhpcyBtZXNzYWdlIGlzIHByb3ByaWV0YXJ5IHRvIEFyaWNl
bnQgYW5kIGlzIGludGVuZGVkIHNvbGVseSANCmZvciB0aGUgdXNlIG9mIA0KdGhlIGluZGl2aWR1
YWwgdG8gd2hvbSBpdCBpcyBhZGRyZXNzZWQuIEl0IG1heSBjb250YWluIHByaXZpbGVnZWQgb3Ig
DQpjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gYW5kIHNob3VsZCBub3QgYmUgDQpjaXJjdWxhdGVk
IG9yIHVzZWQgZm9yIGFueSBwdXJwb3NlIG90aGVyIHRoYW4gZm9yIHdoYXQgaXQgaXMgaW50ZW5k
ZWQuIElmIA0KeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBtZXNzYWdlIGluIGVycm9yLCANCnBsZWFz
ZSBub3RpZnkgdGhlIG9yaWdpbmF0b3IgaW1tZWRpYXRlbHkuIElmIHlvdSBhcmUgbm90IHRoZSBp
bnRlbmRlZCANCnJlY2lwaWVudCwgeW91IGFyZSBub3RpZmllZCB0aGF0IHlvdSBhcmUgc3RyaWN0
bHkNCnByb2hpYml0ZWQgZnJvbSB1c2luZywgY29weWluZywgYWx0ZXJpbmcsIG9yIGRpc2Nsb3Np
bmcgdGhlIGNvbnRlbnRzIG9mIA0KdGhpcyBtZXNzYWdlLiBBcmljZW50IGFjY2VwdHMgbm8gcmVz
cG9uc2liaWxpdHkgZm9yIA0KbG9zcyBvciBkYW1hZ2UgYXJpc2luZyBmcm9tIHRoZSB1c2Ugb2Yg
dGhlIGluZm9ybWF0aW9uIHRyYW5zbWl0dGVkIGJ5IHRoaXMgDQplbWFpbCBpbmNsdWRpbmcgZGFt
YWdlIGZyb20gdmlydXMuIg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KUm9oYyBtYWlsaW5nIGxpc3QNClJvaGNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3
MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JvaGMNCg0KDQoNCioqKioqKioqKioqKioqKioq
KioqKioqICBBcmljZW50LVByaXZhdGUgICAqKioqKioqKioqKioqKioqKioqKioqKg0KIkRJU0NM
QUlNRVI6IFRoaXMgbWVzc2FnZSBpcyBwcm9wcmlldGFyeSB0byBBcmljZW50IGFuZCBpcyBpbnRl
bmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgCnRoZSBpbmRpdmlkdWFsIHRvIHdob20gaXQgaXMg
YWRkcmVzc2VkLiBJdCBtYXkgY29udGFpbiBwcml2aWxlZ2VkIG9yIGNvbmZpZGVudGlhbCBpbmZv
cm1hdGlvbiBhbmQgc2hvdWxkIG5vdCBiZSAKY2lyY3VsYXRlZCBvciB1c2VkIGZvciBhbnkgcHVy
cG9zZSBvdGhlciB0aGFuIGZvciB3aGF0IGl0IGlzIGludGVuZGVkLiBJZiB5b3UgaGF2ZSByZWNl
aXZlZCB0aGlzIG1lc3NhZ2UgaW4gZXJyb3IsIApwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9y
IGltbWVkaWF0ZWx5LiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3Ug
YXJlIG5vdGlmaWVkIHRoYXQgeW91IGFyZSBzdHJpY3RseQpwcm9oaWJpdGVkIGZyb20gdXNpbmcs
IGNvcHlpbmcsIGFsdGVyaW5nLCBvciBkaXNjbG9zaW5nIHRoZSBjb250ZW50cyBvZiB0aGlzIG1l
c3NhZ2UuIEFyaWNlbnQgYWNjZXB0cyBubyByZXNwb25zaWJpbGl0eSBmb3IgCmxvc3Mgb3IgZGFt
YWdlIGFyaXNpbmcgZnJvbSB0aGUgdXNlIG9mIHRoZSBpbmZvcm1hdGlvbiB0cmFuc21pdHRlZCBi
eSB0aGlzIGVtYWlsIGluY2x1ZGluZyBkYW1hZ2UgZnJvbSB2aXJ1cy4iCg==
--=_alternative 003BEE966525732A_=
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCkhpIFdlc3QsPC9mb250
Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5UaGFuayB5b3UgZm9y
IHlvdXIgcmVzcG9uc2UuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5z
LXNlcmlmIj5Ob3cgSSBhbSB3b25kZXJpbmcgYWJvdXQgJm5ic3A7c2VsZWN0aW5nDQp0aGUgJm5i
c3A7dHlwZSBvZiB0aGUgQ29tcHJlc3Npb24gYWxnb3JpdGhtIHRvIHVzZSAmbmJzcDtpbiBTaWdD
b21wLjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+RnJv
bSBzb21lIHdoaXRlcGFwZXJzIEkgY2FtZSB0byBrbm93DQp0aGF0IExaUyBpcyBiZXR0ZXIgdGhh
biBERUZMQVRFIC4gaS5lICZuYnNwO0RFRkxBVEUgY29uc3VtZXMgbW9yZSBDUFUgdGltZQ0KdGhh
biBMWlMuIERFRkxBVEUgZ2l2ZXMgYml0IGJldHRlciBjb21wcmVzc2lvbiByYXRpbyB0aGFuIExa
Uy48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkkgd2Fu
dCB0byB1c2UgTFpTLiBJcyB0aGVyZSBhbnkgdGhpcmQNCnBhcnR5IGxpYnJhcnkgJm5ic3A7YXZh
aWxhYmxlIGZvciBMWlMgY29tcHJlc3Npb24uICggd2l0aCBObyBJUFIgaXNzdWVzDQphbmQgZnJl
ZSBvZiBjb3N0IDotKSkpICk8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPlBsZWFzZSBjbGFyaWZ5IHRoaXMuIDxicj4NCjxicj4NCjxicj4NClRoYW5rcyBh
bmQgUmVnYXJkczxicj4NClJhbmppdGggUmVkZHkuIFY8YnI+DQpFeHRuOiA5MTM0PGJyPg0KTG9j
YXRpb24gOiBGNC0xMjI8L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8YnI+DQo8dGFibGUgd2lkdGg9MTAw
JT4NCjx0ciB2YWxpZ249dG9wPg0KPHRkIHdpZHRoPTQwJT48Zm9udCBzaXplPTEgZmFjZT0ic2Fu
cy1zZXJpZiI+PGI+JnF1b3Q7V2VzdCwgTWFyayZxdW90Ow0KJmx0O21hcmsuYS53ZXN0QHJva2Uu
Y28udWsmZ3Q7PC9iPiA8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+
MDcvMjcvMjAwNyAwMjowOCBQTTwvZm9udD4NCjxicj4NCjx0ZCB3aWR0aD01OSU+DQo8dGFibGUg
d2lkdGg9MTAwJT4NCjx0cj4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZh
Y2U9InNhbnMtc2VyaWYiPlRvPC9mb250PjwvZGl2Pg0KPHRkIHZhbGlnbj10b3A+PGZvbnQgc2l6
ZT0xIGZhY2U9InNhbnMtc2VyaWYiPlJhbmppdGggUmVkZHkgVi9CTFIvSFNTQEhTUzwvZm9udD4N
Cjx0cj4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2Vy
aWYiPmNjPC9mb250PjwvZGl2Pg0KPHRkIHZhbGlnbj10b3A+PGZvbnQgc2l6ZT0xIGZhY2U9InNh
bnMtc2VyaWYiPnJvaGNAaWV0Zi5vcmc8L2ZvbnQ+DQo8dHI+DQo8dGQ+DQo8ZGl2IGFsaWduPXJp
Z2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5TdWJqZWN0PC9mb250PjwvZGl2Pg0K
PHRkIHZhbGlnbj10b3A+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPltyb2hjXSBSRTog
U3RhdGUgYWNrbm93bGVkZ2VtZW50LjwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxlPg0KPHRy
IHZhbGlnbj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJyPg0KPGJy
Pg0KPGJyPjxmb250IHNpemU9Mz4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9y
PWJsdWUgZmFjZT0iQXJpYWwiPkhpIFJhbmppdGgsPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz4m
bmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwiPkl0
J3MgdXAgdG8geW91IHRvIGNvbnN0cnVjdCB0aGUNCmZlZWRiYWNrIHN0cmluZy4gJm5ic3A7SXQg
Y2FuIGJlIHdoYXRldmVyIHlvdSB3YW50IC0tIHRoZSBleGFtcGxlIGluIFJGQw0KMzMyMSBpcywg
aWYgSSByZW1lbWJlciBjb3JyZWN0bHksIHVzaW5nIHRoZSBzdGF0ZSBoYXNoLCBidXQgaXQgZG9l
c24ndA0KaGF2ZSB0byBiZSB0aGF0LjwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+Jm5ic3A7PC9m
b250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZhY2U9IkFyaWFsIj5JbiB5b3VyIGV4
YW1wbGUsIGNvbXByZXNzb3IgQQ0Kd291bGQga25vdyB0aGUgU01TIGF0IEIgKGl0IGhhcyB0byBr
bm93IHRoaXMgZm9yIHRoZSBzZWN1cmUgcmVmZXJlbmNlIHByaW5jaXBsZQ0KdG8gd29yaykgYW5k
IHNvIGtub3dzIHdoaWNoIHN0YXRlcyB3aWxsIGJlIGNyZWF0ZWQgKGFuZCB3aGljaCB3aWxsIGJl
IGRlbGV0ZWQpLg0KJm5ic3A7QSBjYW4gd29yayB0aGlzIG91dCBmcm9tIHRoZSBzdGF0ZS1jcmVh
dGlvbiBydWxlcy48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPiZuYnNwOzwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgY29sb3I9Ymx1ZSBmYWNlPSJBcmlhbCI+Q2hlZXJzLDwvZm9udD4NCjxicj48
Zm9udCBzaXplPTM+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZh
Y2U9IkFyaWFsIj5NYXJrLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+Jm5ic3A7PC9mb250Pg0K
PGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZhY2U9IkFyaWFsIj5QUyAtLSB5b3VyIGRpc2Ns
YWltZXIgc3RhdGVzIHRoYXQNCnRoaXMgaXMgcHJvcHJpZXRhcnkgaW5mb3JtYXRpb24sIHdoaWNo
IGRvZXNuJ3QgcmVhbGx5IGZpdCB3aXRoIHRoaXMgYmVpbmcNCmEgcHVibGljIG1haWxpbmcgbGlz
dC4uLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNp
emU9Mz4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IlRhaG9tYSI+LS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS08Yj48YnI+DQpGcm9tOjwvYj4gUmFuaml0aC5WQGFyaWNlbnQu
Y29tIFttYWlsdG86UmFuaml0aC5WQGFyaWNlbnQuY29tXTxiPjxicj4NClNlbnQ6PC9iPiAyNyBK
dWx5IDIwMDcgMDc6NDc8Yj48YnI+DQpUbzo8L2I+IFdlc3QsIE1hcms8Yj48YnI+DQpDYzo8L2I+
IHJvaGNAaWV0Zi5vcmc8Yj48YnI+DQpTdWJqZWN0OjwvYj4gU3RhdGUgYWNrbm93bGVkZ2VtZW50
Ljxicj4NCjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0K
PGJyPg0KSGkgV2VzdCw8L2ZvbnQ+PGZvbnQgc2l6ZT0zPiA8YnI+DQo8L2ZvbnQ+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCklmIGEgQ29tcHJlc3NvciBBIHJlcXVlc3RzIERl
Y29tcHJlc3NvciBCIHRvIGNyZWF0ZSBhICZuYnNwO0J5dGVjb2RlIHN0YXRlLA0KRHluYW1pYyBz
dGF0ZSBhbmQgYSAmbmJzcDtVU0Qgc3RhdGUgdGhlbiBob3cgZGVjb21wcmVzc29yIEIgYWNrbm93
bGVkZ2VzDQpvZiB0aGVzZSBzdGF0ZXMgdG8gQS48L2ZvbnQ+PGZvbnQgc2l6ZT0zPiA8YnI+DQo8
L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCkkga25vdyBhYm91dCAm
bmJzcDtmZWVkYmFjayBtZWNoYW5pc2FtIC4gTXkgZG91YnQgaXMgYWJvdXQgJm5ic3A7d2hhdCB3
aWxsDQpiZSB0aGUgZmVlZGJhY2sgc3RyaW5nLi4uPzwvZm9udD48Zm9udCBzaXplPTM+IDxicj4N
CjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KU3VwcG9zZSBkZWNv
bXByZXNzb3IgQiBoYXZlIGVub3VnaHMgU01TIHRvIGNyZWF0ZSBCeXRlY29kZSBzdGF0ZSwgRHlu
YW1pYw0Kc3RhdGUgYW5kIGl0IGlzIG5vdCBmb3IgVVNEIHN0YXRlIHRoZW4gaG93IGl0IGluZm9y
bXMgYWJvdXQgc2F2ZWQgc3RhdGVzDQphbmQgdW5zYXZlZCBzdGF0ZXMgdG8gY29tcHJlc3NvciBB
Li4uPzwvZm9udD48Zm9udCBzaXplPTM+IDxicj4NCjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+PGJyPg0KPGJyPg0KPGJyPg0KVGhhbmtzIGFuZCBSZWdhcmRzPGJyPg0KUmFu
aml0aCBSZWRkeS4gVjxicj4NCkV4dG46IDkxMzQ8YnI+DQpMb2NhdGlvbiA6IEY0LTEyMjxicj4N
Cjxicj4NCioqKioqKioqKioqKioqKioqKioqKioqICZuYnNwO0FyaWNlbnQtIENvbmZpZGVudGlh
bCAmbmJzcDsgKioqKioqKioqKioqKioqKioqKioqKio8L2ZvbnQ+PGZvbnQgc2l6ZT0zPg0KPC9m
b250Pg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHI+DQo8dGQgd2lkdGg9MTAwJSBiZ2NvbG9yPXdo
aXRlPjx0dD48Zm9udCBzaXplPTM+JnF1b3Q7RElTQ0xBSU1FUjogVGhpcyBtZXNzYWdlDQppcyBw
cm9wcmlldGFyeSB0byBBcmljZW50IGFuZCBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ug
b2YgPGJyPg0KdGhlIGluZGl2aWR1YWwgdG8gd2hvbSBpdCBpcyBhZGRyZXNzZWQuIEl0IG1heSBj
b250YWluIHByaXZpbGVnZWQgb3IgY29uZmlkZW50aWFsDQppbmZvcm1hdGlvbiBhbmQgc2hvdWxk
IG5vdCBiZSA8YnI+DQpjaXJjdWxhdGVkIG9yIHVzZWQgZm9yIGFueSBwdXJwb3NlIG90aGVyIHRo
YW4gZm9yIHdoYXQgaXQgaXMgaW50ZW5kZWQuDQpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIG1l
c3NhZ2UgaW4gZXJyb3IsIDxicj4NCnBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3IgaW1tZWRp
YXRlbHkuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsDQp5b3UgYXJlIG5v
dGlmaWVkIHRoYXQgeW91IGFyZSBzdHJpY3RseTxicj4NCnByb2hpYml0ZWQgZnJvbSB1c2luZywg
Y29weWluZywgYWx0ZXJpbmcsIG9yIGRpc2Nsb3NpbmcgdGhlIGNvbnRlbnRzIG9mDQp0aGlzIG1l
c3NhZ2UuIEFyaWNlbnQgYWNjZXB0cyBubyByZXNwb25zaWJpbGl0eSBmb3IgPGJyPg0KbG9zcyBv
ciBkYW1hZ2UgYXJpc2luZyBmcm9tIHRoZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zbWl0
dGVkIGJ5IHRoaXMNCmVtYWlsIGluY2x1ZGluZyBkYW1hZ2UgZnJvbSB2aXJ1cy4mcXVvdDs8YnI+
DQo8L2ZvbnQ+PC90dD48L3RhYmxlPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+X19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpSb2hjIG1haWxpbmcgbGlz
dDxicj4NClJvaGNAaWV0Zi5vcmc8YnI+DQpodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9yb2hjPGJyPg0KPC9mb250PjwvdHQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPjxicj4NCjxicj4NCioqKioqKioqKioqKioqKioqKioqKioqICZuYnNwO0FyaWNl
bnQtUHJpdmF0ZSAmbmJzcDsgKioqKioqKioqKioqKioqKioqKioqKio8L2ZvbnQ+DQo8dGFibGU+
PHRyPjx0ZCBiZ2NvbG9yPSNmZmZmZmY+PGZvbnQgY29sb3I9IzAwMDAwMD48cHJlPiJESVNDTEFJ
TUVSOiBUaGlzIG1lc3NhZ2UgaXMgcHJvcHJpZXRhcnkgdG8gQXJpY2VudCBhbmQgaXMgaW50ZW5k
ZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIAp0aGUgaW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzIGFk
ZHJlc3NlZC4gSXQgbWF5IGNvbnRhaW4gcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3Jt
YXRpb24gYW5kIHNob3VsZCBub3QgYmUgCmNpcmN1bGF0ZWQgb3IgdXNlZCBmb3IgYW55IHB1cnBv
c2Ugb3RoZXIgdGhhbiBmb3Igd2hhdCBpdCBpcyBpbnRlbmRlZC4gSWYgeW91IGhhdmUgcmVjZWl2
ZWQgdGhpcyBtZXNzYWdlIGluIGVycm9yLCAKcGxlYXNlIG5vdGlmeSB0aGUgb3JpZ2luYXRvciBp
bW1lZGlhdGVseS4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgeW91IGFy
ZSBub3RpZmllZCB0aGF0IHlvdSBhcmUgc3RyaWN0bHkKcHJvaGliaXRlZCBmcm9tIHVzaW5nLCBj
b3B5aW5nLCBhbHRlcmluZywgb3IgZGlzY2xvc2luZyB0aGUgY29udGVudHMgb2YgdGhpcyBtZXNz
YWdlLiBBcmljZW50IGFjY2VwdHMgbm8gcmVzcG9uc2liaWxpdHkgZm9yIApsb3NzIG9yIGRhbWFn
ZSBhcmlzaW5nIGZyb20gdGhlIHVzZSBvZiB0aGUgaW5mb3JtYXRpb24gdHJhbnNtaXR0ZWQgYnkg
dGhpcyBlbWFpbCBpbmNsdWRpbmcgZGFtYWdlIGZyb20gdmlydXMuIgo8L3ByZT48L2ZvbnQ+PC90
ZD48L3RyPjwvdGFibGU+
--=_alternative 003BEE966525732A_=--


--===============0027386897==
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

--===============0027386897==--




From rohc-bounces@ietf.org Wed Aug 01 08:34:07 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGDOw-0006BQ-2Z; Wed, 01 Aug 2007 08:34:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGDOv-0006BL-6b
	for rohc@ietf.org; Wed, 01 Aug 2007 08:34:05 -0400
Received: from rsys002x.roke.co.uk ([193.118.201.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGDOt-00049f-JJ
	for rohc@ietf.org; Wed, 01 Aug 2007 08:34:05 -0400
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 l71CWMxn017477;
	Wed, 1 Aug 2007 13:32:22 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [rohc] RE: State acknowledgement.
Date: Wed, 1 Aug 2007 13:32:22 +0100
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C51C4A68@rsys005a.comm.ad.roke.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] RE: State acknowledgement.
Thread-Index: AcfUKbRJ+gkjqLvTS3yr9bQbI7CgwAACzEjA
From: "West, Mark" <mark.a.west@roke.co.uk>
To: <Ranjith.V@aricent.com>
X-MailScanner-roke-co-uk: Found to be clean
X-MailScanner-roke-co-uk-SpamCheck: 
X-MailScanner-From: mark.a.west@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
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>
Content-Type: multipart/mixed; boundary="===============1093388338=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1093388338==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D438.02373B04"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7D438.02373B04
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

IA0KSGkgUmFuaml0aCwNCiANClRoZSBzaW1wbGUgYW5zd2VyIGlzIHRoYXQgSSBkb24ndCBrbm93
OiB3ZSBkb24ndCB1c2UgTFpTIGFuZCBJJ3ZlIG5vdCBoYWQgY2F1c2UgdG8gbG9vayBmb3IgYW55
IGltcGxlbWVudGF0aW9ucy4uLg0KIA0KR29vZCBsdWNrLA0KIA0KTWFyay4NCiANCg0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFJhbmppdGguVkBhcmljZW50LmNvbSBbbWFpbHRv
OlJhbmppdGguVkBhcmljZW50LmNvbV0NClNlbnQ6IDAxIEF1Z3VzdCAyMDA3IDExOjQ1DQpUbzog
V2VzdCwgTWFyaw0KQ2M6IHJvaGNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbcm9oY10gUkU6IFN0
YXRlIGFja25vd2xlZGdlbWVudC4NCg0KDQoNCg0KSGkgV2VzdCwgDQoNClRoYW5rIHlvdSBmb3Ig
eW91ciByZXNwb25zZS4gDQoNCk5vdyBJIGFtIHdvbmRlcmluZyBhYm91dCAgc2VsZWN0aW5nIHRo
ZSAgdHlwZSBvZiB0aGUgQ29tcHJlc3Npb24gYWxnb3JpdGhtIHRvIHVzZSAgaW4gU2lnQ29tcC4g
DQoNCkZyb20gc29tZSB3aGl0ZXBhcGVycyBJIGNhbWUgdG8ga25vdyB0aGF0IExaUyBpcyBiZXR0
ZXIgdGhhbiBERUZMQVRFIC4gaS5lICBERUZMQVRFIGNvbnN1bWVzIG1vcmUgQ1BVIHRpbWUgdGhh
biBMWlMuIERFRkxBVEUgZ2l2ZXMgYml0IGJldHRlciBjb21wcmVzc2lvbiByYXRpbyB0aGFuIExa
Uy4gDQoNCkkgd2FudCB0byB1c2UgTFpTLiBJcyB0aGVyZSBhbnkgdGhpcmQgcGFydHkgbGlicmFy
eSAgYXZhaWxhYmxlIGZvciBMWlMgY29tcHJlc3Npb24uICggd2l0aCBObyBJUFIgaXNzdWVzIGFu
ZCBmcmVlIG9mIGNvc3QgOi0pKSkgKSANCg0KUGxlYXNlIGNsYXJpZnkgdGhpcy4gDQoNCg0KVGhh
bmtzIGFuZCBSZWdhcmRzDQpSYW5qaXRoIFJlZGR5LiBWDQpFeHRuOiA5MTM0DQpMb2NhdGlvbiA6
IEY0LTEyMiANCg0KDQoNCioqKioqKioqKioqKioqKioqKioqKioqICBBcmljZW50LVByaXZhdGUg
ICAqKioqKioqKioqKioqKioqKioqKioqKiANCg0KIkRJU0NMQUlNRVI6IFRoaXMgbWVzc2FnZSBp
cyBwcm9wcmlldGFyeSB0byBBcmljZW50IGFuZCBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1
c2Ugb2YgDQoNCnRoZSBpbmRpdmlkdWFsIHRvIHdob20gaXQgaXMgYWRkcmVzc2VkLiBJdCBtYXkg
Y29udGFpbiBwcml2aWxlZ2VkIG9yIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBhbmQgc2hvdWxk
IG5vdCBiZSANCg0KY2lyY3VsYXRlZCBvciB1c2VkIGZvciBhbnkgcHVycG9zZSBvdGhlciB0aGFu
IGZvciB3aGF0IGl0IGlzIGludGVuZGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIG1lc3Nh
Z2UgaW4gZXJyb3IsIA0KDQpwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIGltbWVkaWF0ZWx5
LiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJlIG5vdGlmaWVk
IHRoYXQgeW91IGFyZSBzdHJpY3RseQ0KDQpwcm9oaWJpdGVkIGZyb20gdXNpbmcsIGNvcHlpbmcs
IGFsdGVyaW5nLCBvciBkaXNjbG9zaW5nIHRoZSBjb250ZW50cyBvZiB0aGlzIG1lc3NhZ2UuIEFy
aWNlbnQgYWNjZXB0cyBubyByZXNwb25zaWJpbGl0eSBmb3IgDQoNCmxvc3Mgb3IgZGFtYWdlIGFy
aXNpbmcgZnJvbSB0aGUgdXNlIG9mIHRoZSBpbmZvcm1hdGlvbiB0cmFuc21pdHRlZCBieSB0aGlz
IGVtYWlsIGluY2x1ZGluZyBkYW1hZ2UgZnJvbSB2aXJ1cy4iDQoNCg0KDQo=

------_=_NextPart_001_01C7D438.02373B04
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05U
RU5UPSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KDQoNCjxNRVRBIGNvbnRlbnQ9Ik1TSFRN
TCA1LjUwLjQxMzQuNjAwIiBuYW1lPUdFTkVSQVRPUj48L0hFQUQ+DQo8Qk9EWT4NCjxESVY+PEZP
TlQgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMGZmIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8
RElWPjxTUEFOIGNsYXNzPTU5MzA1MTAxMi0wMTA4MjAwNz48Rk9OVCBmYWNlPUFyaWFsIGNvbG9y
PSMwMDAwZmYgc2l6ZT0yPkhpIA0KUmFuaml0aCw8L0ZPTlQ+PC9TUEFOPjwvRElWPg0KPERJVj48
Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PFNQQU4gY2xhc3M9NTkzMDUxMDEyLTAxMDgyMDA3PjxGT05UIGZhY2U9QXJpYWwgY29s
b3I9IzAwMDBmZiBzaXplPTI+VGhlIA0Kc2ltcGxlIGFuc3dlciBpcyB0aGF0IEkgZG9uJ3Qga25v
dzombmJzcDt3ZSBkb24ndCB1c2UgTFpTIGFuZCBJJ3ZlIG5vdCBoYWQgY2F1c2UgDQp0byBsb29r
IGZvciBhbnkgaW1wbGVtZW50YXRpb25zLi4uPC9GT05UPjwvU1BBTj48L0RJVj4NCjxESVY+PFNQ
QU4gY2xhc3M9NTkzMDUxMDEyLTAxMDgyMDA3PjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBm
ZiANCnNpemU9Mj48L0ZPTlQ+PC9TUEFOPiZuYnNwOzwvRElWPg0KPERJVj48U1BBTiBjbGFzcz01
OTMwNTEwMTItMDEwODIwMDc+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMGZmIHNpemU9Mj5H
b29kIA0KbHVjayw8L0ZPTlQ+PC9TUEFOPjwvRElWPg0KPERJVj48U1BBTiBjbGFzcz01OTMwNTEw
MTItMDEwODIwMDc+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMGZmIA0Kc2l6ZT0yPjwvRk9O
VD48L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElWPjxTUEFOIGNsYXNzPTU5MzA1MTAxMi0wMTA4MjAw
Nz48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwZmYgDQpzaXplPTI+TWFyay48L0ZPTlQ+PC9T
UEFOPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwv
Rk9OVD4mbmJzcDs8L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9IlBBRERJTkctTEVGVDogNXB4
OyBNQVJHSU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDogIzAwMDBmZiAycHggc29saWQiPg0KICA8
RElWIGNsYXNzPU91dGxvb2tNZXNzYWdlSGVhZGVyIGRpcj1sdHIgYWxpZ249bGVmdD48Rk9OVCBm
YWNlPVRhaG9tYSANCiAgc2l6ZT0yPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPEJSPjxCPkZy
b206PC9CPiBSYW5qaXRoLlZAYXJpY2VudC5jb20gDQogIFttYWlsdG86UmFuaml0aC5WQGFyaWNl
bnQuY29tXTxCUj48Qj5TZW50OjwvQj4gMDEgQXVndXN0IDIwMDcgDQogIDExOjQ1PEJSPjxCPlRv
OjwvQj4gV2VzdCwgTWFyazxCUj48Qj5DYzo8L0I+IHJvaGNAaWV0Zi5vcmc8QlI+PEI+U3ViamVj
dDo8L0I+IA0KICBSZTogW3JvaGNdIFJFOiBTdGF0ZSBhY2tub3dsZWRnZW1lbnQuPEJSPjxCUj48
L0ZPTlQ+PC9ESVY+PEJSPjxGT05UIA0KICBmYWNlPXNhbnMtc2VyaWYgc2l6ZT0yPjxCUj5IaSBX
ZXN0LDwvRk9OVD4gPEJSPjxCUj48Rk9OVCBmYWNlPXNhbnMtc2VyaWYgDQogIHNpemU9Mj5UaGFu
ayB5b3UgZm9yIHlvdXIgcmVzcG9uc2UuPC9GT05UPiA8QlI+PEJSPjxGT05UIGZhY2U9c2Fucy1z
ZXJpZiANCiAgc2l6ZT0yPk5vdyBJIGFtIHdvbmRlcmluZyBhYm91dCAmbmJzcDtzZWxlY3Rpbmcg
dGhlICZuYnNwO3R5cGUgb2YgdGhlIA0KICBDb21wcmVzc2lvbiBhbGdvcml0aG0gdG8gdXNlICZu
YnNwO2luIFNpZ0NvbXAuPC9GT05UPiA8QlI+PEJSPjxGT05UIA0KICBmYWNlPXNhbnMtc2VyaWYg
c2l6ZT0yPkZyb20gc29tZSB3aGl0ZXBhcGVycyBJIGNhbWUgdG8ga25vdyB0aGF0IExaUyBpcyBi
ZXR0ZXIgDQogIHRoYW4gREVGTEFURSAuIGkuZSAmbmJzcDtERUZMQVRFIGNvbnN1bWVzIG1vcmUg
Q1BVIHRpbWUgdGhhbiBMWlMuIERFRkxBVEUgDQogIGdpdmVzIGJpdCBiZXR0ZXIgY29tcHJlc3Np
b24gcmF0aW8gdGhhbiBMWlMuPC9GT05UPiA8QlI+PEJSPjxGT05UIA0KICBmYWNlPXNhbnMtc2Vy
aWYgc2l6ZT0yPkkgd2FudCB0byB1c2UgTFpTLiBJcyB0aGVyZSBhbnkgdGhpcmQgcGFydHkgbGli
cmFyeSANCiAgJm5ic3A7YXZhaWxhYmxlIGZvciBMWlMgY29tcHJlc3Npb24uICggd2l0aCBObyBJ
UFIgaXNzdWVzIGFuZCBmcmVlIG9mIGNvc3QgDQogIDotKSkpICk8L0ZPTlQ+IDxCUj48QlI+PEZP
TlQgZmFjZT1zYW5zLXNlcmlmIHNpemU9Mj5QbGVhc2UgY2xhcmlmeSB0aGlzLiANCiAgPEJSPjxC
Uj48QlI+VGhhbmtzIGFuZCBSZWdhcmRzPEJSPlJhbmppdGggUmVkZHkuIFY8QlI+RXh0bjogOTEz
NDxCUj5Mb2NhdGlvbiA6IA0KICBGNC0xMjI8L0ZPTlQ+IDxCUj48QlI+PEJSPjxGT05UIGZhY2U9
c2Fucy1zZXJpZiANCiAgc2l6ZT0yPjxCUj4qKioqKioqKioqKioqKioqKioqKioqKiAmbmJzcDtB
cmljZW50LVByaXZhdGUgJm5ic3A7IA0KICAqKioqKioqKioqKioqKioqKioqKioqKjwvRk9OVD4g
DQogIDxUQUJMRT4NCiAgICA8VEJPRFk+DQogICAgPFRSPg0KICAgICAgPFREIGJnQ29sb3I9I2Zm
ZmZmZj48Rk9OVCBjb2xvcj0jMDAwMDAwPjxQUkU+IkRJU0NMQUlNRVI6IFRoaXMgbWVzc2FnZSBp
cyBwcm9wcmlldGFyeSB0byBBcmljZW50IGFuZCBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1
c2Ugb2YgDQp0aGUgaW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzIGFkZHJlc3NlZC4gSXQgbWF5IGNv
bnRhaW4gcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gYW5kIHNob3VsZCBu
b3QgYmUgDQpjaXJjdWxhdGVkIG9yIHVzZWQgZm9yIGFueSBwdXJwb3NlIG90aGVyIHRoYW4gZm9y
IHdoYXQgaXQgaXMgaW50ZW5kZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgbWVzc2FnZSBp
biBlcnJvciwgDQpwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIGltbWVkaWF0ZWx5LiBJZiB5
b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJlIG5vdGlmaWVkIHRoYXQg
eW91IGFyZSBzdHJpY3RseQ0KcHJvaGliaXRlZCBmcm9tIHVzaW5nLCBjb3B5aW5nLCBhbHRlcmlu
Zywgb3IgZGlzY2xvc2luZyB0aGUgY29udGVudHMgb2YgdGhpcyBtZXNzYWdlLiBBcmljZW50IGFj
Y2VwdHMgbm8gcmVzcG9uc2liaWxpdHkgZm9yIA0KbG9zcyBvciBkYW1hZ2UgYXJpc2luZyBmcm9t
IHRoZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zbWl0dGVkIGJ5IHRoaXMgZW1haWwgaW5j
bHVkaW5nIGRhbWFnZSBmcm9tIHZpcnVzLiINCjwvUFJFPjwvRk9OVD48L1REPjwvVFI+PC9UQk9E
WT48L1RBQkxFPjwvQkxPQ0tRVU9URT48L0JPRFk+PC9IVE1MPg0K

------_=_NextPart_001_01C7D438.02373B04--


--===============1093388338==
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

--===============1093388338==--




From rohc-bounces@ietf.org Mon Aug 06 08:47:28 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1II1za-0004mH-A2; Mon, 06 Aug 2007 08:47:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1II1zZ-0004lq-2d
	for rohc@ietf.org; Mon, 06 Aug 2007 08:47:25 -0400
Received: from rvil-eframer.radvision.com ([80.74.106.104]
	helo=eframer.radvision.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1II1zX-0007kO-7I
	for rohc@ietf.org; Mon, 06 Aug 2007 08:47:24 -0400
Received: (from root@localhost)
	by eframer.radvision.com (8.13.4/8.12.9) id l76CqRH0020374
	for rohc@ietf.org; Mon, 6 Aug 2007 15:52:27 +0300
Received: from rvil-mail1.RADVISION.com (rvil-mail1.radvision.com
	[172.20.2.100])
	by eframer.radvision.com (8.13.4/8.12.9) with ESMTP id l76CqRY5020368
	for <rohc@ietf.org>; Mon, 6 Aug 2007 15:52:27 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Aug 2007 15:47:20 +0300
Message-ID: <7E27141E2F9038419E1FA26127E67EC43C3BDA@rvil-mail1.RADVISION.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-rohc-sigcomp-sip-07, Chapter 9
Thread-Index: AcfYDcTrcXshgBAbQYKz+WaAADgPlQAC4t7wAAOIunA=
From: "Dikla Dror" <Dikla@radvision.com>
To: <rohc@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f560cc438c8be83d0aa5c816c29b481c
Subject: [rohc] draft-ietf-rohc-sigcomp-sip-07, Chapter 9
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="===============0876364677=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0876364677==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D827.EDDCFE8F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7D827.EDDCFE8F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

Hi,=20

I have a question/comment, concerning draft-ietf-rohc-sigcomp-sip-07,
chapter 9.=20

According to this chapter, I might encounter imbalanced compartments at
2 different communicating endpoints in the following scenario:

=20

This scenario includes 2 endpoints (A, B), communicating over TCP.

=20

                                                A
B

                                                |              (1)
INVITE                          |

          Create Compartment (A1)
|--------------------------------------------------------->| Create
Compartment (B1)

                                                |
|

                                                |
(2) 200 OK               |

                                                |
<----------------------------------| Use Compartment (B1)

                                                |
|

                                                |              (3)
INVITE                          |

         Create Compartment (A2)
|<---------------------------------------------------------| Use
Compartment (B1)

                                                |
|

                                                |
|

                                                | (2) 200 OK (Finally
received)                 |

                                                |<--------------------
|

                                                            And so on...

           =20

As you can see endpoint A is sending an INVITE (1) toward B, specifying
its local urn (A's urn). However A doesn't know yet B's urn, thus it
creates a local compartment (A1), related to the INVITE outgoing
connection.=20

Now B:

-          Responds the first INVITE with 200 OK (2), related to
compartment (B1)

-          Sends an outgoing INVITE (3) to A, related to compartment
(B1). This (3) INVITE includes B's urn.=20

=20

However, upon receiving (3) INVITE (before the (2) 200 OK) endpoint A is
not aware of the relation between B's urn and the first INVITE
compartment (A1). Thus, A will maintain 2 different compartments - (A1)
and (A2) for these 2 sessions while B will maintain only one compartment
(B1). This will lead to inconsistency within the SigComp mechanism.

=20

 How can I solve this asymmetry according to the draft?=20

=20

Thanks,

Dikla. =20


------_=_NextPart_001_01C7D827.EDDCFE8F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<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
	{font-family:Arial;
	color:windowtext;}
span.emailstyle18
	{font-family:Arial;
	color:navy;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@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 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have a question/comment, concerning
draft-ietf-rohc-sigcomp-sip-07, chapter 9. </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>According to this chapter, I might encounter =
imbalanced compartments
at 2 different communicating endpoints in the following =
scenario:</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This scenario includes 2 endpoints (A, B), =
communicating
over TCP.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</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;=
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
B</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;
(1)&nbsp;&nbsp;&nbsp;&nbsp;
INVITE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
|</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;Create Compartment (A1)
|---------------------------------------------------------&gt;| Create
Compartment (B1)</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp; (2) 200
OK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;----------------------------------| Use Compartment =
(B1)</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;=
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;
(3)&nbsp;&nbsp;&nbsp;&nbsp;
INVITE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
|</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;Create
Compartment (A2)&nbsp;
|&lt;---------------------------------------------------------| Use =
Compartment
(B1)</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| (2) 200 OK (Finally
received)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&lt;--------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
&nbsp;|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
And so on&#8230;</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;=
&nbsp;&nbsp;
</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As you can see endpoint A is sending an INVITE (1) =
toward B,
specifying its local urn (A&#8217;s urn). However A doesn&#8217;t know =
yet
B&#8217;s urn, thus it creates a local compartment (A1), related to the =
INVITE
outgoing connection. </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Now B:</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=
;
Responds the first INVITE with 200 OK (2), related to compartment =
(B1)</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=
;
Sends an outgoing INVITE (3) to A, related to compartment (B1). This (3) =
INVITE
includes B&#8217;s urn. </span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>However, upon receiving (3) INVITE (before the (2) =
200 OK)
endpoint A is not aware of the relation between B&#8217;s urn and the =
first
INVITE compartment (A1). Thus<font color=3Dnavy><span =
style=3D'color:navy'>,</span></font>
A will maintain 2 different compartments - (A1) and (A2) for these 2 =
sessions
while B will maintain only one compartment (B1). This will lead to
inconsistency within the SigComp mechanism.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;How can I solve this asymmetry according to the =
draft?
</span></font></p>

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C7D827.EDDCFE8F--


--===============0876364677==
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

--===============0876364677==--




From rohc-bounces@ietf.org Fri Aug 10 08:31:54 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJTd3-00074o-8n; Fri, 10 Aug 2007 08:30:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJECE-0002FR-JI
	for rohc@ietf.org; Thu, 09 Aug 2007 16:01:27 -0400
Received: from smtp2-cal.spirentcom.com ([70.137.112.7])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJECE-0006db-62
	for rohc@ietf.org; Thu, 09 Aug 2007 16:01:26 -0400
Received: from spccalexcbe01.AD.SPIRENTCOM.COM ([10.1.1.12]) by
	smtp2-cal.SPIRENTCOM.COM with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 9 Aug 2007 13:01:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 9 Aug 2007 13:01:23 -0700
Message-ID: <F765CD113DF1404886CDB6F298D9AC760128C853@spccalexcbe01.AD.SPIRENTCOM.COM>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: LZBS Algorithm
Thread-Index: AcfawA9uKBhZ5Bx/TlmfksOALEqRmw==
From: "Cornetti, Richard" <Richard.Cornetti@spirent.com>
To: <rohc@ietf.org>
X-OriginalArrivalTime: 09 Aug 2007 20:01:24.0510 (UTC)
	FILETIME=[104853E0:01C7DAC0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
X-Mailman-Approved-At: Fri, 10 Aug 2007 08:30:07 -0400
Subject: [rohc] LZBS Algorithm
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

My name is Richard Cornetti and I am a product manager for Spirent
Communications, my company makes data communications test equipment.

I am working on a state machine based, protocol functional tester. Our
focus is on IMS. Currently I am trying to find the LZBS algorithm, we
plan to implement it for SIP compression. My problem is that I can only
find very few references to LZBS and none of them present the algorithm.

Can someone point me in the right direction or, even better, provide the =
algorithm?

Thanks,
Rick
=A0
Richard Cornetti
PAB Product Marketing
Spirent Communications
900 Main Campus Drive
Suite 201
Raleigh, NC 27606
(O) 919-829-6332
(M) 919-744-1402


<DIV><FONT size=3D"1">

E-mail confidentiality.
--------------------------------
This e-mail contains confidential and / or privileged information belongi=
ng to Spirent Communications plc, its affiliates and / or subsidiaries. I=
f you are not the intended recipient, you are hereby notified that any di=
sclosure, copying, distribution and / or the taking of any action based u=
pon reliance on the contents of this transmission is strictly forbidden. =
If you have received this message in error please notify the sender by re=
turn e-mail and delete it from your system. If you require assistance, pl=
ease contact our IT department at helpdesk@spirent.com.

Spirent Communications plc,
Spirent House, Crawley Business Quarter, Fleming Way, Crawley, West Susse=
x, RH10 9QL, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Spirent House, Crawley Business Quarter, Fleming Way, Crawl=
ey, West Sussex, RH10 9QL, United Kingdom=20

Or if within the US,

Spirent Communications,
26750 Agoura Road, Calabasas, CA, 91302, USA.
Tel No. 1-818-676- 2300=20

</FONT></DIV>

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



From rohc-bounces@ietf.org Fri Aug 10 08:31:59 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJTd3-00072w-0T; Fri, 10 Aug 2007 08:30:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJCaO-0000rc-IA
	for rohc@ietf.org; Thu, 09 Aug 2007 14:18:17 -0400
Received: from mail153.messagelabs.com ([216.82.253.51])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IJCaK-0002j3-Sm
	for rohc@ietf.org; Thu, 09 Aug 2007 14:18:16 -0400
X-VirusChecked: Checked
X-Env-Sender: achari.kakinada@motorola.com
X-Msg-Ref: server-7.tower-153.messagelabs.com!1186683491!5468939!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 15013 invoked from network); 9 Aug 2007 18:18:11 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-7.tower-153.messagelabs.com with SMTP;
	9 Aug 2007 18:18:11 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l79IIBOv003270
	for <rohc@ietf.org>; Thu, 9 Aug 2007 11:18:11 -0700 (MST)
Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142])
	by il06exr04.mot.com (8.13.1/Vontu) with SMTP id l79IIA1m022067
	for <rohc@ietf.org>; Thu, 9 Aug 2007 13:18:10 -0500 (CDT)
Received: from de01exm63.ds.mot.com (de01exm63.am.mot.com [10.176.8.108])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l79II9Wb022058
	for <rohc@ietf.org>; Thu, 9 Aug 2007 13:18:10 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 9 Aug 2007 14:18:09 -0400
Message-ID: <5AE7B4EFBF6A994C91FAC5A6C31C33E003162D14@de01exm63.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ROHC parser ?
thread-index: AcfasaOMNvFIt+F5TNaakNnwhM93Sw==
From: "Kakinada Umamaheswar-W00231" <achari.kakinada@motorola.com>
To: <rohc@ietf.org>
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
X-Mailman-Approved-At: Fri, 10 Aug 2007 08:30:07 -0400
Subject: [rohc] ROHC parser ?
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="===============0907144530=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0907144530==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DAB1.A3EAF81A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DAB1.A3EAF81A
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi,
  Is there a parser available for ROHC in Wireshark / Ethereal. I
appreciate any info in this regard.
=20
Thanks and regards=20
=20
Achari
=20
=20

------_=_NextPart_001_01C7DAB1.A3EAF81A
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D625111618-09082007>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D625111618-09082007>&nbsp; =
Is there a=20
parser available for ROHC in Wireshark / Ethereal. I appreciate any info =
in this=20
regard.</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D625111618-09082007>Thanks and r</SPAN>egards =
</FONT></FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Achari</FONT></DIV>
<DIV align=3Dleft>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C7DAB1.A3EAF81A--


--===============0907144530==
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

--===============0907144530==--




From rohc-bounces@ietf.org Fri Aug 10 08:48:05 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJTsj-0006XI-Ln; Fri, 10 Aug 2007 08:46:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJTsi-0006WV-89
	for rohc@ietf.org; Fri, 10 Aug 2007 08:46:20 -0400
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJTsh-00021d-NY
	for rohc@ietf.org; Fri, 10 Aug 2007 08:46:20 -0400
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.13.1/8.13.1) with ESMTP id l7ACkFZp029615;
	Fri, 10 Aug 2007 13:46:15 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [rohc] ROHC parser ?
Date: Fri, 10 Aug 2007 13:46:15 +0100
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C5011B8824@rsys005a.comm.ad.roke.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] ROHC parser ?
Thread-Index: AcfasaOMNvFIt+F5TNaakNnwhM93SwAmgsFA
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "Kakinada Umamaheswar-W00231" <achari.kakinada@motorola.com>,
	<rohc@ietf.org>
X-MailScanner-roke-co-uk: Found to be clean
X-MailScanner-roke-co-uk-SpamCheck: 
X-MailScanner-From: robert.finking@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: 
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="===============1967004939=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1967004939==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DB4C.70AC8B00"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DB4C.70AC8B00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The simple answer is "no", but to clarify, what are you asking exactly?
ROHC isn't a protocol!  However it possible to write a tool to
auto-generate wire shark parsers for the compressed protocol forms
defined in individual ROHC profiles,  based on the ROHC-FN definition.
To my knowledge, no one has attempted such a feat, though a couple of
parsers for ROHC-FN do exist.
=20
What exactly are you asking?
=20
Raffles

	-----Original Message-----
	From: Kakinada Umamaheswar-W00231
[mailto:achari.kakinada@motorola.com]=20
	Sent: Thursday, August 09, 2007 7:18 PM
	To: rohc@ietf.org
	Subject: [rohc] ROHC parser ?
=09
=09
	Hi,
	  Is there a parser available for ROHC in Wireshark / Ethereal.
I appreciate any info in this regard.
	=20
	Thanks and regards=20
	=20
	Achari
	=20
	=20


------_=_NextPart_001_01C7DB4C.70AC8B00
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1595" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D146504012-10082007><FONT face=3DArial color=3D#008080 =
size=3D2>The=20
simple answer is "no",&nbsp;but to clarify, what are you asking =
exactly?&nbsp;=20
ROHC isn't a protocol!&nbsp; However it possible to write a tool to=20
auto-generate wire shark&nbsp;parsers for the compressed protocol forms =
defined=20
in individual ROHC profiles,&nbsp; based on the ROHC-FN =
definition.&nbsp; To my=20
knowledge, no one has attempted such a feat, though a couple of parsers =
for=20
ROHC-FN do exist.</FONT></SPAN></DIV>
<DIV><SPAN class=3D146504012-10082007><FONT face=3DArial color=3D#008080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D146504012-10082007><FONT face=3DArial color=3D#008080 =
size=3D2>What=20
exactly are you asking?</FONT></SPAN></DIV>
<DIV><SPAN class=3D146504012-10082007><FONT face=3DArial color=3D#008080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D146504012-10082007><FONT face=3DArial color=3D#008080 =

size=3D2>Raffles</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008080 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Kakinada=20
  Umamaheswar-W00231 [mailto:achari.kakinada@motorola.com] =
<BR><B>Sent:</B>=20
  Thursday, August 09, 2007 7:18 PM<BR><B>To:</B>=20
  rohc@ietf.org<BR><B>Subject:</B> [rohc] ROHC parser =
?<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D625111618-09082007>Hi,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D625111618-09082007>&nbsp; Is there a=20
  parser available for ROHC in Wireshark / Ethereal. I appreciate any =
info in=20
  this regard.</SPAN></FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV align=3Dleft><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D625111618-09082007>Thanks and r</SPAN>egards =
</FONT></FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2>Achari</FONT></DIV>
  <DIV align=3Dleft>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7DB4C.70AC8B00--


--===============1967004939==
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

--===============1967004939==--




From rohc-bounces@ietf.org Fri Aug 10 09:31:36 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJUYq-0002sp-0S; Fri, 10 Aug 2007 09:29:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJUYp-0002sk-HO
	for rohc@ietf.org; Fri, 10 Aug 2007 09:29:51 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJUYo-0005WX-7F
	for rohc@ietf.org; Fri, 10 Aug 2007 09:29:51 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id AC6789018A
	for <rohc@ietf.org>; Fri, 10 Aug 2007 09:29:46 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 23962-18 for <rohc@ietf.org>;
	Fri, 10 Aug 2007 09:29:43 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <rohc@ietf.org>; Fri, 10 Aug 2007 09:29:43 -0400 (EDT)
Received: from exchindia3.starentnetworks.com ([10.6.7.5]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 10 Aug 2007 09:30:10 -0400
Received: from 10.6.7.210 ([10.6.7.210]) by exchindia3.starentnetworks.com
	([10.6.7.5]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 10 Aug 2007 13:29:29 +0000
Received: from biplab-desktop by 10.6.7.5; 10 Aug 2007 18:59:36 +0530
Subject: Re: [rohc] ROHC parser ?
From: Biplab Sarkar <bsarkar@starentnetworks.com>
To: Kakinada Umamaheswar-W00231 <achari.kakinada@motorola.com>
In-Reply-To: <5AE7B4EFBF6A994C91FAC5A6C31C33E003162D14@de01exm63.ds.mot.com>
References: <5AE7B4EFBF6A994C91FAC5A6C31C33E003162D14@de01exm63.ds.mot.com>
Organization: Starent Networks
Date: Fri, 10 Aug 2007 18:59:36 +0530
Message-Id: <1186752576.10296.72.camel@biplab-desktop.bng.ind.starentnetworks.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
X-OriginalArrivalTime: 10 Aug 2007 13:30:10.0335 (UTC)
	FILETIME=[92FF3AF0:01C7DB52]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bsarkar@starentnetworks.com
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="===============1265317872=="
Errors-To: rohc-bounces@ietf.org


--===============1265317872==
Content-Type: multipart/alternative; boundary="=-ZyRA+7d03iYuW8UJZtLy"


--=-ZyRA+7d03iYuW8UJZtLy
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Achari,

One can come up with a state based parser for ROHC. But I haven't seen
it "freely" available. If  there is some support from the external
protocols telling that the packets are from a ROHC channel then without
any state machine too one can classify most of the packets. There are
some packets which can't be distinguished without any state machine.

Thanks
Biplab


On Thu, 2007-08-09 at 14:18 -0400, Kakinada Umamaheswar-W00231 wrote:
> Hi,
>   Is there a parser available for ROHC in Wireshark / Ethereal. I
> appreciate any info in this regard.
>  
> Thanks and regards 
>  
> Achari
>  
>  
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

--=-ZyRA+7d03iYuW8UJZtLy
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.14.1">
</HEAD>
<BODY>
Achari,<BR>
<BR>
One can come up with a state based parser for ROHC. But I haven't seen it &quot;freely&quot; available. If&nbsp; there is some support from the external protocols telling that the packets are from a ROHC channel then without any state machine too one can classify most of the packets. There are some packets which can't be distinguished without any state machine.<BR>
<BR>
Thanks<BR>
Biplab<BR>
<BR>
<BR>
On Thu, 2007-08-09 at 14:18 -0400, Kakinada Umamaheswar-W00231 wrote:
<BLOCKQUOTE TYPE=CITE>
    <FONT SIZE="2"><FONT COLOR="#000000">Hi,</FONT></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <FONT SIZE="2"><FONT COLOR="#000000">&nbsp; Is there a parser available for ROHC in Wireshark / Ethereal. I appreciate any info in this regard.</FONT></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <FONT COLOR="#000000">&nbsp;</FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <FONT SIZE="2"><FONT COLOR="#000000">Thanks and regards </FONT></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <FONT COLOR="#000000">&nbsp;</FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <FONT SIZE="2"><FONT COLOR="#000000">Achari</FONT></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <FONT COLOR="#000000">&nbsp;</FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <FONT COLOR="#000000">&nbsp;</FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">Rohc mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:Rohc@ietf.org">Rohc@ietf.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://www1.ietf.org/mailman/listinfo/rohc">https://www1.ietf.org/mailman/listinfo/rohc</A></FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>

--=-ZyRA+7d03iYuW8UJZtLy--


--===============1265317872==
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

--===============1265317872==--




From rohc-bounces@ietf.org Mon Aug 13 11:39:59 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKbzi-0002U7-As; Mon, 13 Aug 2007 11:38:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKbzh-0002Tz-4c
	for rohc@ietf.org; Mon, 13 Aug 2007 11:38:13 -0400
Received: from mms2.broadcom.com ([216.31.210.18])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKbzf-0000JI-Rb
	for rohc@ietf.org; Mon, 13 Aug 2007 11:38:13 -0400
Received: from [10.10.64.154] by mms2.broadcom.com with ESMTP (Broadcom
	SMTP Relay (Email Firewall v6.3.1)); Mon, 13 Aug 2007 08:38:04 -0700
X-Server-Uuid: A6C4E0AE-A7F0-449F-BAE7-7FA0D737AC76
Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id
	8CF052AF; Mon, 13 Aug 2007 08:38:04 -0700 (PDT)
Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by
	mail-irva-10.broadcom.com (Postfix) with ESMTP id 78DCB2AE; Mon, 13 Aug
	2007 08:38:04 -0700 (PDT)
Received: from mail-irva-12.broadcom.com (mail-irva-12.broadcom.com
	[10.10.64.146]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP
	id FOF68127; Mon, 13 Aug 2007 08:37:57 -0700 (PDT)
Received: from NT-IRVA-0752.brcm.ad.broadcom.com (
	nt-irva-0752.brcm.ad.broadcom.com [10.8.194.67]) by
	mail-irva-12.broadcom.com (Postfix) with ESMTP id BF17669CA7; Mon, 13
	Aug 2007 08:37:56 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Aug 2007 08:37:54 -0700
Message-ID: <2E073B3ABB3F664DBA1D1C4D5FB47EF402EE6E46@NT-IRVA-0752.brcm.ad.broadcom.com>
In-Reply-To: <E1IJWuP-0001kv-7e@megatron.ietf.org>
Thread-Topic: A mode bits, ROHC
Thread-Index: AcfbZ6HJDnfcV0lSTkidoVIcJpIjiQCV8now
References: <E1IJWuP-0001kv-7e@megatron.ietf.org>
From: "Simon Kamenkovich" <kamens@broadcom.com>
To: rohc@ietf.org
X-WSS-ID: 6ADEA5563E87114588-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Chow-Sit Tsang-Ping <chowsit@broadcom.com>, lars-erik.jonsson@ericsson.com
Subject: [rohc] A mode bits, ROHC
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

 Dear all

In section 3.3 RFC 4815 mentions that IR and IR-DYN contains mode bits,
But where exactly, it is not specied in the packets format???

Thanks in advance
Simon
Broadcom


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



From rohc-bounces@ietf.org Tue Aug 14 01:17:57 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKolI-0006yB-2n; Tue, 14 Aug 2007 01:16:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKolG-0006y4-D5
	for rohc@ietf.org; Tue, 14 Aug 2007 01:16:10 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IKolF-00060T-LG
	for rohc@ietf.org; Tue, 14 Aug 2007 01:16:10 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id C77C79006A;
	Tue, 14 Aug 2007 01:16:03 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 20054-06; Tue, 14 Aug 2007 01:16:03 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 14 Aug 2007 01:16:03 -0400 (EDT)
Received: from exchindia3.starentnetworks.com ([10.6.7.5]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 14 Aug 2007 01:16:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from 10.6.7.210 ([10.6.7.210]) by exchindia3.starentnetworks.com
	([10.6.7.5]) with Microsoft Exchange Server HTTP-DAV ;
	Tue, 14 Aug 2007 05:15:50 +0000
MIME-Version: 1.0
Received: from biplab-desktop by 10.6.7.5; 14 Aug 2007 10:45:59 +0530
Content-class: urn:content-classes:message
Subject: Re: [rohc] A mode bits, ROHC
Date: Tue, 14 Aug 2007 10:45:59 +0530
Message-ID: <1187068559.6323.3.camel@biplab-desktop>
In-Reply-To: <2E073B3ABB3F664DBA1D1C4D5FB47EF402EE6E46@NT-IRVA-0752.brcm.ad.broadcom.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] A mode bits, ROHC
Thread-Index: AcfeMi30SF0Zb8wWSY+SlZ+SFrcIrA==
References: <E1IJWuP-0001kv-7e@megatron.ietf.org>
	<2E073B3ABB3F664DBA1D1C4D5FB47EF402EE6E46@NT-IRVA-0752.brcm.ad.broadcom.com>
From: "Sarkar, Biplab" <bsarkar@starentnetworks.com>
To: "Simon Kamenkovich" <kamens@broadcom.com>
X-OriginalArrivalTime: 14 Aug 2007 05:16:31.0788 (UTC)
	FILETIME=[469E9EC0:01C7DE32]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: Chow-Sit Tsang-Ping <chowsit@broadcom.com>, rohc@ietf.org,
	lars-erik.jonsson@ericsson.com
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "Sarkar, Biplab" <bsarkar@starentnetworks.com>
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="===============1507881788=="
Errors-To: rohc-bounces@ietf.org


--===============1507881788==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-3OU4jgyXB84U4BHN48TZ"
Content-class: urn:content-classes:message


--=-3OU4jgyXB84U4BHN48TZ
Content-Type: multipart/alternative; boundary="=-gB6ut2gKHrJ6J9wPvW68"


--=-gB6ut2gKHrJ6J9wPvW68
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I believe you are referring to the Mode bit in the RTP's dynamic part.
RFC3095[5.7.7.6]

Thanks
Biplab

On Mon, 2007-08-13 at 08:37 -0700, Simon Kamenkovich wrote:

> Dear all
>=20
> In section 3.3 RFC 4815 mentions that IR and IR-DYN contains mode bits,
> But where exactly, it is not specied in the packets format???
>=20
> Thanks in advance
> Simon
> Broadcom
>=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

--=-gB6ut2gKHrJ6J9wPvW68
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/3.14.1">
</HEAD>
<BODY>
I believe you are referring to the Mode bit in the RTP's dynamic part. RFC3=
095[5.7.7.6]<BR>
<BR>
Thanks<BR>
Biplab<BR>
<BR>
On Mon, 2007-08-13 at 08:37 -0700, Simon Kamenkovich wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE>
<FONT COLOR=3D"#000000">Dear all</FONT>

<FONT COLOR=3D"#000000">In section 3.3 RFC 4815 mentions that IR and IR-DYN=
 contains mode bits,</FONT>
<FONT COLOR=3D"#000000">But where exactly, it is not specied in the packets=
 format???</FONT>

<FONT COLOR=3D"#000000">Thanks in advance</FONT>
<FONT COLOR=3D"#000000">Simon</FONT>
<FONT COLOR=3D"#000000">Broadcom</FONT>


<FONT COLOR=3D"#000000">_______________________________________________</FO=
NT>
<FONT COLOR=3D"#000000">Rohc mailing list</FONT>
<FONT COLOR=3D"#000000"><A HREF=3D"mailto:Rohc@ietf.org">Rohc@ietf.org</A><=
/FONT>
<FONT COLOR=3D"#000000"><A HREF=3D"https://www1.ietf.org/mailman/listinfo/r=
ohc">https://www1.ietf.org/mailman/listinfo/rohc</A></FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>

--=-gB6ut2gKHrJ6J9wPvW68--

--=-3OU4jgyXB84U4BHN48TZ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGwTqP3rQBTW1UPu4RAuUUAKC4Jr6ojAJKJuMcuf1OALvy8zgEIgCeP22i
XOazX6MnUuMyHPHN7YYicXw=
=pXOj
-----END PGP SIGNATURE-----

--=-3OU4jgyXB84U4BHN48TZ--


--===============1507881788==
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

--===============1507881788==--




From rohc-bounces@ietf.org Tue Aug 14 18:26:47 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL4os-00041i-1a; Tue, 14 Aug 2007 18:24:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL4op-00041U-UC; Tue, 14 Aug 2007 18:24:55 -0400
Received: from mclniron02-ext.bah.com ([156.80.1.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IL4oo-0007kB-OG; Tue, 14 Aug 2007 18:24:55 -0400
x-SBRS: None
X-REMOTE-IP: 156.80.7.153
X-IronPort-AV: E=Sophos;i="4.19,261,1183348800"; d="scan'208";a="235616474"
Received: from mclnexbh03.resource.ds.bah.com ([156.80.7.153])
	by mclniron02-int.bah.com with ESMTP; 14 Aug 2007 18:24:52 -0400
Received: from MCLNEXVS06.resource.ds.bah.com ([156.80.7.122]) by
	mclnexbh03.resource.ds.bah.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 14 Aug 2007 18:24:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Comments on ROHC-over-IPsec
Date: Tue, 14 Aug 2007 18:24:25 -0400
Message-ID: <359258A3D7EA4648BF03285FC2E4379102119BBB@MCLNEXVS06.resource.ds.bah.com>
In-Reply-To: <B356D8F434D20B40A8CEDAEC305A1F2404600677@esebe105.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Comments on ROHC-over-IPsec
Thread-Index: AcfNSJFdU0ZqAsmDT9GE56tmDuf0mgRWXF0w
References: <B356D8F434D20B40A8CEDAEC305A1F2404600677@esebe105.NOE.Nokia.com>
From: "Pezeshki, Jonah" <pezeshki_jonah@bah.com>
To: <Pasi.Eronen@nokia.com>,
	<ipsec@ietf.org>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 14 Aug 2007 22:24:52.0319 (UTC)
	FILETIME=[EF007EF0:01C7DEC1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: 
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

Pasi,

Thank you for providing comments to our pending Internet Drafts
(draft-ietf-rohc-hcoipsec and
draft-ertekin-rohc-ipsec-extensions-hcoipsec).  Please find our response
to your comments below (comments inline).

Jonah Pezeshki
Consultant
Booz | Allen | Hamilton
(703) 984-0810

-----

Some comments about draft-ietf-rohc-hcoipsec and
draft-ertekin-rohc-ipsec-extensions-hcoipsec:

1) Overall comment: I'd suggest merging the contents of
draft-ertekin-rohc-ipsec-extensions-hcoipsec into
draft-ietf-rohc-hcoipsec. IMHO this would make them easier to
read: currently there's plenty of copy-pasted text, and
draft-ertekin-... has less than 3 pages of original content.

>>>The intent of "draft-ietf-rohc-hcoipsec" is to provide a framework
and guide for RoHCoIPsec implementers, while
"draft-ertekin-rohc-ipsec-extensions-hcoipsec" is intended as a proposed
standard for the actual extensions to IPsec.  As such, we want to try to
maintain two separate drafts for these different purposes.  However, to
address your comment, we have edited both drafts to limit the redundant
information.  We will resubmit both updated drafts shortly.=20

2) It looks like one very important security consideration isn't
described in the documents yet.

When using normal IPsec (without ROHC) with integrity protection,
packets that "come out" from an SA are always packets that were "sent
in" (unless the key is compromised, some hard cryptographic problem is
broken, or the attacker guesses a correct MAC value).

I've understood that ROHC being "robust" means that it deals "well
enough" with random errors (packets loss, corruption, reordering).
But when combined with IPsec, we need to consider non-random,
intentionally introduced errors as well.

In the current draft, IPsec integrity protection is applied to
compressed packets. The crucial question is thus whether an attacker, by
introducing non-random reordering/packet loss, cause packets to "come
out" that weren't sent in? (Clearly this wouldn't be possible if
integrity protection was applied to uncompressed packets, but that would
be more complex overall.)

I'm not sure what the answer is, but certainly the document needs at
least a convincing explanation about this issue (and the mechanisms ROHC
uses to mitigate random errors, like 8-bit CRC, are not necessarily
enough against intentional errors).

>>>Although traditional RoHC may be susceptible to intentional
reordering events, RoHCoIPsec will utilize the IPsec's sequence number
to enhance RoHC's tolerance to reordering events (intentional and/or
unintentional).  Although this was briefly touched upon in the version
of "draft-ertekin-rohc-ipsec-extensions-hcoipsec" that you commented on,
we have since edited this draft to more clearly define this mechanism
and describe its importance in defending against intended reordering
events.=20

3) It might also be useful to mention that header compression can reveal
information to traffic analysis (by changing packet lengths in certain
ways) that wouldn't be available without compression. For example, if
the original traffic consists of fixed-size packets, after ROHCoIPsec it
might be easier to count how many separate flows there are (and when new
flows start).

>>>We now mention this security concern in both Internet Drafts.
However, it should be noted that this security concern may allow an
attacker to use packet size information to selectively block CID update
messages (i.e. monitoring packet size within the black network, and
selectively blocking "long" packets).  If a RoHCoIPsec implementation
reuses CIDs, this type of attack may cause packets to be incorrectly
routed within the destination red network (i.e. a packet's CID value
being misinterpreted as a previously used value, since the destination
RoHC instance never received the update information).  To resolve this
issue, a new RoHC profile (draft-bormann-rohc-shutdown-profile-00) was
drafted by Carsten Bormann.  This profile (ROHC-DOWN) will ensure that a
CID value cannot be reused until the RoHC compressor receives
confirmation that the RoHC decompressor has successfully cleared the
value.  We have also added text to both drafts to indicate that this
profile must be used if a RoHCoIPsec implementation intends to reuse
CIDs.


4) I'm not sure if the description of combining RoHCoIPsec and IPcomp is
correct. It seems to assume that IPcomp touches only the payload but not
the IP header (in which case doing ROHC-IP-only after IPcomp could be
useful). However, according to RFC 3173, "In the case of an encapsulated
IP header (e.g., tunnel mode encapsulation in IPsec), the datagram
payload is defined to start immediately after the outer IP header;
accordingly, the inner IP header is considered part of the payload and
is compressed."

>>>Thank you for catching this oversight.  We have corrected the order
in which IPcomp is applied to packets within RoHCoIPsec.=20


5) "Furthermore, the RoHC FEEDBACK_FOR channel parameter is set
implicitly to the RoHC channel associated with the SA in the reverse
direction.  Because both of these RoHC channel parameters are set
implicitly, they are not stored in the SPD or SAD."

This pairing of SAs needs more discussion, as it's probably one of the
biggest changes to RFC 4301. When the SAs are created using IKE, the
FEEDBACK_FOR parameters is indeed set implicitly -- but clearly it still
needs to be stored somewhere (in the SAD).

Feedback also introduces another change to RFC 4301: the possibility
that IPsec implementation might have to originate packets. Normally
feedback would be piggy-backed on ordinary data packets, but if there is
no traffic in other direction, presumably a packet containing only
feedback might need to be sent. The document should discuss this issue,
and provide some guidance.

>>>We have modified "draft-ertekin-rohc-ipsec-extensions-hcoipsec" to
indicate that the FEEDBACK_FOR parameter is stored in the SAD.  In
addition, we now mention that, ROHC feedback should be used sparingly
(if at all), and that, when possible, RoHC feedback messages should be
piggybacked on traffic normally traversing the SA designated by
FEEDBACK_FOR.


6) The document should probably cite RFC 4224, and explicitly mention
that some ROHC profiles aren't compatible with reordering channels (such
as ROHCoIPsec).

>>>Our "draft-ietf-rohc-hcoipsec" draft now notes that RFC4224 is to be
used as a guide when implementing RoHCoIPsec over channels that support
packet reordering.

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



From rohc-bounces@ietf.org Tue Aug 14 18:27:34 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL4pn-0004KU-V7; Tue, 14 Aug 2007 18:25:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL4pm-0004Hw-LG; Tue, 14 Aug 2007 18:25:54 -0400
Received: from mclniron02-ext.bah.com ([156.80.1.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IL4pl-0007ku-GW; Tue, 14 Aug 2007 18:25:54 -0400
x-SBRS: None
X-REMOTE-IP: 156.80.7.151
X-IronPort-AV: E=Sophos;i="4.19,261,1183348800"; d="scan'208";a="235617021"
Received: from mclnexbh01.resource.ds.bah.com ([156.80.7.151])
	by mclniron02-int.bah.com with ESMTP; 14 Aug 2007 18:25:53 -0400
Received: from MCLNEXVS06.resource.ds.bah.com ([156.80.7.122]) by
	mclnexbh01.resource.ds.bah.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 14 Aug 2007 18:25:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Comments on ROHC IKEv2 extensions
Date: Tue, 14 Aug 2007 18:25:05 -0400
Message-ID: <359258A3D7EA4648BF03285FC2E4379102119BBD@MCLNEXVS06.resource.ds.bah.com>
In-Reply-To: <B356D8F434D20B40A8CEDAEC305A1F24046009AF@esebe105.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Comments on ROHC IKEv2 extensions
Thread-Index: AcfOFs3kZRwiZyuXQA6DjIR+1rxDNwQjTS2g
References: <B356D8F434D20B40A8CEDAEC305A1F24046009AF@esebe105.NOE.Nokia.com>
From: "Pezeshki, Jonah" <pezeshki_jonah@bah.com>
To: <Pasi.Eronen@nokia.com>,
	<ipsec@ietf.org>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 14 Aug 2007 22:25:53.0261 (UTC)
	FILETIME=[135381D0:01C7DEC2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: 
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

Pasi,

Thank you for providing comments to our pending Internet Draft
(draft-ietf-rohc-ikev2-extensions-hcoipsec-02).  Please find our
response to your comments below (comments inline).

Jonah Pezeshki
Consultant
Booz | Allen | Hamilton
(703) 984-0810

-----

Subject: [rohc] Comments on ROHC IKEv2 extensions

Comments on draft-ietf-rohc-ikev2-extensions-hcoipsec-02:

1) The document doesn't really describe how the negotiation works. For
example, can CREATE_CHILD_SA request contain multiple ROHC_SUPPORTED
payloads? Is the responder required to pick one of them exactly, or is
it allowed to adjust the parameters somehow? E.g. if initiator sends
MAX_CID of 100, is the responder allowed to lower this to 99? What about
the other fields? What you're supposed to do when you e.g. receive a
suboption you don't recognize?

-I have updated the drafts to more specifically define the nature of the
negotiation.  In answer to the posed questions: an exchange may only
contain a single ROHC_SUPPORTED payload (additional ROHC_SUPPORTED
payloads are ignored upon receipt); The responder may adjust the
parameters so that both the initiator and responder will support the
selected value (i.e., if the initiator proposed a MAX_CID value of 15,
and the Responder only supports a MAX_CID of 13, the selected MAX_CID
value will be 13); if the initiator proposed a profile that is not
supported by the responder, this profile will not be supported by the
created Child SA.

2) I'd recommend NOT repeating the generic definition of Notify payload;
the description doesn't 100% match RFC 4306, and it's redundant anyway.

In other words, replace the text by "The Notify Message Type for
ROHC_SUPPORTED is TBD-BY-IANA. The Protocol ID and SPI Size fields are
set to zero.  The RoHC configuration parameters are listed in the
notification data in the following format:"

-I have modified the text, and removed redundant text.  Instead, I
simply refer to RFC4306.

3) Why does the notification data include ROHC PARAMETERS LENGTH?
(the Notify payload already includes a length field, so this seems
redundant)

-Thank you for catching this oversight.  I have removed this field from
the ROHC_SUPPORTED Notify payload.

4) In section 2, is the intent to define a new suboption space, or reuse
the suboption space from RFC 3241? In the former case, IANA
considerations are needed; in latter case, the text should not repeat
the definitions, but just cite RFC 3241.

-I have adjusted this section to simply refer to the RoHC profiles, as
opposed to "suboptions", thus bringing it more inline with the RoHC
framework.  In addition, I refer to both RFC3095 and
draft-ietf-rohc-rfc3095bis-rohcv2-profiles-01 in this section, instead
of repeating text from other drafts.

5) Section 4 (IANA considerations): There are two kinds of IKEv2 notify
messages (error and status); this section should tell IANA which kind of
number to allocate (status is the right one here).

-The IANA Considerations section has been updated to indicate that our
Notify Message is a Status Type.

6) In bit diagrams, replace this
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 with
this
                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

-This has been corrected in our diagram.

7) In reference [ROHCPROF], the URL doesn't work.

-It turns out that this reference had expired.  We have since replaced
it with a different, more recent reference.

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



From rohc-bounces@ietf.org Wed Aug 15 04:20:47 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILE5l-0003l2-VI; Wed, 15 Aug 2007 04:19:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILE5k-0003ku-Ii
	for rohc@ietf.org; Wed, 15 Aug 2007 04:19:00 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILE5j-0002f4-OB
	for rohc@ietf.org; Wed, 15 Aug 2007 04:19:00 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C2F5A20812; Wed, 15 Aug 2007 10:18:58 +0200 (CEST)
X-AuditID: c1b4fb3c-b067fbb0000007e1-d3-46c2b6f2d951
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A419A20690; Wed, 15 Aug 2007 10:18:58 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Aug 2007 10:18:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Aug 2007 10:18:57 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F0459C2DD@esealmw105.eemea.ericsson.se>
In-Reply-To: <4678CE34.20200@effnet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: More comments on ROHCv2 profiles draft
Thread-Index: AcezBxmfBZO2K+RxQUKj5S6VA71u8Arbunzg
References: <A91F30A632473A47B40C18D2B107CA6F04041FEF@esealmw105.eemea.ericsson.se>
	<4678CE34.20200@effnet.com>
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: "Carl Knutsson" <carl.knutsson@effnet.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 15 Aug 2007 08:18:58.0085 (UTC)
	FILETIME=[ED88BD50:01C7DF14]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>
Subject: [rohc] RE: More comments on ROHCv2 profiles draft
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Calle,

sorry for the delayed reply. I agree to the cut&paste issue about the
CRC option, so that will go away.

Regarding the other issue, me and Ghyslain have discussed this and we=20
agree that the feedback parts of the draft lack some information and=20
can also use some re-structuring. So, we propose the following changes
to v2:

- The MSN field inside all feedback is renamed "Acknowledgment Number"
which makes it a lot easier to describe what to put in there and also=20
makes it easier to see that NACKs also contain ACK numbers.
Concequently,
the MSN-NOT-VALID option is now ACKNUMBER-NOT-VALID. We also add this to
terminology with the following text:
   Acknowledgment Number
      The Acknowledgment Number in ROHCv2 profiles is carried in all
      feedback elements and is used for identifying what packet is being
      acknowledged.  The value of this field is usually set to the MSN
      value of the latest successfully decompressed packet in the flow.

- Text in 6.9.1 is updated as follows:
   The Acknowledgment Number field of the feedback formats contains the
   least significant bits of the MSN (see Section 6.2.1) that
   corresponds to the reference header that is being acknowledged.  A
   reference header is a header that has been successfully CRC-8
   validated or CRC verified.  If there is no reference header
   available, the feedback MUST carry an ACKNUMBER-NOT-VALID option.

- The Ack Number field is just "LSBs" of the MSN and not "LSB encoded=20
MSN" (since we're only having one reference, these are actually=20
equivalent, but it makes it easier to understand that if we avoid=20
the word "LSB encoding" for the field in the feedback element

- We feel that since we have 14 bits of Ack number (MSN) inside=20
FEEDBACK-2 and no MSN is longer than 16 bits, the "MSN option" feedback
seems a bit silly. Is there really any case where two more bits would
make any sense (unless we want v2 to support interplanetary ROHC)?
So, we propose to remove this feedback option. The text in 3095 of why
more bits of SN would be needed in feedback really requires the=20
decompressor to know about how many packets are sent in each link RTT,
so we do not think this option is useful in any case.

I think the above changes will make it clear how to choose, encode,=20
decode and use the sequence number of feedback at both compressor and
decompressor.

Unless anyone objects, these changes go into the next revision of=20
the draft

/Kristofer

Carl Knutsson <mailto:carl.knutsson@effnet.com> wrote on den 20 juni
2007 08:50 :

> Hi Kristofer, Ghyslain,
>=20
> I found a small issue in the feedback section.
> copy-and-paste? I believe a more
> detailed description of the msn decompression in the feedback packet
> would improve the draft.
>=20
> Section 6.9.2.1:
> 	"carrying a REJECT option MUST also carry a CRC option."
>=20
> There are no CRC options in ROCHv2 and crc8 is always
> included in feedback-2 packets.
>=20
> In Section 6.9.1, it would be nice with a more detailed description
> how the compressor should decompress the msn in feedback packets.
> There are some more places in the draft that describes the msn in
> feedback, but it does not cover the details on how to
> decompress/compress the field other than that it is lsb-encoded.=20
>=20
> Best regards,
> Carl Knutsson

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



From rohc-bounces@ietf.org Thu Aug 16 07:12:39 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILdFd-000475-Pv; Thu, 16 Aug 2007 07:10:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILdFc-00046i-GK
	for rohc@ietf.org; Thu, 16 Aug 2007 07:10:52 -0400
Received: from rvil-eframer.radvision.com ([80.74.106.104]
	helo=eframer.radvision.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILdFZ-00038Y-1C
	for rohc@ietf.org; Thu, 16 Aug 2007 07:10:52 -0400
Received: (from root@localhost)
	by eframer.radvision.com (8.13.4/8.12.9) id l7GBF4id015628
	for rohc@ietf.org; Thu, 16 Aug 2007 14:15:04 +0300
Received: from rvil-mail1.RADVISION.com (rvil-mail1.radvision.com
	[172.20.2.100])
	by eframer.radvision.com (8.13.4/8.12.9) with ESMTP id l7GBF4T8015622
	for <rohc@ietf.org>; Thu, 16 Aug 2007 14:15:04 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 16 Aug 2007 14:09:37 +0300
Message-ID: <7E27141E2F9038419E1FA26127E67EC43C3BFB@rvil-mail1.RADVISION.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Query about draft-ietf-rohc-sigcomp-sip-07
Thread-Index: Acff9fp1vLcK5p8AQiWn6BnTY7iTLw==
From: "Dikla Dror" <Dikla@radvision.com>
To: <rohc@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4ec58ef3f343ebf5ac40a04538f9a6fc
Subject: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
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="===============1355724832=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1355724832==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DFF5.EED72790"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DFF5.EED72790
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I've sent a question concerning chapter 9 in
draft-ietf-rohc-sigcomp-sip-07 few weeks ago, but got no answer yet.=20

I would appreciate any feedback to the following issue (I've turned my
question into a simpler scenario):=20

=20

According to chapter 9, I might encounter imbalanced compartments at 2
different communicating endpoints in the following scenario:

=20

This scenario includes 2 endpoints (A, B), communicating over TCP.

=20

                                                A
B

                                                |              (1)
INVITE                          |

          Create Compartment (A1)
|--------------------------------------------------------->| Create
Compartment (B1)

                                                |
|

                                                |               (2) 200
OK                             |

=20
|<---------------------------------------------------------| Use
Compartment (B1)

                                                |
|

                                                |              (3)
INVITE                          |

          Create Compartment (A2)
|<---------------------------------------------------------| Use
Compartment (B1)

                                                |
|

                                                |
|

                                                            And so on...

           =20

As you can see endpoint A is sending an INVITE (1) toward B, specifying
its local urn (A's urn). However A doesn't know yet B's urn, thus it
creates a local compartment (A1), related to the INVITE outgoing
connection.=20

Now B:

-          Responds the first INVITE with 200 OK (2), related to
compartment (B1)

-          Sends an outgoing INVITE (3) to A, related to compartment
(B1). This (3) INVITE includes B's urn.=20

=20

However, upon receiving (3) INVITE, endpoint A is not aware of the
relation between B's urn and the first INVITE (1). Thus, A will maintain
2 different compartments - (A1) and (A2) for these 2 sessions while B
will maintain only one compartment (B1). This will lead to inconsistency
within the SigComp mechanism.

=20

 How can I solve this asymmetry according to the draft?=20

=20

Thanks,

Dikla.=20


------_=_NextPart_001_01C7DFF5.EED72790
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<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
	{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,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I&#8217;ve sent a question concerning chapter 9 in =
draft-ietf-rohc-sigcomp-sip-07
few weeks ago, but got no answer yet. </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would appreciate any feedback to the following =
issue (I&#8217;ve
turned my question into a simpler scenario): </span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>According to chapter 9, I might encounter imbalanced
compartments at 2 different communicating endpoints in the following =
scenario:</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This scenario includes 2 endpoints (A, B), =
communicating
over TCP.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</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;=
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
B</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;
(1)&nbsp;&nbsp;&nbsp;&nbsp;
INVITE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
|</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;Create Compartment (A1) =
|---------------------------------------------------------&gt;|
Create Compartment (B1)</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;(2)
200 =
OK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; |</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&lt;---------------------------------------------------------|
Use Compartment (B1)</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;=
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;
(3)&nbsp;&nbsp;&nbsp;&nbsp;
INVITE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
|</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; =
Create
Compartment (A2)
|&lt;---------------------------------------------------------| Use =
Compartment
(B1)</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|</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;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
And so on&#8230;</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;=
&nbsp;&nbsp;
</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As you can see endpoint A is sending an INVITE (1) =
toward B,
specifying its local urn (A&#8217;s urn). However A doesn&#8217;t know =
yet
B&#8217;s urn, thus it creates a local compartment (A1), related to the =
INVITE
outgoing connection. </span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Now B:</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=
;
Responds the first INVITE with 200 OK (2), related to compartment =
(B1)</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=
;
Sends an outgoing INVITE (3) to A, related to compartment (B1). This (3) =
INVITE
includes B&#8217;s urn. </span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>However, upon receiving (3) INVITE, endpoint A is not =
aware
of the relation between B&#8217;s urn and the first INVITE (1). =
Thus<font
color=3Dnavy><span style=3D'color:navy'>,</span></font> A will maintain =
2 different
compartments - (A1) and (A2) for these 2 sessions while B will maintain =
only
one compartment (B1). This will lead to inconsistency within the SigComp
mechanism.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;How can I solve this asymmetry according to the =
draft?
</span></font></p>

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C7DFF5.EED72790--


--===============1355724832==
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

--===============1355724832==--




From rohc-bounces@ietf.org Thu Aug 16 12:43:13 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILiPY-0005HW-Gf; Thu, 16 Aug 2007 12:41:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILiPX-0005HP-Cl
	for rohc@ietf.org; Thu, 16 Aug 2007 12:41:27 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILiPW-0004TG-AZ
	for rohc@ietf.org; Thu, 16 Aug 2007 12:41:27 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 4D77A9019E
	for <rohc@ietf.org>; Thu, 16 Aug 2007 12:41:19 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 14694-02 for <rohc@ietf.org>;
	Thu, 16 Aug 2007 12:41:18 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <rohc@ietf.org>; Thu, 16 Aug 2007 12:41:18 -0400 (EDT)
Received: from exchindia3.starentnetworks.com ([10.6.7.5]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 16 Aug 2007 12:41:48 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [rohc] A mode bits, ROHC
Date: Thu, 16 Aug 2007 22:11:03 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <69FADB84C90B1248A7DE59422771FA0C2F8CD5@exchindia3.starentnetworks.com>
In-Reply-To: <1187068559.6323.3.camel@biplab-desktop>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] A mode bits, ROHC
Thread-Index: AcfeMi30SF0Zb8wWSY+SlZ+SFrcIrAB8U/6Q
From: "Sarkar, Biplab" <bsarkar@starentnetworks.com>
To: <rohc@ietf.org>
X-OriginalArrivalTime: 16 Aug 2007 16:41:48.0273 (UTC)
	FILETIME=[56C7D610:01C7E024]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a9ffb6f997442a3b543bcdaf483b990
Cc: Simon Kamenkovich <kamens@broadcom.com>,
	Chow-Sit Tsang-Ping <chowsit@broadcom.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1779847368=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1779847368==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7E024.3C07544A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7E024.3C07544A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

L-E,

=20

There seems to be some ambiguity over the "mode" attribute for
Profile-0x0002. Since "mode" is not present in IR or IR-DYN pkts, the
statements made in RFC3095[5.6] needs some re-wording for
Profile-0x0002.=20

=20

Thanks

Biplab

=20

=20

-----Original Message-----
From: Sarkar, Biplab [mailto:bsarkar@starentnetworks.com]=20
Sent: Tuesday, August 14, 2007 10:46 AM
To: Simon Kamenkovich
Cc: Chow-Sit Tsang-Ping; rohc@ietf.org; lars-erik.jonsson@ericsson.com
Subject: Re: [rohc] A mode bits, ROHC

=20

I believe you are referring to the Mode bit in the RTP's dynamic part.
RFC3095[5.7.7.6]

Thanks
Biplab

On Mon, 2007-08-13 at 08:37 -0700, Simon Kamenkovich wrote:=20

=20
Dear all
=20
In section 3.3 RFC 4815 mentions that IR and IR-DYN contains mode bits,
But where exactly, it is not specied in the packets format???
=20
Thanks in advance
Simon
Broadcom
=20
=20
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc

------_=_NextPart_001_01C7E024.3C07544A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
 /* 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:blue;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{font-family:"Comic Sans MS";
	color:navy;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@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=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans =
MS";color:navy'>L-E,</span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans =
MS";color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans MS";color:navy'>There =
seems to
be some ambiguity over the &#8220;mode&#8221; attribute for =
Profile-0x0002.
Since &#8220;mode&#8221; is not present in IR or IR-DYN pkts, the =
statements
made in RFC3095[5.6] needs some re-wording for Profile-0x0002. =
</span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans =
MS";color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans =
MS";color:navy'>Thanks</span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans =
MS";color:navy'>Biplab</span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans =
MS";color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D1 color=3Dnavy face=3D"Comic Sans =
MS"><span
style=3D'font-size:9.0pt;font-family:"Comic Sans =
MS";color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Sarkar, Biplab
[mailto:bsarkar@starentnetworks.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, August 14, =
2007
10:46 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Simon Kamenkovich<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Chow-Sit Tsang-Ping;
rohc@ietf.org; lars-erik.jonsson@ericsson.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [rohc] A =
mode bits,
ROHC</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>I believe you are referring to the Mode bit =
in the
RTP's dynamic part. RFC3095[5.7.7.6]<br>
<br>
Thanks<br>
Biplab<br>
<br>
On Mon, 2007-08-13 at 08:37 -0700, Simon Kamenkovich wrote: =
</span></font></p>

<pre style=3D'margin-left:.5in'><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre =
style=3D'margin-left:
.5in'><font size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:black'>Dear all</span></font></pre><pre =
style=3D'margin-left:.5in'><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:black'>In section 3.3 RFC 4815 mentions =
that IR and IR-DYN contains mode bits,</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:black'>But where exactly, it is not =
specied in the packets format???</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre =
style=3D'margin-left:
.5in'><font size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
color:black'>Thanks in advance</span></font></pre><pre =
style=3D'margin-left:.5in'><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;color:black'>Simon</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:black'>Broadcom</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre =
style=3D'margin-left:
.5in'><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:black'>__________________________________=
_____________</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:black'>Rohc mailing =
list</span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:black'><a =
href=3D"mailto:Rohc@ietf.org">Rohc@ietf.org</a></span></font></pre><pre
style=3D'margin-left:.5in'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:black'><a
href=3D"https://www1.ietf.org/mailman/listinfo/rohc">https://www1.ietf.or=
g/mailman/listinfo/rohc</a></span></font></pre></div>

</body>

</html>

------_=_NextPart_001_01C7E024.3C07544A--


--===============1779847368==
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

--===============1779847368==--




From rohc-bounces@ietf.org Fri Aug 17 02:32:10 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILvLl-0001RC-K1; Fri, 17 Aug 2007 02:30:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILvLj-0001R7-PU
	for rohc@ietf.org; Fri, 17 Aug 2007 02:30:23 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILvLj-0004sJ-5W
	for rohc@ietf.org; Fri, 17 Aug 2007 02:30:23 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	CAC2C20C59; Fri, 17 Aug 2007 08:30:21 +0200 (CEST)
X-AuditID: c1b4fb3c-b1681bb0000007e1-e4-46c5407da333
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	AEFB920C28; Fri, 17 Aug 2007 08:30:21 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 08:30:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] A mode bits, ROHC
Date: Fri, 17 Aug 2007 08:30:19 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F0459CA83@esealmw105.eemea.ericsson.se>
In-Reply-To: <69FADB84C90B1248A7DE59422771FA0C2F8CD5@exchindia3.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] A mode bits, ROHC
Thread-Index: AcfeMi30SF0Zb8wWSY+SlZ+SFrcIrAB8U/6QABzna/A=
References: <1187068559.6323.3.camel@biplab-desktop>
	<69FADB84C90B1248A7DE59422771FA0C2F8CD5@exchindia3.starentnetworks.com>
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: "Sarkar, Biplab" <bsarkar@starentnetworks.com>,
	<rohc@ietf.org>
X-OriginalArrivalTime: 17 Aug 2007 06:30:21.0539 (UTC)
	FILETIME=[16323B30:01C7E098]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: Simon Kamenkovich <kamens@broadcom.com>,
	Chow-Sit Tsang-Ping <chowsit@broadcom.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi Biplab,

Clearly, the IR/IR-DYN packets for the non-RTP profiles in 3095 cannot
carry mode bits, so therefore these packet types cannot be used for
the parts of the transitions requiring mode bits. You can still switch
modes via the UOR-2-ext3 packet (see 5.11.3), so just use those instead.
Design-wise, it is not the most brilliant part of 3095, but I see no
need for any adjustments to existing text.

/Kristofer

Sarkar, Biplab <mailto:bsarkar@starentnetworks.com> wrote on den 16
augusti 2007 18:41 :

> L-E,
>=20
>=20
>=20
> There seems to be some ambiguity over the "mode" attribute
> for Profile-0x0002. Since "mode" is not present in IR or
> IR-DYN pkts, the statements made in RFC3095[5.6] needs some
> re-wording for Profile-0x0002.
>=20
>=20
>=20
> Thanks
>=20
> Biplab
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Sarkar, Biplab [mailto:bsarkar@starentnetworks.com]
> Sent: Tuesday, August 14, 2007 10:46 AM
> To: Simon Kamenkovich
> Cc: Chow-Sit Tsang-Ping; rohc@ietf.org; lars-erik.jonsson@ericsson.com
> Subject: Re: [rohc] A mode bits, ROHC
>=20
>=20
>=20
> I believe you are referring to the Mode bit in the RTP's
> dynamic part. RFC3095[5.7.7.6]
>=20
> Thanks
> Biplab
>=20
> On Mon, 2007-08-13 at 08:37 -0700, Simon Kamenkovich wrote:
>=20
>=20
> Dear all
>=20
> In section 3.3 RFC 4815 mentions that IR and IR-DYN contains
> mode bits,
> But where exactly, it is not specied in the packets format???
>=20
> Thanks in advance
> Simon
> Broadcom
>=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

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



From rohc-bounces@ietf.org Fri Aug 17 03:31:39 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILwHK-00034I-Ty; Fri, 17 Aug 2007 03:29:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILlvk-0004Ok-Uz
	for rohc@ietf.org; Thu, 16 Aug 2007 16:26:57 -0400
Received: from kuber.nabble.com ([216.139.236.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILlvj-0002Wy-Mj
	for rohc@ietf.org; Thu, 16 Aug 2007 16:26:56 -0400
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bounces@nabble.com>) id 1ILlvj-0001dt-Bt
	for rohc@ietf.org; Thu, 16 Aug 2007 13:26:55 -0700
Message-ID: <12188875.post@talk.nabble.com>
Date: Thu, 16 Aug 2007 13:26:55 -0700 (PDT)
From: daum <daum3998@yahoo.com>
To: rohc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: daum3998@yahoo.com
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-Mailman-Approved-At: Fri, 17 Aug 2007 03:29:53 -0400
Subject: [rohc] Q) RFC 3095 : ROHC channel identifier
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


Dear all,

Let me ask you a question.


An IP interface can have multiple ROHC channels, and a ROHC channel can have 
multiple Context Ids.

Each ROHC packet header has Context Id(s) field, but there is no ROHC 
channel identifier filed in a ROHC packet.

Q) How does a lower layer know what the ROHC channel identifier is?




Thank you.

-- 
View this message in context: http://www.nabble.com/Q%29-RFC-3095-%3A-ROHC-channel-identifier-tf4281925.html#a12188875
Sent from the IETF - Rohc mailing list archive at Nabble.com.


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



From rohc-bounces@ietf.org Fri Aug 17 03:31:39 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILwHL-00034R-2G; Fri, 17 Aug 2007 03:29:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILm22-0001mZ-U2
	for rohc@ietf.org; Thu, 16 Aug 2007 16:33:26 -0400
Received: from kuber.nabble.com ([216.139.236.158])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILm22-0003yc-Ks
	for rohc@ietf.org; Thu, 16 Aug 2007 16:33:26 -0400
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bounces@nabble.com>) id 1ILm22-0001qx-4V
	for rohc@ietf.org; Thu, 16 Aug 2007 13:33:26 -0700
Message-ID: <12188948.post@talk.nabble.com>
Date: Thu, 16 Aug 2007 13:33:26 -0700 (PDT)
From: daum <daum3998@yahoo.com>
To: rohc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: daum3998@yahoo.com
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Fri, 17 Aug 2007 03:29:53 -0400
Subject: [rohc] Q) ROHC channel identifier.
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


Dear all, 

Let me ask you a question. 


An IP interface can have multiple ROHC channels, and a ROHC channel can have 
multiple Context IDs. 

Each ROHC packet header has Context ID(s) field, but there is no ROHC 
channel identifier field in a ROHC packet. 

Q) How does a lower layer know what the ROHC channel identifier is for a
ROHC packet? 

- Daum


-- 
View this message in context: http://www.nabble.com/Q%29-ROHC-channel-identifier.-tf4281953.html#a12188948
Sent from the IETF - Rohc mailing list archive at Nabble.com.


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



From rohc-bounces@ietf.org Fri Aug 17 03:31:39 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILwHK-00034I-Ty; Fri, 17 Aug 2007 03:29:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILlvk-0004Ok-Uz
	for rohc@ietf.org; Thu, 16 Aug 2007 16:26:57 -0400
Received: from kuber.nabble.com ([216.139.236.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILlvj-0002Wy-Mj
	for rohc@ietf.org; Thu, 16 Aug 2007 16:26:56 -0400
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bounces@nabble.com>) id 1ILlvj-0001dt-Bt
	for rohc@ietf.org; Thu, 16 Aug 2007 13:26:55 -0700
Message-ID: <12188875.post@talk.nabble.com>
Date: Thu, 16 Aug 2007 13:26:55 -0700 (PDT)
From: daum <daum3998@yahoo.com>
To: rohc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: daum3998@yahoo.com
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-Mailman-Approved-At: Fri, 17 Aug 2007 03:29:53 -0400
Subject: [rohc] Q) RFC 3095 : ROHC channel identifier
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


Dear all,

Let me ask you a question.


An IP interface can have multiple ROHC channels, and a ROHC channel can have 
multiple Context Ids.

Each ROHC packet header has Context Id(s) field, but there is no ROHC 
channel identifier filed in a ROHC packet.

Q) How does a lower layer know what the ROHC channel identifier is?




Thank you.

-- 
View this message in context: http://www.nabble.com/Q%29-RFC-3095-%3A-ROHC-channel-identifier-tf4281925.html#a12188875
Sent from the IETF - Rohc mailing list archive at Nabble.com.


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



From rohc-bounces@ietf.org Fri Aug 17 03:31:39 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILwHL-00034R-2G; Fri, 17 Aug 2007 03:29:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILm22-0001mZ-U2
	for rohc@ietf.org; Thu, 16 Aug 2007 16:33:26 -0400
Received: from kuber.nabble.com ([216.139.236.158])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILm22-0003yc-Ks
	for rohc@ietf.org; Thu, 16 Aug 2007 16:33:26 -0400
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bounces@nabble.com>) id 1ILm22-0001qx-4V
	for rohc@ietf.org; Thu, 16 Aug 2007 13:33:26 -0700
Message-ID: <12188948.post@talk.nabble.com>
Date: Thu, 16 Aug 2007 13:33:26 -0700 (PDT)
From: daum <daum3998@yahoo.com>
To: rohc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: daum3998@yahoo.com
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Fri, 17 Aug 2007 03:29:53 -0400
Subject: [rohc] Q) ROHC channel identifier.
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


Dear all, 

Let me ask you a question. 


An IP interface can have multiple ROHC channels, and a ROHC channel can have 
multiple Context IDs. 

Each ROHC packet header has Context ID(s) field, but there is no ROHC 
channel identifier field in a ROHC packet. 

Q) How does a lower layer know what the ROHC channel identifier is for a
ROHC packet? 

- Daum


-- 
View this message in context: http://www.nabble.com/Q%29-ROHC-channel-identifier.-tf4281953.html#a12188948
Sent from the IETF - Rohc mailing list archive at Nabble.com.


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



From rohc-bounces@ietf.org Fri Aug 17 03:31:44 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILwHL-00034a-7J; Fri, 17 Aug 2007 03:29:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILtKi-0006hY-CI
	for rohc@ietf.org; Fri, 17 Aug 2007 00:21:12 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=sd-smtp.ccpu.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILtKh-0000Uh-Fm
	for rohc@ietf.org; Fri, 17 Aug 2007 00:21:12 -0400
Received: from sd-smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.ccpu.com (Postfix) with ESMTP id 49B2C184A0D;
	Thu, 16 Aug 2007 21:21:10 -0700 (PDT)
Received: from sd-exchange.ccsd.ccpu.com (sd-exchange.ccpu.com [172.16.0.203])
	by sd-smtp.ccpu.com (Postfix) with ESMTP id 27C91184965;
	Thu, 16 Aug 2007 21:21:10 -0700 (PDT)
Received: from IN-EXCHANGE.ccin.ccpu.com ([172.25.0.16]) by
	sd-exchange.ccsd.ccpu.com with Microsoft SMTPSVC(6.0.3790.1830);
	Thu, 16 Aug 2007 21:21:08 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Aug 2007 09:50:31 +0530
Message-ID: <22F058C3ED9D784E90CE473F2A9847F0395CB0@in-exchange>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Mode Information in IR/IR Dyn Packets (UDP Profile/ESP profile)
Thread-Index: AcfOdmrfDkFMOSdiRVeVV+Ya+J8TagSDU6sw
From: "Rambabu Gajula" <rambabu.gajula@ccpu.com>
To: "Rambabu Gajula" <rambabu.gajula@ccpu.com>,
	<lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>,
	<aniruddha.kulkarni@effnet.com>
X-OriginalArrivalTime: 17 Aug 2007 04:21:08.0691 (UTC)
	FILETIME=[09238230:01C7E086]
X-TM-AS-Product-Ver: IMSS-7.0.0.1640-3.8.0.1026-15366.002
X-TM-AS-Result: No--14.808-5.0-31-1
X-imss-scan-details: No--14.808-5.0-31-1;No--14.808-5.0-31-1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4
X-Mailman-Approved-At: Fri, 17 Aug 2007 03:29:54 -0400
Cc: 
Subject: [rohc] Mode Information in IR/IR Dyn Packets (UDP Profile/ESP
	profile)
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="===============1941807262=="
Errors-To: rohc-bounces@ietf.org

This is a multi-part message in MIME format.


--===============1941807262==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7E085.F56AB9B4"

This is a multi-part message in MIME format.


------_=_NextPart_001_01C7E085.F56AB9B4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

Hi ROHC Experts,

=20

I am new to the ROHC RFC(3905).

=20

I have couple of queries regarding the ROHC.

=20

=20

=20

1) During Context Relocation Request, how Source RNC (compressor) will
communicate the Mode information to the Target RNC (Compression).

=20

    IR packets (Static part + Dynamic part) not have any mode related
information in case of UPD Profile/ESP profile.

=20

2)  During Mode Change Operation at Compressor side,  the compressor
should choose IR/IR Dyn pkt/UOR2(SN, Mode) after receiving the mode
change request from decompress or.  But in case of IR /IR Dyn packets
UDP/ESP profile we can not send Mode related information.

=20

=20

I would really appreciate your help.

=20

Thanks with regards,

Rambabu Gajula

=20



------_=_NextPart_001_01C7E085.F56AB9B4
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;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1183789499;
	mso-list-type:hybrid;
	mso-list-template-ids:-2107717096 67698705 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><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'>Hi ROHC Experts,<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'>I am new to the ROHC =
RFC(3905).<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'>I have couple of queries regarding the =
ROHC.<o:p></o:p></span></font></p>

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

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

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>1) During Context Relocation =
Request, how Source
RNC (compressor) will communicate the Mode information to the Target RNC
(Compression).<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp;&nbsp; IR packets =
(Static part
+ Dynamic part) not have any mode related information in case of UPD
Profile/ESP profile.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>2) &nbsp;During Mode Change =
Operation at
Compressor side, &nbsp;the compressor should choose IR/IR Dyn =
pkt/UOR2(SN,
Mode) after receiving the mode change request from decompress or. =
&nbsp;But in
case of IR /IR Dyn packets UDP/ESP profile we can not send Mode related =
information.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I would really appreciate your =
help.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><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 with regards,<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'>Rambabu Gajula<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>

</div>

</body>

</html>


------_=_NextPart_001_01C7E085.F56AB9B4--


--===============1941807262==
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

--===============1941807262==--




From rohc-bounces@ietf.org Fri Aug 17 03:57:41 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILwgW-0004K2-L4; Fri, 17 Aug 2007 03:55:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILwgU-0004Jx-JG
	for rohc@ietf.org; Fri, 17 Aug 2007 03:55:54 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILwgT-00075b-UO
	for rohc@ietf.org; Fri, 17 Aug 2007 03:55:54 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5024E20870; Fri, 17 Aug 2007 09:55:53 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-91-46c5548917fb
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3E01A20883; Fri, 17 Aug 2007 09:55:53 +0200 (CEST)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 09:55:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Mode Information in IR/IR Dyn Packets (UDP
	Profile/ESPprofile)
Date: Fri, 17 Aug 2007 09:55:52 +0200
Message-ID: <A91F30A632473A47B40C18D2B107CA6F0459CB05@esealmw105.eemea.ericsson.se>
In-Reply-To: <22F058C3ED9D784E90CE473F2A9847F0395CB0@in-exchange>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Mode Information in IR/IR Dyn Packets (UDP
	Profile/ESPprofile)
Thread-Index: AcfOdmrfDkFMOSdiRVeVV+Ya+J8TagSDU6swAAerm8A=
References: <22F058C3ED9D784E90CE473F2A9847F0395CB0@in-exchange>
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: "Rambabu Gajula" <rambabu.gajula@ccpu.com>,
	<lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>,
	<aniruddha.kulkarni@effnet.com>
X-OriginalArrivalTime: 17 Aug 2007 07:55:52.0972 (UTC)
	FILETIME=[08C4C4C0:01C7E0A4]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: 
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,

comments inline.

Rambabu Gajula <mailto:rambabu.gajula@ccpu.com> wrote on den 17 augusti
2007 06:21 :

> Hi ROHC Experts,
>=20
>=20
>=20
> I am new to the ROHC RFC(3905).
>=20
>=20
>=20
> I have couple of queries regarding the ROHC.
>=20
>=20
> 1) During Context Relocation Request, how Source RNC
> (compressor) will communicate the Mode information to the Target RNC
> (Compression).=20
>=20

First of all, the ROHC WG has not specified any type of context=20
relocation procedure, so I cannot answer your question for any=20
specific technology using any such procedure. But generally, any
context relocation scheme that assumes that it is possible to=20
continue compression by transferring an IR header is inherently broken.
(personally, I would say that any ROHC context relocation procedure=20
will be broken, but that's a whole other discussion)
To compress with ROHC, you need a lot more infomration than just one=20
header, you need a lot of state which is built up over time such as
mode information, sliding window of contexts to use the optimistic
approach, control fields, list compression items not currently present
in the reference header etc.

>=20
>=20
>     IR packets (Static part + Dynamic part) not have any mode
> related information in case of UPD Profile/ESP profile.
>=20

Yes, this is one example why such a context relocation scheme is broken,
and why an IR header is not enough to use for this.

>=20
>=20
> 2)  During Mode Change Operation at Compressor side,  the
> compressor should choose IR/IR Dyn pkt/UOR2(SN, Mode) after
> receiving the mode change request from decompress or.  But in
> case of IR /IR Dyn packets UDP/ESP profile we can not send Mode
> related information.=20

And here's another example, if you transfer in the middle of a mode
transition, you would need to know the state of the transition
(e.g. D_TRANS) which is not part of an IR header.

Summary: Context relocation/transfer is something that has not
been 'blessed' by this WG, and any existing scheme for such a
technology has not been specified here.

BR,
   Kristofer

>=20
>=20
>=20
>=20
>=20
> I would really appreciate your help.
>=20
>=20
>=20
> Thanks with regards,
>=20
> Rambabu Gajula

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



From rohc-bounces@ietf.org Fri Aug 17 04:52:37 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILxXg-0002Iw-Ot; Fri, 17 Aug 2007 04:50:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILxXf-0002Ir-7A
	for rohc@ietf.org; Fri, 17 Aug 2007 04:50:51 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILxXd-0005mG-S0
	for rohc@ietf.org; Fri, 17 Aug 2007 04:50:51 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 3F49790001;
	Fri, 17 Aug 2007 04:50:46 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 02170-11; Fri, 17 Aug 2007 04:50:45 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Fri, 17 Aug 2007 04:50:45 -0400 (EDT)
Received: from exchindia3.starentnetworks.com ([10.6.7.5]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 17 Aug 2007 04:51:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from 10.6.7.67 ([10.6.7.67]) by exchindia3.starentnetworks.com
	([10.6.7.5]) with Microsoft Exchange Server HTTP-DAV ;
	Fri, 17 Aug 2007 08:50:30 +0000
Received: from INDBNG1172 by 10.6.7.5; 17 Aug 2007 14:20:46 +0530
MIME-Version: 1.0
Content-class: urn:content-classes:message
Subject: Re: [rohc] Q) ROHC channel identifier.
Date: Fri, 17 Aug 2007 14:20:46 +0530
Message-ID: <1187340646.6945.57.camel@INDBNG1172.bng.ind.starentnetworks.com>
In-Reply-To: <12188948.post@talk.nabble.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Q) ROHC channel identifier.
Thread-Index: Acfgq6rl/CNX4OZHRPWI1xg5Q667+w==
References: <12188948.post@talk.nabble.com>
From: "Sarkar, Biplab" <bsarkar@starentnetworks.com>
To: "daum" <daum3998@yahoo.com>
X-OriginalArrivalTime: 17 Aug 2007 08:51:15.0570 (UTC)
	FILETIME=[C530FD20:01C7E0AB]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "Sarkar, Biplab" <bsarkar@starentnetworks.com>
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="===============1699132491=="
Errors-To: rohc-bounces@ietf.org


--===============1699132491==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	boundary="=-7LmkWDZHQXcMrzVvowUB"; micalg=pgp-sha1
Content-class: urn:content-classes:message


--=-7LmkWDZHQXcMrzVvowUB
Content-Type: multipart/alternative; boundary="=-vdh6jxlLjzmyFYk8ICk8"


--=-vdh6jxlLjzmyFYk8ICk8
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Daum,

The definition of a ROHC channel is left for the under-lying stack to
handle. ROHC just uses those logical point-to-point channels. So there
is no information regarding channels in ROHC. But I remember there was a
channel information in FEEDBACK_FOR field in some ROHC RFC.

Thanks
Biplab

On Thu, 2007-08-16 at 13:33 -0700, daum wrote:

> Dear all,=20
>=20
> Let me ask you a question.=20
>=20
>=20
> An IP interface can have multiple ROHC channels, and a ROHC channel can h=
ave=20
> multiple Context IDs.=20
>=20
> Each ROHC packet header has Context ID(s) field, but there is no ROHC=20
> channel identifier field in a ROHC packet.=20
>=20
> Q) How does a lower layer know what the ROHC channel identifier is for a
> ROHC packet?=20
>=20
> - Daum
>=20
>=20

--=-vdh6jxlLjzmyFYk8ICk8
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/3.14.1">
</HEAD>
<BODY>
Daum,<BR>
<BR>
The definition of a ROHC channel is left for the under-lying stack to handl=
e. ROHC just uses those logical point-to-point channels. So there is no inf=
ormation regarding channels in ROHC. But I remember there was a channel inf=
ormation in FEEDBACK_FOR field in some ROHC RFC.<BR>
<BR>
Thanks<BR>
Biplab<BR>
<BR>
On Thu, 2007-08-16 at 13:33 -0700, daum wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE>
<FONT COLOR=3D"#000000">Dear all, </FONT>

<FONT COLOR=3D"#000000">Let me ask you a question. </FONT>


<FONT COLOR=3D"#000000">An IP interface can have multiple ROHC channels, an=
d a ROHC channel can have </FONT>
<FONT COLOR=3D"#000000">multiple Context IDs. </FONT>

<FONT COLOR=3D"#000000">Each ROHC packet header has Context ID(s) field, bu=
t there is no ROHC </FONT>
<FONT COLOR=3D"#000000">channel identifier field in a ROHC packet. </FONT>

<FONT COLOR=3D"#000000">Q) How does a lower layer know what the ROHC channe=
l identifier is for a</FONT>
<FONT COLOR=3D"#000000">ROHC packet? </FONT>

<FONT COLOR=3D"#000000">- Daum</FONT>


</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>

--=-vdh6jxlLjzmyFYk8ICk8--

--=-7LmkWDZHQXcMrzVvowUB
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGxWFm3rQBTW1UPu4RAinKAJwL7sSKktgbZb7gUkKLvm+REMCsgQCgms/Y
Pj/zzsFb1KR1JBsbpTpt/+s=
=hKoE
-----END PGP SIGNATURE-----

--=-7LmkWDZHQXcMrzVvowUB--


--===============1699132491==
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

--===============1699132491==--




From rohc-bounces@ietf.org Fri Aug 17 08:10:02 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM0ci-0004ul-Rk; Fri, 17 Aug 2007 08:08:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IM0EZ-0002JR-11
	for rohc@ietf.org; Fri, 17 Aug 2007 07:43:19 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=sd-smtp.ccpu.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IM0EY-0004ek-Bl
	for rohc@ietf.org; Fri, 17 Aug 2007 07:43:18 -0400
Received: from sd-smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.ccpu.com (Postfix) with ESMTP id ABDFE184A5A;
	Fri, 17 Aug 2007 04:43:17 -0700 (PDT)
Received: from sd-exchange.ccsd.ccpu.com (sd-exchange.ccpu.com [172.16.0.203])
	by sd-smtp.ccpu.com (Postfix) with ESMTP id 96C2618494E;
	Fri, 17 Aug 2007 04:43:17 -0700 (PDT)
Received: from IN-EXCHANGE.ccin.ccpu.com ([172.25.0.16]) by
	sd-exchange.ccsd.ccpu.com with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 17 Aug 2007 04:43:16 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
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] Mode Information in IR/IR Dyn Packets (UDP
	Profile/ESPprofile)
Date: Fri, 17 Aug 2007 17:13:06 +0530
Message-ID: <22F058C3ED9D784E90CE473F2A9847F0395CB5@in-exchange>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Mode Information in IR/IR Dyn Packets (UDP
	Profile/ESPprofile)
Thread-Index: AcfOdmrfDkFMOSdiRVeVV+Ya+J8TagSDU6swAAerm8AAB6gnUA==
From: "Rambabu Gajula" <rambabu.gajula@ccpu.com>
To: "Kristofer Sandlund \(LU/EAB\)" <kristofer.sandlund@ericsson.com>,
	<lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>,
	<aniruddha.kulkarni@effnet.com>
X-OriginalArrivalTime: 17 Aug 2007 11:43:16.0098 (UTC)
	FILETIME=[CCB49620:01C7E0C3]
X-TM-AS-Product-Ver: IMSS-7.0.0.1640-3.8.0.1026-15366.002
X-TM-AS-Result: No--14.509-5.0-31-1
X-imss-scan-details: No--14.509-5.0-31-1;No--14.509-5.0-31-1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
X-Mailman-Approved-At: Fri, 17 Aug 2007 08:08:16 -0400
Cc: 
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

Thanks a lot Kristofer.


I have following query regarding the IP Identification (IPV4) number
used=20
across the ROHC RFC 3095).


>From Section 3.4:
IPV4 Identification (16bits) ---> IP-ID

RND: Flag indicating whether the IP-ID behaves randomly.


Here the IP-ID presenting the IP Identification of IP header(IPV4) or
(IP Identification - SN )?


To predict the random behavior, shall we consider the random ness with
in IP Identifications (IPV4), by comparing with the previous packets IP
Identifications values or=20

Off Set IP- ID(off set =3D IP Identification - SN) for current packet =
with
the previous packets?


>From Section: 4.5.5
IP-ID for m =3D decompressed SN of packet m + Offset_m

The above statement gives impression for me IP-ID is IP Identification
of IP header(IPV4).


In Packets type-0, type-1, type-2 we have IP-ID as representations which
is (IP Identification - SN).

The one which is carrying in ROHC General Form for Compressed RTP
packet(IP-ID for Inner IPv4 header, 2 octets if value RND =3D 1).

Is this value is IP Identification (IPV4) or     (IP Identification
-SN)?


Thanks a lot for your help and time.

Regards,
Rambabu Gajula




-----Original Message-----
From: Kristofer Sandlund (LU/EAB)
[mailto:kristofer.sandlund@ericsson.com]=20
Sent: Friday, August 17, 2007 1:26 PM
To: Rambabu Gajula; lars-erik.jonsson@ericsson.com; rohc@ietf.org;
aniruddha.kulkarni@effnet.com
Subject: RE: [rohc] Mode Information in IR/IR Dyn Packets (UDP
Profile/ESPprofile)

Hi,

comments inline.

Rambabu Gajula <mailto:rambabu.gajula@ccpu.com> wrote on den 17 augusti
2007 06:21 :

> Hi ROHC Experts,
>=20
>=20
>=20
> I am new to the ROHC RFC(3905).
>=20
>=20
>=20
> I have couple of queries regarding the ROHC.
>=20
>=20
> 1) During Context Relocation Request, how Source RNC
> (compressor) will communicate the Mode information to the Target RNC
> (Compression).=20
>=20

First of all, the ROHC WG has not specified any type of context=20
relocation procedure, so I cannot answer your question for any=20
specific technology using any such procedure. But generally, any
context relocation scheme that assumes that it is possible to=20
continue compression by transferring an IR header is inherently broken.
(personally, I would say that any ROHC context relocation procedure=20
will be broken, but that's a whole other discussion)
To compress with ROHC, you need a lot more infomration than just one=20
header, you need a lot of state which is built up over time such as
mode information, sliding window of contexts to use the optimistic
approach, control fields, list compression items not currently present
in the reference header etc.

>=20
>=20
>     IR packets (Static part + Dynamic part) not have any mode
> related information in case of UPD Profile/ESP profile.
>=20

Yes, this is one example why such a context relocation scheme is broken,
and why an IR header is not enough to use for this.

>=20
>=20
> 2)  During Mode Change Operation at Compressor side,  the
> compressor should choose IR/IR Dyn pkt/UOR2(SN, Mode) after
> receiving the mode change request from decompress or.  But in
> case of IR /IR Dyn packets UDP/ESP profile we can not send Mode
> related information.=20

And here's another example, if you transfer in the middle of a mode
transition, you would need to know the state of the transition
(e.g. D_TRANS) which is not part of an IR header.

Summary: Context relocation/transfer is something that has not
been 'blessed' by this WG, and any existing scheme for such a
technology has not been specified here.

BR,
   Kristofer

>=20
>=20
>=20
>=20
>=20
> I would really appreciate your help.
>=20
>=20
>=20
> Thanks with regards,
>=20
> Rambabu Gajula



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



From rohc-bounces@ietf.org Wed Aug 22 07:24:04 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INoHz-0005Mc-4g; Wed, 22 Aug 2007 07:22:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INoHy-0005MX-LW
	for rohc@ietf.org; Wed, 22 Aug 2007 07:22:18 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INoHw-0000X3-WF
	for rohc@ietf.org; Wed, 22 Aug 2007 07:22:18 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	24D6C21001; Wed, 22 Aug 2007 13:22:16 +0200 (CEST)
X-AuditID: c1b4fb3e-ae831bb0000007e1-47-46cc1c6713f4
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E77F720F91; Wed, 22 Aug 2007 13:22:15 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 13:22:15 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 13:22:15 +0200
Received: from [131.160.36.58] (E000FB0F665DD.lmf.ericsson.se [131.160.36.58])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 0637727C3;
	Wed, 22 Aug 2007 14:22:15 +0300 (EEST)
Message-ID: <46CC1C66.2050505@ericsson.com>
Date: Wed, 22 Aug 2007 14:22:14 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dikla Dror <Dikla@radvision.com>
Subject: Re: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
References: <7E27141E2F9038419E1FA26127E67EC43C3BFB@rvil-mail1.RADVISION.com>
In-Reply-To: <7E27141E2F9038419E1FA26127E67EC43C3BFB@rvil-mail1.RADVISION.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 22 Aug 2007 11:22:15.0365 (UTC)
	FILETIME=[B150BF50:01C7E4AE]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi,

previous versions of the draft addressed this type of on-the-fly=20
compartment creation. However, the agreement was to go for a simpler=20
solution that requires registrations. Therefore, the compartments would=20
have been created at registration time, not when A and B start=20
exchanging INVITEs.

Cheers,

Gonzalo

Dikla Dror wrote:
> Hi,
>=20
> I=92ve sent a question concerning chapter 9 in=20
> draft-ietf-rohc-sigcomp-sip-07 few weeks ago, but got no answer yet.
>=20
> I would appreciate any feedback to the following issue (I=92ve turned m=
y=20
> question into a simpler scenario):
>=20
> =20
>=20
> According to chapter 9, I might encounter imbalanced compartments at 2=20
> different communicating endpoints in the following scenario:
>=20
> =20
>=20
> This scenario includes 2 endpoints (A, B), communicating over TCP.
>=20
> =20
>=20
>                                                =20
> A                                                          B
>=20
>                                                 |              (1)    =20
> INVITE                          |
>=20
>           Create Compartment (A1)=20
> |--------------------------------------------------------->| Create=20
> Compartment (B1)
>=20
>                                                =20
> |                                                           |
>=20
>                                                 |               (2) 200=
=20
> OK                             |
>=20
>                                                =20
> |<---------------------------------------------------------| Use=20
> Compartment (B1)
>=20
>                                                =20
> |                                                           |
>=20
>                                                 |              (3)    =20
> INVITE                          |
>=20
>           Create Compartment (A2)=20
> |<---------------------------------------------------------| Use=20
> Compartment (B1)
>=20
>                                                =20
> |                                                           |
>=20
>                                                =20
> |                                                           |
>=20
>                                                             And so on=85
>=20
>           =20
>=20
> As you can see endpoint A is sending an INVITE (1) toward B, specifying=
=20
> its local urn (A=92s urn). However A doesn=92t know yet B=92s urn, thus=
 it=20
> creates a local compartment (A1), related to the INVITE outgoing=20
> connection.
>=20
> Now B:
>=20
> -          Responds the first INVITE with 200 OK (2), related to=20
> compartment (B1)
>=20
> -          Sends an outgoing INVITE (3) to A, related to compartment=20
> (B1). This (3) INVITE includes B=92s urn.
>=20
> =20
>=20
> However, upon receiving (3) INVITE, endpoint A is not aware of the=20
> relation between B=92s urn and the first INVITE (1). Thus, A will maint=
ain=20
> 2 different compartments - (A1) and (A2) for these 2 sessions while B=20
> will maintain only one compartment (B1). This will lead to inconsistenc=
y=20
> within the SigComp mechanism.
>=20
> =20
>=20
>  How can I solve this asymmetry according to the draft?
>=20
> =20
>=20
> Thanks,
>=20
> Dikla.
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc


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



From rohc-bounces@ietf.org Wed Aug 22 07:35:13 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INoSn-0003Qi-CG; Wed, 22 Aug 2007 07:33:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INoSm-0003Qc-Go
	for rohc@ietf.org; Wed, 22 Aug 2007 07:33:28 -0400
Received: from rvil-eframer.radvision.com ([80.74.106.104]
	helo=eframer.radvision.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INoSl-0000ki-4C
	for rohc@ietf.org; Wed, 22 Aug 2007 07:33:28 -0400
Received: (from root@localhost)
	by eframer.radvision.com (8.13.4/8.12.9) id l7MBbwj4017755
	for rohc@ietf.org; Wed, 22 Aug 2007 14:37:58 +0300
Received: from rvil-mail1.RADVISION.com (rvil-mail1.radvision.com
	[172.20.2.100])
	by eframer.radvision.com (8.13.4/8.12.9) with ESMTP id l7MBbjOc017743; 
	Wed, 22 Aug 2007 14:37:45 +0300
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"
Subject: RE: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
Date: Wed, 22 Aug 2007 14:31:59 +0300
Message-ID: <2493C64BDF900546B2AA9AECA3892AA6AA70D5@rvil-mail1.RADVISION.com>
In-Reply-To: <46CC1C66.2050505@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
Thread-Index: Acfkrr5z8WgS8tX+RHCJI7iDjp5uuAAASNRw
References: <7E27141E2F9038419E1FA26127E67EC43C3BFB@rvil-mail1.RADVISION.com>
	<46CC1C66.2050505@ericsson.com>
From: "Asher Shiratzky" <Ashers@radvision.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>,
	"Dikla Dror" <Dikla@radvision.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by eframer.radvision.com
	id l7MBbjOc017743
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
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

Simplicity is very important, but what will happened in cases where
there is INVITE without registration like emergency calls?
 

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] 
Sent: Wednesday, August 22, 2007 2:22 PM
To: Dikla Dror
Cc: rohc@ietf.org
Subject: Re: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07

Hi,

previous versions of the draft addressed this type of on-the-fly
compartment creation. However, the agreement was to go for a simpler
solution that requires registrations. Therefore, the compartments would
have been created at registration time, not when A and B start
exchanging INVITEs.

Cheers,

Gonzalo

Dikla Dror wrote:
> Hi,
> 
> I've sent a question concerning chapter 9 in
> draft-ietf-rohc-sigcomp-sip-07 few weeks ago, but got no answer yet.
> 
> I would appreciate any feedback to the following issue (I've turned my

> question into a simpler scenario):
> 
>  
> 
> According to chapter 9, I might encounter imbalanced compartments at 2

> different communicating endpoints in the following scenario:
> 
>  
> 
> This scenario includes 2 endpoints (A, B), communicating over TCP.
> 
>  
> 
>                                                 
> A                                                          B
> 
>                                                 |              (1)

> INVITE                          |
> 
>           Create Compartment (A1)
> |--------------------------------------------------------->| Create
> Compartment (B1)
> 
>                                                 
> |                                                           |
> 
>                                                 |               (2)
200 
> OK                             |
> 
>                                                 
> |<---------------------------------------------------------| Use
> Compartment (B1)
> 
>                                                 
> |                                                           |
> 
>                                                 |              (3)

> INVITE                          |
> 
>           Create Compartment (A2)
> |<---------------------------------------------------------| Use
> Compartment (B1)
> 
>                                                 
> |                                                           |
> 
>                                                 
> |                                                           |
> 
>                                                             And so
on...
> 
>            
> 
> As you can see endpoint A is sending an INVITE (1) toward B, 
> specifying its local urn (A's urn). However A doesn't know yet B's 
> urn, thus it creates a local compartment (A1), related to the INVITE 
> outgoing connection.
> 
> Now B:
> 
> -          Responds the first INVITE with 200 OK (2), related to 
> compartment (B1)
> 
> -          Sends an outgoing INVITE (3) to A, related to compartment 
> (B1). This (3) INVITE includes B's urn.
> 
>  
> 
> However, upon receiving (3) INVITE, endpoint A is not aware of the 
> relation between B's urn and the first INVITE (1). Thus, A will 
> maintain
> 2 different compartments - (A1) and (A2) for these 2 sessions while B 
> will maintain only one compartment (B1). This will lead to 
> inconsistency within the SigComp mechanism.
> 
>  
> 
>  How can I solve this asymmetry according to the draft?
> 
>  
> 
> Thanks,
> 
> Dikla.
> 
> 
> ----------------------------------------------------------------------
> --
> 
> _______________________________________________
> 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



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



From rohc-bounces@ietf.org Wed Aug 22 07:39:14 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INoWg-0006Q6-3O; Wed, 22 Aug 2007 07:37:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INoWd-0006Q0-2z
	for rohc@ietf.org; Wed, 22 Aug 2007 07:37:28 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INoWc-0000oB-AI
	for rohc@ietf.org; Wed, 22 Aug 2007 07:37:27 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8D54120715; Wed, 22 Aug 2007 13:37:25 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-72-46cc1ff5436a
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6FBE4204FA; Wed, 22 Aug 2007 13:37:25 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 13:37:24 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 13:37:24 +0200
Received: from [131.160.36.58] (E000FB0F665DD.lmf.ericsson.se [131.160.36.58])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id B0F0326A0;
	Wed, 22 Aug 2007 14:37:24 +0300 (EEST)
Message-ID: <46CC1FF4.70408@ericsson.com>
Date: Wed, 22 Aug 2007 14:37:24 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Asher Shiratzky <Ashers@radvision.com>
Subject: Re: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
References: <7E27141E2F9038419E1FA26127E67EC43C3BFB@rvil-mail1.RADVISION.com>
	<46CC1C66.2050505@ericsson.com>
	<2493C64BDF900546B2AA9AECA3892AA6AA70D5@rvil-mail1.RADVISION.com>
In-Reply-To: <2493C64BDF900546B2AA9AECA3892AA6AA70D5@rvil-mail1.RADVISION.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2007 11:37:24.0625 (UTC)
	FILETIME=[CF46D010:01C7E4B0]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Cc: rohc@ietf.org, Dikla Dror <Dikla@radvision.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi,

the consensus was to require registrations, with all the pros and cons 
associated with that decision.

Cheers,

Gonzalo


Asher Shiratzky wrote:
> Simplicity is very important, but what will happened in cases where
> there is INVITE without registration like emergency calls?
> 
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
> Sent: Wednesday, August 22, 2007 2:22 PM
> To: Dikla Dror
> Cc: rohc@ietf.org
> Subject: Re: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
> 
> Hi,
> 
> previous versions of the draft addressed this type of on-the-fly
> compartment creation. However, the agreement was to go for a simpler
> solution that requires registrations. Therefore, the compartments would
> have been created at registration time, not when A and B start
> exchanging INVITEs.
> 
> Cheers,
> 
> Gonzalo
> 
> Dikla Dror wrote:
>  > Hi,
>  >
>  > I've sent a question concerning chapter 9 in
>  > draft-ietf-rohc-sigcomp-sip-07 few weeks ago, but got no answer yet.
>  >
>  > I would appreciate any feedback to the following issue (I've turned my
> 
>  > question into a simpler scenario):
>  >
>  > 
>  >
>  > According to chapter 9, I might encounter imbalanced compartments at 2
> 
>  > different communicating endpoints in the following scenario:
>  >
>  > 
>  >
>  > This scenario includes 2 endpoints (A, B), communicating over TCP.
>  >
>  > 
>  >
>  >                                                
>  > A                                                          B
>  >
>  >                                                 |              (1)
> 
>  > INVITE                          |
>  >
>  >           Create Compartment (A1)
>  > |--------------------------------------------------------->| Create
>  > Compartment (B1)
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                 |               (2)
> 200
>  > OK                             |
>  >
>  >                                                
>  > |<---------------------------------------------------------| Use
>  > Compartment (B1)
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                 |              (3)
> 
>  > INVITE                          |
>  >
>  >           Create Compartment (A2)
>  > |<---------------------------------------------------------| Use
>  > Compartment (B1)
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                             And so
> on...
>  >
>  >           
>  >
>  > As you can see endpoint A is sending an INVITE (1) toward B,
>  > specifying its local urn (A's urn). However A doesn't know yet B's
>  > urn, thus it creates a local compartment (A1), related to the INVITE
>  > outgoing connection.
>  >
>  > Now B:
>  >
>  > -          Responds the first INVITE with 200 OK (2), related to
>  > compartment (B1)
>  >
>  > -          Sends an outgoing INVITE (3) to A, related to compartment
>  > (B1). This (3) INVITE includes B's urn.
>  >
>  > 
>  >
>  > However, upon receiving (3) INVITE, endpoint A is not aware of the
>  > relation between B's urn and the first INVITE (1). Thus, A will
>  > maintain
>  > 2 different compartments - (A1) and (A2) for these 2 sessions while B
>  > will maintain only one compartment (B1). This will lead to
>  > inconsistency within the SigComp mechanism.
>  >
>  > 
>  >
>  >  How can I solve this asymmetry according to the draft?
>  >
>  > 
>  >
>  > Thanks,
>  >
>  > Dikla.
>  >
>  >
>  > ----------------------------------------------------------------------
>  > --
>  >
>  > _______________________________________________
>  > 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
> 
> 


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



From rohc-bounces@ietf.org Wed Aug 22 07:39:52 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INoXJ-0007Qy-CZ; Wed, 22 Aug 2007 07:38:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INoXH-0007Qt-Cw
	for rohc@ietf.org; Wed, 22 Aug 2007 07:38:08 -0400
Received: from rvil-eframer.radvision.com ([80.74.106.104]
	helo=eframer.radvision.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INoXD-0006zD-RE
	for rohc@ietf.org; Wed, 22 Aug 2007 07:38:07 -0400
Received: (from root@localhost)
	by eframer.radvision.com (8.13.4/8.12.9) id l7MBha4U017823
	for rohc@ietf.org; Wed, 22 Aug 2007 14:43:36 +0300
Received: from rvil-mail1.RADVISION.com (rvil-mail1.radvision.com
	[172.20.2.100])
	by eframer.radvision.com (8.13.4/8.12.9) with ESMTP id l7MBhU07017813; 
	Wed, 22 Aug 2007 14:43:30 +0300
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"
Subject: RE: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
Date: Wed, 22 Aug 2007 14:37:50 +0300
Message-ID: <7E27141E2F9038419E1FA26127E67EC43C3C0B@rvil-mail1.RADVISION.com>
In-Reply-To: <46CC1C66.2050505@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
Thread-Index: AcfkrrTqnWD0BJGFSeWTktKH3mbrXgAAM8Og
From: "Dikla Dror" <Dikla@radvision.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by eframer.radvision.com
	id l7MBhU07017813
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi,
Thanks for your reply. I have a further question:
There might be applications, which do not handle registrations; the new
draft refers these applications as well, see chapter 9.3: "Note that
linking the lifetime of SIP/SigComp compartments to registration state
limits the applicability of this specification. In particular, SIP user
agents that do not register but, for example, only handle PUBLISH or
SUBSCRIBE/NOTIFY transactions are not able create SIP/SigComp
compartments following this       specification."
How will these applications maintain SigComp compartments? I think the
draft should deal with this issue. 

Thanks,
Dikla. 

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] 
Sent: Wednesday, August 22, 2007 2:22 PM
To: Dikla Dror
Cc: rohc@ietf.org
Subject: Re: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07

Hi,

previous versions of the draft addressed this type of on-the-fly 
compartment creation. However, the agreement was to go for a simpler 
solution that requires registrations. Therefore, the compartments would 
have been created at registration time, not when A and B start 
exchanging INVITEs.

Cheers,

Gonzalo

Dikla Dror wrote:
> Hi,
> 
> I've sent a question concerning chapter 9 in 
> draft-ietf-rohc-sigcomp-sip-07 few weeks ago, but got no answer yet.
> 
> I would appreciate any feedback to the following issue (I've turned my

> question into a simpler scenario):
> 
>  
> 
> According to chapter 9, I might encounter imbalanced compartments at 2

> different communicating endpoints in the following scenario:
> 
>  
> 
> This scenario includes 2 endpoints (A, B), communicating over TCP.
> 
>  
> 
>                                                 
> A                                                          B
> 
>                                                 |              (1)

> INVITE                          |
> 
>           Create Compartment (A1) 
> |--------------------------------------------------------->| Create 
> Compartment (B1)
> 
>                                                 
> |                                                           |
> 
>                                                 |               (2)
200 
> OK                             |
> 
>                                                 
> |<---------------------------------------------------------| Use 
> Compartment (B1)
> 
>                                                 
> |                                                           |
> 
>                                                 |              (3)

> INVITE                          |
> 
>           Create Compartment (A2) 
> |<---------------------------------------------------------| Use 
> Compartment (B1)
> 
>                                                 
> |                                                           |
> 
>                                                 
> |                                                           |
> 
>                                                             And so
on...
> 
>            
> 
> As you can see endpoint A is sending an INVITE (1) toward B,
specifying 
> its local urn (A's urn). However A doesn't know yet B's urn, thus it 
> creates a local compartment (A1), related to the INVITE outgoing 
> connection.
> 
> Now B:
> 
> -          Responds the first INVITE with 200 OK (2), related to 
> compartment (B1)
> 
> -          Sends an outgoing INVITE (3) to A, related to compartment 
> (B1). This (3) INVITE includes B's urn.
> 
>  
> 
> However, upon receiving (3) INVITE, endpoint A is not aware of the 
> relation between B's urn and the first INVITE (1). Thus, A will
maintain 
> 2 different compartments - (A1) and (A2) for these 2 sessions while B 
> will maintain only one compartment (B1). This will lead to
inconsistency 
> within the SigComp mechanism.
> 
>  
> 
>  How can I solve this asymmetry according to the draft?
> 
>  
> 
> Thanks,
> 
> Dikla.
> 
> 
>
------------------------------------------------------------------------
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc



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



From rohc-bounces@ietf.org Wed Aug 22 07:52:39 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INojf-0007L4-2B; Wed, 22 Aug 2007 07:50:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INoje-0007G9-AY
	for rohc@ietf.org; Wed, 22 Aug 2007 07:50:54 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INojd-0007Dk-Fw
	for rohc@ietf.org; Wed, 22 Aug 2007 07:50:54 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	4C69D2116E; Wed, 22 Aug 2007 13:50:52 +0200 (CEST)
X-AuditID: c1b4fb3e-af032bb0000007e1-74-46cc231c7ab6
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0253E21174; Wed, 22 Aug 2007 13:50:52 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 13:50:51 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 13:50:50 +0200
Received: from [131.160.36.58] (E000FB0F665DD.lmf.ericsson.se [131.160.36.58])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id A2B7C2468;
	Wed, 22 Aug 2007 14:50:50 +0300 (EEST)
Message-ID: <46CC231A.5080003@ericsson.com>
Date: Wed, 22 Aug 2007 14:50:50 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dikla Dror <Dikla@radvision.com>
Subject: Re: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
References: <7E27141E2F9038419E1FA26127E67EC43C3C0B@rvil-mail1.RADVISION.com>
In-Reply-To: <7E27141E2F9038419E1FA26127E67EC43C3C0B@rvil-mail1.RADVISION.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2007 11:50:51.0022 (UTC)
	FILETIME=[AFED3AE0:01C7E4B2]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

Hi,

the text you are referring to simply says that that is out of the scope 
of this draft. If you think that supporting that is important, you can 
write an additional specification.

Cheers,

Gonzalo


Dikla Dror wrote:
> Hi,
> Thanks for your reply. I have a further question:
> There might be applications, which do not handle registrations; the new
> draft refers these applications as well, see chapter 9.3: "Note that
> linking the lifetime of SIP/SigComp compartments to registration state
> limits the applicability of this specification. In particular, SIP user
> agents that do not register but, for example, only handle PUBLISH or
> SUBSCRIBE/NOTIFY transactions are not able create SIP/SigComp
> compartments following this       specification."
> How will these applications maintain SigComp compartments? I think the
> draft should deal with this issue.
> 
> Thanks,
> Dikla.
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
> Sent: Wednesday, August 22, 2007 2:22 PM
> To: Dikla Dror
> Cc: rohc@ietf.org
> Subject: Re: [rohc] Query about draft-ietf-rohc-sigcomp-sip-07
> 
> Hi,
> 
> previous versions of the draft addressed this type of on-the-fly
> compartment creation. However, the agreement was to go for a simpler
> solution that requires registrations. Therefore, the compartments would
> have been created at registration time, not when A and B start
> exchanging INVITEs.
> 
> Cheers,
> 
> Gonzalo
> 
> Dikla Dror wrote:
>  > Hi,
>  >
>  > I've sent a question concerning chapter 9 in
>  > draft-ietf-rohc-sigcomp-sip-07 few weeks ago, but got no answer yet.
>  >
>  > I would appreciate any feedback to the following issue (I've turned my
> 
>  > question into a simpler scenario):
>  >
>  > 
>  >
>  > According to chapter 9, I might encounter imbalanced compartments at 2
> 
>  > different communicating endpoints in the following scenario:
>  >
>  > 
>  >
>  > This scenario includes 2 endpoints (A, B), communicating over TCP.
>  >
>  > 
>  >
>  >                                                
>  > A                                                          B
>  >
>  >                                                 |              (1)
> 
>  > INVITE                          |
>  >
>  >           Create Compartment (A1)
>  > |--------------------------------------------------------->| Create
>  > Compartment (B1)
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                 |               (2)
> 200
>  > OK                             |
>  >
>  >                                                
>  > |<---------------------------------------------------------| Use
>  > Compartment (B1)
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                 |              (3)
> 
>  > INVITE                          |
>  >
>  >           Create Compartment (A2)
>  > |<---------------------------------------------------------| Use
>  > Compartment (B1)
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                
>  > |                                                           |
>  >
>  >                                                             And so
> on...
>  >
>  >           
>  >
>  > As you can see endpoint A is sending an INVITE (1) toward B,
> specifying
>  > its local urn (A's urn). However A doesn't know yet B's urn, thus it
>  > creates a local compartment (A1), related to the INVITE outgoing
>  > connection.
>  >
>  > Now B:
>  >
>  > -          Responds the first INVITE with 200 OK (2), related to
>  > compartment (B1)
>  >
>  > -          Sends an outgoing INVITE (3) to A, related to compartment
>  > (B1). This (3) INVITE includes B's urn.
>  >
>  > 
>  >
>  > However, upon receiving (3) INVITE, endpoint A is not aware of the
>  > relation between B's urn and the first INVITE (1). Thus, A will
> maintain
>  > 2 different compartments - (A1) and (A2) for these 2 sessions while B
>  > will maintain only one compartment (B1). This will lead to
> inconsistency
>  > within the SigComp mechanism.
>  >
>  > 
>  >
>  >  How can I solve this asymmetry according to the draft?
>  >
>  > 
>  >
>  > Thanks,
>  >
>  > Dikla.
>  >
>  >
>  >
> ------------------------------------------------------------------------
>  >
>  > _______________________________________________
>  > Rohc mailing list
>  > Rohc@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/rohc
> 
> 


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



From rohc-bounces@ietf.org Wed Aug 29 16:34:52 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUDr-00025h-Hg; Wed, 29 Aug 2007 16:33:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQTwr-0000Iw-SY; Wed, 29 Aug 2007 16:15:35 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IQTwq-0006al-N8; Wed, 29 Aug 2007 16:15:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 8517C328BD;
	Wed, 29 Aug 2007 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IQTwM-0004Cp-CT; Wed, 29 Aug 2007 16:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IQTwM-0004Cp-CT@stiedprstage1.ietf.org>
Date: Wed, 29 Aug 2007 16:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-ikev2-extensions-hcoipsec-03.txt 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

--NextPart

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

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

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ikev2-extensions-hcoipsec-03.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-03.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-03.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-8-29152826.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-8-29152826.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 Wed Aug 29 16:47:47 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUQK-0000B5-4i; Wed, 29 Aug 2007 16:46:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUPp-0008DY-8C; Wed, 29 Aug 2007 16:45:31 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQUPo-0003LA-Oz; Wed, 29 Aug 2007 16:45:29 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id D2E532AC84;
	Wed, 29 Aug 2007 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IQTwM-0004DB-KA; Wed, 29 Aug 2007 16:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IQTwM-0004DB-KA@stiedprstage1.ietf.org>
Date: Wed, 29 Aug 2007 16:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-ipsec-extensions-hcoipsec-00.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		: IPsec Extensions to Support Robust Header Compression over IPsec (RoHCoIPsec)
	Author(s)	: E. Ertekin, et al.
	Filename	: draft-ietf-rohc-ipsec-extensions-hcoipsec-00.txt
	Pages		: 9
	Date		: 2007-8-29
	
   Integrating RoHC with IPsec (RoHCoIPsec) offers the combined benefits
   of IP security services and efficient bandwidth utilization.  Before
   this can be realized, however, several extensions to the Security
   Policy Database (SPD), the Security Association Database (SAD), and
   the IPsec process are required.  This document describes the IPsec
   extensions required to support RoHCoIPsec.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ipsec-extensions-hcoipsec-00.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-ipsec-extensions-hcoipsec-00.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-ipsec-extensions-hcoipsec-00.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-8-29154610.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-ipsec-extensions-hcoipsec-00.txt

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

Content-Type: text/plain
Content-ID: <2007-8-29154610.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 Wed Aug 29 16:47:52 2007
Return-path: <rohc-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUQJ-0000Al-RT; Wed, 29 Aug 2007 16:45:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUPp-0008DX-80; Wed, 29 Aug 2007 16:45:31 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQUPo-0003L9-Oy; Wed, 29 Aug 2007 16:45:29 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id AAC6F2AC7F;
	Wed, 29 Aug 2007 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IQTwM-0004Cm-Bh; Wed, 29 Aug 2007 16:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IQTwM-0004Cm-Bh@stiedprstage1.ietf.org>
Date: Wed, 29 Aug 2007 16:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-hcoipsec-06.txt 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

--NextPart

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

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

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-hcoipsec-06.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-06.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-06.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-8-29152659.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-8-29152659.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--




