RE: [rohc] rohc over xxx?
"Dr. Carsten Bormann" <cabo@tzi.org> Mon, 04 March 2002 11:38 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19888 for <rohc-archive@odin.ietf.org>; Mon, 4 Mar 2002 06:38:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA22092; Mon, 4 Mar 2002 06:36:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA22033 for <rohc@optimus.ietf.org>; Mon, 4 Mar 2002 06:36:21 -0500 (EST)
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19849 for <rohc@ietf.org>; Mon, 4 Mar 2002 06:35:02 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3]) by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g24BQgI00967; Mon, 4 Mar 2002 12:26:42 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>, 'Wang Hui' <whui@mail.ustc.edu.cn>, rohc@ietf.org
Subject: RE: [rohc] rohc over xxx?
Date: Mon, 04 Mar 2002 12:26:41 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGOEKIHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <A943FD84BD9ED41193460008C791805003E31E6C@ESEALNT419.al.sw.ericsson.se>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit
> > [3] > > How to deal with the handover in the mobile ip? While the mobile node > > moving to another domain, how could the compression context in its old > > access router be moved to the new access router fast? > > This is not within the scope (charter) of ROHC. Let me add that context transfer is being discussed in the SEAMOBY WG, e.g.: draft-ietf-seamoby-context-transfer-problem-stat-04.txt There actually was a document on header compression context transfer, draft-kenward-seamoby-ct-rohc-reqs-00.txt, but this has been lying dormant for a while. Gruesse, Carsten _______________________________________________ Rohc mailing list Rohc@ietf.org https://www1.ietf.org/mailman/listinfo/rohc
- RE: [rohc] rohc over xxx? Lars-Erik Jonsson (EPL)
- RE: [rohc] rohc over xxx? Dr. Carsten Bormann
- RE: [rohc] rohc over xxx? Wang Hui
- RE: [rohc] rohc over xxx? Lars-Erik Jonsson (EPL)