RFC 1466:Guidelines for Management of IP Address S...
RFC-Ref

subscriber


Click on the red underlined text to get to the source

... registry is unbiased and and widely recognized by network providers and subscribers within the geographic region. It is also important that there is just a single regional registry ...
... IR directly. Depending on the circumstances the network subscriber may be referred to the regional registry, but the IR ...
... service any network subscriber if necessary. ...


... network numbers to assign to a network subscriber based on the subscriber's 24 month projection of required end system addresses ...
... assign to a network subscriber based on the subscriber's 24 month projection of required end system addresses according to the ...
... networks If the subscriber's network is divided into logically distinct LANs ...
... network numbers, the above criteria may apply on a per-LAN basis. For example, if a subscriber has 600 hosts equally divided across ten Ethernets ...
... hosts equally divided across ten Ethernets, the allocation to that subscriber could be ten Class C network ...
... network numbers; one for each Ethernet. The subscriber would have to support the request with to deviate from the stated criteria with an engineering plan. ...
... engineering plan. These criteria are not intended to cause a subscriber to subnet Class ...
... Class C networks unneccessarily. Although, if a subscriber has a small number of hosts per subnet ...
... number of hosts per subnet, the subscriber should investigate the feasibility of subnetting Class C network ...
... plan detailing why subnetting is impossible. If a subscriber has a requirement for more than 4096 unique IP addresses it could conceivably receive a Class ...
... Class B network number. However, there are cases where a subscriber may request a larger block of Class C network ...
... Class C network numbers that should be assigned to a subscriber consists of 64 contiguous Class C networks. This would ...


... Rekhter, Y. and Topolcic, C., "Exchanging Routing Information across Provider/Subscriber boundaries in CIDR environment", Work in Progress, February 1993. ...



Google
Web
RFC-Ref