RFC 2374 on IPv6 Global Unicast Address Format

[RFC Editor <rfc-ed at ISI.EDU>]

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


        RFC 2374:

        Title:	    An IPv6 Aggregatable Global Unicast Address Format
	Author(s):  R. Hinden, M. O'Dell, S. Deering
	Status:     Proposed Standard
	Date:       July 1998
        Mailbox:    hinden at iprg.nokia.com, mo at uunet.uu.net,
		    deering at cisco.com
	Pages:      12
        Characters: 25068
        Obsoletes:  2073


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

This document defines an IPv6 aggregatable global unicast address
format for use in the Internet.  The address format defined in this
document is consistent with the IPv6 Protocol [IPV6] and the "IPv6
Addressing Architecture" [ARCH].  It is designed to facilitate
scalable Internet routing.

This document is a product of the IPNG Working Group of the IETF.

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

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

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
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/rfc2374.txt>