[NSIS] Comments on draft-westphal-nsis-qos-mobileip-00.txt
Gabor Fodor <erafodo@ESEALNT448.al.sw.ericsson.se> Fri, 28 June 2002 14:36 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 KAA28629 for <nsis-archive@odin.ietf.org>; Fri, 28 Jun 2002 10:36:32 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA29716 for nsis-archive@odin.ietf.org; Fri, 28 Jun 2002 10:37:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28385; Fri, 28 Jun 2002 10:19:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28294 for <nsis@optimus.ietf.org>; Fri, 28 Jun 2002 10:19:39 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27774 for <nsis@ietf.org>; Fri, 28 Jun 2002 10:18:51 -0400 (EDT)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137]) by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g5SEJXRb022512; Fri, 28 Jun 2002 16:19:33 +0200 (MEST)
Received: from wrtw014.wrn.ki.sw.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T)) id QAA08324; Fri, 28 Jun 2002 16:19:32 +0200
Received: from wrtw014 by wrtw014.wrn.ki.sw.ericsson.se (8.8.8+Sun/client-1.3) id QAA06467; Fri, 28 Jun 2002 16:19:32 +0200 (MET DST)
Message-Id: <200206281419.QAA06467@wrtw014.wrn.ki.sw.ericsson.se>
Date: Fri, 28 Jun 2002 16:19:32 +0200
From: Gabor Fodor <erafodo@ESEALNT448.al.sw.ericsson.se>
Reply-To: Gabor Fodor <erafodo@ESEALNT448.al.sw.ericsson.se>
To: cedric@iprg.nokia.com, hemant.chaskar@nokia.com
Cc: nsis@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset="us-ascii"
Content-MD5: xulppB/f2PDTaW77JTFbFw==
X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4m sparc
Subject: [NSIS] Comments on draft-westphal-nsis-qos-mobileip-00.txt
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Next Steps in Signaling <nsis.ietf.org>
X-BeenThere: nsis@ietf.org
Hi Cedric and Hemant, I understand from the mail discussions and especially from the interim meeting, that the WG is encouraged to take into consideration the requirements formulated in : http://www.ietf.org/internet-drafts/ draft-ietf-mobileip-qos-requirements-02.txt From that perspective, I think that your draft is an important input and can evolve to a good design base. However, I also understand that the group is in the process of discussing the requirements and the framework drafts, so I am not sure whether starting discussing this draft is appropriate right now. Anyway, here comes a set of comments from my perspective. Best regards /Gabor --------------------------------------------------------------- 1 I agree that we need to consider a QoS signaling that works in a mobile/wireless environment and that the wireless bandwidth economy must be an important factor. From this point of view, I would like to see a more clear discussion on the requirements that this draft provides the solution for. Clearly, we have at least two important input documents: the NSIS requirement doc and the mobileip-qos-requirements doc. I think that your framework draft should try to identify which of these requirements it considers important and which new ones it adds to those. 2 I also agree that we need to differentiate between the "edge" signaling, the context transfer signaling and the "data path signaling". We need to be careful with statements like "lightweight signaling mechanism required over the wireless link". We indeed want to minimize both the number and the length of signaling messages over the air (so in that sense it should be lightweight), but we do want to provide enough information to efficiently configure wireless resources, often per user flow and per-flow state maintenance with support of bi-directional assymmetric reservation, etc. I think that the draft should define what is meant by "wireless bandwidth economy" and discuss more the requirements specifically on the edge signaling. 3 The draft talks about the negotiation procedures (in 4.2). In my opinion the draft should identify the requirement more clearly, preferably with a reference to either the NSIS or the mobile IP requirement draft. Is there a difference between negotiation (which takes place upon QoS initiation time) and QoS adaptation signaling which may take place upon hand-over ? 4 I am not sure that it is meaningful at this point to start discussing specific solution approaches. You seem to propose to use ICMP as a design base for both edge signaling and for context transfer (AR to AR). At least for the edge signaling, we need to consider the edge specific requirements before we start discussing what existing or new protocol can be the design base for that. 5 You mention RFC2998 as one of your basic references, which I think is a very useful RFC in this context as well. However, from the draft it is not clear how you use that in the proposed architecture. (Since ICMP seems to be the base and not RSVP.) 6 You identify QoS release as a necessary functionality. Here there is a need to identify if the protocol should support soft state (in which case this explicit QoS release may not be necessary) or not. 7 As a minor detail issue, I see some problems with the definition of the cross-over router. I believe that your definition in 4.1.3 would identify several routers as cross-over router, whereas later on it seems that only the first merging point is really used as cross-over router. By the way, the notion of cross-over router in my opinion should be introduced when you present the whole model around the figure in Section 1, but this is a presentation issue. > From: Cedric Westphal <cedric@iprg.nokia.com> > To: nsis@ietf.org > CC: hemant.chaskar@nokia.com > Content-Transfer-Encoding: 7bit > Content-Transfer-Encoding: 7bit > Subject: [NSIS] QoS framework. > Hi all, > > we put together a document representing our perspective on a > NSIS qos signaling framework. > > Here is the abstract: > > Abstract > > This draft provides a framework for QoS signaling that is optimized > for Mobile IP handoffs. It covers the horizontal signaling between > access routers (ARs) as well as the vertical signaling along the > packet data path, both of which are triggered by handoff of mobile > node (MN). The key design goals are wireless bandwidth economy, > fast QoS establishment along the new data path after handoff and > secure protocol operation. > > > The document will eventually be available from the i-d editor queue. However, > only after Yokohama meeting. You can find it at: > http://people.nokia.net/~cedric/Papers/draft-westphal-nsis-qos-mobileip-00.txt > in the meantime. > Please send your comments, > > Cedric & Hemant. > > > > > _______________________________________________ > nsis mailing list > nsis@ietf.org > https://www1.ietf.org/mailman/listinfo/nsis _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] Comments on draft-westphal-nsis-qos-mobile… Gabor Fodor
- [NSIS] Re: Comments on draft-westphal-nsis-qos-mo… Cedric Westphal
- [NSIS] RE: Comments on draft-westphal-nsis-qos-mo… Hemant.Chaskar
- Re: [NSIS] Re: Comments on draft-westphal-nsis-qo… Gabor Fodor
- Re: [NSIS] RE: Comments on draft-westphal-nsis-qo… Xiaoming Fu
- RE: [NSIS] RE: Comments on draft-westphal-nsis-qo… Hemant.Chaskar