BTW.Media
Édition du jourVeille stratégique Internet
ConnexionS'inscrire

AFRINIC · Veille des RIR

AFRINIC Whois Database Update Process

Commencez ici pour consulter l’historique, proposition par proposition : ce qui a changé, pourquoi cela comptait, qui a défendu quoi, comment les positions ont évolué, ce qui a été décidé et quelles lacunes subsistent dans les preuves.

Faits sourcés

Identifiant
AFPUB-2014-GEN-001
RIR
AFRINIC
Statut officiel
Withdrawn
Statut normalisé
Retirée
Introduction
15 mai 2014
Dernière mise à jour des sources
12 oct. 2026
Couverture
Partielle

Qui a réellement façonné le débat ?

3Total des participants
2Contributeurs à la discussion
1Acteurs formels
2Messages de discussion
2Entités effectives
100 %Part des cinq premiers
1Personnes couvrant 50 %
2Personnes couvrant 80 %

Évolution de la politique

DRAFT-01
18 mai 2014
Faits sourcés ↗

source_comparison_limit · Both captures identify draft-01. The earlier capture is only an archive placeholder, while the original RPD announcement supplies the proposal text. This is recovery of missing evidence, not evidence of a policy amendment; no substantive policy change can be inferred by comparing the empty wrapper with the recovered draft.

Faits sourcés −
📦 Archived Content — This page was originally hosted at 1133-afrinic-whois-database-update-process-afpub-2014-gen-001-draft-01 and has been preserved locally. This page references content from the AFRINIC archive.
Faits sourcés ↗
Faits sourcés +
Draft Policy name: AfriNIC Whois Database Update Process Unique identifier: AFPUB-2014-GEN-001-DRAFT-01 Status: New Submission Date 15 MAY 2014 Author:Jean Robert Hountomey
Faits sourcés ↗
DRAFT-02
Retirée · Withdrawn
Inconnue
Faits sourcés ↗

annual_validation_and_holder_duties · The draft strengthens annual validation from staff 'should' language to a mandatory check. It also directly requires object owners to check and update at least annually and organizations to update records when requesting resources or services. These are proposed obligations; the withdrawn draft does not itself establish current enforceability.

Faits sourcés −
Furthermore, at least once a year or at the renewal of resources, AFRINIC staff should conduct a whois database information validation. 3. The Proposal AfriNIC members are committed through the RSA to maintain their data and keep it accurate. AfriNIC will then maintain accuracy of whois information through periodical database clean up or update. AfriNIC will periodically ask object owners in the Whois Database to actively check and update the accuracy of data in AfriNIC whois database.
Faits sourcés ↗
Faits sourcés +
Furthermore, at least once a year or at the renewal of resources, AFRINIC staff must conduct a whois database information validation. 3) Proposal AFRINIC members are committed through the RSA to maintain their data and keep it accurate. AFRINIC must then maintain accuracy of whois information through periodical database clean up and update. Object owners in the whois Database are required at least once a year to actively check and update the accuracy of their data in AFRINIC whois database.
Faits sourcés ↗

response_and_reminder_deadlines · Draft-01 allows one month for an email response. Draft-02 specifies 30 days and adds a reminder on day 15 warning that a further 15 days without response leads to a grace period.

Faits sourcés −
3.2.1 - AfriNIC staff will ask members to confirm accuracy of their records in the Whois database in a month’s timeframe when contacted by email. 3.2.2 - After one month, AfriNIC Staff will use any communication tools at their discretion to contact those who have not answered or those whose email has bounced back. 3.2.3 - After another month of unresponsive response, the record will be marked invalid.
Faits sourcés ↗
Faits sourcés +
AFRINIC staff will ask members by email to confirm the accuracy of their records in the Whois database within thirty (30) days. Fifteen (15) days after the first contact initiation, AFRINIC staff will send a reminder email to members who have not responded, notifying them that they will enter a "Grace Period" within 15 days, should a response still not be forthcoming.
Faits sourcés ↗

