Re: [Seamoby] RE: what is edge signalling? (was: RE: [NSIS] Re: Comments on draft-westphal-nsis-qos-mobileip-00.txt)

Charlie Perkins <charliep@iprg.nokia.com> Mon, 08 July 2002 14:23 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 KAA16264 for <seamoby-archive@odin.ietf.org>; Mon, 8 Jul 2002 10:23:05 -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 KAA19257; Mon, 8 Jul 2002 10:17: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 KAA19198 for <seamoby@optimus.ietf.org>; Mon, 8 Jul 2002 10:17:40 -0400 (EDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15923; Mon, 8 Jul 2002 10:16:47 -0400 (EDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id HAA15938; Mon, 8 Jul 2002 07:17:05 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g68EH4t26649; Mon, 8 Jul 2002 07:17:04 -0700
X-mProtect: <200207081417> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.22.18, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdxpq7Th; Mon, 08 Jul 2002 07:17:02 PDT
Message-ID: <3D299E8D.9E31EFD2@iprg.nokia.com>
Date: Mon, 08 Jul 2002 07:15:41 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gary Kenward <gkenward@nortelnetworks.com>
CC: nsis@ietf.org, "'seamoby@ietf.org'" <seamoby@ietf.org>
Subject: Re: [Seamoby] RE: what is edge signalling? (was: RE: [NSIS] Re: Comments on draft-westphal-nsis-qos-mobileip-00.txt)
References: <9FBD322B7824D511B36900508BF93C9C01AA4BDC@zcard031.ca.nortel.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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

Hello Gary,

I have a comment on another point in your earlier message.

Gary Kenward wrote:

> In my view, if CT is in place, then NSIS should not be invoked as a
> result of a handover.

Suppose a handover has occurred, and some QoS has been negotiated
via CT between two access routers to support the mobile node at the new
access routers.  This could involve having the new router making sure
it has sufficient capacity to support the mobile device, and making sure

that the tunnel between the two routers can be managed with small
enough delay.

Then, after the handover is complete, it might be better to renegotiate
QoS so that the previous access router no longer was required to
maintain the excess capacity needed to serve the tunnel to the new
access router.  This could involve signaling so that packets are
routed directly to the new access router, presumably with some QoS
negotiation.  This could involve NSIS.

Thus, I don't agree with your statement above.  But I am willing to
agree
that CT should not necessarily be intertwined with NSIS.

Regards,
Charlie P.



>


_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby