Re: [rohc] question about draft-bormann-rohc-over-802-00.txt

Carsten Bormann <cabo@tzi.org> Tue, 29 March 2005 20:10 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 PAA19960 for <rohc-web-archive@ietf.org>; Tue, 29 Mar 2005 15:10:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGN9X-0005sP-IJ for rohc-web-archive@ietf.org; Tue, 29 Mar 2005 15:17:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGN1V-0003H8-Lm; Tue, 29 Mar 2005 15:09:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGN1T-0003H3-7o for rohc@megatron.ietf.org; Tue, 29 Mar 2005 15:09:12 -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 PAA19830 for <rohc@ietf.org>; Tue, 29 Mar 2005 15:09:09 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGN8D-0005rD-Rd for rohc@ietf.org; Tue, 29 Mar 2005 15:16:11 -0500
Received: from [IPv6:::1] (imh [134.102.224.4]) by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id j2TK8tVo029554; Tue, 29 Mar 2005 22:08:56 +0200 (MEST)
In-Reply-To: <db95d40c05032908265269eef@mail.gmail.com>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk> <db95d40c0412071707b0c2e1b@mail.gmail.com> <C7666E10-48EE-11D9-B3CF-000A95DC4DB6@tzi.org> <db95d40c04122008155a0416fe@mail.gmail.com> <d1ba43fa626fb030b44ff955e33c3364@tzi.org> <42416950.4090701@enst-bretagne.fr> <db95d40c05032315243d47c7d7@mail.gmail.com> <29ed16a405032505371a35ee56@mail.gmail.com> <db95d40c0503251422528f89dc@mail.gmail.com> <a0a74cff0b622b0082d543bd111c9b65@tzi.org> <db95d40c05032908265269eef@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <779fa8f88fadaa3f168ff7ec228a2828@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] question about draft-bormann-rohc-over-802-00.txt
Date: Tue, 29 Mar 2005 22:08:55 +0200
To: Pedro Fortuna <pedro.fortuna@gmail.com>
X-Mailer: Apple Mail (2.619.2)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org, francis.dupont@enst-bretagne.fr, anacarolina.minaburo@enst-bretagne.fr, Carsten Bormann <cabo@tzi.org>, Laurent Toutain <Laurent.Toutain@enst-bretagne.fr>, ayed_samiha@yahoo.fr
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.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

On Mar 29 2005, at 18:26 Uhr, Pedro Fortuna wrote:

> Carsten, did you find any AP that allow the reception of LLC frames,
> but always send DIX frames when bridging to a different 802 link type?
> (e.g. receive a 802.11 frame with LLC and forward a 802.3 DIX frame)

No, we didn't see that behavior.
(Note that we did not use SNAP, in which case this behaviour would have 
been likely.)

> In my previous messages, I made the assumption (maybe an incorrect
> one) that most bridges would behave like this. But maybe there aren't
> any APs with this kind of behaviour. I didn't made any tests yet.

We certainly need to expand our tests.  Right now, we only have half a 
dozen or so types of access points available for testing.

However, it is clear that any AP *should* forward LLC frames just fine.
The point of the testing can only be to find out about the failure 
modes of deployed APs and to make sure ROHC-over-802 is robust to these 
failure modes.

Gruesse, Carsten


_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc