Re: [rohc] Add-CID and large_CID
Carsten Bormann <cabo@tzi.org> Tue, 21 July 2009 14:31 UTC
Return-Path: <cabo@tzi.org>
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 177913A6C6C for <rohc@core3.amsl.com>; Tue, 21 Jul 2009 07:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 fZdiylt31vTP for <rohc@core3.amsl.com>; Tue, 21 Jul 2009 07:31:15 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id F23F33A68DD for <rohc@ietf.org>; Tue, 21 Jul 2009 07:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id n6LEV4iB025222; Tue, 21 Jul 2009 16:31:04 +0200 (CEST)
Received: from wlan-client-342.informatik.uni-bremen.de (wlan-client-342.informatik.uni-bremen.de [134.102.117.94]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id A935DBC92; Tue, 21 Jul 2009 16:31:04 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
To: cai.wei2@zte.com.cn
In-Reply-To: <OFDEEFA30A.BFFC603A-ON482575FA.003EF748-482575FA.004082EC@zte.com.cn>
References: <OFDEEFA30A.BFFC603A-ON482575FA.003EF748-482575FA.004082EC@zte.com.cn>
Message-Id: <325C91BB-C25A-4204-ACE4-9F5A0A043C18@tzi.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 21 Jul 2009 16:31:03 +0200
X-Mailer: Apple Mail (2.935.3)
Cc: rohc@ietf.org
Subject: Re: [rohc] Add-CID and large_CID
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: Tue, 21 Jul 2009 14:31:19 -0000
RFC 4995, section 5.2.1.3:
When the ROHC channel is configured with a large CID space:
o The large CID is always present and is represented using the
encoding scheme of Section 5.3.2, limited to two octets. In
this case, the Header starts with a packet type indication.
So no, there cannot be an Add-CID octet there in this case; don't send
them.
While there may not be a technical problem for a decopressor in
accepting an Add-CID octet in large-CID mode, it is not quite clear
what that means, there is no need, and this goes beyond any reasonable
concept of robustness.
Gruesse, Carsten
- Re: [rohc] Add-CID and large_CID Klaus Warnke
- [rohc] Add-CID and large_CID cai.wei2
- Re: [rohc] Add-CID and large_CID Carsten Bormann