RFC 2732 on IPv6 Literal Addresses in URL's

RFC Editor <rfc-ed@ISI.EDU> Fri, 17 December 1999 20:03 UTC

Message-Id: <199912171951.LAA15381@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2732 on IPv6 Literal Addresses in URL's
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 17 Dec 1999 11:51:04 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2732

        Title:	    Format for Literal IPv6 Addresses in URL's
        Author(s):  R. Hinden, B. Carpenter, L. Masinter
        Status:     Standards Track
	Date:       December 1999
        Mailbox:    hinden@iprg.nokia.com, brian@icair.org,
                    masinter@parc.xerox.com 
        Pages:      5
        Characters: 7984
	Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-ietf-ipngwg-url-literal-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2732.txt


This document defines the format for literal IPv6 Addresses in URL's
for implementation in World Wide Web browsers.  This format has been
implemented in the IPv6 versions of several widely deployed browsers
including Microsoft Internet Explorer, Mozilla, and Lynx.  It is also
intended to be used in the IPv6 version of the service location
protocol.

This document incudes an update to the generic syntax for Uniform
Resource Identifiers defined in RFC 2396 [URL].  It defines a syntax
for IPv6 addresses and allows the use of "[" and "]" within a URI
explicitly for this reserved purpose.

This document is a product of the IPNG 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2732.txt"><ftp://ftp.isi.edu/in-notes/rfc2732.txt>

RFC 2732 on IPv6 Literal Addresses in URL's RFC Editor