bounced_contact_followup · Draft-01 waits one month before alternative contact attempts, including for bounced mail. Draft-02 requires immediate attempts through alternative means when an email is returned as undeliverable.

Faits sourcés −
3.2.1 - AfriNIC staff will ask members to confirm accuracy of their records in the Whois database in a month’s timeframe when contacted by email. 3.2.2 - After one month, AfriNIC Staff will use any communication tools at their discretion to contact those who have not answered or those whose email has bounced back. 3.2.3 - After another month of unresponsive response, the record will be marked invalid.
Faits sourcés ↗
Faits sourcés +
For contacts whose email has bounced back for "Non Delivery", AFRINIC Staff will immediately begin attempting to reach organizations via alternative means of communication.
Faits sourcés ↗

grace_period_timing · Draft-01 refers to another month before marking an unresponsive record invalid. Draft-02 defines a grace period starting 31 days after first contact and lasting 30 days, during which staff continue trying to reach members through available communication tools.

Faits sourcés −
3.2.1 - AfriNIC staff will ask members to confirm accuracy of their records in the Whois database in a month’s timeframe when contacted by email. 3.2.2 - After one month, AfriNIC Staff will use any communication tools at their discretion to contact those who have not answered or those whose email has bounced back. 3.2.3 - After another month of unresponsive response, the record will be marked invalid.
Faits sourcés ↗
Faits sourcés +
Thirty one (31) days after the first contact initiation starts the Grace Period. The Grace period lasts thirty (30) days. During the Grace Period, AFRINIC Staff will use any communication tools at their discretion to reach points of contact for member organizations who have not confirmed the accuracy of their records.
Faits sourcés ↗

invalidation_and_publication · Invalidation is tied to the end of the grace period, 61 days after initial contact. Publication changes from a discretionary report about resources with invalid contacts to a required list of non-responsive contacts and associated objects, published within 24 hours.

Faits sourcés −
3.2.3 - After another month of unresponsive response, the record will be marked invalid. 3.2.4 - AfriNIC may publish publicly a report about number resources with invalid POC.
Faits sourcés ↗
Faits sourcés +
3.3.3 - Record is marked invalid and the community notified. At the end of the Grace Period (61 days after the first contact initiation), AFRINIC will publish, within 24 hours, the list of non-responsive contacts and the objects associated with them. The associated objects will be marked INVALID.
Faits sourcés ↗

rectification_before_expiry · Draft-02 adds a procedure to remove a non-expired invalid resource record from the public website after its owner confirms the update in writing. AFRINIC must acknowledge within 72 hours; withdrawal should follow within 72 hours of that acknowledgement. Draft-01's publication-and-reclamation sequence contains no corresponding removal timetable.

Faits sourcés −
3.2.4 - AfriNIC may publish publicly a report about number resources with invalid POC. 3.2.5 - One year after the first contact initiation, if the data is still not accurate and the organization has failed to respond to the call to resolve the data inconsistency, AfriNIC may claim the number resources back.
Faits sourcés ↗
Faits sourcés +
An invalid resource record that has not expired can be withdrawn from the publicly available website after the object owners (new or old) address written notification to AFRINIC confirming that the records have been updated. AFRINIC shall acknowledge the object owner notification within 72 hours of receipt, and the withdrawal of the object from the publicly available website should occur within 72 hours of such acknowledgement.
Faits sourcés ↗

expiry_and_reclamation · At the one-year endpoint, Draft-01 permits reclamation if inaccurate data and non-response persist. Draft-02 requires marking the resource expired and reclaiming its associated number resources into AFRINIC's pool.

