API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Preference is stored in this browser only.

IETF RFC 2506
[ACTIVE]

Media Feature Tag Registration Procedure

Metadata

Publisher
IETF
Doc Type
Best Practice
Pages
12
Abstract
This document defines a registration procedure which uses the Internet Assigned Numbers Authority (IANA) as a central registry for the media feature vocabulary. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date
1999-03-01
Status Note
Best Current Practice
DOI
10.17487/RFC2506
Link
https://doi.org/10.17487/RFC2506
Author(s)
Koen Holtman
Dr. Andrew Mutz
Ted Hardie
Keyword(s)
Data, Formats
Latest version of IETF RFC 2506

Document Versions — IETF RFC 2506

  • ▶ IETF RFC 2506 (1999-03-01)
    THIS DOC [ACTIVE] [LATEST VERSION]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC2506.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 2506, Media Feature Tag Registration Procedure. Available at https://doi.org/10.17487/RFC2506
Snippet:
IETF RFC 2506, Media Feature Tag Registration Procedure. Available at https://doi.org/10.17487/RFC2506

HTML (ISO 690 compliant)

Preview:
IETF RFC 2506, Media Feature Tag Registration Procedure. Available at https://doi.org/10.17487/RFC2506
Snippet:
<span class="citation"><cite>IETF RFC 2506</cite>, Media Feature Tag Registration Procedure. Available at <a href="https://doi.org/10.17487/RFC2506" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2506</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 2506, Media Feature Tag Registration Procedure
doi: 10.17487/RFC2506
url: https://doi.org/10.17487/RFC2506
Snippet:
<li>
<cite id="bib-rfc2506">IETF RFC 2506</cite>, Media Feature Tag Registration Procedure
<span class="doi">10.17487/RFC2506</span>
</li>

Referenced By