RE: [NSIS] Re: Modularity and grouping QoS requirements
"Vlora Rexhepi (ELN)" <Vlora.Rexhepi@eln.ericsson.se> Fri, 01 March 2002 10:29 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 FAA05333 for <nsis-archive@odin.ietf.org>; Fri, 1 Mar 2002 05:29:02 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id FAA27495 for nsis-archive@odin.ietf.org; Fri, 1 Mar 2002 05:29:04 -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 FAA26238; Fri, 1 Mar 2002 05:25:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA26200 for <nsis@optimus.ietf.org>; Fri, 1 Mar 2002 05:25:01 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05091 for <nsis@ietf.org>; Fri, 1 Mar 2002 05:24:58 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62]) by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g21AOxB04916 for <nsis@ietf.org>; Fri, 1 Mar 2002 11:24:59 +0100 (MET)
Received: FROM esealnt747.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Fri Mar 01 11:20:33 2002 +0100
Received: by ESEALNT747.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19) id <F4H17R01>; Fri, 1 Mar 2002 11:20:26 +0100
Message-ID: <E244E44D6AB85E40AEEF7EAABE3545FAF7846A@enleent104.nl.eu.ericsson.se>
From: "Vlora Rexhepi (ELN)" <Vlora.Rexhepi@eln.ericsson.se>
To: 'Cedric Westphal' <cedric@iprg.nokia.com>
Cc: "'brunner@ccrle.nec.de'" <brunner@ccrle.nec.de>, "Georgios Karagiannis (ELN)" <Georgios.Karagiannis@eln.ericsson.se>, "'john.loughney@nokia.com'" <john.loughney@nokia.com>, nsis@ietf.org
Subject: RE: [NSIS] Re: Modularity and grouping QoS requirements
Date: Fri, 01 Mar 2002 11:20:23 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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, |one reason for using the model in draft-nsis rather than the one in |draft-partain is that it allows to define mobility requirements. I do not agree. In the draft-partain QoS requirements are derived from particular scenarios, one of them being the Mobile IP scenario and the mobility requirements are part of the draft. In the Mobile IP scenario this is already shown, when a handoff occurs the new reservation is needed from the NAR to the "Joint point of reservation" router that is located into the QoS aware segment that maintains an end to end reservation but due to handover it may change/modify this reservation. [NSIS] WG draft on the other hand on the mobility requirements refers draft-ietf-mobileip-qos-requirements-01.txt. If you compare the draft-partain and draft-ietf-mobileip-qos-requirements-02.txt. you'll see that that these mobility requirements are in both drafts. |For instance, think of a handoff, where the previous access |router (PAR) |transfers QoS context to the new access router (NAR). |There is no NAR-PAR interface in draft-partain; however, it is easy |to see that the NAR is a QC (making the CAC decision at least) for |the new path, and PAR a QI. Note that in draft-partain the Access Routers are denoted as Border Node, so one of the QoS context transfer requirements that will apply to an interface similar to your the NAR-PAR is given in Section 5.2.2, draft-partain. However, this is not explained in detail how it would be done. Probably there may be more issues related to the interworking with QoS context transfer protocols defined in SEAMOBY. Do you already see any other requirements on such interface? |Another drawback of the 'interface' framework is that QoS signaling is |not necessary limited to interfaces. For instance, to update some |reservation |after a handoff, you'd need to signal to the crossover router(s), |wherever it |is. Most likely this crossover router does not correspond to |any interface. |Note that draft-nsis either does not provide such framework, |but it could |easily (should) be added with a QoS Termination point |abstraction. I think |it is a dead end to assume the starting point and the end point of the |QoS signaling to |be some pre-defined interface. Draft-nsis goes a half step in the right |direction by allowing the starting point to be anywhere and |abstracting |it into |the QI, which is a better starting point. The purpose of grouping the requirements according to different interfaces where they apply to is not to limit the starting and ending point of the protocol. The purpose is to see which requirements apply to different parts of the network in the end-to-end path. We all agree that what is needed in the access is not the same as what is needed in the core, which means that we need to identify these requirements for a protocol that we would like to use end-to-end. The only way to achieve this is by supporting modularity in the protocol. Further draft-partain does not restrict the starting point of the protocol either. The major problem in the [NSIS] WG draft is that the requirements are deined for the abstract entities QI/QC and if there is no idea on where in the network this requirements apply it is going to be difficult to design an NSIS protocol fulfilling these requirements. Regards, Vlora _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] Modularity and grouping QoS requirements Georgios Karagiannis (ELN)
- [NSIS] Re: Modularity and grouping QoS requiremen… Marcus Brunner
- [NSIS] RE: Modularity and grouping QoS requiremen… Georgios Karagiannis (ELN)
- [NSIS] FW: Modularity and grouping QoS requiremen… Georgios Karagiannis (ELN)
- RE: [NSIS] Re: Modularity and grouping QoS requir… Vlora Rexhepi (ELN)
- Re: [NSIS] Re: Modularity and grouping QoS requir… danny.goderis
- [NSIS] RE: Modularity and grouping QoS requiremen… john.loughney
- RE: [NSIS] RE: Modularity and grouping QoS requir… Hancock, Robert
- RE: [NSIS] RE: Modularity and grouping QoS requir… Vlora Rexhepi (ELN)
- RE: [NSIS] RE: Modularity and grouping QoS requir… john.loughney
- Re: [NSIS] Re: Modularity and grouping QoS requir… Cedric Westphal
- Re: [NSIS] Re: Modularity and grouping QoS requir… Lars.Westberg
- RE: [NSIS] Re: Modularity and grouping QoS requir… Vlora Rexhepi (ELN)
- RE: [NSIS] RE: Modularity and grouping QoS requir… Vlora Rexhepi (ELN)
- RE: [NSIS] RE: Modularity and grouping QoS requir… Georgios Karagiannis (ELN)
- RE: [NSIS] RE: Modularity and grouping QoS requir… Hancock, Robert
- RE: [NSIS] RE: Modularity and grouping QoS requir… Georgios Karagiannis (ELN)
- Re: [NSIS] Re: Modularity and grouping QoS requir… Cedric Westphal
- RE: [NSIS] RE: Modularity and grouping QoS requir… john.loughney
- RE: [NSIS] RE: Modularity and grouping QoS requir… john.loughney
- RE: [NSIS] RE: Modularity and grouping QoS requir… john.loughney
- RE: [NSIS] RE: Modularity and grouping QoS requir… john.loughney
- RE: [NSIS] RE: Modularity and grouping QoS requir… Vlora Rexhepi (ELN)
- RE: [NSIS] RE: Modularity and grouping QoS requir… john.loughney
- RE: [NSIS] RE: Modularity and grouping QoS requir… Georgios Karagiannis (ELN)