RIPE NCC · RIR Watchdog

Policy

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.

RIR Watchdog

Policy records

01Policy records
02Policy evolution
03Entities
04Sources and coverage

Coverage: Partial

Freshness: Stale · Last refresh: Oct 13, 2026, 8:12 PM

Earliest captured: Jun 30, 1992Known gaps: www.ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-address-policy-wg: Source coverage is incomplete. · The source boundary has not yet been reached. · www.ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-accountability-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-agm-nominations-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-all-anchors-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-anti-abuse-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-atlas-sponsors-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-atlas-sw-probes-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-bcop-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-coc-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-connect-bof-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-connect-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-cooperation-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-db-help-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-db-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-diversity-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-dns-resolver-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-dns-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-dp-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-eb-candidates-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-eix-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-election-cc-team-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-enum-announce-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-enum-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-green-tech-hackathon-orga-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-hackathon-list-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-icann-plan-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-iot-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ipmap-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ipmt-dev-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ipv6-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-irrtoolset-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-lir-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-mat-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-measure-voip-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-members-discuss-unmoderated-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-members-discuss-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-myasntesting-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ncc-announce-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ncc-services-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-nccdays-pc-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-opensource-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-persian-lir-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-policy-announce-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-raci-list-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-regional-russia-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-regional-ukraine-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-atlas-ambassadors-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-atlas-tools-maintainers-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-atlas-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-chair-discuss-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-db-requirements-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-forum-test-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-list-unmoderated-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-list-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripe-parents-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ripecast-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-rirs-lea-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ris-int-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-ris-users-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-routing-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-rpslng-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-security-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-see-regional-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-techsec-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-tld-wg-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached. · ripencc-tt-tf-ripe.net: Source coverage is incomplete. · The source boundary has not yet been reached.

Freshness: Stale · Last refresh: Oct 13, 2026, 8:12 PM

136Policies

49People with verified identities

94Source accounts awaiting identity resolution

32Participated in 2+ policies

3Participated in 5+ policies

34.3%Top-five discussion share

UnknownMedian effective participants

11People covering 50%

Participation concentration

Who actually shaped this RIR?

Discussion statistics are still being updated. Figures shown reflect the records processed so far.

Open a linked profile to follow that person or organisation across policies, messages and changing positions. Every figure remains tied to the stated source coverage.

Recurring people and organisations

Gert Doering16 Policies participated · 41 Discussion messages
Nick Hyrka9 Policies participated · 9 Discussion messages
Jordi Palet Martinez5 Policies participated · 4 Discussion messages
Sander Steffann4 Policies participated · 24 Discussion messages
Unknown3 Policies participated · 47 Discussion messages
Randy Bush3 Policies participated · 18 Discussion messages
Remco van Mook3 Policies participated · 15 Discussion messages
Filiz Yilmaz3 Policies participated · 8 Discussion messages
Geoff Huston3 Policies participated · 5 Discussion messages
Mark Scholten3 Policies participated · 5 Discussion messages

Policy

Policy records

Policy

Policy records

Who actually shaped this RIR?

Policy records

Clarification of Definition for "ASSIGNED PA"

Assignment Clarification in IPv6 Policy

Publication of Legal Address of Internet Number Resource Holders

PDP Clarification

Fixing Outdated Information in the IPv4 Policy

Organisation-LIR Clarification in IPv6 Policy

Regular abuse-c Validation

Reducing Initial IPv4 Allocation, Aiming to Preserve a Minimum of IPv4 Space for Newcomers

Publish statistics on Intra-RIR Legacy updates

Synchronising the Initial and Subsequent IPv6 Allocation Policies

Policy for Inter-RIR Transfers of Internet Resources

Allow IPv4 PI transfer

Abandoning the Minimum Allocation Size for IPv4

Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text

No Restrictions on End User Assignments in Intra-RIR Transfers

PA/PI Unification IPv6 Address Space

Openness about Policy Violations

Resource Certification for non-RIPE NCC Members

Removal of requirement for certification of reallocated IPv4 addresses

Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis