RFC 2072:Router Renumbering Guide
RFC-Ref

ISP


Click on the red underlined text to get to the source

... APNIC) or by an Internet Service Provider (ISP). This assignment of a value in the most significant bit positions historically has been ...
... High-order-part-only renumbering is most common when an organization changes ISPs, and needs to renumber into the new provider's space. The old prefix ...
... Both the high-order and low-order parts may change. This might happen when the enterprise changes to a new ISP, who assigns address space from a CIDR block rather than a classful network ...


... boundary routers that connect the domain to a single ISP. ...
... data base, but the reverse mapping data base may be maintained by its ISP. This can require coordination when changing providers. ...


... enterprise has been using 10.0.0.0/8 as its primary prefix, but has introduced an ISP whose registered addresses were in 172.31.0.0/16. ...


... externally-controlled part of the prefix, as might be the case when an organization changes ISPs and renumbers into the ISP's address space, without changing the internal subnet ...
... prefix, as might be the case when an organization changes ISPs and renumbers into the ISP's address space, without changing the internal subnet structure. ...


... configuration changes. Since the outside screening router may be under the control of the ISP rather than the entrerprise, administrative coordination will be needed. ...


... routing mechanism between some customers and their ISPs, as a means simpler than BGP for the customer ...


... BGP. RIP is not infrequently used to allow ISPs to learn dynamically of new customer routes, although there are security concerns in such an approach. ...
... Routing Arbiter). If an ISP whose previous address space came from a different provider ...


... DNS changes. Coordinate changes with affected external organizations (e.g., ISPs, business partners, routing registries) ...



Google
Web
RFC-Ref