Your IP address is 35.175.191.46
IPv4 Exhaustion - IPv4 Exhaustion
Please select your question category
Search FAQs
All FAQs
View all frequently asked questions
Tags
View FAQ Tags
Billing

AFRINIC membership and resources related billing FAQs.

WHOIS Database

AFRINIC WHOIS related FAQs
General Queries

General FAQs related to AFRINIC activites
MyAFRINIC

MyAFRINIC portal related FAQs
Membership and Resource Request

Membership related queries

AFRINIC member

FAQ for Existing members
BPKI

AFRINIC BPKI Services
IPv4 Exhaustion

FAQs related to IPv4 Exhaustion and its impact on AFRINIC
FAQs - IPv4 Exhaustion

FAQs related to IPv4 Exhaustion and its impact on AFRINIC

1. How did IPv4 address pool get exhausted?

There are 232 (around 4.3 billion) unique IPv4 addresses and in the early days of the Internet, this seemed like a huge amount. But the Internet grew faster than anyone could have predicted and engineers soon realised that the limited supply of IPv4 address space would not be enough to meet future demand for emerging users and connected devices. In anticipation of this, the Internet Engineering Task Force (IETF) developed, tested and standardised IPv6 in the late 1990s.

2. What will happen when AFRINIC starts assigning IPv4 address space from the last /8 of address space?

AFPUB-2010-v4-005: “The IPv4 Soft Landing Policy”will come into effect.

This proposal describes how AFRINIC will allocate and manage IPv4 resources during the IPv4 "Exhaustion Phase".

3. Who decided how to distribute AFRINIC’s last /8 of IPv4 address space?

The AFRINIC community proposed, developed and accepted AFPUB-2010-v4-005: “The IPv4 Soft Landing Policy” using the AFRINIC Policy Development Process (PDP). The AFRINIC Board of Directors ratified this policy in 2011.

4. Now that the other RIRs are assigning from their own last /8s or will do so in the near future, does this mean that AFRINIC will see an increase in its own IPv4 allocation rates?

AFRINIC has seen consumption rates increase rapidly over the last few months. In the near future, it is inevitable that AFRINIC will become the only region where, with correct justification, significant amounts of IPv4 address space can be obtained. We expect this to lead to a sharp increase in requests and our Member Services Team is preparing accordingly for this. All requests are evaluated and any eventual allocations are made according to the community-defined IPv4 allocation policy.

5. What can I do about IPv4 exhaustion?

Nothing. The only way to ensure that networks continue to run seamlessly and all devices around the world can continue to communicate with each other is to deploy IPv6 on networks and run them in parallel with IPv4 networks. You can find out more about how you can plan for your IPv6 deployment by looking at the information on our IPv4 Exhaustion section, our IPv6 Deployment section and our Training website. 

6. Does IPv4 exhaustion mean that the Internet will stop working?

No. The Internet will continue to operate as normal. However, unless networks are IPv6 ready, devices IPv6 enabled and content made available over IPv6, there is a very real possibility that certain parts of the network that remains on IPv4-only may become unreachable to those connecting with an IPv6 address and vice versa. The only solution is for network operators to deploy IPv6 as soon as possible.

7. AFRINIC still has a supply of IPv4 address space. Why should we deploy IPv6 when there’s still enough IPv4 for African networks?

In those regions where operators can only obtain small IPv4 allocations because their RIR has exhausted its supply of IPv4, many now have to invest in IPv6 networks if they have not already done so. It is extremely important that African network operators also start their transitioning process as soon as possible to ensure they can continue communicating with IPv4 and IPv6 networks in other regions. This is the only way to guarantee that all Internet users will be able to freely access the global Internet from Africa and to ensure that Africa remains a global player in online world.

8. Where can I find out more about IPv6 Deployment?

AFRINIC has a comprehensive IPv6 programme that includes information, deployment guides, free training courses and an IPv6 test bed for operators to test IPv6 networks on. You can also find more information on our IPv4 Exhaustion section, our IPv6 Deployment and our Training website. Government representatives can download our IPv6 for Governments handbook.

Display #

Profile Information

Application afterLoad: 0.003 seconds, 0.71 MB
Application afterInitialise: 0.058 seconds, 2.70 MB
Application afterRoute: 0.352 seconds, 5.95 MB
Application afterDispatch: 0.388 seconds, 7.00 MB
Application afterRender: 0.570 seconds, 9.54 MB

