RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-qos-mobileip-00. txt
"Geib, Ruediger" <Ruediger.Geib@t-systems.com> Thu, 11 July 2002 08:32 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 EAA13179 for <seamoby-archive@odin.ietf.org>; Thu, 11 Jul 2002 04:32:36 -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 EAA21332; Thu, 11 Jul 2002 04:25:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21249 for <seamoby@optimus.ietf.org>; Thu, 11 Jul 2002 04:24:58 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12786; Thu, 11 Jul 2002 04:24:03 -0400 (EDT)
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Thu, 11 Jul 2002 10:23:39 +0200
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19) id <3VR7PRVX>; Thu, 11 Jul 2002 10:24:16 +0200
Message-Id: <DFD875E85664D3118FA6080006277DE70362CAE9@U8PN2.blf01.telekom.de>
From: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
To: kempf@docomolabs-usa.com, Madjid.Nakhjiri@motorola.com, rajeev@iprg.nokia.com, Hemant.Chaskar@nokia.com
Cc: gkenward@nortelnetworks.com, seamoby@ietf.org, nsis@ietf.org
Subject: RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-qos-mobileip-00. txt
Date: Thu, 11 Jul 2002 10:24:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA21252
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: 8bit
Hi James > The point I was trying to make is that given CT of QoS > context succeeds, NSIS signaling at the new access subnet is > unnecessary. Thus, it could be viewed as a kind of > optimization. If CT fails, then signaling would be needed. [RG] If this means "QoS related CT replaces MN signaling during [RG] handoff", given that the related resource reservation [RG] doesn't change. > I did not mean to imply that any changes were required in the > generic CT requirements (though perhaps there would need to be > some changes in the QoS specific context definition). [RG] QoS CT should use the NSIS resource reservation parameters [RG] as basic input for its own QoS parameters. Whether the [RG] original NSIS parameters are copied or derived [RG] technology or domain specific parameters are used for CT [RG] doesn't matter if the result is as if the original NSIS [RG] parameters were used to establish resources at the new AR. > Is this accurate, from the NSIS viewpoint? One case where I > could see it not being accurate is if there were some changes > required behind the access router in order to obtain QoS for > the mobile on the new router, but perhaps there are others. [RG] This may have to be clarified. I wouldn't expect an MN [RG] to get involved into tunnel set up and release, should [RG] this be the way an access network supports QoS and [RG] mobility. A local NSIS solution may be used within [RG] the access network to provide the required signaling. [RG] But I'd expect this to be invisible to the MN. [RG] I think NSIS and SEAMOBY must agree how both interwork. [RG] Besides the QoS parameter issue, an MN should be aware [RG] of the fact whether CT is supported and whether it is [RG] succesful (or whether it wasn't). [RG] To me this seems to be a loose cooperation. If NSIS and [RG] SEAMOBY conclude to ignore each other, I'd regard both [RG] as a waste of time with regard to wireless mobility [RG] combined with QoS. Regards, Rüdiger _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… Gary Kenward
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… Nakhjiri Madjid-MNAKHJI1
- Re: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… James Kempf
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… Nakhjiri Madjid-MNAKHJI1
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… Geib, Ruediger
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… Gary Kenward
- Re: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… James Kempf
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… Gary Kenward
- Re: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… James Kempf
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… john.loughney
- Re: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… James Kempf
- RE: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-… Geib, Ruediger