A new Request for Comments is now available in online RFC libraries.


        RFC 1866:

        Title:      Hypertext Markup Language - 2.0
        Author:     T. Berners-Lee & D. Connolly
        Date:       November 1995
        Mailbox:    timbl@w3.org, connolly@w3.org
        Pages:      77
        Characters: 146,904
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1866.txt


The Hypertext Markup Language (HTML) is a simple markup language used
to create hypertext documents that are platform independent. HTML
documents are SGML documents with generic semantics that are
appropriate for representing information from a wide range of domains.
HTML markup can represent hypertext news, mail, documentation, and
hypermedia; menus of options; database query results; simple
structured documents with in-lined graphics; and hypertext views of
existing bodies of information.  HTML has been in use by the World
Wide Web (WWW) global information initiative since 1990. This
specification roughly corresponds to the capabilities of HTML in
common use prior to June 1994. HTML is an application of ISO Standard
8879:1986 Information Processing Text and Office Systems; Standard
Generalized Markup Language (SGML).  The "text/html" Internet Media
Type (RFC 1590) and MIME Content Type (RFC 1521) is defined by this
specification.  This RFC is the product of the HyperText Markup
Language Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute