References to RFC 2533
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 3841 |
Caller Preferences for the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 4141 |
SMTP and MIME Extensions for Content Conversion
References Referenced by |
Proposed Standard | normatively references | |
RFC 7904 |
A SIP Usage for REsource LOcation And Discovery (RELOAD)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3840 |
Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | informatively references | |
RFC 4249 |
Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components
References Referenced by |
Informational | informatively references | |
RFC 4367 |
What's in a Name: False Assumptions about DNS Names
References Referenced by |
Informational | informatively references | |
RFC 4479 |
A Data Model for Presence
References Referenced by |
Proposed Standard | informatively references | |
RFC 4596 |
Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension
References Referenced by |
Informational | informatively references | |
RFC 2799 |
Request for Comments Summary RFC Numbers 2700-2799
References Referenced by |
Informational | Possible Reference | |
RFC 3343 |
The Application Exchange (APEX) Presence Service
References Referenced by |
Historic | Possible Reference | |
RFC 3795 |
Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
References Referenced by |
Informational | Possible Reference | |
RFC 4021 |
Registration of Mail and MIME Header Fields
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 2530 |
Indicating Supported Media Features Using Extensions to DSN and MDN
References Referenced by |
Proposed Standard | Reference | |
RFC 2531 |
Content Feature Schema for Internet Fax
References Referenced by |
Proposed Standard | Reference | |
RFC 2532 |
Extended Facsimile Using Internet Mail
References Referenced by |
Proposed Standard | Reference | |
RFC 2738 |
Corrections to "A Syntax for Describing Media Feature Sets"
References Referenced by |
Proposed Standard | Reference | |
RFC 2879 |
Content Feature Schema for Internet Fax (V2)
References Referenced by |
Proposed Standard | Reference | |
RFC 2880 |
Internet Fax T.30 Feature Mapping
References Referenced by |
Informational | Reference | |
RFC 2912 |
Indicating Media Features for MIME Content
References Referenced by |
Proposed Standard | Reference | |
RFC 2913 |
MIME Content Types in Media Feature Expressions
References Referenced by |
Proposed Standard | Reference | |
RFC 2938 |
Identifying Composite Media Features
References Referenced by |
Proposed Standard | Reference | |
RFC 3297 |
Content Negotiation for Messaging Services based on Email
References Referenced by |
Proposed Standard | Reference |