RFC 5363: Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services

This document describes the need for SIP URI-list services and provides requirements for their invocation. Additionally, it defines a framework for SIP…

Read RFC 5363 on the RFC Editor

Outgoing relationships (12 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3261: SIP: Session Initiation Protocol
Normative reference — RFC 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
Normative reference — RFC 5360: A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)
Informative reference — RFC 4575: A Session Initiation Protocol (SIP) Event Package for Conference State
Informative reference — RFC 4825: The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Informative reference — RFC 4662: A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists
Informative reference — RFC 5367: Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)
Informative reference — RFC 5364: Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists
Informative reference — RFC 5365: Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)
Informative reference — RFC 5366: Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)
Informative reference — RFC 4453: Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 5370: The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model
Informatively referenced by — RFC 5876: Updates to Asserted Identity in the Session Initiation Protocol (SIP)