LACNIC · RIR 观察
Update the policy on transfers due to mergers/acquisitions
从这里开始，逐项查看提案记录：发生了哪些变化、为何重要、各方提出了什么主张、立场如何演变、最终作出了什么决定，以及证据仍存在哪些缺口。
来源事实
- 政策编号
- LAC-2018-2
- RIR
- LACNIC
- 官方状态
- Abandoned
- 标准化状态
- 已放弃
- 提出时间
- 2018年2月7日
- 最近来源更新
- 2026年11月1日
- 覆盖范围
- 部分
究竟是谁影响了这场辩论？
政策演变
One-year restriction following a prior transfer · The restriction was narrowed. The old wording covered blocks previously transferred under either section 2.3.2.17 or 2.3.2.18 and prohibited another transfer generally for one year. The new wording covers blocks previously transferred under section 2.3.2.17 and prohibits transfer under section 2.3.2.18 for one year.
来源事实 −
. - A block that has previously been transferred under sections 2.3.2.17 or 2.3.2.18 may not be transferred again for a period of one year as of the date on which the previous transfer was concluded. This also applies to sub-blocks, i.e., any group of addresses contained in the block that is transferr来源事实 ↗
来源事实 +
. - A block that has previously been transferred under section 2.3.2.17, may not be transferred again under section 2.3.2.18 for a period of one year as of the date on which the previous transfer was concluded. This also applies to sub-blocks, i.e., any group of addresses contained in the block that is transferr来源事实 ↗
Restriction following initial or additional allocation or assignment · The waiting period was reduced from three years to one year, and the prohibition was narrowed from transfers generally to transfers under section 2.3.2.17.
来源事实 −
d. - Blocks and sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs may not be transferred for a period of three years as of their date of allocation or assignme来源事实 ↗
来源事实 +
d. - Blocks and sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs may not be transferred under section 2.3.2.17 for a period of one year as of their date of allocation or assignme来源事实 ↗
Additional information about the adjustment · The new version adds a statement that, according to comments, the proposal was adjusted to remove the restriction on transferring a block again under section 2.3.2.17; the old version contained no corresponding explanation.
One-year restriction on subsequent transfers · The old text prohibited a block transferred under section 2.3.2.17 from being transferred under section 2.3.2.18 for one year from the prior transfer's conclusion and applied that prohibition to all sub-blocks. The new text instead prohibits retransferring the block in full for one year and expressly allows transfers of up to 20% of its addresses during that period; it does not state the prior conclusion-date trigger.
来源事实 −
- A block that has previously been transferred under section 2.3.2.17, may not be transferred again under section 2.3.2.18 for a period of one year as of the date on which the previous transfer was concluded. This also applies to sub-blocks, i.e., any group of addresses contained in the block that is transferred.来源事实 ↗
来源事实 +
2.3.2.17.2 - A block that has previously been transferred under this policy may not be transferred again in full for a period of one year. 2.3.2.17.2.1 – During this one-year period, only transfers of up to 20% of the addresses of a transferred block will be allowed.来源事实 ↗
Holding period for resources received directly from LACNIC or its NIRs · The old text imposed a one-year waiting period before blocks or sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs could be transferred under section 2.3.2.17. That restriction is absent from the complete replacement paragraph in the new text.
来源事实 −
- Blocks and sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs may not be transferred under section 2.3.2.17 for a period of one year as of their date of allocation or assignment.来源事实 ↗
来源事实 +
Add a paragraph at the end of section 2.3.2.17: 2.3.2.17.1.- Transferred legacy resources will no longer be considered as such. 2.3.2.17.2 - A block that has previously been transferred under this policy may not be transferred again in full for a period of one year. 2.3.2.17.2.1 – During this one-year period, only transfers of up to 20% of the addresses of a transferred block will be allowed.来源事实 ↗
Structure of the proposed paragraph for section 2.3.2.17 · The numbered provision format beginning with section 2.3.2.17.1 was replaced by an unnumbered “Note that” bullet list.
Restrictions on partial transfers during the one-year period · The proposal added a requirement that permitted partial transfers have a prefix length equal to or shorter than the minimum allowed by policies in force and align with a CIDR bit boundary.
来源事实 −
2.3.2.17.2.1 – During this one-year period, only transfers of up to 20% of the addresses of a transferred block will be allowed.来源事实 ↗
来源事实 +
- During this one-year period, only transfers of up to 20% of the addresses of a transferred block will be allowed. Such transfers must have a prefix length equal or shorter than the minimum allowed by the policies currently in force and match a CIDR bit boundary来源事实 ↗
讨论时间线
实体
- 未知 · 已找到公开来源；身份核验待处理讨论消息3首次活动2018年2月7日最近活动2018年7月27日首次明确立场未知最近明确立场未知立场变化0观点一致性证据不足，无法评估一致性其他政策20
- Mike Burns · 身份尚未解析讨论消息1首次活动2018年3月7日最近活动2018年3月7日首次明确立场反对最近明确立场反对立场变化0观点一致性一致其他政策0
- André Costa · 身份尚未解析讨论消息1首次活动2018年9月25日最近活动2018年9月25日首次明确立场反对最近明确立场反对立场变化0观点一致性一致其他政策0
- Daniel Miroli · 身份尚未解析讨论消息1首次活动2018年3月7日最近活动2018年3月7日首次明确立场未知最近明确立场未知立场变化0观点一致性证据不足，无法评估一致性其他政策1
- Paola Perez · 身份尚未解析讨论消息1首次活动2018年10月9日最近活动2018年10月9日首次明确立场未知最近明确立场未知立场变化0观点一致性未明确表明立场其他政策17
来源与覆盖
公开讨论记录
- lacnic-politicas
- 最早收录
- 1999年10月21日
- 最近收录
- 2026年10月30日
- 最近刷新
- 2026年8月13日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 3,636
- 已知缺口
- 28
- www.lacnic.net
- lacnic-anuncios
- 最早收录
- 2002年3月15日
- 最近收录
- 2026年10月27日
- 最近刷新
- 2026年11月2日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 1,879
- 已知缺口
- 0
- lacnic-ietf-lac
- 最早收录
- 2013年5月30日
- 最近收录
- 2015年12月30日
- 最近刷新
- 2026年11月1日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 1,133
- 已知缺口
- 0
- lacnic-infofrida
- 最早收录
- 2006年8月14日
- 最近收录
- 2011年9月13日
- 最近刷新
- 2026年11月1日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 292
- 已知缺口
- 0
- lacnic-iot
- 最早收录
- 2015年10月6日
- 最近收录
- 2017年7月11日
- 最近刷新
- 2026年11月1日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 373
- 已知缺口
- 0
- lacnic-lacnog
- 最早收录
- 2026年8月1日
- 最近收录
- 2026年10月30日
- 最近刷新
- 2026年11月2日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 8,703
- 已知缺口
- 4
- lacnic-lactf
- 最早收录
- 2004年4月13日
- 最近收录
- 2013年12月30日
- 最近刷新
- 2026年11月1日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 5,257
- 已知缺口
- 0
- lacnic-seguridad
- 最早收录
- 2006年1月26日
- 最近收录
- 2007年12月28日
- 最近刷新
- 2026年11月1日
- 覆盖范围
- 来源覆盖尚不完整。
- 加载中
- 1,356
- 已知缺口
- 0
覆盖范围
部分
最早收录: 1999年10月21日
最近收录: 2026年11月2日
新鲜度
已知缺口
- politicas.lacnic.net: 来源覆盖尚不完整。 · 尚未达到来源边界。
- www.lacnic.net: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-politicas: 来源覆盖尚不完整。 · 尚未达到来源边界。
- www.lacnic.net: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-anuncios: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-ietf-lac: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-infofrida: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-iot: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-lacnog: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-lactf: 来源覆盖尚不完整。 · 尚未达到来源边界。
- lacnic-seguridad: 来源覆盖尚不完整。 · 尚未达到来源边界。