Re: [rohc] One DOubt Regarding the ROHC-TCP
Klaus Warnke <klaus.warnke@acticom.de> Mon, 27 July 2009 11:55 UTC
Return-Path: <klaus.warnke@acticom.de>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D0173A6C05 for <rohc@core3.amsl.com>; Mon, 27 Jul 2009 04:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level:
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[AWL=0.899, BAYES_00=-2.599, J_CHICKENPOX_83=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHpxkrDCFBIv for <rohc@core3.amsl.com>; Mon, 27 Jul 2009 04:55:42 -0700 (PDT)
Received: from mail.acticom-networks.com (mail.acticom-networks.com [87.106.254.214]) by core3.amsl.com (Postfix) with ESMTP id 7670C3A63EB for <rohc@ietf.org>; Mon, 27 Jul 2009 04:55:41 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.acticom-networks.com (Postfix) with ESMTP id DD7421C00428; Mon, 27 Jul 2009 13:55:42 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at acticom-networks.com
Received: from mail.acticom-networks.com ([127.0.0.1]) by localhost (mail.acticom-networks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cVTuCVDyztko; Mon, 27 Jul 2009 13:55:35 +0200 (CEST)
Received: from godfather.bln.acticom.de (mail.oosoft.net [212.99.204.33]) by mail.acticom-networks.com (Postfix) with ESMTP id B62351C00429; Mon, 27 Jul 2009 13:55:35 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by godfather.bln.acticom.de (Postfix) with ESMTP id CF151F3ADA; Mon, 27 Jul 2009 13:55:34 +0200 (CEST)
X-Virus-Scanned: amavisd-new at bln.acticom.de
Received: from godfather.bln.acticom.de ([127.0.0.1]) by localhost (godfather.bln.acticom.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBtCtiY2eJor; Mon, 27 Jul 2009 13:55:32 +0200 (CEST)
Received: from [192.168.33.27] (tornado.bln.acticom.de [192.168.33.27]) by godfather.bln.acticom.de (Postfix) with ESMTP id 2BF3FF3AD7; Mon, 27 Jul 2009 13:55:32 +0200 (CEST)
Message-ID: <4A6D95B4.7080504@acticom.de>
Date: Mon, 27 Jul 2009 13:55:32 +0200
From: Klaus Warnke <klaus.warnke@acticom.de>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Ganesh <ganeshbabukamma@gmail.com>
References: <adc9dae40907270400y2a860657p156c8e620b4264df@mail.gmail.com> <adc9dae40907270401i7e3e84dcv4fa2bc09e4770ea0@mail.gmail.com> <4A6D8DCD.8090604@acticom.de> <adc9dae40907270431s62756664s92b999a6aa71d98d@mail.gmail.com>
In-Reply-To: <adc9dae40907270431s62756664s92b999a6aa71d98d@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org
Subject: Re: [rohc] One DOubt Regarding the ROHC-TCP
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 11:55:43 -0000
Ganesh wrote: > Klaus Warnke, > so ur mentioning that when the negotiation is happening between > compressor and decompressor, it has to be done based on each profile, > not on version based, > i.e it can be only RTP profile (0x101) for version 1 and all other > profiles,UDP, ESP can be version 0 etc?? Yes, I think so. Maybe it makes no sense to mix profile versions, but I think the "server" version should offer both versions, and the "client" version maybe support the RFC3095 or RoHCv2 versions of the profiles. > is it the efficient way of doing that one, for mobile implementation > for 3gpp based things, as their is constrains on memory and processing > resources.. > In my opinion, if both versions are activated but for different > profiles, there wont be problem for Network nodes, as there is not > constraint on memory or processing resources. Sorry, but I can't make a statement about that. > > Pls comment on the doubts i have. > > > Thanks & Regards > Ganesh br Klaus Warnke > . > > > > > > 2009/7/27 Klaus Warnke <klaus.warnke@acticom.de > <mailto:klaus.warnke@acticom.de>> > > Ganesh, > > the version of profile used, is negotiated for every profile > independent, not for all profiles together. For the TCP profile > only one version exist (yet). Therefore the profile has the > identifier 0x0006. For IP/UDP/RTP two version exist: > > RFC3905: 0x0001 > RFC5225: 0x0101 > > The upper octet is the version number, the lower the profile > number itself. Because while compression and de-compression only > one lower octet is send, the version has to be negotiation first. > It is a little bit confusing, that for the TCP profile the > version number is 0, but for the TCP profile only a on the RoHC > FN definition exists. If it makes sense to mix profiles, using > the RTP profile version 0 from RFC3095 and UPD version 1 defined > in RoHC FN, I don't know. But it is possible from my point of view. > > br > Klaus Warnke > > Ganesh wrote: > > Hi all, THe RFC 4996, is more inclined to ROHCV2 profiles, but > the profile number is defined as 0x006 (version 1), as per the > RFC 5225, if we have multiple variants of ROHC versions, then > the ROHC compressor and decompressor after negotiation has to > use only one version, if version 2 is selected, then how the > TCP packets will be compressed?? > Can any one please reply to the Question?? > > > > Thanks & Regards, > Ganesh Babu Kamma > > ------------------------------------------------------------------------ > > _______________________________________________ > Rohc mailing list > Rohc@ietf.org <mailto:Rohc@ietf.org> > https://www.ietf.org/mailman/listinfo/rohc > >
- [rohc] One DOubt Regarding the ROHC-TCP Ganesh
- Re: [rohc] One DOubt Regarding the ROHC-TCP Klaus Warnke
- Re: [rohc] One DOubt Regarding the ROHC-TCP Ganesh
- Re: [rohc] One DOubt Regarding the ROHC-TCP Klaus Warnke
- Re: [rohc] One DOubt Regarding the ROHC-TCP Robert Stangarone