RFC 3021 on 31-Bit Prefixes on IPv4 Links

RFC Editor <rfc-ed@ISI.EDU> Mon, 18 December 2000 18:41 UTC

Message-Id: <200012181831.KAA14056@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3021 on 31-Bit Prefixes on IPv4 Links
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 18 Dec 2000 10:31:23 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3021

        Title:	    Using 31-Bit Prefixes on IPv4 Point-to-Point Links
        Author(s):  A. Retana, R. White, V. Fuller, D. McPherson
        Status:     Standards Track
	Date:       December 2000
        Mailbox:    aretana@cisco.com, riw@cisco.com,
                    vaf@valinor.barrnet.net, danny@ambernetworks.com 
        Pages:      10
        Characters: 19771
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-retana-31bits-03.txt

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


With ever-increasing pressure to conserve IP address space on the
Internet, it makes sense to consider where relatively minor changes
can be made to fielded practice to improve numbering efficiency.  One
such change, proposed by this document, is to halve the amount of
address space assigned to point-to-point links (common throughout the
Internet infrastructure) by allowing the use of 31-bit subnet masks
in a very limited way.

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/rfc3021.txt"><ftp://ftp.isi.edu/in-notes/rfc3021.txt>

RFC 3021 on 31-Bit Prefixes on IPv4 Links RFC Editor