Shapira, Noam (Shapira_Noam@icomverse.com)
Sun, 29 Jul 2001 08:04:38 +0300
Hi James,
Thanks for you response, we opened a mailing list 'snap@lists.neystadt.org'
- I would be happy if you would join.
>>What is a VoiceFax?
The VoiceFax means fax with voice annotation. Actually, from other
responses, as well as yours, I was thinking of using
draft-ietf-vpim-hint-07.txt, for the message type attribute - any comments?
About the second comment:
>>Is the protocol extensible enough to be notified when other messages
>>are received (such as when there is new physical mail waiting at some
>>location, for instance)?
I am not sure I understand the question - can you elaborate?
>>Why is it based on HTTP instead of RFC-822?
The proposal is not based on HTTP - rather, the proposal was implemented
over HTTP - as the transport Layer. As you can see in the proposal, most of
the proposal uses RFC-822 - mostly in the attributes values & formatting. We
might need to improve it - but this is the spirit of things.
Thanks for your response,
Noam
-----Original Message-----
From: James P. Salsman [mailto:bovik@best.com]
Sent: Wednesday, July 25, 2001 10:23 AM
To: Shapira, Noam
Cc: vpim@lists.neystadt.org
Subject: draft-shapira-snap-01.txt
Noam,
Thank you for the opportunity to read your draft on the
Simple Notification and Alarm Protocol (SNAP).
> MessageType = "MessageType=" ("email" | "voice" | "fax" | "Video" |
> "number" | "emptycaptured" | "VoiceFax")
What is a VoiceFax?
Is the protocol extensible enough to be notified when other messages
are received (such as when there is new physical mail waiting at some
location, for instance)?
Why is it based on HTTP instead of RFC-822?
Cheers,
James
This archive was generated by hypermail 2.0b3 on Sun Jul 29 2001 - 08:06:07 IDT