Common Profile for Instant Messaging (CPIM)

Peterson, Jon

doi:10.17487/rfc3860

Cited by 26 publications

(17 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(Emergency) service URL: The service URL is a protocol-specific (e.g., SIP) or protocol-agnostic (e.g., im: [RFC3860]) identifier that contains the address of the PSAP or other emergency service. It depends on the specific signaling or data transport protocol used to reach the emergency service.…”

Section: Locationmentioning

confidence: 99%

Requirements for Emergency Context Resolution with Internet Technologies

Marshall¹,

Schulzrinne²

2008

View full text Add to dashboard Cite

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. AbstractThis document defines terminology and enumerates requirements for the context resolution of emergency calls placed by the public using voice-over-IP (VoIP) and general Internet multimedia systems, where Internet protocols are used end to end.

show abstract

Section: Locationmentioning

confidence: 99%

Requirements for Emergency Context Resolution with Internet Technologies

Marshall¹,

Schulzrinne²

2008

View full text Add to dashboard Cite

show abstract

“…o The rendezvous mechanism MUST be able to natively transport im: URIs or automatically translate im: URIs [27] into the addressing identifiers of the rendezvous protocol.…”

Section: Applicability Of Msrpmentioning

confidence: 99%

“…MSRP sessions may go to a gateway to other Common Profile for Instant Messaging (CPIM) [27] compatible protocols. If this occurs, the gateway MUST maintain session state, and MUST translate between the MSRP session semantics and CPIM semantics, which do not include a concept of sessions.…”

Section: Cpim Compatibilitymentioning

confidence: 99%

The Message Session Relay Protocol (MSRP)

Jennings¹,

Campbell²,

Mahy³

2007

View full text Add to dashboard Cite

“…Provide rich presence information that is at least as powerful as common commercial presence systems. Such feature-parity simplifies transition to systems complying with the Common Profile for Instant Messaging (CPIM) [14], both in terms of user acceptance and protocol conversion. Table 1 In general, it is unlikely that a presentity will publish or announce all of these elements at the same time.…”

Section: Introductionmentioning

confidence: 99%