References to rfc4825

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