RE: [rohc] question about rohc tcp profile
"Kristofer Sandlund \(LU/EAB\)" <kristofer.sandlund@ericsson.com> Fri, 01 December 2006 07:43 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gq33g-0007ne-RV; Fri, 01 Dec 2006 02:43:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gq33f-0007nW-4T for rohc@ietf.org; Fri, 01 Dec 2006 02:43:43 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gq33X-0000Qh-KV for rohc@ietf.org; Fri, 01 Dec 2006 02:43:43 -0500
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id E98BF1014; Fri, 1 Dec 2006 08:43:32 +0100 (CET)
Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Dec 2006 08:43:32 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] question about rohc tcp profile
Date: Fri, 01 Dec 2006 08:43:32 +0100
Message-ID: <A91F30A632473A47B40C18D2B107CA6F0351994B@esealmw105.eemea.ericsson.se>
In-Reply-To: <20061130132905.48281.qmail@web27614.mail.ukl.yahoo.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rohc] question about rohc tcp profile
Thread-Index: AccUg267SHdv+0pMT3W530fY6/QrmQAmF07A
From: "Kristofer Sandlund (LU/EAB)" <kristofer.sandlund@ericsson.com>
To: ben ata ibtissem <ibtissemata@yahoo.fr>, rohc@ietf.org
X-OriginalArrivalTime: 01 Dec 2006 07:43:32.0699 (UTC) FILETIME=[668AD2B0:01C7151C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
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, just adding some more information to what Mark has already said. If you're implementing ROHC-TCP, my most important advice would be: a) If you are starting from scratch: Immediately shred and delete all copies of RFC3095 that you have lying around to confusing framework with profiles. Implement the framework from the ROHC framework draft (see below) b) If you already have a RFC3095 implementation: Immediately shred and delete all copies of RFC3095 that you have lying around to avoid confusing framework with profiles. Re-use the framework implementation as-is. So in either case, reading RFC3095 will only cause you grief (it already has since you're asking about R-mode). ROHC-TCP does not have any _normative_ reference to RFC3095 so there is no reason to read that one when implementing the ROHC-TCP profile. The only documents you need to read are ROHC-TCP, ROHC-FN and ROHC Framework: http://www.ietf.org/internet-drafts/draft-ietf-rohc-rfc3095bis-framework-04.txt http://tools.ietf.org/wg/rohc/draft-ietf-rohc-formal-notation/draft-ietf-rohc-formal-notation-12.txt http://tools.ietf.org/wg/rohc/draft-ietf-rohc-tcp/draft-ietf-rohc-tcp-14.txt Regarding uni/bi-directional operation of the ROHC-TCP profile, the logic is quite clearly stated in sections 4.2.2, 5.2.1, 5.2.1.2 and 5.3.2 of the tcp-14 draft, so you should read those. BR, Kristofer ben ata ibtissem <mailto:ibtissemata@yahoo.fr> wrote on den 30 november 2006 14:29 : > hello, > I implement the profile rohc tcp of rohc ,but i have > one probleme, in fact for rohc to transit from one > mode to an other i.e for example from unidirectionnel > mode to o mode or R mode, it use the feedbacks and > especially the field mode in witch the decompressor > indicate what mode he wish to use , but for the > feedbacks of tcp this field(mode field ) don't exist > so it can't transit from one mode to an other , to my > opinion since the tcp is usally bidirectionnel and all > is acquitted so the profile rohc tcp we allways be in > the R mode > the question is:is it, my opinion, true or not, and if > it is true , we wil have an other problem in fact rohc > always start in the Unidirectionnel mode so how can i > do i.e can i initialise the mode directly in the R > mode or i can't? > thank you > > > > > > > ______________________________________________________________ > _____________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau > Yahoo! Mail et son interface révolutionnaire. > http://fr.mail.yahoo.com > > _______________________________________________ > Rohc mailing list > Rohc@ietf.org > https://www1.ietf.org/mailman/listinfo/rohc _______________________________________________ Rohc mailing list Rohc@ietf.org https://www1.ietf.org/mailman/listinfo/rohc
- [rohc] question about rohc tcp profile ben ata ibtissem
- RE: [rohc] question about rohc tcp profile Finking, Robert
- [rohc] question about rohc tcp profile ben ata ibtissem
- RE: [rohc] question about rohc tcp profile West, Mark
- RE: [rohc] question about rohc tcp profile Kristofer Sandlund (LU/EAB)