RE: [lemonade] some questions in draft-ietf-lemonade-notifications-03

[<Zoltan.Ordogh at nokia.com>]

>>Ben,
>>Why would anyone use MMS for notification? It it nothing more than a
>WAP Push (well, there is a bit more but from email 
>notification point of view
>>nothing useful). Why not use WAP Push right away (without all the
>hassle that comes with MMS)?
>
>I'd guess that it's because all the WAP-push-and-fetch 
>functionality is handled by the platform.  For example, on a 
>Symbian-based device, it's easy to write a watcher process 
>that will spot incoming MMS messages and process them, so from 
>the point of view of the programmer you get a messaging system 
>that will handle large messages as simply as SMS handles small 
>ones, without any additional hassle.  Sure, it's more complex 
>from the OS's point of view, but that's hidden from the 
>programmer.  Similarly, most message-service providers provide 
>APIs (over HTTP or RPC) that make sending MMS messages as easy 
>as sending SMSs.
Hmmm. You have a point about trying to make it as simple as sending
SMSes.
However, I feel that is is a waste of resources and bandwidth - I heard
it expressed from operators already (they are even reluctant to use Wap
Push and prefer SMS because it comsumes the least).
When You get an MMS, this goes down:
1. You get a Wap Push message to tell You that You have an MMS.
2. You do HTTP/GET to fetch the MMS Message.
3. You get the HTTP respnse that contains that the actual notification.
Now scale this up to a million user. This is the reason why I do not see
any reason why would anyone do MMS - it adds with way too much
signalling (and, consequently wait times) over the wireless network.
But, my understanding is that the client can decide which notification
medium to use (please correct if I am wrong), so one can choose to use
SMS, Wap Push, MMS, right?

_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade