Fw: RFC 3021 on 31-Bit Prefixes on IPv4 Links

FYI.

----- Original Message ----- 
From: "RFC Editor" <rfc-ed at ISI.EDU>
To: <IETF-Announce: ;>
Cc: <rfc-ed at ISI.EDU>
Sent: Monday, December 18, 2000 7:31 PM
Subject: RFC 3021 on 31-Bit Prefixes on IPv4 Links


> 
> 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 at cisco.com, riw at cisco.com,
>                     vaf at valinor.barrnet.net, danny at 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 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 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.
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT00280.dat
Type: application/octet-stream
Size: 102 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/lir-wg/attachments/20010103/c257b0a0/attachment.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rfc3021.txt
URL: <https://www.ripe.net/ripe/mail/archives/lir-wg/attachments/20010103/c257b0a0/attachment.txt>