RE: [Sipping] Internet draft on missed calls / msgs notification

["Banibrata Dutta" <dutta at india.hp.com>]

Without having read the entire draft (I quickly skimmed thru it), I have a
feeling that if we are planning to extend the scope from missed-calls (or
even with the limited scope) to calls placed or successfully received, we
should put in place some mandatory privacy mechanisms. Such
records/information is previleged and can be sensitive.

my $0.02,
- banibrata dutta

-----Original Message-----
From: sipping-bounces at ietf.org [mailto:sipping-bounces at ietf.org] On Behalf
Of Paul Kyzivat
Sent: Wednesday, September 28, 2005 3:15 AM
To: Jeroen van Bemmel
Cc: Francois Audet; sipping at ietf.org
Subject: Re: [Sipping] Internet draft on missed calls / msgs notification



Jeroen van Bemmel wrote:
> Perhaps it would be an idea to come up with a list of such explicit 
> requirements, and add that to the draft under section 3 (which now has 
> 3 lines describing the problem). So far we have:
> - it MUST be possible to receive information on calls on any endpoint
> - the list of calls for a given identity SHOULD be complete, meaning 
> it SHOULD include information on calls placed while no endpoints were 
> registered for that user, while one or more endpoints were busy, ....[ 
> more cases here ]
> - the call information MUST be treated as privacy sensitive, it SHOULD 
> NOT be shared over an unsecure channel and integrity mechanisms SHOULD 
> be used
> 
> I would also suggest to extend the scope from "missed calls" to "calls" 
> or "call log", including calls that were answered (but perhaps on a 
> different endpoint than used for viewing the information). It should 
> also be considered how information from different sources is merged 
> (e.g. forked calls, 1 endpoint reports 'busy' and the other accepts, 
> how is the call logged?)

I agree.

And calls that were placed, rather than received, are also of interest. 
Again there is the value of seeing a consolidated list of all for the AOR,
rather than just those placed by a particular UA.

	Paul

> Perhaps a discussion on giving others permission to view your calls 
> (e.g. a secretary on behalf of her boss) would be in place
> 
> Regards,
> 
> jeroen
> 
> ----- Original Message ----- From: "Francois Audet" <audet at nortel.com>
> To: <sipping at ietf.org>
> Sent: Tuesday, September 27, 2005 9:02 PM
> Subject: RE: [Sipping] Internet draft on missed calls / msgs 
> notification
> 
> 
> 
> I think the key point is Dave's point about the ability to see missed 
> calls on a variety of devices that may not have received the INVITEs 
> in the first place.
> 
> Today, missed calls are logged individually at the devices themselves 
> (using P2P, to use Henry's terminology).
> 
> If one of those devices is "not always on", like a PC client for 
> example, or a mobile device, it will not be able to see the "missed 
> calls" that landed elsewhere (on the desk phone at work, or on a home 
> phone or whatever).
> 
> The "cost of server" argument is interesting, but it really depend on 
> the enviroment you are in. In some environments, like an Enterprise 
> for example, the cost of the "server" may not be an issue. And having 
> the ability to see "all missed calls" may be quite important.
> 
> I think a missed call package is a decent idea.
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use 
> sip-implementors at cs.columbia.edu for questions on current sip Use 
> sip at ietf.org for new developments of core SIP
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use 
> sip-implementors at cs.columbia.edu for questions on current sip Use 
> sip at ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP Use
sip-implementors at cs.columbia.edu for questions on current sip Use
sip at ietf.org for new developments of core SIP




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP