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


        RFC 2017:

        Title:      Definition of the URL
                    MIME External-Body Access-Type
        Author:     N. Freed,  K. Moore, A. Cargille
        Date:       October 1996
        Mailbox:    ned@innosoft.com, moore@cs.utk.edu
        Pages:      5
        Characters: 9,000
        Updates/Obsoletes:  None

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


This memo defines a new access-type for message/external-body MIME
parts for Uniform Resource Locators (URLs).  URLs provide schemes to
access external objects via a growing number of protocols, including
HTTP, Gopher, and TELNET.  An initial set of URL schemes are defined
in RFC 1738. This RFC is the product of the Mail Extensions 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 and Mary Kennedy
USC/Information Sciences Institute