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


        RFC 1980:

        Title:      A Proposed Extension to HTML : Client-Side Image
                    Maps 
        Author:     J. Seidman
        Date:       August 1996
        Mailbox:    jim@spyglass.com
        Pages:      7
        Characters: 13,448
        Updates/Obsoletes: none

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


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.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  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