> -----Original Message----- > From: Paul Kyzivat [mailto:[EMAIL PROTECTED] > Sent: 25 September 2008 04:43 > To: Elwell, John > Cc: Schmidt, Christian 1. (NSN - DE/Munich); ext Shida > Schubert; [email protected] > Subject: Re: [BLISS] Need feedbacks on > ACH configuration use cases > > John, > > Elwell, John wrote: > > In response to both Theo's and Christian's use cases, I > think we have to clearly differentiate between ACH and > presence. Setting and monitoring a profile such as "out of > office" or "in meeting" or "DND" is very much like presence > publishing and watching. Where ACH kicks in is the treatment > of calls when such a condition exists, e.g., if in "out of > office", forward my calls to cellphone or to voicemail. Also > as part of ACH a UA needs to be able to monitor whether > forwarding is set and under what conditions/profiles it would > be invoked, but we can use presence to see whether a profile > is activated. Does this make sense? > > I agree with you that there is a tight coupling here. > It makes good sense to view the ACH as actions driven by a > policy which > is in turn parameterized by presence status. Mostly you > should then just > need to see that your presence status is accurate, and the ACH should > follow. (I would think that most people would rarely need to > change the > policy itself.) > > But I don't follow your idea that the "profile" itself would > be presence > state. [JRE] Perhaps I didn't express myself too clearly, but I think we are agreed that there is a line to be drawn between presence and the ACH action taken as a result of a particular presence condition. The UA needs to be able to monitor and control the ACH action to be taken.
John _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
