AFRINIC · RIR 观察
AFRINIC Whois Database Update Process
从这里开始,逐项查看提案记录:发生了哪些变化、为何重要、各方提出了什么主张、立场如何演变、最终作出了什么决定,以及证据仍存在哪些缺口。
来源事实
- 政策编号
- AFPUB-2014-GEN-001
- RIR
- AFRINIC
- 官方状态
- Withdrawn
- 标准化状态
- 已撤回
- 提出时间
- 2014年5月15日
- 最近来源更新
- 2026年10月12日
- 覆盖范围
- 部分
究竟是谁影响了这场辩论?
政策演变
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.
来源事实 −
📦 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.来源事实 ↗
来源事实 +
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来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
For contacts whose email has bounced back for "Non Delivery", AFRINIC Staff will immediately begin attempting to reach organizations via alternative means of communication.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.来源事实 ↗
来源事实 +
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.来源事实 ↗
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.
来源事实 −
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.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.来源事实 ↗
讨论时间线
实体
加载更多失败
- Adam Nelson · 身份尚未解析讨论消息1首次活动2014年11月7日最近活动2014年11月7日首次明确立场未知最近明确立场未知立场变化0观点一致性未明确表明立场其他政策4
- Jean-Robert Hountomey · 身份尚未解析讨论消息0首次活动未知最近活动未知首次明确立场未知最近明确立场未知立场变化0观点一致性未明确表明立场其他政策1
来源与覆盖
公开讨论记录
- afrinic-rpd
- 最早收录
- 2004年8月4日
- 最近收录
- 2026年8月25日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 13,116
- 已知缺口
- 0
- www.afrinic.net
- afrinic-africann
- 最早收录
- 2026年8月3日
- 最近收录
- 2026年10月2日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 2,598
- 已知缺口
- 0
- afrinic-afripv6-discuss
- 最早收录
- 2015年8月17日
- 最近收录
- 2026年9月18日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 2,538
- 已知缺口
- 0
- afrinic-announce
- 最早收录
- 2015年8月18日
- 最近收录
- 2026年9月18日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 2,497
- 已知缺口
- 0
- afrinic-community-discuss
- 最早收录
- 2015年9月11日
- 最近收录
- 2019年12月29日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 3,127
- 已知缺口
- 0
- afrinic-dbwg
- 最早收录
- 2026年8月4日
- 最近收录
- 2026年10月6日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 941
- 已知缺口
- 0
- afrinic-dnssec-ops
- 最早收录
- 2015年8月18日
- 最近收录
- 2016年12月1日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 307
- 已知缺口
- 0
- afrinic-icp2-review
- 最早收录
- 2025年4月10日
- 最近收录
- 2025年11月10日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 0
- 已知缺口
- 0
- afrinic-measurement-wg
- 最早收录
- 2018年2月1日
- 最近收录
- 2024年11月22日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 138
- 已知缺口
- 0
- afrinic-mira
- 最早收录
- 2020年11月17日
- 最近收录
- 2024年11月22日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 0
- 已知缺口
- 0
- afrinic-ois-wg
- 最早收录
- 2021年9月9日
- 最近收录
- 2024年11月22日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 0
- 已知缺口
- 0
- afrinic-rpki-discuss
- 最早收录
- 2016年1月15日
- 最近收录
- 2026年4月23日
- 最近刷新
- 2026年10月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 154
- 已知缺口
- 0
覆盖范围
部分
最早收录: 2004年8月4日
最近收录: 2026年10月13日
新鲜度
已知缺口
- www.afrinic.net: 来源覆盖尚不完整。 · 尚未达到来源边界。
- www.afrinic.net: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-rpd: 来源覆盖尚不完整。 · 尚未达到来源边界。
- www.afrinic.net: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-africann: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-afripv6-discuss: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-announce: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-community-discuss: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-dbwg: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-dnssec-ops: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-measurement-wg: 来源覆盖尚不完整。 · 尚未达到来源边界。
- afrinic-rpki-discuss: 来源覆盖尚不完整。 · 尚未达到来源边界。
