HTML
HTML (HyperText Markup Language) and hypertext document formats
HTML subjects:
- MHTML2 RFCs
HTML RFCs (16)
RFC 8216: HTTP Live Streaming
Informational- R. Pantos
- W. May
- August 2017
- Independent Stream publication
Abstract
This document describes a protocol for transferring unbounded streams of multimedia data. It specifies the data format of the files and the actions to be taken by the server (sender) and the clients (receivers) of the streams. It describes version 7 of this protocol.
Abstract
This document describes a protocol for transferring unbounded streams of multimedia data. It specifies the data format of the files and the actions to be taken by the server (sender) and the clients (receivers) of the streams. It describes version 7 of this protocol.
RFC 7992: HTML Format for RFCs
Informational- J. Hildebrand
- P. Hoffman
- December 2016
- IAB publication
Abstract
In order to meet the evolving needs of the Internet community, the canonical format for RFCs is changing from a plain-text, ASCII-only format to an XML format that will, in turn, be rendered into several publication formats. This document defines the HTML format that will be rendered for an RFC or Internet-Draft.
Abstract
In order to meet the evolving needs of the Internet community, the canonical format for RFCs is changing from a plain-text, ASCII-only format to an XML format that will, in turn, be rendered into several publication formats. This document defines the HTML format that will be rendered for an RFC or Internet-Draft.
RFC 7993: Cascading Style Sheets (CSS) Requirements for RFCs
Informational- H. Flanagan
- December 2016
- IAB publication
Abstract
The HTML format for RFCs assigns style guidance to a Cascading Style Sheet (CSS) specifically defined for the RFC Series. The embedded, default CSS as included by the RFC Editor is expected to take into account accessibility needs and to be built along a responsive design model. This document describes the requirements for the default CSS used by the RFC Editor. The class names are based on the classes defined in "HTML for RFCs" (RFC 7992).
Abstract
The HTML format for RFCs assigns style guidance to a Cascading Style Sheet (CSS) specifically defined for the RFC Series. The embedded, default CSS as included by the RFC Editor is expected to take into account accessibility needs and to be built along a responsive design model. This document describes the requirements for the default CSS used by the RFC Editor. The class names are based on the classes defined in "HTML for RFCs" (RFC 7992).
RFC 5791: RFC 2731 ("Encoding Dublin Core Metadata in HTML") Is Obsolete
Informational- J. Reschke
- J. Kunze
- February 2010
- IETF publication
Abstract
This document obsoletes RFC 2731, "Encoding Dublin Core Metadata in HTML", as further development of this specification has moved to the Dublin Core Metadata Initiative (DCMI). This document is not an Internet Standards Track specification; it is published for informational purposes.
Abstract
This document obsoletes RFC 2731, "Encoding Dublin Core Metadata in HTML", as further development of this specification has moved to the Dublin Core Metadata Initiative (DCMI). This document is not an Internet Standards Track specification; it is published for informational purposes.
RFC 2854: The 'text/html' Media Type
Informational- D. Connolly
- L. Masinter
- June 2000
- Legacy publication
Abstract
This document summarizes the history of HTML development, and defines the "text/html" MIME type by pointing to the relevant W3C recommendations. This memo provides information for the Internet community.
Abstract
This document summarizes the history of HTML development, and defines the "text/html" MIME type by pointing to the relevant W3C recommendations. This memo provides information for the Internet community.
RFC 2731: Encoding Dublin Core Metadata in HTML
Informational- J. Kunze
- December 1999
- Legacy publication
Abstract
The Dublin Core is a small set of metadata elements for describing information resources. This document explains how these elements are expressed using the META and LINK tags of HTML. This memo provides information for the Internet community.
Obsoleted by RFC 5791
Abstract
The Dublin Core is a small set of metadata elements for describing information resources. This document explains how these elements are expressed using the META and LINK tags of HTML. This memo provides information for the Internet community.
RFC 2659: Security Extensions For HTML
Experimental- E. Rescorla
- A. Schiffman
- August 1999
- IETF publication
- Security Area
Abstract
This memo describes a syntax for embedding S-HTTP negotiation parameters in HTML documents. This memo defines an Experimental Protocol for the Internet community.
Abstract
This memo describes a syntax for embedding S-HTTP negotiation parameters in HTML documents. This memo defines an Experimental Protocol for the Internet community.
RFC 2387: The MIME Multipart/Related Content-type
Proposed Standard- E. Levinson
- August 1998
- IETF publication
- Applications Area
Abstract
This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
Abstract
This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
RFC 2392: Content-ID and Message-ID Uniform Resource Locators
Proposed Standard- E. Levinson
- August 1998
- IETF publication
- Applications Area
Abstract
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
Abstract
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
RFC 2111: Content-ID and Message-ID Uniform Resource Locators
Proposed Standard- E. Levinson
- March 1997
- IETF publication
- Applications Area
Abstract
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
Obsoleted by RFC 2392
Abstract
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
RFC 2112: The MIME Multipart/Related Content-type
Proposed Standard- E. Levinson
- March 1997
- IETF publication
- Applications Area
Abstract
The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
Obsoleted by RFC 2387
Abstract
The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
RFC 2070: Internationalization of the Hypertext Markup Language
Historic- F. Yergeau
- G. Nicol
- G. Adams
- M. Duerst
- January 1997
- IETF publication
- Applications Area
Abstract
This document is meant to address the issue of the internationalization (i18n, i followed by 18 letters followed by n) of HTML by extending the specification of HTML and giving additional recommendations for proper internationalization support. [STANDARDS-TRACK]
Obsoleted by RFC 2854
Abstract
This document is meant to address the issue of the internationalization (i18n, i followed by 18 letters followed by n) of HTML by extending the specification of HTML and giving additional recommendations for proper internationalization support. [STANDARDS-TRACK]
RFC 1980: A Proposed Extension to HTML : Client-Side Image Maps
Historic- J. Seidman
- August 1996
- Legacy publication
Abstract
The markup language known as "HTML/2.0" provides for image maps. Image maps are document elements which allow clicking different areas of an image to reference different network resources, as specified by Uniform Identifier (URIs). The image map capability in HTML/2.0 is limited in several ways, such as the restriction that it only works with documents served via the "HTTP" protocol, and the lack of a viable fallback for users of text-only browsers. This document specifies an extension to the HTML language, referred to as "Client- Side Image Maps," which resolves these limitations.
Obsoleted by RFC 2854
Abstract
The markup language known as "HTML/2.0" provides for image maps. Image maps are document elements which allow clicking different areas of an image to reference different network resources, as specified by Uniform Identifier (URIs). The image map capability in HTML/2.0 is limited in several ways, such as the restriction that it only works with documents served via the "HTTP" protocol, and the lack of a viable fallback for users of text-only browsers. This document specifies an extension to the HTML language, referred to as "Client- Side Image Maps," which resolves these limitations.
RFC 1942: HTML Tables
Historic- D. Raggett
- May 1996
- IETF publication
- Applications Area
Abstract
This specification extends HTML to support a wide variety of tables. This memo defines an Experimental Protocol for the Internet community.
Obsoleted by RFC 2854
Abstract
This specification extends HTML to support a wide variety of tables. This memo defines an Experimental Protocol for the Internet community.
RFC 1866: Hypertext Markup Language - 2.0
Historic- T. Berners-Lee
- D. Connolly
- November 1995
- IETF publication
- Applications Area
Abstract
This document defines a HTML 2.0 (to distinguish it from the previous informal specifications). [STANDARDS-TRACK]
Obsoleted by RFC 2854
Abstract
This document defines a HTML 2.0 (to distinguish it from the previous informal specifications). [STANDARDS-TRACK]
RFC 1867: Form-based File Upload in HTML
Historic- E. Nebel
- L. Masinter
- November 1995
- IETF publication
- Applications Area
Abstract
Since file-upload is a feature that will benefit many applications, this proposes an extension to HTML to allow information providers to express file upload requests uniformly, and a MIME compatible representation for file upload responses. This memo defines an Experimental Protocol for the Internet community.
Obsoleted by RFC 2854
Abstract
Since file-upload is a feature that will benefit many applications, this proposes an extension to HTML to allow information providers to express file upload requests uniformly, and a MIME compatible representation for file upload responses. This memo defines an Experimental Protocol for the Internet community.
Subscribe to HTML
Get notified when:
- RFC changes to status, obsoleted by, updates, updated by, or subseries.
- New RFC added to this subject or below
- The subject was merged into another.