% Datatracker information for RFCs on the Legacy Stream is unfortunately often
% incorrect. Please correct the bibtex below based on the information in the
% actual RFC at https://rfc-editor.org/rfc/rfc936.txt

@misc{rfc936,
    series =    {Request for Comments},
    number =    936,
    howpublished =  {RFC 936},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC0936},
    url =       {https://www.rfc-editor.org/info/rfc936},
    author =    {},
    title =     {{Another Internet subnet addressing scheme}},
    pagetotal = 4,
    year =      1985,
    month =     feb,
    abstract =  {There have been several proposals for schemes to allow the use of a single Internet network number to refer to a collection of physical networks under common administration which are reachable from the rest of the Internet by a common route. Such schemes allow a simplified view of an otherwise complicated topology from hosts and gateways outside of this collection. They allow the complexity of the number and type of these networks, and routing to them, to be localized. Additions and changes in configuration thus cause no detectable change, and no interruption of service, due to slow propagation of routing and other information outside of the local environment. These schemes also simplify the administration of the network, as changes do not require allocation of new network numbers for each new cable installed. This proposal discusses an alternative scheme, one that has been in use at the University of California, Berkeley since April 1984. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.},
}