References to draft-ietf-simple-xcap

This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 4826
As rfc4825
Extensible Markup Language (XML) Formats for Representing Resource Lists
References Referenced by
Proposed Standard normatively references
RFC 4827
As rfc4825
An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents
References Referenced by
Proposed Standard normatively references
RFC 5025
As rfc4825
Presence Authorization Rules
References Referenced by
Proposed Standard normatively references
RFC 5874
As rfc4825
An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources
References Referenced by
Proposed Standard normatively references
RFC 5875
As rfc4825
An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package
References Referenced by
Proposed Standard normatively references
RFC 5039
As rfc4825
The Session Initiation Protocol (SIP) and Spam
References Referenced by
Informational informatively references
RFC 5261
As rfc4825
An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors
References Referenced by
Proposed Standard informatively references
RFC 5360
As rfc4825
A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 5363
As rfc4825
Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services
References Referenced by
Proposed Standard informatively references
RFC 5365
As rfc4825
Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 5580
As rfc4825
Carrying Location Objects in RADIUS and Diameter
References Referenced by
Proposed Standard informatively references
RFC 6080
As rfc4825
A Framework for Session Initiation Protocol User Agent Profile Delivery
References Referenced by
Proposed Standard informatively references
RFC 6155
As rfc4825
Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
References Referenced by
Proposed Standard informatively references
RFC 6280
As rfc4825
An Architecture for Location and Location Privacy in Internet Applications
References Referenced by
Best Current Practice informatively references
RFC 6632
As rfc4825
An Overview of the IETF Network Management Standards
References Referenced by
Informational informatively references
RFC 6753
As rfc4825
A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)
References Referenced by
Proposed Standard informatively references
RFC 6772
As rfc4825
Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
References Referenced by
Proposed Standard informatively references
RFC 6914
As rfc4825
SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)
References Referenced by
Informational informatively references
RFC 7199
As rfc4825
Location Configuration Extensions for Policy Management
References Referenced by
Proposed Standard informatively references
RFC 7200
As rfc4825
A Session Initiation Protocol (SIP) Load-Control Event Package
References Referenced by
Proposed Standard informatively references
RFC 8048
As rfc4825
Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence
References Referenced by
Proposed Standard informatively references