Memory Usage

10052912

26 queries logged

  1. SELECT m.*, c.`option` AS component
      FROM www3menu AS m
      LEFT JOIN www3components AS c
      ON m.componentid = c.id
      WHERE m.published = 1
      ORDER BY m.sublevel, m.parent, m.ordering
  2. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(1,11,20,304,324,262,231,275,340,393,791,661,12,51,348,805,831,13,52,154,795,14,24,53,793,15,797,16,62,803,17,799,68,97,27,387,619,191,221,172,170,76,171,337,418,521,845,175,174,177,237,176,499,511,455,481,523,547,671,184,185,188,423,837,527,179,181,204,235,156,158,159,384,475,675,629,160,161,162,157,192,621,268,270,266,321,264,265,338,416,483,519,843,276,283,278,282,477,677,279,631,280,281,429,277,382,305,306,307,308,424,835,317,330,318,319,320,325,326,327,328,529,341,342,343,345,350,349,408,351,354,745,489,509,356,479,525,549,673,388,400,403,404,405,406,419,513,399,394,396,397,395,617,615,663,665,801,414,163,731,733,735,737,715,739,741,789,743,269,271,272,292,289,290,291,293,294,339,295,420,386,807,811,285,286,288,819,383,287,515,567,809,817,415,284,633,763,315,312,561,563,565,767,314,380,517,332,333,334,335,336,370,346,347,311,378,787,352,364,362,365,833,719,366,367,368,411,412,453,825,379,357,358,359,360,361,371,431,459,463,467,469,471,473,531,533,537,539,541,543,545,599,609,601,605,485,487,491,493,495,497,551,553,557,559,841,573,575,577,579,581,583,585,591,589,777,779,813,749,751,753,755,747,757,759,761,783,373,374,375,376,721,417,829,669,353,413,461,535,781,727,667,611,597,603,815,769,635,637,639,641,645,643,647,649,651,653,655,657,659,785,821,823,827,697,701,703,705,707,709,711)
       
      AND jf_content.reference_table='menu'
  3. SELECT *
      FROM www3rokcandy
      WHERE published=1
  4. SELECT template
      FROM www3templates_menu
      WHERE client_id = 0
      AND (menuid = 0 OR menuid = 513)
      ORDER BY menuid DESC
      LIMIT 0, 1
  5. SELECT *
      FROM www3fsf_settings
  6. SELECT *
      FROM www3fsf_settings_big
  7. SELECT *
      FROM www3fsf_settings_view
  8. SELECT *
      FROM www3fsf_faq_cat
      WHERE published = 1
      ORDER BY ordering
  9. SELECT *
      FROM www3fsf_user
      WHERE user_id = '0'
  10. SELECT id, link
      FROM www3menu
      WHERE link LIKE '%option=com_fsf%'
      AND published = 1
  11. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(400,388,404,393,394,395,396,397,399,403,405,406,419,513)
       
      AND jf_content.reference_table='menu'
  12. SELECT *
      FROM www3fsf_faq_faq
      WHERE faq_cat_id = '13'
      AND published = 1
      ORDER BY ordering
  13. SELECT *
      FROM www3fsf_faq_faq
      WHERE faq_cat_id = '13'
      AND published = 1
      ORDER BY ordering
      LIMIT 0, 15
  14. SELECT *
      FROM www3fsf_faq_tags
      WHERE faq_id IN (191, 193, 195, 197, 199, 201, 203, 205)
      GROUP BY tag
      ORDER BY tag
  15. SELECT COUNT(*) AS cnt
      FROM www3fsf_faq_tags
  16. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  17. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  18. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  19. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  20. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  21. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  22. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  23. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  24. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  25. SELECT id, title, module, POSITION, content, showtitle, control, params
      FROM www3modules AS m
      LEFT JOIN www3modules_menu AS mm
      ON mm.moduleid = m.id
      WHERE m.published = 1
      AND m.access <= 0
      AND m.client_id = 0
      AND ( mm.menuid = 513 OR mm.menuid = 0 )
      ORDER BY POSITION, ordering
  26. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(79,330,35,326,331,347,345,329,292,335)
       
      AND jf_content.reference_table='modules'

Language Files Loaded

Untranslated Strings Diagnostic

None

Untranslated Strings Designer

None