RFC 1930:Guidelines for creation, selection, and r...
RFC-Ref

service provider


Click on the red underlined text to get to the source

... This memo is aimed at network operators and service providers who need to understand under what circumstances they should make use of an AS ...


... prefix has exactly the same rout- ing policy as the other customers of the site's service provider, and there is no need to make any distinction in rout- ing information. ...
... group of prefixes which connects to more than one service provider (i.e. more than one AS with its own routing policy ...
... single AS, distinct from the ASes of its service providers. This allows the customer the ability to have a different repre- ...
... This allows the customer the ability to have a different repre- sentation of policy and preference among the different service providers. This is ALMOST THE ONLY case where a network operator ...
... * Transition / "future-proofing" Often a site will be connected to a single service provider but has plans to connect to another at some point in the future. This is not enough of a reason to create ...
... need it. The AS number space is finite and the limited amount of re-engineering needed when you connect to another service provider should be considered as a natural step in transition. * History ...


... should only be looked at if practical to do so and fully coordinated between customers and service providers involved. ...



Google
Web
RFC-Ref