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