AFRINIC · Vigilancia de RIR
AFRINIC Whois Database Update Process
Consulta aquí el historial de cada propuesta: qué cambió, por qué fue relevante, quién defendió cada postura, cómo evolucionaron las posiciones, qué se decidió y dónde persisten las lagunas en la evidencia.
Hechos con fuentes
- ID de política
- AFPUB-2014-GEN-001
- RIR
- AFRINIC
- Estado oficial
- Withdrawn
- Estado normalizado
- Retirada
- Presentada
- 15 may 2014
- Última actualización de fuentes
- 12 oct 2026
- Cobertura
- Parcial
¿Quiénes marcaron realmente el debate?
Evolución de la política
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.
Hechos con fuentes −
📦 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.Hechos con fuentes ↗
Hechos con fuentes +
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 HountomeyHechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
For contacts whose email has bounced back for "Non Delivery", AFRINIC Staff will immediately begin attempting to reach organizations via alternative means of communication.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
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.
Hechos con fuentes −
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.Hechos con fuentes ↗
Hechos con fuentes +
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.Hechos con fuentes ↗
Cronología del debate
Entidades
No se pudo cargar más
- Mensajes de discusión1Primera actividad5 dic 2014Última actividad5 dic 2014Primera postura explícitaDesconocidaÚltima postura explícitaDesconocidaCambios de postura0Coherencia del punto de vistaNo hay pruebas suficientes para evaluar la coherenciaOtras políticas13
- Adam Nelson · Identidad sin resolverMensajes de discusión1Primera actividad7 nov 2014Última actividad7 nov 2014Primera postura explícitaDesconocidaÚltima postura explícitaDesconocidaCambios de postura0Coherencia del punto de vistaNo se expresa una postura explícitaOtras políticas4
- Jean-Robert Hountomey · Identidad sin resolverMensajes de discusión0Primera actividadDesconocidaÚltima actividadDesconocidaPrimera postura explícitaDesconocidaÚltima postura explícitaDesconocidaCambios de postura0Coherencia del punto de vistaNo se expresa una postura explícitaOtras políticas1
Fuentes y cobertura
Fuentes oficiales
Archivos de debates públicos
- afrinic-rpd
- Primera captura
- 4 ago 2004
- Última captura
- 25 ago 2026
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 13.116
- Vacíos conocidos
- 0
- www.afrinic.net
- afrinic-africann
- Primera captura
- 3 ago 2026
- Última captura
- 2 oct 2026
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 2612
- Vacíos conocidos
- 0
- afrinic-afripv6-discuss
- Primera captura
- 17 ago 2015
- Última captura
- 18 sept 2026
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 2538
- Vacíos conocidos
- 0
- afrinic-announce
- Primera captura
- 18 ago 2015
- Última captura
- 18 sept 2026
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 2497
- Vacíos conocidos
- 0
- afrinic-community-discuss
- Primera captura
- 11 sept 2015
- Última captura
- 29 dic 2019
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 3127
- Vacíos conocidos
- 0
- afrinic-dbwg
- Primera captura
- 4 ago 2026
- Última captura
- 6 oct 2026
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 954
- Vacíos conocidos
- 0
- afrinic-dnssec-ops
- Primera captura
- 18 ago 2015
- Última captura
- 1 dic 2016
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 307
- Vacíos conocidos
- 0
- afrinic-icp2-review
- Primera captura
- 10 abr 2025
- Última captura
- 10 nov 2025
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 0
- Vacíos conocidos
- 0
- afrinic-measurement-wg
- Primera captura
- 1 feb 2018
- Última captura
- 22 nov 2024
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 138
- Vacíos conocidos
- 0
- afrinic-mira
- Primera captura
- 17 nov 2020
- Última captura
- 22 nov 2024
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 0
- Vacíos conocidos
- 0
- afrinic-ois-wg
- Primera captura
- 9 sept 2021
- Última captura
- 22 nov 2024
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 0
- Vacíos conocidos
- 0
- afrinic-rpki-discuss
- Primera captura
- 15 ene 2016
- Última captura
- 23 abr 2026
- Última actualización
- 14 oct 2026
- Cobertura
- La cobertura de la fuente está incompleta.
- Cargando
- 154
- Vacíos conocidos
- 0
Cobertura
Parcial
Primera captura: 4 ago 2004
Última captura: 14 oct 2026
Actualización
Vacíos conocidos
- www.afrinic.net: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- www.afrinic.net: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-rpd: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- www.afrinic.net: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-africann: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-afripv6-discuss: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-announce: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-community-discuss: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-dbwg: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-dnssec-ops: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-measurement-wg: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
- afrinic-rpki-discuss: La cobertura de la fuente está incompleta. · Aún no se ha alcanzado el límite de la fuente.
