|

3. APNIC Internet Number Resource Policies

Part 3: IPv6 Policy

1 Leave a comment on paragraph 1 0 9.0. IPv6 allocations

2 Leave a comment on paragraph 2 0 9.1. Minimum IPv6 allocation

3 Leave a comment on paragraph 3 0 The minimum allocation size for IPv6 address space is /32.

4 Leave a comment on paragraph 4 0 Organizations that meet the initial allocation criteria are eligible to receive the minimum allocation. Larger initial allocations may be justified if:

  1. 5 Leave a comment on paragraph 5 0
  2. The organization provides comprehensive documentation of planned IPv6 infrastructure which would require a larger allocation; or
  3. The organization provides comprehensive documentation of all of the following:

7 Leave a comment on paragraph 7 0 In either case, an allocation will be made which fulfils the calculated address requirement, in accordance with the HD-Ratio based utilization policy.

8 Leave a comment on paragraph 8 0 9.2. Initial IPv6 allocations

9 Leave a comment on paragraph 9 0 9.2.1. Account holders with existing IPv4 space

10 Leave a comment on paragraph 10 0 Subject to Section 9.1., existing IPv4 networks may be considered in determining the initial IPv6 allocation size. APNIC applies a minimum size for IPv6 allocations to facilitate prefix-based filtering.

11 Leave a comment on paragraph 11 0 APNIC Members that have been delegated an IPv4 address block from APNIC, but have no IPv6 space, can qualify for an appropriately sized IPv6 block under the matching IPv6 policy. For example, a Member that has received an IPv4 IXP assignment will be eligible to receive an IPv6 IXP assignment.

12 Leave a comment on paragraph 12 0 The size of the IPv6 delegation for Members that meet this criteria will be based on the following:

  • 13 Leave a comment on paragraph 13 0
  • A Member that has an IPv4 allocation is eligible for a /32 IPv6 address block.
  • A Member that has an IPv4 assignment is eligible for a /48 IPv6 address block.

14 Leave a comment on paragraph 14 0 If an APNIC Member wishes to receive an initial allocation or assignment larger than the sizes described above, the Member will need to apply under the alternative criteria described in Section 9.2.2. and Section 10.1. below.

15 Leave a comment on paragraph 15 0 9.2.2. Account holders without existing IPv4 space

16 Leave a comment on paragraph 16 0 To qualify for an initial allocation of IPv6 address space, an organization must:

  1. 17 Leave a comment on paragraph 17 0
  2. Be an LIR
  3. Not be an end site
  4. Plan, within two years, to provide IPv6 connectivity to other organizations/end-users to which it will make assignments.

18 Leave a comment on paragraph 18 0 The allocation size, in case an address block bigger than the default one (as indicated in 9.2.1.) is requested, will be based on the umber of users, the extent of the organization’s infrastructure, the hierarchical and geographical structuring of the organization, the segmentation of infrastructure for security and the planned longevity of the allocation.

19 Leave a comment on paragraph 19 0 Private networks (those not connected to the public Internet) may also be eligible for an IPv6 address space allocation provided they meet equivalent criteria to those listed above.

20 Leave a comment on paragraph 20 0 9.3. Subsequent IPv6 allocations

21 Leave a comment on paragraph 21 0 Organizations that hold an existing IPv6 allocation may receive a subsequent allocation in accordance with the following policies.

22 Leave a comment on paragraph 22 0 9.3.1. Existing IPv6 address space holders

23 Leave a comment on paragraph 23 0 Organizations that received /35 IPv6 allocation under the previous IPv6 address policy [RIRv6-Policies] are immediately entitled to have their allocation expanded to a /32 address block, without providing justification, so long as they satisfy the criteria inSection 9.2.2.

24 Leave a comment on paragraph 24 0 The /32 address block will contain the already allocated smaller address block (one or multiple /35 address blocks in many cases) that was already reserved by the RIR for a subsequent allocation to the organization. Requests for additional space beyond the minimum /32 size will be evaluated as discussed elsewhere in this document.

