Re: [Seamoby] framework for DMHA protocol
ralf.schmitz@ccrle.nec.de Wed, 02 January 2002 11:16 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 GAA02399 for <seamoby-archive@odin.ietf.org>; Wed, 2 Jan 2002 06:16:02 -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 FAA02059; Wed, 2 Jan 2002 05:54:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA02030 for <seamoby@optimus.ietf.org>; Wed, 2 Jan 2002 05:54:24 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02090 for <seamoby@ietf.org>; Wed, 2 Jan 2002 05:54:20 -0500 (EST)
From: ralf.schmitz@ccrle.nec.de
Received: from citadel.mobility.ccrle.nec.de ([192.168.156.1]) by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id g02As5A66042; Wed, 2 Jan 2002 11:54:05 +0100 (CET)
Received: from DVORAK (dvorak.mobility.ccrle.nec.de [192.168.101.42]) by citadel.mobility.ccrle.nec.de (Postfix on SuSE eMail Server 2.0) with ESMTP id 27576C052; Wed, 2 Jan 2002 11:54:05 +0100 (CET)
To: "Jari T. Malinen" <jmalinen@iprg.nokia.com>
Date: Wed, 02 Jan 2002 11:53:53 +0100
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [Seamoby] framework for DMHA protocol
Cc: seamoby@ietf.org
Message-ID: <3C32F4D1.20791.BDBD84@localhost>
Priority: normal
In-reply-to: <3C23D802.5E052D52@iprg.nokia.com>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit
On 21 Dec 2001, at 16:46, Jari T. Malinen wrote: Hi Jari, please see my comments in line... > Hello, > > Having a design team framework document is ok, currently the draft-renker > gives a multitude of choices to do a protocol. Ultimately we'll need something > simple and unambiguous. => Agreed. We'll need something simple and unambiguous, but at the same time we should not restrict ourself too much at this early stage of the protocol design. The 'multitude of choices' offer a variety of possibilities in order to be as flexible and open as possible. All the choices are up for discussion so that the group can (hopefully) come out with the desired simple and unambiguous protocol. > This would need strong modification to become a > real protocol from its current format which looks more like an architecture > with candidate modes for several functionalities. > > I second that the requirement for protocol independence is important. > Hence, I suggest structuring the document in a way that decouples the protocol > from all other protocols (MIPv6 etc. included) so much that they do not need > ideally to be even refered to at all. If needed, there should be appendices > describing interaction but only in the case it is essential for the > working of the protocol in some mode etc. Interdependences should be > minimized. => Isn't this exactly what Marco proposed in his mail (seebelow)?! I think, the idea of 'moving the Mobile IPv6 options ... into the Annex .. ' is a good step forward towards the required protocol independance. kind regards ralf > > Merry Christmas and a Happy New year all, > > -Jari > > On Fri, Dec 21, 2001 at 06:45:59PM +0100, Marco Liebsch wrote: > > Dear all, > > I will try to structure a draft framework, which is then for discussion > > on the list, taking first the protocol as it is now and moving the > > Mobile IPv6 options to be considered for MIP optimization purposes into > > the Annex (open). We have to think about extensions and address the > > parts the assessment draft refers to. Until first framework is > > available, please be referred to the current version of the base-line > > concept draft-renker-paging-ipv6-01.txt and also think of issues to be > > clarifed with respect to what is already written. So we can address > > these issues and have enhancements in the first draft version, which > > could be submitted end of January, if the WG agrees and we proceed. What > > do you think? > > > > I wish you all a merry Christmas and a happy new year. I will be back in > > the office around Jan, 10th. > > > > Marco > > > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby > -- Ralf Schmitz NEC Europe Ltd. - Network Laboratories E-Mail: Ralf.Schmitz@ccrle.nec.de http://www.ccrle.nec.de/ Adenauerplatz 6 D-69115 Heidelberg - Germany Phone: +49 (0)6221/ 13 70 8 - 12 Fax: +49 (0)6221/ 13 70 8 - 28 _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] comments on the paging protocol assessm… Yoshihiro Ohba
- Re: [Seamoby] comments on the paging protocol ass… James Kempf
- Re: [Seamoby] comments on the paging protocol ass… Yoshihiro Ohba
- Re: [Seamoby] comments on the paging protocol ass… James Kempf
- Re: [Seamoby] comments on the paging protocol ass… Jari T. Malinen
- Re: [Seamoby] comments on the paging protocol ass… Yoshihiro Ohba
- Re: [Seamoby] framework for DMHA protocol Jari T. Malinen
- Re: [Seamoby] comments on the paging protocol ass… James Kempf
- Re: [Seamoby] comments on the paging protocol ass… James Kempf
- Re: [Seamoby] comments on the paging protocol ass… Yoshihiro Ohba
- Re: [Seamoby] comments on the paging protocol ass… James Kempf
- Re: [Seamoby] framework for DMHA protocol ralf.schmitz