[AVT] Proposed change to Enhanced CRTP
Tmima Koren <tmima@cisco.com> Sat, 12 July 2003 06:46 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27509 for <avt-archive@odin.ietf.org>; Sat, 12 Jul 2003 02:46:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bE96-0006Ti-B4 for avt-archive@odin.ietf.org; Sat, 12 Jul 2003 02:46:14 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6C6kCOK024900 for avt-archive@odin.ietf.org; Sat, 12 Jul 2003 02:46:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bE8u-0006Sn-Kw; Sat, 12 Jul 2003 02:46:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bBIs-0002L5-Fo for avt@optimus.ietf.org; Fri, 11 Jul 2003 23:44:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05075 for <avt@ietf.org>; Fri, 11 Jul 2003 23:44:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bBIq-0007YP-00 for avt@ietf.org; Fri, 11 Jul 2003 23:44:04 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by ietf-mx with esmtp (Exim 4.12) id 19bBIp-0007Xv-00 for avt@ietf.org; Fri, 11 Jul 2003 23:44:03 -0400
Received: from tmima-w2k01.cisco.com (rtp-vpn1-408.cisco.com [10.82.225.152]) by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h6C3hM0s005010; Fri, 11 Jul 2003 23:43:23 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030711182950.0303f2a8@mira-sjcm-2.cisco.com>
X-Sender: tmima@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 11 Jul 2003 20:41:24 -0700
To: Stephen Casner <casner@acm.org>, avt@ietf.org
From: Tmima Koren <tmima@cisco.com>
Cc: RFC Editor <rfc-editor@rfc-editor.org>, geevjohn@hotmail.com, brucet@cisco.com, pruddy@cisco.com, Allison Mankin <mankin@psg.com>, Jon Peterson <jon.peterson@neustar.biz>, csp@csperkins.org, magnus.westerlund@era.ericsson.se, Tmima Koren <tmima@cisco.com>
In-Reply-To: <20030710152138.H4360-100000@oak.packetdesign.com>
References: <4.3.2.7.2.20030703143001.02a60310@mira-sjcm-2.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_25267062==_.ALT"
Subject: [AVT] Proposed change to Enhanced CRTP
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
We'd like to propose a change to the Enhanced CRTP draft, draft-ietf-avt-crtp-enhance-07.txt http://www.ietf.org/internet-drafts/draft-ietf-avt-crtp-enhance-07.txt One of the enhancements is to add a Headers Checksum (HDRCKSUM) when UDP checksum is not present (see section 2.2). The UDP checksum is used by the decompressor to periodically validate the reconstructed packets. When not present, a HDRCKSUM may be inserted by the compressor replacing the missing UDP checksum. The decompressor removes the HDRCKSUM after validating the reconstructed packet. Currently the HDRCKSUM covers the pseudo-IP header, the UDP header and the fixed part of the RTP header (first 12 bytes). Those are the only parts of the reconstructed packet that can be validated by the HDRCKSUM. The CSRC list is not included in the HDRCKSUM. We propose to include the CSRC list in the HDRCKSUM since the CSRC list is part of the header compression context. The CSRC list is stored at the decompressor context and inserted to the restored packets. If the HDRCKSUM does not cover the CSRC list and the CSRC list at the decompressor is errored, a bad CSRC list will be restored into multiple packets until the CSRC list changes and is resent by the compressor as an update. If the HDRCKSUM covers the CSRC list, an error in the CSRC list will be caught early and corrected. When there is a change in the CSRC list, the CSRC list is sent as an update to the context. The CSRC list should be treated in the same way as the other context updating changes and be included in the HDRCKSUM. On the other hand, adding the CSRC list to the HDRCKSUM requires more processing calculating the HDRCKSUM. Also if the accuracy of the CSRC list is not crucial and the CSRC list is included in the HDRCKSUM, then an error in the CSRC list will result in dropping a few packets while the contexts are getting synchronized. The proposed change to the text is as follows: Old: The HDRCKSUM is calculated in the same way as a UDP checksum except that it does not cover all of the UDP data. That is, the HDRCKSUM is the 16-bit one's complement of the one's complement sum of the pseudo-IP header (as defined for UDP), the UDP header, and the first 12 bytes of the UDP data which are assumed to hold the fixed part of an RTP header. The extended part of the RTP header and the RTP data will not be included in the HDRCKSUM. New: The HDRCKSUM is calculated in the same way as a UDP checksum except that it does not cover all of the UDP data. That is, the HDRCKSUM is the 16-bit one's complement of the one's complement sum of the pseudo-IP header (as defined for UDP), the UDP header, the first ^^^^ 12 bytes of the UDP data which are assumed to hold the fixed part of an RTP header, and the CSRC list. ^^^^^^^^^^^^^^^^^^^ The extended part of the RTP header beyond the CSRC list and the RTP data ^^^^^^^^^^^^^^^^^^^^ will not be included in the HDRCKSUM.
- [AVT] Proposed change to Enhanced CRTP Tmima Koren
- [AVT] Re: Proposed change to Enhanced CRTP Stephen Casner