25 Leave a comment on paragraph 25 0 9.3.2. Applied HD-Ratio

26 Leave a comment on paragraph 26 0 Subsequent allocation will be provided when an organization (ISP/LIR) satisfies the evaluation threshold of past address utilization in terms of the number of sites in units of /56 assignments.

27 Leave a comment on paragraph 27 0 The HD-Ratio [RFC 3194] is used to determine the utilization thresholds that justify the allocation of additional address as described below.

28 Leave a comment on paragraph 28 0 The HD-Ratio value of 0.94 is adopted as indicating an acceptable address utilization for justifying the allocation of additional address space. Appendix A provides a table showing the number of assignments that are necessary to achieve an acceptable utilization value for a given address block size.

29 Leave a comment on paragraph 29 0 9.3.3. Alternative allocation criteria

30 Leave a comment on paragraph 30 0 Alternatively, a subsequent allocation may be provided where an organization (ISP/LIR) can demonstrate a valid reason for requiring the subsequent allocation. For guidelines on what will be considered a valid technical or other reason, see “APNIC guidelines for IPv6 allocation and assignment requests”.

31 Leave a comment on paragraph 31 0 9.3.4. Size of subsequent allocation

32 Leave a comment on paragraph 32 0 When an organization has achieved an acceptable utilization for its allocated address space, it is immediately eligible to obtain an additional allocation that results in a doubling of the address space allocated to it.

33 Leave a comment on paragraph 33 0 Where possible, except where separate disaggregated ranges are requested for multiple discrete networks, the allocation will be made from an adjacent address block, meaning that its existing allocation is extended by one bit to the left.

34 Leave a comment on paragraph 34 0 If an organization needs more address space, it must provide documentation justifying its new requirements. The allocation size, will be based on the new needs (the number of users, the extent of the organization’s infrastructure, the hierarchical and geographical structuring of the organization, the segmentation of infrastructure for security and the planned longevity of the allocation).

35 Leave a comment on paragraph 35 0  

36 Leave a comment on paragraph 36 0 10.0. IPv6 assignments

37 Leave a comment on paragraph 37 0 APNIC Members that have been delegated an IPv4 address block from APNIC, but have no IPv6 space, can qualify for an appropriately sized IPv6 block under the matching IPv6 policy. For example, a Member that has received an IPv4 IXP assignment will be eligible to receive an IPv6 IXP assignment.

38 Leave a comment on paragraph 38 0 10.1. Criteria for IPv6 Assignments

39 Leave a comment on paragraph 39 0 To qualify for an IPv6 assignment from APNIC, requestors must demonstrate their eligibility under one of the following four criteria;

41 Leave a comment on paragraph 41 0 10.1.1. IPv6 for multihoming

42 Leave a comment on paragraph 42 0 An organization is eligible to receive a portable assignment from APNIC if it is currently, or plans to be, multihomed.

43 Leave a comment on paragraph 43 0 The minimum assignment made under these terms is /48.

44 Leave a comment on paragraph 44 0 10.1.2. IPv6 critical infrastructure

45 Leave a comment on paragraph 45 0 The following critical infrastructure networks, if operating in the Asia Pacific region, are eligible to receive a portable assignment:

  • 46 Leave a comment on paragraph 46 0
  • Root domain name system (DNS) server;
  • Global top level domain (gTLD) nameservers;
  • Country code TLD (ccTLDs) nameservers;
  • IANA;
  • Regional Internet Registry (RIRs); and
  • National Internet Registry (NIRs).

47 Leave a comment on paragraph 47 0 Assignments to critical infrastructure are available only to the actual operators of the network infrastructure performing such functions. Registrar organizations which do not actually host the network housing the registry infrastructure, will not be eligible for an assignment under this policy.

48 Leave a comment on paragraph 48 0 The maximum assignment made under these terms is /32 per operator.

