Subject: Re: Integerated Services

From: braden (Bob Braden)
Date: Mon, 24 Jan 1994 16:47:25 -0800

Michael,

There are two IETF working groups just getting started.  The Integrated
Services WG has a mailing list [email-masked].  The other is more
narrowly focussed on the RSVP setup protocol; its list is
[email-masked].  I am forwarding your message to both.

The short answer is that people in the research community are aware of
the mobility+reservation problem, but have put it off until we finish
with the non-mobile case.

If you are willing to tolerate occasional Admission Control failures,
then the soft-state setup mechanism of RSVP should just handle mobility
without change (after you have solved the mobile routing problem, which
you must do anyway)  [Don't tell me that users won't tolerate
occasional Admission Control failures... have you tried to telephone LA
this week??]  Since the bandwidth requirements of mobile systems tend
to be relatively modest, this might be a feasible approach.

Bob Braden

. *> From [email-masked] Mon Jan 24 15:40:31 1994
  *> Date: Mon, 24 Jan 94 15:40:19 PST
  *> From: [email-masked] (Michael Bradley)
  *> To: [email-masked]
  *> Subject: Integerated Services
  *> Content-Length: 778
  *> X-Lines: 23
  *> 
  *> 
  *> Couple of issues - is there a discussion list
  *> for the Integrated Services work? 
  *> 
  *> Secondly, we are looking at QoS models for future 
  *> high speed wireless systems and believe that
  *> the IETF work on the Internet Integrated Services
  *> provides a good starting point. This work 
  *> however seems to assume that the end points
  *> are fixed. This is obviously untrue in a 
  *> with a wireless subnet where end systems can move.
  *> The obvious difficulty is what happens
  *> when a QoS has been negotiated and the
  *> end system move to a "router" that was
  *> not part of the original path and therefore
  *> nota  party to the negotiation? Maybe this could
  *> be added to the tasks that the mobile-ip folks 
  *> are address, but I doubt it. Thoughts would
  *> be appreciated.
  *> 
  *>   Michael Bradley
  *>   Motorola Wireless Data Group
  *> 
  *>