Faits sourcés −
3.2.5 - One year after the first contact initiation, if the data is still not accurate and the organization has failed to respond to the call to resolve the data inconsistency, AfriNIC may claim the number resources back.
Faits sourcés ↗
Faits sourcés +
One year after the first contact initiation, if the data is still not accurate and the organization has failed to respond to the requests to resolve the data inconsistency, AFRINIC will mark the Resource EXPIRED and claim the associated number resources back. The resource will go back to AFRINIC's pool.
Faits sourcés ↗

reapplication_after_expiry · Draft-02 adds a new application and associated fees when an organization returns after expiry, without a guarantee of receiving the same resources. Reclaimed resources are removed from the public list. Draft-01's reclamation clause does not specify these consequences.

Faits sourcés −
3.2.5 - One year after the first contact initiation, if the data is still not accurate and the organization has failed to respond to the call to resolve the data inconsistency, AfriNIC may claim the number resources back.
Faits sourcés ↗
Faits sourcés +
If the Organization contacts AFRINIC after the expiration, a new application with associated fees will be required with no guarantee that the Organization will keep the same resource. Once the resource is reclaimed, it will be removed from the publicly available website.
Faits sourcés ↗

refunds_after_reclamation · Draft-02 adds an explicit no-refund provision when an expired record's resources return to AFRINIC's pool. The old one-year reclamation provision does not specify this financial consequence.

Faits sourcés −
3.2.5 - One year after the first contact initiation, if the data is still not accurate and the organization has failed to respond to the call to resolve the data inconsistency, AfriNIC may claim the number resources back.
Faits sourcés ↗
Faits sourcés +
3.3.6. - No Refund. This current policy gives a year to an Organization to update its information in the AFRINIC Database before expiration. In case a record reaches an expiration status and is returned to AFRINIC's pool, the organization cannot claim a refund for any portion of unused fund.
Faits sourcés ↗

time_counting · Draft-02 defines literal calendar time rather than working days, daily start and expiry times, and the time zone of AFRINIC's registered address. This replaces the earlier draft's unqualified month-based timing with an explicit counting convention.

Faits sourcés −
3.2.1 - AfriNIC staff will ask members to confirm accuracy of their records in the Whois database in a month’s timeframe when contacted by email.
Faits sourcés ↗
Faits sourcés +
3.3.7. - Hours and timezone. For the purposes of this policy time periods specified are literal and not based on working days. Where time frames are specified in days, a day is deemed to have begun at 00:01 after the communication is received/sent. The time frame expires at 23:59 on the corresponding days. Times are based on the timezone relevant to the registered address of AFRINIC.
Faits sourcés ↗

Chronologie du débat

  1. Version officielle

    draft-01

    Faits sourcés ↗

  2. Version officielle

    DRAFT-02

    Retirée · Withdrawn

    Faits sourcés ↗

  3. Présentation

    Présentation

    Faits sourcés ↗

  4. Version officielle

    DRAFT-02

    Faits sourcés ↗

  5. Version officielle

    DRAFT-01

    Faits sourcés ↗

Entités

