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 ?
Évolution de la politique
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 HountomeyFaits 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
Entités
Impossible de charger plus d’éléments
- Messages de discussion1Première activité5 déc. 2014Dernière activité5 déc. 2014Première position expliciteInconnueDernière position expliciteInconnueChangements de position0Cohérence du point de vueÉléments insuffisants pour évaluer la cohérenceAutres politiques13
- Adam Nelson · Identité non résolueMessages de discussion1Première activité7 nov. 2014Dernière activité7 nov. 2014Première position expliciteInconnueDernière position expliciteInconnueChangements de position0Cohérence du point de vueAucune position explicite n’a été énoncéeAutres politiques4
- Jean-Robert Hountomey · Identité non résolueMessages de discussion0Première activitéInconnueDernière activitéInconnuePremière position expliciteInconnueDernière position expliciteInconnueChangements de position0Cohérence du point de vueAucune position explicite n’a été énoncéeAutres 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
- 14 oct. 2026
- Couverture
- La couverture de la source est incomplète.
- Chargement
- 13 116
- Lacunes connues
- 0
- www.afrinic.net
- afrinic-africann
- Première capture
- 3 août 2026
- Dernière capture
- 2 oct. 2026
- Dernière actualisation
- 14 oct. 2026
- Couverture
- La couverture de la source est incomplète.
- Chargement
- 2 618
- Lacunes connues
- 0
- afrinic-afripv6-discuss
- Première capture
- 17 août 2015
- Dernière capture
- 18 sept. 2026
- Dernière actualisation
- 14 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
- 14 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
- 14 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
- 14 oct. 2026
- Couverture
- La couverture de la source est incomplète.
- Chargement
- 960
- Lacunes connues
- 0
- afrinic-dnssec-ops
- Première capture
- 18 août 2015
- Dernière capture
- 1 déc. 2016
- Dernière actualisation
- 14 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
- 14 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
- 14 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
- 14 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
- 14 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
- 14 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: 14 oct. 2026
Actualité
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.
