Subject: RE: [SIP] draft-mahy-sip-message-waiting-01.txt

From: Jay Batson <[email-masked]>
Date: Tue, 19 Jun 2001 18:37:19 -0400

My comments aren't timely, so my apologies.

Venkatesh's comments are also consistent with typical IETF protocol / 
application design.  Example:  Neither SMTP nor POP/IMAP specify how the 
email "user agent" (Eudora, Netscape, Outlook) provides visual indication 
of email message priority (X-Priority).

The creator of a given user agent defines its own user interfaces to 
information that is provided in the standardized lower later protocol.  End 
users then choose among available user agents (and behaviors) to get their 
desired interaction.

Applications at either end of a transaction may want to agree on 
Experimental extensions to show more information, such as the type that 
Jean-Francois suggests.  In fact, this is how X-Priority came into being in 
email!  Eudora just up and did it one day, and everybody else did what they 
did!

-jb

At 03:29 PM 4/26/01, Venkatesh Venkataramanan wrote:
>I would think that the functionality of SIP ends when it delivers the
>requested Notification. What the phone/the entity does with it(light a lamp,
>render the same on a display, provide stutter dial tone or audible
>notification et al) is more a matter of the local policy (depending upon the
>capabilities of the end point).
>
>Venkatesh
>
>-----Original Message-----
>From: Jean-Francois Mule [mailto:[email-masked]]
>Sent: Thursday, April 26, 2001 12:42 AM
>To: 'Rohan Mahy'; [email-masked]; [email-masked]
>Subject: [SIP] draft-mahy-sip-message-waiting-01.txt
>
>
>Hi,
>The I-D mentions audible/visual message waiting indications in the
>introduction but then remains silent on this.
>Has there been any considerations to include the type of mwi
>(audible/visual) as optional in application/simple-message-summary?
>Jean-Francois Mule.
>Clarent
>
>_______________________________________________
>This list is for continuing development of the SIP protocol.
>The sip-implementor's list is the place to discuss implementation,
>and to receive advice on understanding existing sip.
>To subscribe to it, send mail to
>[email-masked] with "subscribe" in the body.
>
>
>_______________________________________________
>This list is for continuing development of the SIP protocol.
>The sip-implementor's list is the place to discuss implementation,
>and to receive advice on understanding existing sip.
>To subscribe to it, send mail to
>[email-masked] with "subscribe" in the body.

-------------
PingMe!
Jay Batson
CEO
Pingtel Corp.
mailto:[email-masked]
781-938-5306 (office)