Actualité: Périmé
  1. Seun Ojedeji
    Messages de discussion1
    Première activité5 déc. 2014
    Dernière activité5 déc. 2014
    Première position expliciteInconnue
    Dernière position expliciteInconnue
    Changements de position0
    Cohérence du point de vueÉléments insuffisants pour évaluer la cohérence
    Autres politiques13
    Actualité: Périmé

    Dernière tentative de recherche: 25 sept. 2026

    Identité vérifiée: 25 sept. 2026

    Federal University Oye-Ekiti · Historique
    Job Principal Network Engineer Organisation Federal University Oye-Ekiti
    meeting.afrinic.net

    Profils publics vérifiés

    Messages de discussion
    1
    Première activité
    5 déc. 2014
    Dernière activité
    5 déc. 2014
    Première position explicite
    Inconnue
    Dernière position explicite
    Inconnue
    Changements de position
    0
    Cohérence du point de vue
    Éléments insuffisants pour évaluer la cohérence
    Autres politiques
    13

    Première position explicite: Inconnue → Dernière position explicite: Inconnue · Changements de position: 0

    Cohérence du point de vue: Éléments insuffisants pour évaluer la cohérence

    Seun Ojedeji's available statements mainly document policy-development procedure rather than personal positions on the merits of proposals. His two February 2015 explanations consistently distinguish ordinary IPv4 allocation requirements from an anycast purpose. His questions about out-of-region use do not establish a settled position, and the co-chairs' differing consensus reports concern different proposals and stages. The record therefore supports a narrow finding of consistent operational interpretation, but not a general verdict on his substantive views across these policies.

    AFPUB-2012-V4-001-DRAFT-01

    Évaluation: Cohérent · The two February 2015 explanations are compatible: an ordinary IPv4 application must meet the usual utilization requirements, and anycast may then be its intended use within the policy and bylaws. The later agreement clarifies the earlier distinction rather than reversing it.

    Réserves: This finding concerns the interpretation of ordinary allocation requirements, not support for a particular policy amendment. · Only the two supplied February 2015 statements establish this continuity.

    Correct but at that point, it's a normal v4 application with all the utilization requirements.

    Agree; so long as the normal v4 allocation requirements are meet which includes utilization requirements, the purpose can then be anycast or anything within the limitation of the policy/bylaw ;)

    No Reverse Unless Assigned

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The July 2013 reminder keeps No Reverse Unless Assigned in last call and sets out how comments will be assessed. It gives no personal position on the proposal's merits and no second substantive statement with which to assess continuity.

    Réserves: The announced future assessment and communication date are plans, not evidence of a decision already made.

    All comments that were received from the Public policy meeting (AFRINIC18, Lusaka) and up until 31st July 2013 will be evaluated by the co-chairs to determine the final state of this policy proposal, which will be communicated to the PDWG on 2013-08-08 by the co-chairs.

    Anycast resource assignments in the AFRINIC region

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The sequence reports meeting consensus and last call, then an unopposed minor change and a forthcoming recommendation, and finally a draft awaiting Board ratification. These are compatible stages of a process. They do not establish a sustained personal stance on the anycast proposal's substantive terms.

    Réserves: A report of meeting consensus or an intended recommendation is not proof of Board ratification. · The suggestion to propose an update through the normal PDP is procedural advice, not endorsement of that update.

    The co-chairs will soon formally recommend ratification of this policy proposal to the AFRINIC Board.

    There is a related policy awaiting board ratification which you may want to look at and then propose an update through following the normal PDP (policy development process)

    Resource Reservations for Internet Exchange Points

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The December 2014 report of no consensus and the later AFRINIC-22 agenda both place IXP resource reservations in continuing discussion. Neither states Ojedeji's personal position, so they cannot establish consistency or inconsistency on the proposed reservation rules.

    Réserves: No consensus at one meeting is not permanent rejection; scheduling further discussion is not endorsement.

    Resource Reservation for Internet Exchange Points (AFPUB-2014-GEN-004-DRAFT-01)

    Number Resources Transfer Policy (AFPUB-2015-GEN-001-DRAFT-01)

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The two January 2016 messages report the same AFRINIC23 outcome for the transfer proposal; the second explicitly repairs formatting. They are not two independent personal opinions and provide no basis for a verdict on Ojedeji's substantive transfer-policy stance.

    Réserves: The reported outcome is no consensus and a return to the mailing list, not personal opposition or the policy's later status.

    Number Resources Transfer Policy (AFPUB-2015-GEN-001-DRAFT-01) No Consensus ? back to *rpd *list

    Initial attempt got out of format. trying again.

    Number Resources Transfer Policy (AFPUB-2015-GEN-001-DRAFT-01) No Consensus ? back to *rpd *list

    AFRINIC Whois Database Update Process

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The only supplied statement reports that the author withdrew the Whois Database Update Process proposal. Reporting another person's withdrawal does not disclose Ojedeji's own view of the proposal or a change in that view.

    Réserves: This is a co-chairs' meeting-status announcement, not the sender withdrawing his own support.

    Out-Of-Region Use of AFRINIC Internet Number Resources

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The October 2014 messages question how the proposal would affect expansion in Africa and the resource needs of offshore offices and points of presence. Later messages announce discussion, a revised draft and no-consensus outcomes. The questions do not settle a personal position, and the procedural announcements cannot supply one or demonstrate its reversal.

    Réserves: The no-consensus reports describe their respective meetings and must not be treated as the policy's current status. · The May 2015 update notice contains an inconsistent policy identifier; its title, author and out-of-region-use link identify its subject without resolving that documentary error.

    Just to be clear, do you think this policy will deny availability of IP resource to organisations that intend to expand their growth in Africa?

    In summary you are saying offshore offices and pops devices will require so much IP resource than the customers being served by the organisation [1]

    Draft Policy name: Out-Of-Region Use of AFRINIC Internet Number Resources Unique identifier: AFPUB-2014-GEN-001-DRAFT-03

    Out-Of-Region Use of AFRINIC Internet Number Resources (AFPUB-2014-GEN-002-DRAFT-03) No Consensus ? back to *rpd *list

    AFRINIC Service Guidelines

    Évaluation: Éléments insuffisants pour évaluer la cohérence · Reporting no consensus for Service Guidelines and later placing it on the meeting agenda are compatible procedural acts. Neither provides a substantive personal position to compare over time.

    Réserves: Continuing the discussion does not imply support, and the earlier no-consensus report does not imply permanent rejection.

    AFRINIC Service Guidelines (AFPUB-2014-GEN-005-DRAFT-01)

    AFRINIC Board statement on resource allocation — 25 November 2014

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The December 2014 reply invites the other participant to turn a suggested protection into a written policy proposal. That single invitation establishes a preference for using the policy process, but not endorsement of a particular allocation threshold or enough evidence to assess change over time.

    Réserves: Do not infer support for a specific /18 threshold from the invitation to draft a policy.

    I have spotted a possible policy item ;) could you consider writing a policy that achieve what you've mentioned above?

    Anycast resource assignments in the AFRINIC region · Out-Of-Region Use of AFRINIC Internet Number Resources

    Évaluation: Éléments insuffisants pour évaluer la cohérence · The same co-chairs' announcement reports consensus and last call for anycast while returning out-of-region use to the list without consensus. Different outcomes for different proposals do not demonstrate contradictory personal positions: the announcement records the meeting's conclusions, not Ojedeji's votes or a common substantive rule applied inconsistently.

    Réserves: Assess personal consistency only from attributable substantive positions, preserving the distinction between a chair's procedural reporting and individual advocacy.

    1. 5 déc. 2014 · Procédural ou neutre

      [rpd] Policy Proposals and Minutes of the PDP Meeting in Mauritius - Status

      Les éléments de preuve validés ne sont pas disponibles.

      Faits sourcés ↗
    Chronologies des positions par politique:AFPUB-2012-DNS-001 · Inconnue · Éléments insuffisants pour évaluer la cohérenceAFPUB-2012-GEN-001 · Inconnue · Aucune position explicite n’a été énoncéeAFPUB-2012-V4-001 · Inconnue · CohérentAFPUB-2013-GEN-001 · Inconnue · Aucune position explicite n’a été énoncéeAFPUB-2013-V4-001 · Inconnue · Aucune position explicite n’a été énoncéeAFPUB-2013-V4-002 · Inconnue · Aucune position explicite n’a été énoncéeAFPUB-2013-V6-001 · Inconnue · Aucune position explicite n’a été énoncéeAFPUB-2014-GEN-001 · Inconnue · Éléments insuffisants pour évaluer la cohérenceafpub-2014-gen-002 · Inconnue · Éléments insuffisants pour évaluer la cohérenceAFPUB-2014-GEN-003 · Inconnue · Éléments insuffisants pour évaluer la cohérenceafpub-2014-gen-004 · Inconnue · Éléments insuffisants pour évaluer la cohérenceAFPUB-2014-GEN-005 · Inconnue · Éléments insuffisants pour évaluer la cohérenceAFPUB-2015-GEN-001 · Inconnue · Éléments insuffisants pour évaluer la cohérenceAFRINIC Board statement on resource allocation — 25 November 2014 · Inconnue · Éléments insuffisants pour évaluer la cohérence

    Messages de politique: 91

  2. Adam Nelson · Identité non résolue
    Messages de discussion1
    Première activité7 nov. 2014
    Dernière activité7 nov. 2014
    Première position expliciteInconnue
    Dernière position expliciteInconnue
    Changements de position0
    Cohérence du point de vueAucune position explicite n’a été énoncée
    Autres politiques4
  3. Jean-Robert Hountomey · Identité non résolue
    Messages de discussion0
    Première activitéInconnue
    Dernière activitéInconnue
    Première position expliciteInconnue
    Dernière position expliciteInconnue
    Changements de position0
    Cohérence du point de vueAucune position explicite n’a été énoncée
    Autres politiques1

