IETF Logo Mail Archive

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

Ana Minaburo <anacarolina.minaburo@enst-bretagne.fr> Wed, 23 March 2005 22:40 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 RAA01521 for <rohc-web-archive@ietf.org>; Wed, 23 Mar 2005 17:40:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DEEcC-0001vW-4i for rohc-web-archive@ietf.org; Wed, 23 Mar 2005 17:46:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DEEWG-0001iM-KJ; Wed, 23 Mar 2005 17:40:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DE5XN-0000W4-Bo for rohc@megatron.ietf.org; Wed, 23 Mar 2005 08:04:41 -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 IAA10211 for <rohc@ietf.org>; Wed, 23 Mar 2005 08:04:40 -0500 (EST)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DE5cp-0005Nn-K5 for rohc@ietf.org; Wed, 23 Mar 2005 08:10:21 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id j2ND4Gg26455; Wed, 23 Mar 2005 14:04:16 +0100
Received: from [193.52.74.146] (pc-rsm-01 [193.52.74.146]) by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with ESMTP id j2ND4FGw018027; Wed, 23 Mar 2005 14:04:16 +0100 (MET)
Message-ID: <42416950.4090701@enst-bretagne.fr>
Date: Wed, 23 Mar 2005 14:04:16 +0100
From: Ana Minaburo <anacarolina.minaburo@enst-bretagne.fr>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] question about draft-bormann-rohc-over-802-00.txt
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk> <550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org> <db95d40c0412071707b0c2e1b@mail.gmail.com> <C7666E10-48EE-11D9-B3CF-000A95DC4DB6@tzi.org> <db95d40c04122008155a0416fe@mail.gmail.com> <d1ba43fa626fb030b44ff955e33c3364@tzi.org>
In-Reply-To: <d1ba43fa626fb030b44ff955e33c3364@tzi.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 23 Mar 2005 17:40:07 -0500
Cc: "rohc@ietf.org" <rohc@ietf.org>, Francis Dupont <Francis.Dupont@enst-bretagne.fr>, ayed samiha <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: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

Hi!

After reading your draft of ROHC over 802, and looking at the LLC 
encapsulation,  I was wondering why do not use ROHC directly with the 
Ethernet header using a self describing padding?

Ana


>


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

v2.23.0 | Report a Bug | By Email