References to draft-ietf-conneg-feature-reg

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 3840
As bcp31
Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard normatively references
RFC 4235
As bcp31
An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard normatively references
RFC 4281
As bcp31
The Codecs Parameter for "Bucket" Media Types
References Referenced by
Proposed Standard normatively references
RFC 4569
As bcp31
Internet Assigned Number Authority (IANA) Registration of the Message Media Feature Tag
References Referenced by
Informational normatively references
RFC 5259
As bcp31
Internet Message Access Protocol - CONVERT Extension
References Referenced by
Proposed Standard normatively references
RFC 5626
As rfc2506
Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard normatively references
RFC 5626
As bcp31
Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard normatively references
RFC 7866
As rfc2506
Session Recording Protocol
References Referenced by
Proposed Standard normatively references
RFC 7866
As bcp31
Session Recording Protocol
References Referenced by
Proposed Standard normatively references
RFC 3841
As bcp31
Caller Preferences for the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 5688
As rfc2506
A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtypes
References Referenced by
Proposed Standard informatively references
RFC 5688
As bcp31
A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtypes
References Referenced by
Proposed Standard informatively references
RFC 6809
As rfc2506
Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 6809
As bcp31
Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 6913
As rfc2506
Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 6913
As bcp31
Indicating Fax over IP Capability in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 8848
As rfc2506
Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
References Referenced by
Experimental informatively references
RFC 8848
As bcp31
Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)
References Referenced by
Experimental informatively references
RFC 2533
As rfc2506
A Syntax for Describing Media Feature Sets
References Referenced by
Proposed Standard Possible Reference
RFC 2987
As rfc2506
Registration of Charset and Languages Media Features Tags
References Referenced by
Proposed Standard Possible Reference
RFC 3840
As rfc2506
Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard Possible Reference
RFC 3841
As rfc2506
Caller Preferences for the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard Possible Reference
RFC 4235
As rfc2506
An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard Possible Reference
RFC 4569
As rfc2506
Internet Assigned Number Authority (IANA) Registration of the Message Media Feature Tag
References Referenced by
Informational Possible Reference
RFC 5259
As rfc2506
Internet Message Access Protocol - CONVERT Extension
References Referenced by
Proposed Standard Possible Reference
RFC 2530
As rfc2506
Indicating Supported Media Features Using Extensions to DSN and MDN
References Referenced by
Proposed Standard Reference
RFC 2530
As bcp31
Indicating Supported Media Features Using Extensions to DSN and MDN
References Referenced by
Proposed Standard Reference
RFC 2531
As bcp31
Content Feature Schema for Internet Fax
References Referenced by
Proposed Standard Reference
RFC 2533
As bcp31
A Syntax for Describing Media Feature Sets
References Referenced by
Proposed Standard Reference
RFC 2534
As bcp31
Media Features for Display, Print, and Fax
References Referenced by
Proposed Standard Reference
RFC 2879
As rfc2506
Content Feature Schema for Internet Fax (V2)
References Referenced by
Proposed Standard Reference
RFC 2880
As rfc2506
Internet Fax T.30 Feature Mapping
References Referenced by
Informational Reference
RFC 2912
As rfc2506
Indicating Media Features for MIME Content
References Referenced by
Proposed Standard Reference
RFC 2913
As rfc2506
MIME Content Types in Media Feature Expressions
References Referenced by
Proposed Standard Reference
RFC 2938
As rfc2506
Identifying Composite Media Features
References Referenced by
Proposed Standard Reference
RFC 2987
As bcp31
Registration of Charset and Languages Media Features Tags
References Referenced by
Proposed Standard Reference
RFC 3297
As rfc2506
Content Negotiation for Messaging Services based on Email
References Referenced by
Proposed Standard Reference
RFC 3297
As bcp31
Content Negotiation for Messaging Services based on Email
References Referenced by
Proposed Standard Reference