RE:

["Dolan, Michael F (Mike)" <mfdolan@lucent.com>]

Tim,

I would hope to be able to buy something like this in a couple of years!!

Mike

-----Original Message-----
From: tim clifford [mailto:tjc@lacunanet.net]
Sent: Thursday, July 26, 2001 11:04 PM
To: Dolan, Michael F (Mike); Dana L. Blair; Atsushi Takeshita;
more@psg.com
Subject: RE: 


mike
do you really have one of those, can i get one at compusa???

;-)

tc

> -----Original Message-----
> From: owner-more@ops.ietf.org [mailto:owner-more@ops.ietf.org]On Behalf
> Of Dolan, Michael F (Mike)
> Sent: Thursday, July 26, 2001 5:55 PM
> To: Dana L. Blair; Atsushi Takeshita; more@psg.com
> Subject: RE:
>
>
> Dana,
>
> If you want to transfer your call to your "fixed line"
> environment, why not
> consider a terminal device that configures itself to available
> "peripherals"
> and access networks.  E.G.  My phone is using cellular technology and I am
> getting an audio stream (voice).  I get "close enough" to my
> office building
> and my terminal detects 802.11b and moves (Mobile IP) to that access
> network.  As a result, the video screen lights up and I now get the video
> portion of my session.  As I enter my office, I set my terminal
> in a cradle
> and a large screen on my desk lights up (auto-configuration to available
> peripherals), while the terminal transfers the IP streams to the 100 Mbps
> Ethernet (Mobile IP).
>
> Mike Dolan
>
> -----Original Message-----
> From: Dana L. Blair [mailto:dblair@cisco.com]
> Sent: Wednesday, July 25, 2001 10:26 AM
> To: Atsushi Takeshita; more@psg.com
> Subject: RE:
>
>
> >   -----Original Message-----
> >   From: owner-more@ops.ietf.org
> [mailto:owner-more@ops.ietf.org]On Behalf
> >   Of Atsushi Takeshita
> >   Sent: Wednesday, July 25, 2001 12:44 AM
> >   To: more@psg.com
> >   Subject: Re:
> >
> >
> >   Dana,
> >
> >   > The second example above seems to imply handoff from one
> >   > access network to another with the same terminal.  Mobile
> >   > IP works for this.
> >
> >   I agree.
> >
> >   > The first example and your definition suggests that a user
> >   > is using one terminal
> >   > then starts using another terminal and needs some mobility
> >   > between the useage of each terminal.  Can you provide
> >   > a specific application and usage scenario where this is
> >   > important ?
> >
> >   At this moment, I don't find any applications like that.
> >   However, in the future, I think we will have such applications.
> >   Let me give two examples.
> >   1) A user is videoconferencing the mobile
> >     terminal. Then the user transfer the videoconference
> >     to a videoconference system connected to a fixed network.
> >   2) A user is playing a network game on mobile a terminal.
> >     The the user transfer the game to the game terminal like
> >     PlayStation.
>
> Thanks for the explaination.
>
> In fact, session mobility as
> you just described it would be useful today with my cell phone.
> For example, I am on the phone in my car and walk to my cubicle
> while on the phone.  Once in my cube, I would like to transfer the
> call to my desk phone for a variety of reasons regarding cost,
> power, security, ... but I can't with existing cell phone
> capabilities.
>
> >
> >   My definition of session mobility may be different from
> >   one described in the I-D.
> >
> >   > Is accounting information for application usage an area that
> >   > you think the IETF should consider standardizing ?  I am not
> >   > aware of work in the IETF in this area, but I can check if needed.
> >
> >   I'm not sure.
> >   But it seems it's out of IETF's scope.
>
> I agree it's probably out of IETF's scope.
>
> Dana
>
> >
> >   ------------------------------------------
> >   TAKESHITA, Atsushi
> >   DoCoMo Communications Laboratories USA, Inc.
> >   takeshita@dcl.docomo-usa.com
> >   Tel: 408-451-4705 / Fax: 408-573-1090
> >   ------------------------------------------
> >
> >
> >