RFC1817 on CIDR and Classful Routing
"Joyce K. Reynolds" <jkrey@isi.edu> Fri, 04 August 1995 15:47 UTC
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa11420; 4 Aug 95 11:47 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa12140; 4 Aug 95 11:47 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11096; 4 Aug 95 11:46 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10784; 4 Aug 95 11:29 EDT
Received: from [128.9.160.160] by CNRI.Reston.VA.US id aa11579; 4 Aug 95 11:29 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA18452>; Fri, 4 Aug 1995 08:29:48 -0700
Message-Id: <199508041529.AA18452@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1817 on CIDR and Classful Routing
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 04 Aug 1995 08:31:42 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 1817: Title: CIDR and Classful Routing Author: Y. Rekhter Date: August 1995 Mailbox: yakov@cisco.com Pages: 2 Characters: 3,416 Updates/Obsoletes: none URL: ftp://ds.internic.net/rfc/rfc1817.txt Classless Inter-Domain Routing (CIDR) is used in the Internet as the primary mechanism to improve scalability of the Internet routing system. This document represents the IAB's (Internet Architecture Board) evaluation of the current and near term implications of CIDR on organizations that use Classful routing technology. This memo provides information for the Internet community. This memo 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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@ISI.EDU. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@ISI.EDU 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 admin@DS.INTERNIC.NET. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information. Joyce K. Reynolds 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.
- RFC1817 on CIDR and Classful Routing Joyce K. Reynolds