idnits 2.17.00 (12 Aug 2021) /tmp/idnits6919/draft-ietf-ipv6-unicast-aggr-v2-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3587 5 Title: IPv6 Global Unicast Address Format 6 Author(s): R. Hinden, S. Deering, E. Nordmark 7 Status: Informational 8 Date: August 2003 9 Mailbox: bob.hinden@nokia.com, erik.nordmark@sun.com 10 Pages: 5 11 Characters: 8783 12 Obsoletes: 2374 14 I-D Tag: draft-ietf-ipv6-unicast-aggr-v2-03.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3587.txt 18 This document obsoletes RFC 2374, "An IPv6 Aggregatable Global Unicast 19 Address Format". It defined an IPv6 address allocation structure that 20 includes Top Level Aggregator (TLA) and Next Level Aggregator (NLA). 21 This document makes RFC 2374 and the TLA/NLA structure historic. 23 This document is a product of the IP Version 6 Working Group of the 24 IETF. 26 This memo provides information for the Internet community. It does 27 not specify an Internet standard of any kind. Distribution of this 28 memo is unlimited. 30 This announcement is sent to the IETF list and the RFC-DIST list. 31 Requests to be added to or deleted from the IETF distribution list 32 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 33 added to or deleted from the RFC-DIST distribution list should 34 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 36 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 37 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 38 help: ways_to_get_rfcs. For example: 40 To: rfc-info@RFC-EDITOR.ORG 41 Subject: getting rfcs 43 help: ways_to_get_rfcs 45 Requests for special distribution should be addressed to either the 46 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 47 specifically noted otherwise on the RFC itself, all RFCs are for 48 unlimited distribution.echo 49 Submissions for Requests for Comments should be sent to 50 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 51 Authors, for further information.