RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-framework-02.txt
"Sarkar, Biplab" <bsarkar@starentnetworks.com> Tue, 17 October 2006 18:07 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtLk-00016Z-89; Tue, 17 Oct 2006 14:07:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtLj-00016T-Sx for rohc@ietf.org; Tue, 17 Oct 2006 14:07:35 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZtLg-0008VX-8X for rohc@ietf.org; Tue, 17 Oct 2006 14:07:35 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx0.starentnetworks.com (Postfix) with ESMTP id 1400890067 for <rohc@ietf.org>; Tue, 17 Oct 2006 14:07:28 -0400 (EDT)
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 24309-10 for <rohc@ietf.org>; Tue, 17 Oct 2006 14:07:27 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com [12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP for <rohc@ietf.org>; Tue, 17 Oct 2006 14:07:27 -0400 (EDT)
Received: from exchindia3.starentnetworks.com ([10.6.0.5]) by exchtewks1.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 17 Oct 2006 14:07:26 -0400
Content-class: urn:content-classes:message
Subject: RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-framework-02.txt
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Oct 2006 23:37:22 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <69FADB84C90B1248A7DE59422771FA0C2F8B0D@exchindia3.starentnetworks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-framework-02.txt
Thread-Index: Acbot54l/opxYgmoQw2Uz1VghUnrLgJWuyaQ
From: "Sarkar, Biplab" <bsarkar@starentnetworks.com>
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
X-OriginalArrivalTime: 17 Oct 2006 18:07:26.0972 (UTC) FILETIME=[1A84D3C0:01C6F217]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: rohc@ietf.org
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
L-E, I have gone through the document draft-ietf-rohc-rfc3095bis-framework-02.txt. The document looks fine. I have a few questions which I am putting down below. [1] 5.1.2 - I see the mention of the per-channel parameters for link layer negotiations. The attribute "FEEDBACK_FOR" seems to be a new one which is not there even in RFC3095 or in RFC3759. I believe it is an implicit requirement which might have evolved from RFC3759, but this requires more explanation. - Can we get some more details about the range of the values that would be negotiated here? - BTW are we planning to define some guidelines as to how the under layer is going to define each ROHC channel? - Is a non negative integer enough to capture this feedback channel? - In case multiple feedback channels shares one channel, how will the compressor de-multiplex the feedback pkts? [2] Do we need to capture the general behavior when CRC checks fails? I was wondering if it was right to ignore a S-NACK/NACK packet even though the CRC check fails? [RFC3095:5.7.6.4] Since the link was not good the decompressor went out of sync and was sending a S-NACK/NACK, Now the feedback pkt might get corrupted and the optional element CRC might force us to discard this pkt. I think we should ignore a feedback ACK and its subsequent context updating behavior if the CRC check fails. But a NACK/SNACK should be always accepted. [3] A general question. Why do we have both CRC-7 and CRC-8 algo? Why not just one of them? [4] Is there any strict need for all future variants of the rohc profiles to be back ward compatible? Since we are negotiating the entire 16-bit integer I don't see any direct need for that. Thanks Biplab -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Friday, October 06, 2006 1:20 AM To: i-d-announce@ietf.org Cc: rohc@ietf.org Subject: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-framework-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Robust Header Compression Working Group of the IETF. Title : The RObust Header Compression (ROHC) Framework Author(s) : L. Jonsson, et al. Filename : draft-ietf-rohc-rfc3095bis-framework-02.txt Pages : 37 Date : 2006-10-5 The RObust Header Compression (ROHC) protocol provides an efficient, flexible and future-proof header compression concept. It is designed to operate efficiently and robustly over various link technologies with different characteristics. The ROHC framework, along with a set of compression profiles, was initially defined in RFC 3095. To improve and simplify the ROHC specifications, this document explicitly defines the ROHC framework separately, and thus replaces the framework specification of RFC 3095. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rohc-rfc3095bis-framework -02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rohc-rfc3095bis-framework-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rohc-rfc3095bis-framework-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Rohc mailing list Rohc@ietf.org https://www1.ietf.org/mailman/listinfo/rohc
- [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-fram… Internet-Drafts
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Sarkar, Biplab
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rtp-impl-gu… Lars-Erik Jonsson (LU/EAB)
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Lars-Erik Jonsson (LU/EAB)
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Sarkar, Biplab
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Lars-Erik Jonsson (LU/EAB)
- [rohc] Reveiw - draft-ietf-rohc-rfc3095bis-framew… Carl Knutsson
- [rohc] RE: Reveiw - draft-ietf-rohc-rfc3095bis-fr… Lars-Erik Jonsson (LU/EAB)
- [rohc] Re: Reveiw - draft-ietf-rohc-rfc3095bis-fr… Carl Knutsson
- Re: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Magnus Westerlund
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Ghyslain Pelletier (LU/EAB)
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Lars-Erik Jonsson (LU/EAB)
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… pelle
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Ghyslain Pelletier (LU/EAB)
- RE: [rohc] I-D ACTION:draft-ietf-rohc-rfc3095bis-… Lars-Erik Jonsson (LU/EAB)