[rohc] Clarification Required regarding the Context Replication
Anil Maguluri <Anil.Maguluri@lntinfotech.com> Fri, 25 June 2010 12:09 UTC
Return-Path: <Anil.Maguluri@lntinfotech.com>
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 6F6183A67F6 for <rohc@core3.amsl.com>;
Fri, 25 Jun 2010 05:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.67
X-Spam-Level:
X-Spam-Status: No, score=-3.67 tagged_above=-999 required=5 tests=[AWL=-2.062,
BAYES_50=0.001, FS_REPLICA=0.994, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
RCVD_IN_DNSWL_MED=-4]
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 XrmszLop0SYj for
<rohc@core3.amsl.com>; Fri, 25 Jun 2010 05:09:47 -0700 (PDT)
Received: from mail96.messagelabs.com (mail96.messagelabs.com [216.82.254.19])
by core3.amsl.com (Postfix) with ESMTP id D553F3A6845 for <rohc@ietf.org>;
Fri, 25 Jun 2010 05:09:46 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Anil.Maguluri@lntinfotech.com
X-Msg-Ref: server-15.tower-96.messagelabs.com!1277467760!41859925!2
X-StarScan-Version: 6.2.4; banners=lntinfotech.com,-,-
X-Originating-IP: [203.101.96.8]
Received: (qmail 28999 invoked from network); 25 Jun 2010 12:09:54 -0000
Received: from unknown (HELO BLRINMSHTCAS02.bglrodc.lntinfotech.com)
(203.101.96.8) by server-15.tower-96.messagelabs.com with AES128-SHA
encrypted SMTP; 25 Jun 2010 12:09:54 -0000
Received: from blrinmsmbx01.bglrodc.lntinfotech.com ([169.254.1.177]) by
BLRINMSHTCAS02.bglrodc.lntinfotech.com ([172.28.0.83]) with mapi;
Fri, 25 Jun 2010 17:39:35 +0530
From: Anil Maguluri <Anil.Maguluri@lntinfotech.com>
To: "rohc@ietf.org" <rohc@ietf.org>
Date: Fri, 25 Jun 2010 17:39:13 +0530
Thread-Topic: Clarification Required regarding the Context Replication
Thread-Index: AcsUXzmYUn+tfTpBTrK0BygAELAaLA==
Message-ID: <903D13EA90218E43BA0881BC8B569C7D2317FF38@BLRINMSMBX01.bglrodc.lntinfotech.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_903D13EA90218E43BA0881BC8B569C7D2317FF38BLRINMSMBX01bgl_"
MIME-Version: 1.0
Cc: Anil Kumar Maguluri <anilmaguluri@gmail.com>
Subject: [rohc] Clarification Required regarding the Context Replication
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: Fri, 25 Jun 2010 12:09:56 -0000
Hi All, I am implementing the Context Replication mechanism for TCP (ROHCv2 Profile-6). Please clarify me whether my understanding is right or not. 1. When Base CID will be same as CID ? As per my understanding the scenario will be: All the CID's are used at the compressor and it received a new flow. At that time compressor will check which CID is idle, so that it can use that CID for the new flow instead of sending as Profile-4 or Profile-0 based on the supported profiles. a. Is my understanding is right? b. Is there any other scenario where Base CID = CID? c. Should I reset the compressor/decompressor context (Mode, State, Counters) if the Base CID = CID? As per my understanding, we should not reset the context (Mode, State, Counters). "RFC 4996, 6.1.1. Master Sequence Number (MSN): When the MSN is initialized, it SHOULD be initialized to a random value. The compressor should only initialize a new MSN for the initial IR or IR-CR packet sent for a CID that corresponds to a context that is not already associated with this profile. In other words, if the compressor reuses the same CID to compress many TCP flows one after the other, the MSN is not reinitialized but rather continues to increment monotonically. For context replication, the compressor does not use the MSN of the base context when sending the IR-CR packet, unless the replication process overwrites the base context (i.e., Base CID == CID). Instead, the compressor uses the value of the MSN if it already exists in the ROHC-TCP context being associated with the new flow (CID); otherwise, the MSN is initialized to a new value. " d. Should we start the Heuristics for the new flow if BCID = CID? As per my understanding, we should not start the Heuristics in case of BCID = CID, but we should do the Heuristics is BCID != CID? Is my understanding is right? Thanks for your support. Regards, Anil Kumar Maguluri ________________________________ This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. ______________________________________________________________________
- [rohc] Clarification Required regarding the Conte⦠Anil Maguluri