[rohc] Review of draft-bormann-rohc-over-802-00.txt

Bernard Aboba <aboba@internaut.com> Mon, 29 November 2004 12:56 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15291 for <rohc-web-archive@ietf.org>; Mon, 29 Nov 2004 07:56:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYl9N-0008Sm-8V for rohc-web-archive@ietf.org; Mon, 29 Nov 2004 08:01:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYkoK-0002ck-LC; Mon, 29 Nov 2004 07:39:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXqy3-0004lK-5E for rohc@megatron.ietf.org; Fri, 26 Nov 2004 20:01:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14629 for <rohc@ietf.org>; Fri, 26 Nov 2004 20:01:37 -0500 (EST)
Received: from outbound.mailhop.org ([63.208.196.171] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXr2Q-0008Eo-Hq for rohc@ietf.org; Fri, 26 Nov 2004 20:06:11 -0500
Received: from c-67-182-139-247.client.comcast.net ([67.182.139.247] helo=internaut.com) by outbound.mailhop.org with esmtpa (Exim 4.42) id 1CXqxv-000MVN-2a for rohc@ietf.org; Fri, 26 Nov 2004 20:01:32 -0500
Received: from localhost (aboba@localhost) by internaut.com (8.10.2/8.10.2) with ESMTP id iAR11TO31018 for <rohc@ietf.org>; Fri, 26 Nov 2004 17:01:30 -0800
Date: Fri, 26 Nov 2004 17:01:29 -0800
From: Bernard Aboba <aboba@internaut.com>
To: rohc@ietf.org
Message-ID: <Pine.LNX.4.56.0411261659040.30341@internaut.com>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="-1488819285-194129012-1101410422=:7703"
Content-ID: <Pine.LNX.4.56.0411261659041.30341@internaut.com>
X-Mail-Handler: MailHop Outbound by DynDNS.org
X-Originating-IP: 67.182.139.247
X-Report-Abuse-To: abuse@dyndns.org (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: aboba
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1fb4c76a9d88e8fb8b791f63f8d1b07f
X-Mailman-Approved-At: Mon, 29 Nov 2004 07:39:18 -0500
Subject: [rohc] Review of draft-bormann-rohc-over-802-00.txt
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>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: dd055ca905b7a8538e016a7989511901

Here's my review.  There may be some tricky issues to watch out for with
respect to negotiation of ROHC capabilities on IEEE 802 networks that
may make it difficult to achieve the desired level of uniformity.

Also, as noted by Mike Moreton:

"The IEEE RAC gets very upset about anyone using OUIs in a non-standard
way, so I doubt you'd get a lot of support for using the
locally administered or I/G bits to distinguish your frames.  However,
802.11 already uses a full LLC/SNAP header, so using such
a header would be fine for 802.11, and as you say elsewhere probably
wouldn't make a great deal of difference for 802.3.

I think the padding issue is interesting - it's funny how a drop-off in
the original Ethernet specification is still causing us
problems all these years later..."
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc