Internet DRAFT - draft-ietf-ipv6-unicast-aggr-v2

draft-ietf-ipv6-unicast-aggr-v2



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


        RFC 3587

        Title:      IPv6 Global Unicast Address Format
        Author(s):  R. Hinden, S. Deering, E. Nordmark
        Status:     Informational
        Date:       August 2003
        Mailbox:    bob.hinden@nokia.com, erik.nordmark@sun.com
        Pages:      5
        Characters: 8783
        Obsoletes:  2374

        I-D Tag:    draft-ietf-ipv6-unicast-aggr-v2-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3587.txt


This document obsoletes RFC 2374, "An IPv6 Aggregatable Global Unicast
Address Format".  It defined an IPv6 address allocation structure that
includes Top Level Aggregator (TLA) and Next Level Aggregator (NLA).
This document makes RFC 2374 and the TLA/NLA structure historic.

This document is a product of the IP Version 6 Working Group of the
IETF. 

This memo provides information for the Internet community.  It 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@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.