RFC 950: Internet Standard Subnetting Procedure
In plain English — editorial summary, not part of the RFC
This memo discusses the utility of "subnets" of Internet networks, which are logically visible sub-sections of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This memo specifies procedures for the use of subnets. These procedures are for hosts (e.g., workstations). The procedures used in and between subnet gateways are not fully described. Important motivation and background information for a subnetting standard is provided in RFC-940. This RFC specifies a protocol for the ARPA-Internet community. If subnetting is implemented it is strongly recommended that these procedures be followed.
Document record
- Document ID
- RFC950
- Published
- August 1985
- Authors
- J.C. Mogul; J. Postel
- Status
- INTERNET STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 18
- Also known as
- STD5
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 1620Internet Architecture Extensions for Shared MediaCurrent
May 1994
- RFC 1637DNS NSAP Resource RecordsObsoleted
June 1994
- RFC 1706DNS NSAP Resource RecordsUpdated
October 1994
- RFC 1797Class A Subnet ExperimentCurrent
April 1995
- RFC 1868ARP Extension - UNARPCurrent
November 1995
- RFC 1931Dynamic RARP Extensions for Automatic Network Address AcquisitionCurrent
April 1996
- RFC 2469A Caution On The Canonical Ordering Of Link-Layer AddressesCurrent
December 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?