W3C home > Mailing lists > Public > ietf-discuss@w3.org > September 2000

Re: Mobile Multimedia Messaging Service

From: vint cerf <vcerf@MCI.NET>
Date: Sat, 16 Sep 2000 08:12:13 -0400
To: (wrong string) ältström <paf@cisco.com>, "James P. Salsman" <bovik@best.com>, Jim.Mathis@Motorola.com, ned.freed@innosoft.com
Cc: discuss@apps.ietf.org, ietf-mmms@imc.org, ietf@ietf.org
Message-id: <4.3.2.7.2.20000916080817.0561f7f0@shoe.reston.mci.net>
patrik,

would it be useful, in the context of establishing peer-to-peer communications
(or even client/server communications) with limited-function mobile devices,
to use SIP as a framework for negotiating the parameters that should guide the
nature of the exchange? I'm thinking, for instance, of a web server that may
usefully discover the functional limits of a mobile before it starts to send
content to that device. The mobile uses SIP to report to the server that it
has X amount of memory, Y amount of display area, color or not, average 
data rate it can send or receive, and so on. This information would be used
by the server to configure what it sends to be compatible with the receiving
unit.

perhaps this is an idea that is already being pursued in an IETF working group?

Vint

At 09:35 AM 9/16/2000 +0200, Patrik Fältström wrote:
>At 14.52 -0700 00-09-15, James P. Salsman wrote:
>>If there has been no charter proposed for a MMMS working group, I
>>intend to propose one as follows.
>
>I have no memory of a charter.
>
>>Proposed milestones:  The goals of the MMMS WG will include the
>>publication of specifications, as described above, on the following
>>topics:  interoperable end-to-end Internet service access on mobile
>>devices, including descriptions of existing end-to-end wireless
>>Internet service arrangements; implementation guidelines for multimedia
>>messaging services on mobile devices using existing Internet messaging
>>standards; guidelines concerning performance implications of link
>>constraints, including TCP behaviors during extended periods of
>>wireless link downtime; and wired PPP access from mobile Internet
>>devices.
>
>This is too open-ended. I want a more specific list of documents that you are to create, and the list of issues you are to discuss should also say what is _NOT_ in scope of the wg.
>
>My personal interest is not so much in multimedia, but in a discussion on how one should design an application layer protocol (and maybe "how should one use existing protocols, like IMAP") so it works for "mobile" clients.
>
>You should by the way define a "mobile client"...
>
>I felt the discussion at the BOF ended up with "a client which have very limited bandwidth to the network, often connected to many different internet providers, limited memory and screen", or something like that.
>
>  paf
Received on Saturday, 16 September 2000 08:11:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 March 2006 20:11:27 GMT