49 Leave a comment on paragraph 49 0 10.1.3. IPv6 for Internet Exchange Points

50 Leave a comment on paragraph 50 0 Internet Exchange Points are eligible to receive a portable assignment from APNIC to be used exclusively to connect the IXP participant devices to the Exchange Point.

51 Leave a comment on paragraph 51 0 The minimum assignment made under these terms is /48.

52 Leave a comment on paragraph 52 0 Global routability of the portable assignment is left to the discretion of the IXP and its participants.

53 Leave a comment on paragraph 53 0 10.1.4. Provider Independent IPv6 assignment

54 Leave a comment on paragraph 54 0 Requests for Provider Independent assignments must include a detailed plan of intended usage of the proposed address block over at least the 12 months following the allocation.

55 Leave a comment on paragraph 55 0 10.1.4.1. Initial assignment

56 Leave a comment on paragraph 56 0 Organizations are eligible for an IPv6 Provider Independent delegation if they are able to demonstrate a valid reason that an assignment from their ISP, or LIR, is not suitable.

57 Leave a comment on paragraph 57 0 For guidelines on what will be considered a valid technical or other reason, see “APNIC guidelines for IPv6 allocation and assignment requests“.

58 Leave a comment on paragraph 58 0 The minimum size of the assignment is a /48. The considerations of Section 5.2.4.3 “Assignment of multiple /48s to a single end site” must be followed if multiple /48s are requested. “APNIC guidelines for IPv6 allocation and assignment requests“.

59 Leave a comment on paragraph 59 0 10.1.4.2. Subsequent assignment

60 Leave a comment on paragraph 60 0 Subsequent Provider Independent assignments may be delegated to organizations that are able to demonstrate

  • 61 Leave a comment on paragraph 61 0
  • why an additional portable assignment is required and why an assignment from an ISP or other LIR cannot be used for this purpose;
  • that the use of the initial provider independent delegation generated the minimum possible number of global routing announcements and the maximum aggregation of that block; and,
  • how the subsequent assignment will be managed to minimize the growth of the global IPv6 routing table.

62 Leave a comment on paragraph 62 0  

63 Leave a comment on paragraph 63 0 11.0. Transfer of IPv6 resources

64 Leave a comment on paragraph 64 0 APNIC will only recognize the transfer of IPv6 addresses as the result of Merger & Acquisition activity. The following conditions and consequences apply.

65 Leave a comment on paragraph 65 0 11.1. Updating registration details

66 Leave a comment on paragraph 66 0 If an LIR changes ownership (due to a merger, sale, or takeover), then the new entity must register any changes to its network usage and contact personnel. If the effect of the ownership change is that the LIR changes name, then the LIR must provide to APNIC relevant legal documentation supporting the name change.

67 Leave a comment on paragraph 67 0 11.2. Effect on membership agreement

68 Leave a comment on paragraph 68 0 If an LIR changes ownership then the new entity should advise APNIC of the change. APNIC membership is not transferable from one entity to another; however, if the effect of the ownership change is that the LIR becomes a subsidiary of another entity, and the infrastructures of the respective entities remain fully independent, then the membership agreement may continue.

69 Leave a comment on paragraph 69 0 11.3. Consequences for allocations

70 Leave a comment on paragraph 70 0 Following ownership change of an LIR, APNIC will review the status of any allocations that are held by the new entity or entities, with regard to the practical effect on their infrastructures.

71 Leave a comment on paragraph 71 0 If the practical effect of ownership change is that the infrastructures are merged, then APNIC will not continue to make separate allocations to both. This situation will invalidate the membership agreement of the LIR that is effectively subsumed.

72 Leave a comment on paragraph 72 0 When assessing the status of allocations, APNIC requires full disclosure of all address space held by all of the entities in question. If full disclosure is not made, then APNIC will consider any allocations to be invalid and will require that they be returned.

Pages: 1 2 3 4 5 6
Page 4

Source: https://comment.apnic.net/?page_id=81&page=4