RFC 4826: Extensible Markup Language (XML) Formats for Representing Resource Lists

In multimedia communications, presence, and instant messaging systems, there is a need to define Uniform Resource Identifiers (URIs) that represent services…

Read RFC 4826 on the RFC Editor

Outgoing relationships (9 related RFCs)

Normative reference — RFC 3261: SIP: Session Initiation Protocol
Normative reference — RFC 2141: URN Syntax
Normative reference — RFC 3023: XML Media Types
Normative reference — RFC 2648: A URN Namespace for IETF Documents
Normative reference — RFC 4825: The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Informative reference — RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification
Informative reference — RFC 3856: A Presence Event Package for the Session Initiation Protocol (SIP)
Informative reference — RFC 3859: Common Profile for Presence (CPP)
Informative reference — RFC 4662: A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists

Incoming relationships (6 related RFCs)

Normatively referenced by — RFC 5989: A SIP Event Package for Subscribing to Changes to an HTTP Resource
Normatively referenced by — RFC 5875: An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package
Informatively referenced by — RFC 4825: The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards
Informatively referenced by — RFC 5556: Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement
Informatively referenced by — RFC 6914: SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)