[rohc] Re: Review of draft-bormann-rohc-over-802-00.txt
Carsten Bormann <cabo@tzi.org> Mon, 29 November 2004 13:44 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 IAA20455 for <rohc-web-archive@ietf.org>; Mon, 29 Nov 2004 08:44:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYluA-0001Q4-Gt for rohc-web-archive@ietf.org; Mon, 29 Nov 2004 08:49:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYllP-0007ei-OM; Mon, 29 Nov 2004 08:40:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYlfb-0006Dn-Fh for rohc@megatron.ietf.org; Mon, 29 Nov 2004 08:34:23 -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 IAA19387 for <rohc@ietf.org>; Mon, 29 Nov 2004 08:34:22 -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 1CYlkS-00018h-RE for rohc@ietf.org; Mon, 29 Nov 2004 08:39:25 -0500
Received: from [IPv6:::1] (imh [134.102.224.4]) by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id iATDY44R028135; Mon, 29 Nov 2004 14:34:05 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 29 Nov 2004 14:34:02 +0100
To: "'rohc@ietf.org'" <rohc@ietf.org>, Stephen McCann <stephen.mccann@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: Mark West <mark.a.west@roke.co.uk>, Andrew McDonald <andrew.mcdonald@roke.co.uk>, 'Bernard Aboba' <aboba@INTERNAUT.COM>, Carsten Bormann <cabo@tzi.org>, Robert Hancock <robert.hancock@roke.co.uk>, Eleanor Hepworth <eleanor.hepworth@roke.co.uk>
Subject: [rohc] Re: 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.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
On Nov 29 2004, at 12:28 Uhr, McCann, Stephen wrote: > Carsten, > I've only had a short time to quickly look at your I-D, but > one thing that I did want to ask, is the applicability of this > scheme to both IEEE 802.5 and 802.17, in that these are not > ethernet based systems. > > I know that the 'iporpr' wg is doing some work in this area, but > I just wondered if your I-D only refers to 802 media which support > the ethernet type? Stephen, thank you for that comment; I've completely stopped thinking about rings. While the discussion is framed in terms of the more visible 802 standards, the intention indeed is to cover all 802-style L2s that commonly might be concatenated by bridge-like L2-only units (including even the non-802 FDDI, as this may form part of a bridged L2 path that leads to a wireless access point). Since the solution (subset) proposed uses an LLC-style length field, I believe it does apply to 802.5 (but then I've never actually worked with 802.5, so I'm not sure). In particular, I don't know how source-routing would interact with any negotiation/announce protocol. I don't know enough about 802.17 to comment (I was under the impression that 802.17 is ethertype-based, though). > PS : I have the same problems on the IEEE 802 side with IEEE 802.21 How do these problems manifest themselves in 802.21? Gruesse, Carsten _______________________________________________ Rohc mailing list Rohc@ietf.org https://www1.ietf.org/mailman/listinfo/rohc
- [rohc] Review of draft-bormann-rohc-over-802-00.t… Bernard Aboba
- [rohc] Re: Review of draft-bormann-rohc-over-802-… Carsten Bormann
- Re: [rohc] Re: Review of draft-bormann-rohc-over-… Pedro Fortuna
- Re: [rohc] Re: Review of draft-bormann-rohc-over-… Pedro Fortuna
- Re: [rohc] Re: Review of draft-bormann-rohc-over-… Carsten Bormann
- Re: [rohc] Review of draft-bormann-rohc-over-802-… Carsten Bormann
- Re: [rohc] Re: Review of draft-bormann-rohc-over-… Pedro Fortuna
- Re: [rohc] question about draft-bormann-rohc-over… Ana Minaburo
- Re: [rohc] question about draft-bormann-rohc-over… Pedro Fortuna
- Re: [rohc] question about draft-bormann-rohc-over… Ana Minaburo
- Re: [rohc] question about draft-bormann-rohc-over… Pedro Fortuna
- Re: [rohc] question about draft-bormann-rohc-over… Carsten Bormann
- Re: [rohc] question about draft-bormann-rohc-over… Pedro Fortuna
- Re: [rohc] question about draft-bormann-rohc-over… Carsten Bormann