Sources et couverture

Sources officielles

Archives des discussions publiques

  • afrinic-rpd
    Première capture
    4 août 2004
    Dernière capture
    25 août 2026
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    13 106
    Lacunes connues
    0
  • www.afrinic.net
  • afrinic-africann
    Première capture
    3 août 2026
    Dernière capture
    2 oct. 2026
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    2 622
    Lacunes connues
    0
  • afrinic-afripv6-discuss
    Première capture
    17 août 2015
    Dernière capture
    18 sept. 2026
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    2 538
    Lacunes connues
    0
  • afrinic-announce
    Première capture
    18 août 2015
    Dernière capture
    18 sept. 2026
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    2 497
    Lacunes connues
    0
  • afrinic-community-discuss
    Première capture
    11 sept. 2015
    Dernière capture
    29 déc. 2019
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    3 127
    Lacunes connues
    0
  • afrinic-dbwg
    Première capture
    4 août 2026
    Dernière capture
    6 oct. 2026
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    965
    Lacunes connues
    0
  • afrinic-dnssec-ops
    Première capture
    18 août 2015
    Dernière capture
    1 déc. 2016
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    307
    Lacunes connues
    0
  • afrinic-icp2-review
    Première capture
    10 avr. 2025
    Dernière capture
    10 nov. 2025
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    0
    Lacunes connues
    0
  • afrinic-measurement-wg
    Première capture
    1 févr. 2018
    Dernière capture
    22 nov. 2024
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    138
    Lacunes connues
    0
  • afrinic-mira
    Première capture
    17 nov. 2020
    Dernière capture
    22 nov. 2024
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    0
    Lacunes connues
    0
  • afrinic-ois-wg
    Première capture
    9 sept. 2021
    Dernière capture
    22 nov. 2024
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    0
    Lacunes connues
    0
  • afrinic-rpki-discuss
    Première capture
    15 janv. 2016
    Dernière capture
    23 avr. 2026
    Dernière actualisation
    15 oct. 2026
    Couverture
    La couverture de la source est incomplète.
    Chargement
    154
    Lacunes connues
    0

Couverture

Partielle
Première capture: 4 août 2004
Dernière capture: 15 oct. 2026

Actualité

Actualité: Périmé · Dernière actualisation:

Lacunes connues

  • www.afrinic.net: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • www.afrinic.net: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-rpd: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • www.afrinic.net: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-africann: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-afripv6-discuss: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-announce: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-community-discuss: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-dbwg: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-dnssec-ops: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-measurement-wg: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.
  • afrinic-rpki-discuss: La couverture de la source est incomplète. · La limite de la source n’a pas encore été atteinte.