Re: [rohc] Constant IP-ID in the RTP Profile(0x0001)
Biplab Sarkar <bsarkar@starentnetworks.com> Thu, 03 January 2008 11:47 UTC
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 1JAOYE-0005Ig-OU; Thu, 03 Jan 2008 06:47:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JAOYC-0005IW-Sm for rohc@ietf.org; Thu, 03 Jan 2008 06:47:52 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JAOYC-00059E-Dq for rohc@ietf.org; Thu, 03 Jan 2008 06:47:52 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx0.starentnetworks.com (Postfix) with ESMTP id 8ACFA188032; Thu, 3 Jan 2008 06:47:48 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1]) by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23937-07; Thu, 3 Jan 2008 06:47:47 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com [10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP; Thu, 3 Jan 2008 06:47:47 -0500 (EST)
Received: from exchindia3.starentnetworks.com ([10.6.7.5]) by exchtewks1.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 3 Jan 2008 06:45:39 -0500
Received: from [10.6.7.67] ([10.6.7.67]) by exchindia3.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Jan 2008 17:15:35 +0530
Subject: Re: [rohc] Constant IP-ID in the RTP Profile(0x0001)
From: Biplab Sarkar <bsarkar@starentnetworks.com>
To: "Gangadharan G, TLS-Chennai" <Gangadharang@hcl.in>
In-Reply-To: <66E8AEE9980BB44CA5FCAD39EBA56AC60340B281@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
References: <66E8AEE9980BB44CA5FCAD39EBA56AC60340B281@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
Organization: Starent Networks
Date: Thu, 03 Jan 2008 17:17:59 +0530
Message-Id: <1199360879.23248.49.camel@INDBNG1172.bng.ind.starentnetworks.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.1
X-OriginalArrivalTime: 03 Jan 2008 11:45:35.0008 (UTC) FILETIME=[26EBD200:01C84DFE]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
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="===============1603174860=="
Errors-To: rohc-bounces@ietf.org
Hi Gangadharan, IP-ID can be over-written with the value of RTP-SN at the compressor before compression for all "un-fragmented" IPv4 packets. This will enhance the compression. Since IP-ID is used in IP fragmentation, we can basically ignore its real value for "un-fragmented" IP packets. Thanks & Regards, Biplab Sarkar On Thu, 2008-01-03 at 17:07 +0530, Gangadharan G, TLS-Chennai wrote: > Hi All, > > > > In the Linux Suse 10.1 machine, the value of the IP-ID in the IPv4 > header is always zero (i.e., constant) in the entire IP datagrams. > > The IP-ID Encoding, as per RFC 3095, of the RTP profile doesn’t handle > this case (constant IP-ID). > > > > Also this issue had been discussed in the mailing list. > > http://www1.ietf.org/mail-archive/web/rohc/current/msg01502.html > > > > When I searched in the Internet, I found few proposed solutions (yet > to read them). > > (draft-ietf-rohc-rfc3095bis-improvements-03.txt, > draft-kapoor-rohc-rtp-new-requirements-00.txt, > > RFC 3643 -- A Compression Profile for IP) > > > > Please let me know the solution/standard that everyone is following > for this issue in the RTP Profile. > > > > Thanks, > > Gangadharan > > > > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > It shall not attach any liability on the originator or HCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily > reflect the opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, > modification, distribution and / or publication of > this message without the prior written consent of the author of this > e-mail is strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. Before opening any mail and > attachments please check them for viruses and defect. > > ----------------------------------------------------------------------------------------------------------------------- > > > _______________________________________________ > 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] Constant IP-ID in the RTP Profile(0x0001) Gangadharan G, TLS-Chennai
- Re: [rohc] Constant IP-ID in the RTP Profile(0x00… Biplab Sarkar
- RE: [rohc] Constant IP-ID in the RTP Profile(0x00… Kristofer Sandlund
- RE: [rohc] Constant IP-ID in the RTP Profile(0x00… Biplab Sarkar
- RE: [rohc] Constant IP-ID in the RTP Profile(0x00… Kristofer Sandlund