Dear colleagues, in this new version of the CC draft the role of the callee's monitor's presence server functionality was made more precise. It was clarified that the the presence status instantiates as soon as it receives a SUBSCRIBE message because without the presence status there would be no CCE's availability state.
Further the wording was improved, especially regarding the consistency of CC recall and CC call. Regards, Martin > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[email protected]] > Im Auftrag von [email protected] > Gesendet: Dienstag, 27. November 2012 14:56 > An: [email protected] > Cc: [email protected] > Betreff: [BLISS] I-D Action: draft-ietf-bliss-call-completion-17.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Basic Level of > Interoperability for SIP Services Working Group of the IETF. > > Title : Call Completion for Session > Initiation Protocol (SIP) > Author(s) : Dale R. Worley > Martin Huelsemann > Roland Jesske > Denis Alexeitsev > Filename : draft-ietf-bliss-call-completion-17.txt > Pages : 37 > Date : 2012-11-27 > > Abstract: > The call completion feature defined in this specification > allows the > caller of a failed call to be notified when the callee becomes > available to receive a call. > > For the realization of a basic solution without queuing, this > document references the usage of the dialog event package > (RFC 4235) > that is described as 'automatic redial' in the SIP Service Examples > (RFC 5359). > > For the realization of a more comprehensive solution with queuing, > this document introduces an architecture for implementing these > features in the Session Initiation Protocol where "call completion" > implementations associated with the caller's and callee's endpoints > cooperate to place the caller's request for call completion into a > queue at the callee's endpoint, and when a caller's > request is ready > to be serviced, re-attempt of the original, failed call is made. > > The architecture is designed to interoperate well with > existing call- > completion solutions in other networks. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-bliss-call-completion > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-bliss-call-completion-17 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-bliss-call-completion-17 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > BLISS mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/bliss > _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
