Policy Archive

Last Modified on -

 

Details
  • Ref. Name:
    AFPUB-2006-ASN-001
  • Old Ref:
    afpol-chgasn200504
  • Status:
    Implemented
  • Date:
    17 May 2005
  • Author:
    Mark Tinka

1) Introduction

Precision in ASN policy documents about Assignment criteria ** Section 4 of the policy document

Was:

"4.0 Eligibility for an AS Number assignment:

--------------------------------------------

There are a limited number of available AS Numbers. Therefore, it is important to determine which sites require unique AS Numbers and which do not. Sites that do not require a unique AS Number should use one or more of the AS Numbers reserved for private use. Those numbers are: 64512 through 65535 (RFC 1930).

In order to qualify for an AS number, the requesting organization must fulfill the following requirements:

  • A unique routing policy (its policy differs from its border gateway peers).
  • A multi-homed site.
  • An organization will also be eligible if it can demonstrate that it will meet the above criteria upon receiving an ASN (or within a reasonably short time thereafter). 
  • All requests for ASNs under these criteria will be evaluated using the guidelines described in RFC1930 "Guidelines for the creation, selection and registration of an Autonomous System (AS)"." 

 

Should be

"4.0 Eligibility for an AS Number assignment:

--------------------------------------------- 

There are a limited number of available AS Numbers. Therefore, it is important to determine which sites require unique AS Numbers and which do not. Sites that do not require a unique AS Number should use one or more of the AS Numbers reserved for private use. Those numbers are: 64512 through 65535 (RFC 1930).

In order to qualify for an AS number, the requesting organization must fulfill the following requirements:

  • o A unique routing policy (its policy differs from its border gateway peers).
  • A multi-homed site.
  • An organization will also be eligible if it can demonstrate that it will meet the above criteria upon receiving an ASN (or within a reasonably short time thereafter).
  • Be an AfriNIC member in a good standing* (End-User or LIR type). All requests for ASNs under these criteria will be evaluated using the guidelines described in RFC1930 "Guidelines for the creation, selection and registration of an Autonomous System (AS)"."

 

2) Incentive

The original policy do not give precision on the membership criteria for ASN assignment. To better control this resource assignment Organisation using ASN must be specifically identified by AfriNIC.

 

 

History
17.04.2005 Proposal first posted to rpd mailing list.
13.12.2005 Consensus reached at AfriNIC 3 (Cairo - Egypt) to send to AfriNIC board for approval
09.02.2006 15 Days Last Call for Comments period starts
24.02.2006 15 Days Last Call for Comments ends.

Last Modified on -

 

Details
  • Ref. Name:
    AFPUB-2007-GEN-001
  • Old Ref:
    afpol-af200611
  • Status:
    Implemented
  • Date:
    13 Jun 2007
  • Author:
    • Adiel A. Akplogan

1) Incentive

In the very changing environment of the Internet and related services it is generally difficult to precisely plan IP addresses usage two years ahead. Further to that AfriNIC members may at the moment appear to have an unfair advantage over those in other regions. This will mean that all LIRs will plan their address space needs within the same time frames.

 

2) Introduction

This proposal suggests that AfriNIC should start allocating/assigning enough IPv4 and IPv6 address space to last a member's 1 year addressing needs (as opposed to currently 2, as is the practice).

 

3) Abstract

Current IPv4/v6 policy does not explicitly mention a timeframe that AfriNIC requires its members to plan for when requesting IP address space. The practice however is to allocate/assign enough IP address space to satisfy a member's two year requirements. This period is shorter in most of the other regions:

  • ARIN: 6 months
  • APNIC: 12 months
  • LACNIC: 3 months
  • RIPE: 24 months

 

4) Motivation

Fairness

Having a different allocation/assignment period could be seen as offering advantages to LIRs in one region over those in another. With a shorter allocation/assignment period, a member can only plan for the short term, whereas others will have more flexibility in terms of their planning. AfriNIC members may at the moment appear to have an unfair advantage over those in other regions. This will mean that all LIRs will plan their address space needs within the same time frames in all regions.

More accurate allocation based on real needs

With evaluation based on one year needs, it will be easy for LIR to precise in their needs statement. It will also contribute to speed up the evaluation process by AfriNIC's IP analysts as they won't have to assess too much new services which are not yet implemented but only planed (in two years period time) by the requestor.

Currently there are similar proposals in the LACNIC and RIPE regions to change this period to one year. ARIN has also adopted a similar policy.

 

5) Summary

In view of the above criteria, AfriNIC should allocate/assign enough IPv4 and IPv6 address space to last a member's 1 year addressing needs.

 

 

History
22.11.2006 Proposal first posted to rpd by author
02.05.2007 Consensus to accept reached during AfriNIC-6 in Abuja, Nigeria.
08.05.2007 15 Days Last Call period starts
23.05.2007 15 Days Last Call period ends.
13.06.2007 Implemented

Page 50 of 63