[rohc] Support of ROHC Piggyback Feedback in LTE
Karthik Balaguru <Karthik.Balaguru@lntinfotech.com> Thu, 25 June 2009 12:54 UTC
Return-Path: <Karthik.Balaguru@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 E67DD3A6B04 for <rohc@core3.amsl.com>; Thu, 25 Jun 2009 05:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.489
X-Spam-Level:
X-Spam-Status: No, score=-5.489 tagged_above=-999 required=5 tests=[AWL=1.110, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 pQxN7hS5mmi6 for <rohc@core3.amsl.com>; Thu, 25 Jun 2009 05:54:42 -0700 (PDT)
Received: from mail96.messagelabs.com (mail96.messagelabs.com [216.82.254.19]) by core3.amsl.com (Postfix) with SMTP id 1A34B3A6D92 for <rohc@ietf.org>; Thu, 25 Jun 2009 05:53:44 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Karthik.Balaguru@lntinfotech.com
X-Msg-Ref: server-13.tower-96.messagelabs.com!1245934302!39142218!1
X-StarScan-Version: 6.0.0; banners=lntinfotech.com,-,-
X-Originating-IP: [203.101.96.4]
Received: (qmail 25542 invoked from network); 25 Jun 2009 12:51:43 -0000
Received: from bangaloresmtp.lntinfotech.com (HELO bangaloresmtp.lntinfotech.com) (203.101.96.4) by server-13.tower-96.messagelabs.com with SMTP; 25 Jun 2009 12:51:43 -0000
Received: from Bangalore.lntinfotech.com ([172.28.0.3]) by bangaloresmtp.lntinfotech.com (Lotus Domino Release 7.0.3) with ESMTP id 2009062518233028-98701 ; Thu, 25 Jun 2009 18:23:30 +0530
To: rohc@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF4774DF8E.E95CB052-ON652575E0.0033DFE9-652575E0.0046A641@lntinfotech.com>
From: Karthik Balaguru <Karthik.Balaguru@lntinfotech.com>
Date: Thu, 25 Jun 2009 18:21:40 +0530
X-MIMETrack: Serialize by Router on BANGALORE/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/25/2009 06:21:41 PM, Serialize complete at 06/25/2009 06:21:41 PM, Itemize by SMTP Server on BangaloreSMTP/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/25/2009 06:23:30 PM, Serialize by Router on BangaloreSMTP/LNTINFOTECH(Release 7.0.3|September 26, 2007) at 06/25/2009 06:23:31 PM, Serialize complete at 06/25/2009 06:23:31 PM
Content-Type: multipart/alternative; boundary="=_alternative 0046A632652575E0_="
Subject: [rohc] Support of ROHC Piggyback Feedback in LTE
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: Thu, 25 Jun 2009 12:54:43 -0000
Hi, Need clarifications on ROHC Piggyback feedback support in LTE. LTE standrad states that PDCP Control Packet (Feedback) shall not be ciphered (Reference - 3GPP TS 36.323 V8.5.0, Section 5.5.4 ) and PDCP data packets shall be ciphered by configured algorithm (Reference - Section 5.2.1, 5.2.2 ) . In case of Piggyback feedback packet, DataPacket will be attatched at the end of feedback packet. (RFC 3095 - Page no 43,44 & Section 5.2.2) 1. In LTE PDCP, If the Data Packet should be ciphered for these piggyback packets , then how will the Peer entity generate COUNT input for ciphering algorithm as PDCP-SN is not available ? 2. In LTE PDCP, Can the data Packet be sent without ciphering in Piggyback Feedback packets ? Further reference w.r.t RFC 3095 - Page no 44 d) To allow piggybacking, 5), it is possible to deduce the length of feedback information by examining the first few octets of the feedback. This allows the decompressor to pass piggybacked feedback information to the associated same-side compressor without understanding its format. The length information decouples the decompressor from the compressor in the sense that the decompressor can process the compressed header immediately without waiting for the compressor to hand it back after parsing the feedback information. Kindly clarify regarding the support of RoHC piggyback Feedback in LTE ? Thx in advans, Karthik Balaguru ______________________________________________________________________
- [rohc] Support of ROHC Piggyback Feedback in LTE Karthik Balaguru
- Re: [rohc] Support of ROHC Piggyback Feedback in … pelle
- Re: [rohc] Support of ROHC Piggyback Feedback in … Karthik Balaguru
- [rohc] SN Encoding clarification Karthik Balaguru
- Re: [rohc] SN Encoding clarification Ang Way Chuang
- Re: [rohc] SN Encoding clarification Karthik Balaguru
- Re: [rohc] SN Encoding clarification Ang Way Chuang