[26/02/2008] IPv6 PI reachability
On June 13, 2007, the AfriNIC community adopted after long debates, the policy for IPv6 PI assignments for end-sites (http://www.afrinic.net/docs/policies/afpol-v6200701.htm).
In a message on August 14, 2007, Mark J Elkins informed the community of the difficulties he was facing with the routing of the PI prefix 2001:43f8:30::/48. (https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000129.html)
The prefix recorded only a visibility of 80% while PA allocations, i-e the /32 of AfriNIC showed a visibility bordering the 100%. (http://www.sixxs.net/tools/grh/dfp/all/?country=za)
AIRRS project team has decided to make some investigations:
1- To identify the causes of the problems
2- To identify possible solutions
II-1 Situation of the allocations of IPv6 addresses in the five regions
If all the five regions allocate IPv6 prefixes to LIRs with a minimum of /32, the situation varies according to the region with regard to the portable assignments.
The intial provider independent assignment size to an end-site should be a /48, or a shorter prefix if the end-site can justify it.
Three portable assignments cases are authorized in the Asia Pacific region:
- Organizations multihomed or projected to become it within three month are qualified to receive a portable assignment.
The minimum assignment made under these terms is /48.
- The following critical infrastructure networks, if operating in the Asia Pacific region, are eligible to receive a portable assignment:
- root domain name system (DNS) server;
- global top level domain (gTLD) nameservers;
- country code TLD (ccTLDs) nameservers;
- Regional Internet Registry (RIRs); and
- National Internet Registry (NIRs).
The maximum assignment made under these terms is /32 per operator.
- 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.
The minimum assignment made under these terms is /48.
Micro-allocations are also made for Internet operators of critical infrastructures, like the public IXPs, core DNS service providers (e.g. ICANN-sanctioned root, gTLD, and ccTLD operators) as well as the RIRs and IANA.
These allocations will be no longer than a /48. Multiple allocations may be granted in certain situations.
The micro-allocations are available at: www.arin.net/reference/micro_allocations.html
LACNIC makes micro-allocations in case of projects and network infrastructure that are key or critical for the operation and development of IPv6 within the region, such as IXPs (Internet Exchange Points), NAPs (Network Access Points), RIRs (Regional Internet Registries), DNS ccTLD providers, among others.
These allocations shall be made in blocks smaller than or equal a /32 but always greater than or equal to a /48.
In RIPE region, the portable assignments are possible for root servers operators operating in the region on the minimum allocated to LIRs at the moment, which is /32 (http://www.ripe.net/ripe/docs/ripe-233.html
Certain operators of TLD (ccTLD and gTLD) can be qualified to receive assignments for DNS Anycast service. The size of the allocated prefix is /48.
IXPs are qualified to receive assignments. If the requesting organization is confident that it will never need more than a single network then a /64 will be assigned. Otherwise, a /48 will be assigned. http://www.ripe.net/ripe/docs/ripe-256.html
II-2 Prefixes and minimum allocation and assignment size per region
The prefixes list and minimum of allocation and assignment size can be found for the five regions at the following places:
III-Course of the investigations
In order to carry out the investigations, the AIRRS (African Internet resources and
Routing Statistics) project team requested a temporary PI assignment of a /48 for some testing purpose. The prefix assigned by AfriNIC is the 2001:43f8:40::/48.
Tests environment uses AS33764 which has IPv6 transit from AS1280 and AS2905. The prefix has been announced and was accepted by both upstreams.
AS1280 passed the prefix to its peers and this gave a visibility of 81% on the scale of Ghost Route Hunter's IPv6 DFP visibility. (http://www.sixxs.net/tools/grh/dfp/afrinic/)
Our exchanges with the NOC of AS2905 revealed the followings:
1- Only /48 from the ARIN micro-allocations block 2001:500::/30 are passed to peers by AS12702 and AS701.
2- These ASes filter IPv6 routes on the /32 boundary.
3- They are not adjusting filters for PI /48 as announced by RIRs, because on the global IPv6 view, IPv6 PI isn't defined in any RFC.
4- Their IPv6 routing filters decision is to not support PI assignment approach until the IPv6 multihoming and PI topic is somehow standardized.
The visibility recorded by /48 from ARIN micro-allocations from 2001:500::/30 shows the impact of these types of routes filtering on the routing. (http://www.sixxs.net/tools/grh/dfp/arin/)
On the basis of our experiment, we present the following findings for consideration by the AfriNIC community:
1- The concept of IPv6 portable assignment is not yet widely accepted by the global community,
2- Certain operators filter IPv6 prefixes on the /32 boundary and are not adjusting filters to accommodate PI assignments as announced by the RIRs
3- The concept of IPv6 micro-allocation for critical Internet infrastructures seems acceptable.
Regarding the IPv6 PI assignment, we recommend the dissociation of the cases:
- Define the rules for portable assignments for critical Internet infrastructures. Those recognized overall seem to be: Publics IXPs, core DNS service providers (e.g. ICANN-sanctioned root, gTLD, and ccTLD operators) as well as the RIRs and IANA.
- For the IPv6 global portable assignment, consider a concerted work with the other communities which have adopted similar policy for a better communication on the issue, as /48 for end-site seems to be preferred to /32.
This work could include the standardization of the maintenance and distribution of filtering recommendations based of RIRs allocations and assignments minimum size and specific blocks used for them. An example of effort in this direction is the one published at:
AIRRS project team thanks AfriNIC for its support for this work.
[25/03/2008] AfriNIC-8/AfNOG2008: Registration is now open
[14/05/2008] Board Elections 2008:Opening of public comments
[03/06/2008] Member Survey 2008
[11/06/2008] New Board Members
During the 2008 AGM held in Morocco after the AfriNIC-8 meeting, two seats on the AfriNIC Board (of Directors) - (the Central and Indian Ocean seats) were renewed.
After the vote, Didier Rukeratabaro Kasole (Democratic Republic of Congo) and Viv Padayatchy (Mauritius) were elected as primary BoDs, while Jean Philemon Kissangou (Congo) and Lala Andriamampianina (Madagascar) were elected as alternates for their respective regions.
Congratulations for the new board members and we wish them success during their term.
[06/08] Last call for comments on ''Global Policy For Comments on Global Policy for the Allocation of the remaining IPv4 Address Space
[29/12/08] AfriNIC to implement next phase of the 4-byte AS Number policy from 1/1/2009
The policy for assignment of AS Numbers in the region (Please see
http://www.afrinic.net/docs/policies/afpol-asn0604.htm) requires AfriNIC to
treat requests for AS Numbers w.e.f 01/01/2009 as follows:
On 1 January 2009 the registry will process applications that
specifically request 2-byte only AS Numbers and allocate such
AS Numbers as requested by the applicant. In the absence of any
specific request for a 2-byte only AS Number, a 4-byte only AS
Number will be allocated by the registry.
We would therefore like to inform the community that from 01/01/2009,
unless a 2-byte AS Number has been explicitly requested, AfriNIC will be
assigning 4-byte AS Numbers to any organization requiring an AS Number.
It is important to check that your routers as well as those of your peers,
can understand 4-byte ASNs, as this is a relatively new implementation.
For more information about 4-byte AS Numbers, please see: