|
Дополнение к заявке на получение провайдеро-независимых IP-адресов.
Прокомментируйте пожалуйста дополнение, составленное RIPE'ом к
заявке на получение провайдеро-независимых IP-адресов (PI addresses).
# There are certain pieces of information we need in every request for # PI space. Please re-check your request. If you have not answered the # questions below you should do so now. The Hostmaster will not be able # to complete the evaluation of your request if you have not addressed # the points below. # # 1. Why is PI space required rather than PA space? # # - If PI is requested for multi-homing please explain why the second # provider cannot route PA space as a more specific route (with the # PA block holder adding a more specific route too). # # - If you are considering PI space instead of becoming an LIR (i.e. # using PI space as an allocation and making assignments to end-users # from it) you should be aware that this is not according to policy as # described in the RIPE Document, "European Internet Registry Policies # and Procedures" document, RIPE-185, Section 3.1 "Introduction": # # Address space is assigned by IRs to end users who use it to operate # the specific networks described in an address space request. IRs # guarantee that no other end user will be assigned the same address # space during the validity of the assignment. # # - So if you will have end-users with their own networks, PA space # should be assigned by an LIR. # # 2. Please check you are not requesting for extra address space for routing # or administrative reasons. If for example, 80 IPs are sufficient, the # subnet size should be a /26 and a /28, and not a /25. Please note the # requirements of the "European Internet Registry Policies and Procedures" # document, RIPE-185, Section 3.4.1 "Assignments within Allocations": # # Suppose a request can be satisfied with either a number of small # chunks of address space or with a single large one. For example, if # 384 addresses are sufficient to satisfy a request, but no more than # 256 will be used in a single physical subnet, then the user can be # assigned a /24 and a /25 rather than a /23, which results in saving a # /25 for another user. In accordance with the conservation goal, Local # IRs are encouraged to assign multiple ranges of addresses in such # cases, rather than a single large range. Of course the effort to do so # should increase as the amount of address space that can be saved in # doing so increases. # # - Also, please note "Provider Independent vs Provider Aggregatable # Address Space", RIPE-127, Section 2, "Assignment Policies": # # Assignment criteria for both kinds of address space will be exactly # identical with regards to the amount of address space assigned, the # registration requirements etc. This also implies that assigning PI # space prefixes longer than 24 bits is perfectly acceptable if the # request does not merit 8 bits of address space to be assigned. # # 3. Please confirm whether you have made the end-user aware of the # warning given in "Provider Independent vs Provider Aggregatable # Address Space", RIPE-127, Section 3, "Detailed Recommendations": # # Assignment of this address space is valid as long as the criteria # for the original assignment are still met. However, assignment of # address space does NOT imply that this address space will be # ROUTABLE ON ANY PART OF THE INTERNET. It is expected that users # will have to pay a premium for actual routing of PI addresses as # opposed to PA addresses. It may eventually become impossible to get # relatively small amounts of PI space routed on most of the # Internet. We strongly suggest you contact any prospective service # provider for information about the possibility and pricing of # service when using PI addresses. # # You are required to confirm that the points mentioned above have been # read and confirmed and that your customer requesting the PI Address # Space is fully aware of the disadvantages with Provider Independent # Address Space. |