Special-Use IPv4 Addresses
draft-iana-special-ipv4-05

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3330.
Author IANA
Last updated 2015-10-14 (Latest revision 2002-08-14)
RFC stream Legacy
Intended RFC status Informational
Formats
txt htmlized bibtex bibxml
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3330 (Informational)
Action Holders
(None)
Telechat date (None)
Responsible AD Randy Bush
IESG note
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-iana-special-ipv4-05 
A new Request for Comments is now available in online RFC libraries.

        RFC 3330
                                                          
        Title:      Special-Use IPv4 Addresses
        Author(s):  IANA
        Status:     Informational
        Date:       September 2002
        Mailbox:    iana@iana.org
        Pages:      7
        Characters: 16200
        Updates/Obsoletes/SeeAlso:    None
                                                          
        I-D Tag:    draft-iana-special-ipv4-05.txt

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

This document describes the global and other specialized IPv4 address
blocks that have been assigned by the Internet Assigned Numbers
Authority (IANA).  It does not address IPv4 address space assigned to
operators and users through the Regional Internet Registries.  It also
does not address allocations or assignments of IPv6 addresses or
autonomous system numbers.

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.