Policy Archive

Last Modified on -
Details
  • Ref. Name:
    AFPUB-2004-DNS-001
  • Old Ref:
    afpol-v6200407-000
  • Status:
    Implemented
  • Date:
    30 Jun 2004
  • Author:
    • Adiel Akplogan
    • Ernest Byaruhanga

1) Abstract

This document describes the policy for reverse delegation of IPv4 assignments and allocations in the AFRINIC service region. Please note that AFRINIC registers only reverse delegations and is not involved in the domain name registration system.

 

2) Introduction

AFRINIC provides support to enable applications to map to a domain name from an IP address. Reverse delegation is achieved by use of the in-addr.arpa (IPv4) and ip6.arpa (IPv6) domains.

 

3) Obtaining Delegation of an in-addr.arpa Sub-zone

AFRINIC only accepts requests for reverse delegation under in-addr.arpa from AFRINIC active LIRs. End Users must send their requests to the LIR from which they obtained the addresses, or in the case of Provider Independent addresses, to any of the LIRs of their choice. AFRINIC will carry out tests to ensure that the name server for the zone that the reverse delegation is being requested is up and configured as per the recommendedations in RFC1912.

 

4) Reverse Delegation for Provider Aggregatable (PA) Address Space

AFRINIC will only make delegations on 8-bit boundaries (/16 or /24). Multiple delegations may be requested to cover CIDR prefixes shorter blocks bigger than a /24.

 

5) Reverse Delegation for Provider Independent (PI) Address Space

AFRINIC will reverse delegate a zone in in-addr.arpa to an End User that has been assigned PI space.

For delegations of address blocks smaller than a /24 the method described in "Classless IN-ADDR.ARPA Delegation"[RFC 2317] will be used.

 

6) Validity of the Reverse Delegation

AFRINIC accepts requests for delegation and modifications of delegations from LIRs whose membership status is up-to-date.

Ipv6 Reverse Delegation

IETF consensus was reached that the IP6.ARPA domain be used for address to DNS name mapping for the IPv6 address space. Refer to:

  • RFC2874
  • RFC3596
  • Delegation of Ip6.arpa - Delegation of the ip6.arpa domain is done by the Intenet Assigned Numbers Authority (IANA). Names within this zone are delegated to Regional Internet Registries in accordance with their respective delegation of IPv6 address space. The process for requesting IPv6 reverse delegation in IP6.ARPA is described at here

 

Last Modified on -

 

Details
  • Ref. Name:
    AFPUB-2014-GEN-005-DRAFT-01
  • Status:
    Under Discussion
  • Date:
    26 Oct 2014
  • Author(s):
    - Karmann Olumomo

1)   Summary of the Problem being addressed by this proposal

Some members are experiencing extreme long wait for their additional allocation request to get passed, some members are experiencing none technical information requested from AFRINIC (customer data, marketing channels etc), in order to improve overall service quality of AFRINIC, here is the policy.

 

2) Summary of How this Proposal Addresses the Problem

To improve overall service quality and transparency of AFRINIC’s number resource services by documenting roles and responsibilities of AFRINIC.

 

3) Proposal

3.1) AFRINIC should make decision on subsequent allocation requests based on AFRINIC policy, and conclude a request no longer than the 20% of the total period AFRINIC approves the resources for. (E.g. If AFRINIC is issuing resources to its member to meet its 12 months needs, the longest waiting time for AFRINIC allocation process should not be longer than 20%*12month, to cope with 80% utilization requirement for additional allocation). If AFRINIC was not able to make decision on a certain request within this period, for each additional month beyond this period, the requesting member should receive percentage of the requested period of the total request until such decision has been made, in order to protect member from smooth running of its business.

 

3.2) AFRINIC should publish standardized base information request for each typical type of resource allocation.

 

3.3) AFRINIC should not store, request any marketing or business related none-technical information from its member, for example, customer data, marketing channel, and marketing budget.

 

3.4) AFRINIC allocations should be solely made based on current policy, no other factor other than policy should infer with AFRINIC’s decision on processing allocation requests.

 

3.5) Unless otherwise appealed, AFRINIC Board should not be directly involved in IP allocation process.

 

3.6) For the interest of overall policy development process, other RIR staff as well as its governing body personnel (advisor or board member, for example) should not be involved in AFRINIC policy development process.

 

3.7) AFRINIC policy working group chair election should be conducted independent from AFRINIC board nomination committee; candidates should be free of any requirement.

 

Page 13 of 65