Summary

  • On 7 July 2026, the 80th JP Domain Name Advisory Committee agreed that displaying the managing designated registrar name (管理指定事業者名) in JPRS's RDAP query results is appropriate; a formal answer was to be drafted by the chair and secretariat, and no final answer or JPRS implementation decision has been located on the public record (source).
  • The committee sits inside a contractual instrument chain: the JPRS–JPNIC memorandum on the JP domain name registration management business transfer agreement, under which JPNIC also evaluates JPRS annually — the 2025-cycle evaluation, received 17 June 2026, found no violation of registry responsibility items and no problem with JPRS's financial condition (source).
  • The RDAP display change would make registrar identity visible in every JP domain query — a transparency measure whose authority derives from advisory consensus, not from a public order, leaving open who can challenge, delay or refuse it.

The Decision on the Record

The operative language in the meeting summary is narrow and precise. According to the provider-reported verbatim excerpt from the committee materials page: the secretariat explained discussion material 2, titled "論点資料：JPRSのRDAPサービスにおいてJPドメイン名の検索結果に管理指定事業者名を表示することについて" (discussion material on displaying the managing designated registrar name in JPRS's RDAP query results for JP domain names), and "委員間で議論が行われ、JPRSのRDAPサービスにおけるJPドメイン名の検索結果に管理指定事業者名を表示することが妥当である旨、合意がなされた" — discussion took place among the members, and agreement was reached that such display is appropriate (source).

Three things in that sentence matter for governance analysis. First, what was agreed is not a rule change but a judgment of appropriateness (妥当). Second, the body that reached it is an advisory committee, not the registry operator itself. Third, the record stops at agreement: a draft formal answer (答申書) was to be prepared by the chair and secretariat following the discussion, and this run has located no published final answer and no JPRS implementation decision or timeline.

Which Instrument Grants the Power

The committee does not self-authorize. Provider reporting places the JP Domain Name Advisory Committee as a body created under the memorandum concerning the JP domain name registration management business transfer agreement (JPドメイン名登録管理業務移管契約に関する覚書) between JPNIC and JPRS — the same memorandum under which JPNIC evaluates JPRS annually. The evaluation notice received on 17 June 2026, covering the 2025 reporting cycle, states that JPNIC found JPRS not in violation of the registry responsibility items stipulated in the transfer agreement and found no problem with JPRS's financial condition; the same notice form has recurred annually from 2022 through 2025 (source).

That chain matters because it distinguishes coordination from contract from public authority. JPRS operates the .jp registry under a contract track with JPNIC; the advisory committee is a consultative layer above the operator, not a regulator above it. Its consensus has authority only insofar as JPNIC's memorandum, JPRS's own decisions and the drafting of a formal answer give it effect. Nothing in the located record shows a public-law power to order disclosure.

The committee's composition on 7 July 2026 also frames whose judgment the consensus represents: 浦川伸一 as chair, 金子宏直 as vice-chair, and members including 鎌田俊介, 曽根秀昭, 長田三紀 and 山下克典, with 山下克典 having succeeded 藤嶋久 in the designated-business-sector seat effective 1 July 2026 (source). A six-day-old membership change preceding a disclosure agreement is exactly the kind of procedural detail that a records-based review should note without over-reading: the located minutes do not link the rotation to the outcome.

What Transparency in RDAP Actually Changes

RDAP is the successor protocol to WHOIS for registration data. Displaying the managing designated registrar name in JP domain query results would attach an operator-visible fact — which designated registrar manages the registration — to every RDAP response. The professional uses are obvious: abuse handlers reach the responsible registrar faster; brand-protection teams map enforcement surfaces; researchers trace phishing infrastructure.

The risks the provider-reported minutes discussion flagged are the mirror image: naming registrars in public query output can itself aid attackers who use registrar identity to select targets or craft credible social-engineering approaches. Per provider reporting, the fuller minutes discuss a preparation period in the range of six to twelve months and anti-phishing and anti-social-engineering safeguards, though those details remain provider-reported and require corroboration before use as asserted facts.

What has not yet appeared on the public record is the thing that would convert appropriateness into effect: a final formal answer from the committee and a JPRS implementation decision. Until those exist, the only verifiable facts are the 7 July 2026 agreement, the drafting assignment, and the absence of a located follow-on instrument (source).

Context: A Quiet Governance Year

The 2026 JPRS announcement stream is otherwise dominated by operational advisories — DNS software vulnerability notices for BIND, Unbound, PowerDNS, Knot and NSD running through 18 September 2026 — punctuated by a handful of governance items: the 24 February 2026 revision of the JP-DRP Rules of Procedure, the 7 January 2026 revision of the JP domain registration rules, the 26 March 2026 publication of the JP Domain Name Registry Report 2025, the 17 June 2026 evaluation receipt, the advisory committee materials of July, and a 5 August 2026 note marking .jp's 40th anniversary (source; 2026 index; notice index). No new IANA redelegation or ICANN ccTLD instrument change appears in the 2026 index.

A separate, economic track also expands JPRS's institutional footprint: on 31 January 2026, JPRS announced that it had passed all test suites of ICANN's technical evaluation as a Registry Service Provider ahead of the new gTLD round scheduled to begin in April 2026, and that evaluated RSPs published on 30 January 2026 listed JPRS as the only one from Japan (source). The ICANN listing itself was not independently inspected in this run; the material is context, not a claim about the RDAP decision.

Evidence Boundaries

This article distinguishes what the record shows from what inference would add. The record shows: a dated agreement in a committee summary, the drafting assignment, the annual JPNIC evaluation result, and the shape of the 2026 announcement stream. It does not show: the contents of the formal answer (none located), any JPRS implementation decision, the full criteria JPNIC applies in its evaluation, or the operational safeguards the fuller minutes may discuss beyond provider-reported summaries.

Where an inference crosses from advisory consensus to implementation, no located instrument links the two; that inference is unsourced editorial judgment and is flagged as such rather than asserted.