APNIC · RIR Watchdog
Clarification on Sub-Assignments
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
- Policy ID
- prop-124
- RIR
- APNIC
- Official status
- Abandoned
- Normalized status
- Abandoned
- Introduced
- Mar 29, 2018
- Last source update
- Oct 13, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Proposal title and stated protocol scope · The title removes the IPv6 qualifier, changing from “Clarification on IPv6 Sub-Assignments” to “Clarification on Sub-Assignments.”
Applicability to APNIC assignments and allocations · The new problem statement expressly limits the proposal to direct APNIC end-user assignments and LIR assignments for exclusive infrastructure use, and expressly excludes LIR allocations; the old problem statement begins without this applicability limitation.
Source facts −
When the policy was drafted, the concept of assignments/sub-assignments did not consider a practice very common in IPv4 which is replicated and even amplified in IPv6: the use of IP addresses for point-to-point links or VPNs.Source facts ↗
Source facts +
Note that this proposal is ONLY relevant when end-users obtain direct assignments from APNIC, or when a LIR obtains, also from APNIC, and assignment for exclusive use within its infrastructure. Consequently this is NOT relevant in case of LIR allocations.Source facts ↗
IPv4 NAT and WAN-link rationale · The old text attributes the lack of an IPv4 problem to NAT usage. The new text qualifies this as applying when NAT is used and adds that assigned addresses are then limited to the WAN link as infrastructure or interconnection addressing.
Source facts +
In IPv4, typically, this is not a problem if NAT is being used, because the assigned addresses are only for the WAN link, which is part of the infrastructure or interconnection.Source facts ↗
Objective and APNIC existing-practices rationale · The old objective includes a separate explanation about redefining the concept for new IPv6 uses. The new objective omits that explanation and instead states that the ISP, data-center, and similar-case prohibition accords with existing APNIC practices.
Source facts −
This proposal clarifies this situation in this regard and better define the concept, particularly considering new uses of IPv6 (RFC8273), by means of new text. It also clarifies that the usage of sub-assignments in ISPs, data centers and similar cases is not allowed.Source facts ↗
Source facts +
It also clarifies that the usage of sub-assignments in ISPs, data centers and similar cases is not allowed, according to the existing practices of APNIC.Source facts ↗
Situation in other regions · The old text describes RIPE as corrected, notes a RIPE policy/impact-analysis discrepancy, says an amendment was submitted, identifies AfriNIC as having reached consensus, and says submissions were made to LACNIC and ARIN. The new text instead states directly that the situation has been corrected in AFRINIC, ARIN, LACNIC, and RIPE.
Source facts −
This situation, has already been corrected in RIPE, and the policy was updated in a similar way, even if right now there is a small discrepancy between the policy text that reached consensus and the RIPE NCC Impact Analysis. A new policy proposal has been submitted to amend that, and the text is the same as presented by this proposal at APNIC. Same text has also been submitted to AfriNIC (already reached consensus), LACNIC and ARIN.Source facts ↗
Source facts +
This situation, has already been corrected in AFRINIC, ARIN, LACNIC and RIPE.Source facts ↗
Form of the proposed amendment · The old version instructs that a new paragraph be added after the existing paragraph and labels the existing wording “Actual text.” The new version removes that instruction and labels the existing wording “Current Text.”
Permitted use and prohibited sub-assignments in proposed Section 2.2.3 · The proposed operative text is reformulated: “original holder” becomes “original recipient,” use by third-party devices is conditioned on operation within the infrastructure, and the prohibition is restated as sub-assignments to third parties outside that infrastructure and provision of address space to third parties in data centers or similar cases.
Source facts −
The address space assignment is only for use by the original holder of said assignment, as well as for third party devices, as long as they are operating within the original holder infrastructure. Sub-assignments are not allowed outside that infrastructure (for example using sub-assignments for ISP customers), neither for providing addressing space to third parties in data-centers (or similar cases)Source facts ↗
Source facts +
The assigned address space must only be used by the original recipient of the assignment, as well as for third party devices provided they are operating within said infrastructure. Therefore, sub-assignments to third parties outside said infrastructure (for example using sub-assignments for ISP customers), and providing addressing space to third parties in data-centers (or similar cases), are not allowed.Source facts ↗
Debate timeline
Public discussion
Re: [sig-policy] prop-124-v006: Clarification on Sub-Assignments
2 Discussion messages · 2 Entities
Source facts 1 ↗Source facts 2 ↗Public discussion
Re: [sig-policy] prop-133: Clarification on Sub-Assignments
6 Discussion messages · 3 Entities
Source facts 1 ↗Source facts 2 ↗Source facts 3 ↗Source facts 4 ↗Source facts 5 ↗Source facts 6 ↗Public discussion
Re: [sig-policy] prop-133-v003: Clarification on Sub-Assignments
2 Discussion messages · 2 Entities
Source facts 1 ↗Source facts 2 ↗
Entities
- Discussion messages9First activitySep 9, 2019Last activityMar 2, 2021First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies18Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
Identity verified: Oct 11, 2026
The IPv6 Company · Historical Name: Jordi Palet Martínez Email: [email protected] Organization: The IPv6 Company
politicas.lacnic.netVerified public profiles
- Discussion messages
- 9
- First activity
- Sep 9, 2019
- Last activity
- Mar 2, 2021
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 18
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
Jordi Palet's two January 2022 interventions seek a sound basis for decisions: a broader Policy SIG discussion where views remain divided, and Secretariat input on unresolved questions about historical resources. These are compatible procedural positions. One intervention per proposal does not establish a history of substantive support, opposition or reversal.
Experimental Allocations – no reservation for IPv4
Assessment: Insufficient evidence to assess consistency · Palet calls for the disputed experimental-allocation issue to reach the broader Policy SIG. He does not claim that consensus already exists or state a final vote on the allocation rule. This single procedural intervention cannot establish a change of position.
Conditions: The call to determine consensus is distinct from evidence that consensus was achieved.
it is neccesary to have the discussion in a broader community, the Policy SIG.
Recovery of unused historical resources
Assessment: Insufficient evidence to assess consistency · On recovery of historical resources, Palet requests Secretariat input, particularly on legal questions. Asking for that information leaves the substantive recovery decision open; it is not an endorsement of a particular legal interpretation.
Conditions: No later answer or explicit final policy preference is supplied.
especially the legal aspects. May be in this case, is not just the chairs but the secretariat who should provide some inputs.
Experimental Allocations – no reservation for IPv4 · Recovery of unused historical resources
Assessment: Consistent · Seeking wider community deliberation on one proposal and specialist Secretariat input on another are compatible ways to resolve different decision gaps. Neither message assigns the Secretariat authority to replace community consensus. The comparison supports procedural compatibility, not a shared substantive vote on the two policies.
Conditions: The proposals raise different questions and each is represented by one message.
It is the only way to determine consensus in a PDP valid way.
the secretariat who should provide some inputs.
- Sep 9, 2019 · Unknown
Re: [sig-policy] prop-124-v006: Clarification on Sub-Assignments
Validated evidence is unavailable.
Source facts ↗ - Feb 16, 2020 · Unknown
Re: [sig-policy] prop-133-v001: Secretariat impact assessment
Validated evidence is unavailable.
Source facts ↗ - Feb 18, 2020 · Unknown
Re: [sig-policy] New version - prop-133-v002: Clarification on Sub-Assignments
Validated evidence is unavailable.
Source facts ↗ - Feb 21, 2020 · Unknown
[sig-policy] prop-133: Clarification on Sub-Assignments
Validated evidence is unavailable.
Source facts ↗ - Feb 21, 2020 · Unknown
Re: [sig-policy] prop-133: Clarification on Sub-Assignments
Validated evidence is unavailable.
Source facts ↗ - Feb 22, 2020 · Unknown
Re: [sig-policy] prop-133: Clarification on Sub-Assignments
Validated evidence is unavailable.
Source facts ↗ - Feb 24, 2020 · Unknown
Re: [sig-policy] prop-133: Clarification on Sub-Assignments
Validated evidence is unavailable.
Source facts ↗ - Feb 26, 2020 · Unknown
Re: [sig-policy] prop-133: Clarification on Sub-Assignments
Validated evidence is unavailable.
Source facts ↗ - Mar 2, 2021 · Unknown
Re: [sig-policy] Policy Discussion in bdNOG for APNIC51
Validated evidence is unavailable.
Source facts ↗
Per-policy stance timelines:prop-121 · Unknown · No explicit position statedprop-122 · Unknown · No explicit position statedprop-124 · Unknown · No explicit position statedprop-125 · Unknown · No explicit position statedprop-126 · Unknown · No explicit position statedprop-128 · Unknown · No explicit position statedprop-130 · Unknown · No explicit position statedprop-131 · Unknown · No explicit position statedprop-133 · Unknown · No explicit position statedprop-134 · Unknown · No explicit position statedprop-135 · Unknown · No explicit position statedprop-139 · Unknown · No explicit position statedprop-140 · Unknown · No explicit position statedprop-143 · Unknown · No explicit position statedprop-148 · Unknown · No explicit position statedprop-154 · Unknown · No explicit position statedprop-157 · Unknown · No explicit position statedExperimental Allocations – no reservation for IPv4 · Unknown · Insufficient evidence to assess consistencyRecovery of unused historical resources · Unknown · Insufficient evidence to assess consistencyTotal policy messages: 141
- Srinivas Chendi · Identity unresolvedDiscussion messages7First activityFeb 14, 2020Last activityMay 28, 2021First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies23
- Bertrand Cherrier · Identity unresolvedDiscussion messages2First activitySep 17, 2018Last activityFeb 24, 2020First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies18
- chku · Identity unresolvedDiscussion messages2First activityAug 10, 2020Last activityFeb 8, 2021First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
- George Odagi · Identity unresolvedDiscussion messages2First activityMar 4, 2020Last activityMar 26, 2020First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
- Md. Abdul Awal · Identity unresolvedDiscussion messages1First activityFeb 26, 2019Last activityFeb 26, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies5
- Tsurumaki, Satoru · Identity unresolvedDiscussion messages1First activityFeb 17, 2020Last activityFeb 17, 2020First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
- Satoru Tsurumaki · Identity unresolvedDiscussion messages1First activitySep 2, 2019Last activitySep 2, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies14
- Unknown · Identity unresolvedDiscussion messages1First activityMar 1, 2021Last activityMar 1, 2021First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies3
- bdNOG Secretariat · Identity unresolvedDiscussion messages1First activityMar 2, 2021Last activityMar 2, 2021First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
- Discussion messages1First activityFeb 17, 2020Last activityFeb 17, 2020First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies6
- chku · Identity unresolvedDiscussion messages1First activityFeb 28, 2019Last activityFeb 28, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies17
Sources and coverage
Official policy sources
Public discussion archives
- apnic-sig-policy
- Earliest captured
- Jun 1, 2001
- Latest captured
- Sep 21, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 405
- Known gaps
- 36
- apnic-sig-policy
- Earliest captured
- Jun 1, 2001
- Latest captured
- Sep 21, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,594
- Known gaps
- 0
- www.apnic.net
- conference.apnic.net
- apnic-academy-talk-apnic.net
- Earliest captured
- Jan 12, 2023
- Latest captured
- Jan 19, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,098
- Known gaps
- 0
- apnic-afg-community-apnic.foundation
- Earliest captured
- Sep 27, 2023
- Latest captured
- Jun 24, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,054
- Known gaps
- 0
- apnic-apac-ict-women-apnic.net
- Earliest captured
- Oct 22, 2024
- Latest captured
- Aug 11, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,544
- Known gaps
- 0
- apnic-apix-chair-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- apnic-apix-secretary-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- apnic-apix-treasurer-apnic.net
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 0
- Known gaps
- 0
- apnic-apnic-alumni-apnic.net
- Earliest captured
- Feb 14, 2024
- Latest captured
- Jul 14, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,550
- Known gaps
- 0
- apnic-apnic-announce-apnic.net
- Earliest captured
- Jun 11, 2025
- Latest captured
- Sep 3, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,904
- Known gaps
- 0
- apnic-apnic-foundation-discuss-apnic.foundation
- Earliest captured
- Sep 12, 2022
- Latest captured
- Mar 11, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,190
- Known gaps
- 0
- apnic-apnic-services-apnic.net
- Earliest captured
- Aug 31, 2020
- Latest captured
- Aug 4, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,630
- Known gaps
- 0
- apnic-apnic-talk-lists.apnic.net
- Earliest captured
- Apr 15, 2004
- Latest captured
- Sep 8, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,744
- Known gaps
- 0
- apnic-apnic-transfers-apnic.net
- Earliest captured
- Sep 21, 2012
- Latest captured
- Feb 22, 2025
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,591
- Known gaps
- 0
- apnic-bgp-stats-lists.apnic.net
- Earliest captured
- Aug 30, 2026
- Latest captured
- Sep 15, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,767
- Known gaps
- 0
- apnic-community-elections-apnic.net
- Earliest captured
- Nov 12, 2021
- Latest captured
- Nov 22, 2021
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5
- Known gaps
- 0
- apnic-community-events-apnic.net
- Earliest captured
- May 9, 2025
- Latest captured
- Aug 19, 2025
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,753
- Known gaps
- 1
- apnic-diversity-in-leadership-apnic.net
- Earliest captured
- Jun 9, 2026
- Latest captured
- Jul 8, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 125
- Known gaps
- 0
- apnic-ianaxfer-apnic.net
- Earliest captured
- Mar 27, 2014
- Latest captured
- Jul 11, 2019
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,614
- Known gaps
- 0
- apnic-icp-2review-apnic.net
- Earliest captured
- Apr 24, 2025
- Latest captured
- Sep 1, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,070
- Known gaps
- 0
- apnic-measurement-apnic.net
- Earliest captured
- May 31, 2023
- Latest captured
- Mar 8, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,616
- Known gaps
- 0
- apnic-mvnog-apnic.net
- Earliest captured
- Feb 5, 2026
- Latest captured
- Sep 28, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 140
- Known gaps
- 0
- apnic-orbit-discuss-apnic.net
- Earliest captured
- Sep 13, 2022
- Latest captured
- Nov 13, 2022
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 661
- Known gaps
- 0
- apnic-pngnog-apnic.net
- Earliest captured
- Dec 26, 2019
- Latest captured
- Oct 28, 2024
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,427
- Known gaps
- 1
- apnic-security-discuss-apnic.net
- Earliest captured
- Mar 27, 2024
- Latest captured
- Aug 16, 2024
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,436
- Known gaps
- 0
- apnic-sig-cooperation-apnic.net
- Earliest captured
- Jan 15, 2015
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,637
- Known gaps
- 1
- apnic-sig-guidelines-review-apnic.net
- Earliest captured
- Jun 3, 2026
- Latest captured
- Sep 2, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,371
- Known gaps
- 0
- apnic-sig-nir-lists.apnic.net
- Earliest captured
- May 13, 2004
- Latest captured
- Sep 4, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,738
- Known gaps
- 0
- apnic-sig-routingsecurity-apnic.net
- Earliest captured
- Apr 3, 2020
- Latest captured
- Aug 25, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,494
- Known gaps
- 0
- apnic-user-feedback-group-apnic.net
- Earliest captured
- Sep 12, 2022
- Latest captured
- Jul 14, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,197
- Known gaps
- 0
- apnic-wg-pdr-apnic.net
- Earliest captured
- Mar 29, 2021
- Latest captured
- Sep 21, 2022
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,187
- Known gaps
- 1
- apnic-youth4ig-lists.apnic.net
- Earliest captured
- Feb 19, 2020
- Latest captured
- Jul 28, 2023
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,544
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jun 1, 2001
Latest captured: Oct 13, 2026
Freshness
Known gaps
- www.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-policy: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-policy: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- conference.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-academy-talk-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-afg-community-apnic.foundation: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apac-ict-women-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apix-chair-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apix-secretary-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apix-treasurer-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-alumni-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-announce-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-foundation-discuss-apnic.foundation: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-services-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-talk-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-apnic-transfers-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-bgp-stats-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-community-elections-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-community-events-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-diversity-in-leadership-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-ianaxfer-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-icp-2review-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-measurement-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-mvnog-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-orbit-discuss-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-pngnog-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-security-discuss-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-cooperation-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-guidelines-review-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-nir-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-sig-routingsecurity-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-user-feedback-group-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-wg-pdr-apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- apnic-youth4ig-lists.apnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.