Summary

  • ICANN’s decisive moves were not rulings on geographical-indication law. On 22 March 2014, the New gTLD Program Committee directed .WINE and .VIN back into normal evaluation and said no additional safeguards were required. On 4 April, it separately stopped the start of contracting for 60 days. The first act set the programme direction; the second bought negotiating time. Neither act wrote a wine-origin obligation into a Registry Agreement.
  • Governments and wine-industry organisations could issue an Early Warning, develop GAC advice, correspond with ICANN, seek reconsideration and enter the Cooperative Engagement Process. Those routes affected attention, timing and bargaining leverage, but they did not give those participants control of the contract. The NGPC controlled programme processing; ICANN controlled contracting; the then-IANA root-zone process handled readiness and delegation; the operator implemented registration and reservation policy within the agreement.
  • The .WINE and .VIN Registry Agreements signed on 18 June 2015 contain enforceable Public Interest Commitments. Their provision headed “Geographic name protection”, however, points to Specification 5’s country-and-territory reservations rather than a bespoke list of wine appellations. The agreements contain applicable-law, trademark and abuse mechanisms and give the operator reservation discretion, but they do not publish a wine-specific GI undertaking, protected-appellation schedule or GI adjudication procedure.
  • Participant-side accounts describe a private settlement that produced operational reservations and allocations for selected wine-origin names. The full instrument is not in the public record assembled here, so its parties, duration, remedies and succession rules cannot safely be stated. The later assignment of both agreements to Binky Moon, LLC and the rebranding of the Donuts–Afilias group as Identity Digital changed the operator chain, not the published 2015 contractual baseline.

The first decision was to move; the second was to wait

On 22 March 2014, ICANN’s New gTLD Program Committee directed the .WINE and .VIN applications to proceed through the normal evaluation process. The resolution said that no additional safeguards would be required. Less than two weeks later, the same committee directed ICANN’s chief executive not to begin contracting for 60 days so that the applicants and affected parties could negotiate. One decision set the programme’s legal and procedural direction; the other controlled timing. The first removed a hold. The second created bargaining space. Neither inserted a wine-origin rule into a registry contract. The 22 March resolution and the 4 April resolution show how an institution can accommodate opposition procedurally without transferring decision power or changing the contractual baseline.

That distinction matters because the public controversy was framed in the language of protection. France’s 2012 GAC Early Warning and later governmental submissions reflected concern that second-level names under .WINE or .VIN could be used in ways that diluted or misappropriated recognised geographical indications. June Station and Holly Shadow answered that the Applicant Guidebook did not create a GI-specific regime and that ordinary public-interest, trademark and applicable-law mechanisms were the programme’s baseline.

ICANN therefore had to decide whether to make additional origin protection a condition of programme progression and contracting. It did not have to determine, and did not determine, the substantive validity of every asserted origin right in every jurisdiction.

The eventual contract path is more revealing than the volume of correspondence. A government warning could force attention onto an application but not compel withdrawal. GAC advice could delay the programme and require Board consideration but, in the absence of consensus against the strings, did not itself reject them. An independent legal analysis could inform the Board but did not bind it. Reconsideration could test specified procedural defects but did not reopen the merits merely because requesters disputed the legal analysis.

Cooperative engagement could create leverage for private negotiation but did not automatically produce an ICANN-enforceable term. The executed Registry Agreement, its incorporated specifications and applicable policies defined the operator’s duties to ICANN; later technical and root-zone steps made the TLD operational. The case is therefore a chain of non-substitutable powers, not a single decision labelled “approval”.

A global root had no field marked “wine GI”

Geographical indications do not operate as one uniform global title; the legal landscape described in Passa’s analysis was fragmented by jurisdiction, legal instrument and the status of individual names. Their legal force can depend on treaties, regional systems, national legislation, bilateral arrangements and product categories. Some protected wine names also function as trademarks in some places; others are protected through public-law appellation systems; some terms are contested or treated as generic elsewhere. The DNS, by contrast, requires one globally unique delegation for a top-level string and then allows registrations beneath it according to a registry’s contract and policies. A second-level name under .wine can be visible worldwide even though the claimed right and the alleged infringement vary by jurisdiction.

That mismatch did not make protection impossible. It made the design choice consequential. ICANN could have required the registry operator to reserve a defined list, verify claimants, create an allocation process and accept an enforcement mechanism. It could have written a narrower obligation to follow authoritative decisions from specified bodies. It could have relied on ordinary law and post-registration disputes. It could also have relied on operator discretion without making the private criteria part of the ICANN contract. Each option allocated rule-making, evidence assessment, error costs and remedy to different institutions.

The 2012 Applicant Guidebook did not create a dedicated GI-only objection or second-level rights-protection regime comparable to the programme’s trademark mechanisms. That absence became the applicants’ central institutional argument. In their August 2013 response to GAC advice, June Station and Holly Shadow said the Guidebook contained no provisions protecting wine and spirit GIs as such. They offered open registration, compliance with applicable law, WHOIS auditing, abuse controls and trademark-focused products, while reserving discretion to suspend or cancel registrations. They also said they had no current plan to amend the applications, although they remained open to further discussion. That was a proposal for compliance and operator discretion, not submission to a public GI licensing authority.

The difference between a legal-rights mechanism and a GI regime is easy to blur. The Trademark Clearinghouse, sunrise procedures, claims notices and the applicants’ Domains Protected Marks List could assist rights holders whose interests fit the trademark system. They did not determine which appellations deserved protection solely because a government or producer organisation recognised them as GIs. An “applicable law” clause similarly did not select the applicable jurisdiction, decide whether a term was protected there, or identify which remedy should follow.

It required lawful conduct while leaving the antecedent legal questions to other processes.

Two applications, two status paths

The applied-for strings travelled together politically but not procedurally. ICANN’s .WINE application record identifies June Station, LLC, application 1-1515-14214, and records a passed Initial Evaluation, a resolved contention set and the result “Prevailed Contention”. ICANN’s .VIN application record identifies Holly Shadow, LLC, application 1-1538-23177, and records a passed Initial Evaluation, a GAC Early Warning and eventual delegation. The .VIN record does not show a contention set comparable to .WINE. These pages are historical application-processing records; ICANN warns that applicant information on them is not maintained as the current registry record after delegation.

That status difference constrains what can safely be said about “winning”. The BGC’s consolidated reconsideration recommendation identifies Afilias Limited, dot Wine Limited and June Station as the three .WINE applicants. June Station eventually prevailed. The official .WINE readiness report says contention was resolved through one of the recognised routes—community priority evaluation, auction or self-resolution—but does not identify which route produced the result. The source set used for this article therefore does not establish whether auction or private settlement was decisive. The .VIN readiness report, by contrast, marks contention resolution as not applicable.

Application status was not contracting, and contracting was not delegation. Passing Initial Evaluation meant that the application had cleared that evaluation stage. Resolving contention meant that one applicant remained eligible to advance for the string. A signed Registry Agreement created enforceable obligations between ICANN and the operator. Pre-delegation testing and IANA’s readiness assessment examined technical and process prerequisites. Root-zone entry made the top-level domain operational in the public DNS.

The .WINE/.VIN controversy repeatedly crossed these stages, and political statements sometimes used “delegation” as shorthand for all of them. The records do not permit that compression.

France’s Early Warning opened a channel, not a veto

The first source in the commissioned period is France’s GAC Early Warning on .VIN, issued on 20 November 2012. France argued that “wine” and “vin” referred to a product defined and regulated under European law and that wine geographical indications were subject to a specific regulatory framework. Its suggested remediation was withdrawal or an objection procedure safeguarding GIs. The form asked whether the applicant would withdraw or continue, encouraged contact with affected parties and offered an enhanced refund for timely withdrawal. It did not itself order ICANN to reject the application.

The warning’s institutional function was notice plus political escalation. France could place a documented public-policy concern into the application record. The applicant retained the choice to continue. The GAC as a whole could later develop advice. The Board remained responsible for deciding how that advice affected programme processing. The warning therefore widened participation but did not transfer control over the application.

The absence of a veto did not remove the operational risk identified in the warning. A second-level registration could combine a protected name with .VIN or .WINE in a manner that appeared authoritative to consumers. A registry’s open-registration model might make such names available before a rights holder knew of the application. But the remedy proposed in the warning—an objection procedure protecting GIs—required institutional design. Someone would have to define the protected list, decide standing, assess evidence, handle conflicting claims, determine exceptions and enforce results.

The warning identified the risk; it did not supply that machinery.

Beijing created a contracting gate without stopping every process

In April 2013, the GAC advised the Board not to proceed beyond Initial Evaluation for a group of sensitive strings that included .WINE and .VIN while further GAC consideration continued. The NGPC’s 4 June 2013 scorecard accepted that advice. Its wording was precise: evaluation and dispute-resolution processes could continue, but ICANN would not enter registry agreements for the listed strings “for now”. The applications were not rejected, suspended in every respect or delegated. Contracting was held behind a status gate.

That gate demonstrated the Board committee’s practical power. A GAC position changed the sequence even though it did not supply a final substantive rule. Applicants could continue to build their cases and resolve other programme requirements, but they could not compel ICANN to sign. Governments obtained time in which to seek a common position. The delay burden fell principally on the applicants, while parties seeking safeguards gained time before contracting and any later root-zone step.

The applicants responded by reframing the dispute as one about the proper boundary of ICANN’s programme. Their August 2013 submission accepted general safeguards: accredited registrars, prohibitions on unlawful and abusive activity, technical analysis of security threats, transparent policies and several voluntary rights-protection tools. It also emphasised open access for lawful users of generic terms. The applicants said inappropriate use of GIs might violate applicable law and could be mitigated through registry discretion, but they rejected the premise that the TLD itself should be restricted to its most common wine-related use.

This was a consequential combination. Open registration reduced the risk that a sector could monopolise a generic string. Operator discretion offered a way to act against particular names. Yet discretion was not equivalent to a claimant’s enforceable right. A rights holder could ask the operator to act, but unless the contract or another binding policy defined the operator’s duty, the operator retained judgement over whether and how to intervene. The same flexibility that made a negotiated solution possible also left uncertainty about standing, evidence and remedy.

When GAC consensus ran out

By September 2013, the GAC had not reached consensus on additional safeguards for .WINE and .VIN. Its advice was that the applications should proceed through normal evaluation. The Buenos Aires communiqué later suggested that the Board might seek a clear understanding of the legally complex and politically sensitive background before deciding the next steps towards delegation. The Board committee used that opening to commission an independent legal analysis. The 22 March 2014 resolution records the sequence and states the operational result: normal evaluation would resume and no additional safeguards would be required.

The absence of GAC consensus did not mean the absence of government opposition. Individual governments continued to press for GI protections, while others opposed imposing additional conditions. Under the then-Bylaws and Applicant Guidebook, consensus GAC advice against an application carried a stronger institutional consequence than concern expressed by some members. The Board still had discretion and had to address the advice it received, but the GAC did not produce a collective instruction that these two applications should not proceed. Participation remained broad; the decisive procedural threshold was consensus.

This distinction explains why the Board could say it was accepting GAC advice when it moved the applications forward. It was accepting the GAC’s September advice that there was no consensus on additional safeguards and that normal evaluation should resume. Later critics saw the outcome as insufficiently responsive to the concerns that had driven the earlier hold. The Board saw it as implementation of the advice actually adopted. The disagreement was partly substantive, but it was also about which institutional artefact counted: concern voiced by multiple governments, or consensus advice in the form recognised by the programme.

Passa’s opinion separated legal compulsion from contractual choice

Professor Jérôme Passa’s independent legal analysis became the most disputed document in the chain. Its central conclusion, also recorded in the NGPC rationale, was that no rule of geographical-indication law or general principle obliged ICANN either to reject the applications or to accept them subject to specific conditions. That conclusion answered a question of legal compulsion. It did not establish that ICANN lacked power to negotiate conditions, that GI protection was undesirable or that no registration under the TLDs could infringe a right.

The analysis also recognised pathways short of rejection. A registry agreement could require respect for GIs and third-party rights; naming rules and registry–registrant relations could carry protections; particular disputes could be addressed under applicable law. This is the critical boundary in the document. “ICANN is not legally obliged to impose this condition” is not the same proposition as “ICANN cannot impose this condition”. The first leaves a policy and contracting choice. The second would remove it. The Board relied on the former.

Passa did not decide the applications. He supplied analysis commissioned by the NGPC. The committee chose the question, received the opinion, considered other submissions and adopted the resolution. Governments and producer organisations could attack the opinion’s reasoning, but the expert had no root-zone authority and no contracting signature. Treating the analysis as the decision obscures where institutional responsibility lay.

The opinion also exposed the limits of using a registry contract to settle substantive law. A clause requiring compliance with all valid GIs would still need a method for identifying validity across jurisdictions. A list supplied by one regional system might overprotect terms considered generic elsewhere. A requirement to obey final court or administrative orders would be narrower but slower and territorially fragmented. An ICANN-created adjudication procedure would make the DNS institution a new forum for questions on which trade law had not converged. The NGPC could choose among these designs, but none was merely technical.

The 22 March resolution set the programme default, not the GI merits

Resolution 2014.03.22.NG01 is often described as ICANN allowing the strings to proceed. More precisely, the NGPC accepted the GAC advice recorded in September 2013 and directed normal evaluation. Its rationale expressly stated that no additional safeguards would be required. It did not grant a Registry Agreement, declare the applicants technically ready, resolve .WINE contention or direct IANA to enter either string in the root. Those later acts remained contingent.

The resolution nevertheless fixed the substantive default. Unless a later accountability mechanism, negotiation or Board act changed it, ICANN staff could process the applications under the ordinary programme and standard contract. That default gave the applicants bargaining leverage. Opponents were no longer negotiating against an indefinite institutional hold; they were negotiating against a path that would eventually reach contracting if remaining requirements were met.

The Board’s rationale also made a legitimacy claim: it had considered conflicting government letters, applicant responses and the independent analysis. A documented consideration record supports transparency. It does not by itself prove that every argument received correct weight or that affected parties possessed a remedy. Transparency reveals the inputs and the stated reasoning. Accountability asks whether a recognised body can test a violation and order a consequence. The next phase of the case turned on that difference.

Singapore challenged the process used to obtain the answer

In its 27 March 2014 Singapore advice, the GAC said there appeared to be at least one process violation or procedural error. It invoked a then-Bylaws provision requiring an opportunity to comment on external advice before a Board decision and advised the Board to reconsider before delegation. It also encouraged applicants and interested parties to continue negotiations. The GAC’s itemised record preserves both strands: a procedural objection and a negotiated-solution request.

The NGPC responded in its 4 April resolution by accepting the Singapore advice as an item to address but rejecting the asserted violation. It reasoned that the Passa paper had not been sought as “External Expert Advice” under the cited Bylaws article; it had been obtained under Module 3.1 of the Applicant Guidebook as part of programme implementation. The Guidebook, the committee said, did not require a further GAC consultation after such analysis and before the Board acted. That classification decided the procedural issue. The same document could be external in an ordinary descriptive sense yet not fall within the legal category that triggered the claimed comment right.

The same 4 April act imposed the 60-day contracting pause. This was a safeguard of opportunity, not a safeguard of outcome. It gave parties more time to negotiate but did not specify what they had to agree, require either applicant to reserve a name, extend a GI-specific objection procedure or condition the eventual contract on consensus. The NGPC also recommended that the full Board consider whether ICANN was the proper venue for such legally complex disputes. That recommendation recognised a jurisdictional problem while leaving the applications on the existing programme path.

The institutional bargain was asymmetrical. Governments obtained delay and continued access. Applicants retained the default that no extra condition had been imposed. ICANN avoided deciding which appellations deserved global DNS protection. Negotiation could still create a practical solution, but the parties seeking safeguards now had to obtain applicant consent unless the Board changed course.

Thirteen reconsideration requests met a bounded accountability mechanism

Governments and GI organisations then filed thirteen requests challenging the March and April resolutions. The requesters included the European Commission, several national governments and organisations representing appellation producers. Their arguments addressed alleged failures to consider material information, reliance on false or misleading information, the treatment of GAC procedure, the status and quality of the Passa analysis, and the 60-day negotiation window. The BGC’s 14 May recommendation consolidated the issues; the NGPC’s 6 June resolution adopted the recommendation to deny all thirteen requests.

The denial illustrates the difference between access to review and access to a merits remedy. Under the then-Bylaws standard applied in the BGC recommendation, a challenge to Board action had to fit specified grounds, including failure to consider material information or reliance on false or inaccurate information. The BGC concluded that the Board had considered the relevant material, had not relied on false information and had not violated the Bylaws in commissioning or using the legal analysis. Disagreement with Passa’s legal reasoning was not itself a ground for reconsideration. Disagreement with the choice of a 60-day window was not enough either.

Standing and timing further narrowed the route to relief. The BGC reasoned that the claimed harm presupposed delegation without the safeguards the requesters wanted; at that point neither string had been delegated, and contracting had been held. The alleged adverse effect was therefore treated as speculative. This produced an accountability tension: before delegation, the harm was considered premature; after delegation, reversing an operational TLD would have been more difficult and disruptive. The procedure was available, but its threshold shaped when a challenge could produce relief.

The committee acknowledged the requesters’ participation and continued to encourage negotiation. Acknowledgement did not alter the legal result. The resolutions remained in force. No additional GI safeguard entered the programme through reconsideration. The requesters had secured a reasoned denial, not a rehearing of whether ICANN ought to create a wine-origin regime.

The outcome does not establish that the substantive objections were weak. It establishes that reconsideration was not designed to decide them on that record. A mechanism can be functioning according to its terms and still be an incomplete route for the policy conflict brought to it. The relevant governance question is not whether a requester was heard; it is what the reviewing body could lawfully test and what consequence it could impose.

CEP moved the dispute from review posture to bargaining

Reconsideration closed one accountability route, but it did not end the hold. By 27 May 2015, ICANN’s Cooperative Engagement Process status report still listed two active matters concerning both strings: one invoked on 4 July 2014 by the European Commission on behalf of EU member states, and another invoked on 8 July by wine-industry organisations. CEP was voluntary and preceded an Independent Review Process; its stated purpose was to resolve or narrow issues that a complainant contemplated taking to IRP. It was not a tribunal, produced no merits judgment and did not itself amend an application or contract. It moved the dispute from a review posture into direct engagement with ICANN.

The negotiating possibility was more ambitious than a private promise. In an ICANN letter of 22 October 2014, chief executive Fadi Chehadé told French minister Axelle Lemaire that contracting remained on hold and that the parties were developing a reserved-list mechanism. The letter said the names would be protected through the Registry Agreement, with rules for allocating them to parties possessing interests and rights; ICANN would then monitor compliance. That description identified the route by which origin protection could have become public and ICANN-enforceable: a defined list or procedure incorporated into the contract.

It also shows that, in October 2014, the eventual legal form had not yet been fixed.

The available later accounts describe a narrower landing. A 2016 oriGIn manual on GIs and new gTLDs, produced by an organisation advocating GI protection, says the CEP complaints were dropped around early June 2015 and that Donuts and wine-industry stakeholders reached an undisclosed agreement. It says there were no special changes to the .WINE or .VIN Registry Agreements and no new Public Interest Commitment precedent, while reporting that Prosecco, Champagne, Port and Sherry were registered by beneficiaries in January 2016. That is useful evidence of a practical accommodation, but it is an interested secondary account, not the agreement itself. Elsewhere the manual says Donuts won auctions for both strings, a statement inconsistent with the official .VIN readiness record marking contention as not applicable. That error is a reason to rely on the manual only for bounded claims that are independently consistent with the contract and status records.

A later presentation by David Taylor described selected names being reserved under several criteria, allocation outside ordinary first-come, first-served registration, a Domain Name Wine Trustee and a charitable donation. It also displayed examples of appellation names allocated under the arrangement. This supplies operational detail from a participant-side account, but not the legal text, claimant standing rules, appeal rights, duration, change-control provisions or remedies. A private agreement may bind its signatories, and an operator may implement it through discretionary reservation powers, without making every term enforceable by ICANN.

The contract contemplated in October was not the contract published in June

ICANN signed the .WINE Registry Agreement with June Station and the .VIN Registry Agreement with Holly Shadow on 18 June 2015. The current .WINE contract page and .VIN contract page identify both as base, non-sponsored agreements and preserve that date. Execution was an institutional threshold: before it, applicant statements and negotiations could influence the terms; after it, ICANN compliance depended on obligations incorporated into the agreement, later amendments and policies validly made applicable under it.

The main agreement gives the operator considerable reservation power. Section 2.6 requires compliance with Specification 5 but also permits the operator to establish or modify policies for blocking additional strings at its discretion. Section 2.8 requires the programme’s legal-rights protections and permits additional protections chosen by the operator. It also requires reasonable investigation and response to reports of illegal conduct from law-enforcement and governmental or quasi-governmental agencies, subject to applicable law. These clauses make voluntary GI reservations operationally possible. They do not identify which wine names qualify, who may claim them, which jurisdiction’s law controls or whether an adverse reservation decision can be appealed.

Specification 11 shows what ICANN could enforce as a Public Interest Commitment. Section 2 is intentionally omitted: application statements, intentions or business plans were not imported there. Section 3 contains standard commitments concerning accredited registrars, unlawful and abusive activity, technical security analysis, transparent registration policies and non-exclusive treatment of a generic string. Sections 3 and 4 are subject to the Public Interest Commitment Dispute Resolution Procedure, and the agreement contemplates remedies that can extend to termination. The remedy can therefore be substantial, but its object is bounded: PICDRP can test, and ICANN can enforce, written commitments—not every expectation expressed during GAC debate or private negotiation.

Section 4’s wording resolves the central evidentiary question. Its open-registration commitment says lawful registrants cannot be excluded merely because they are associated with a minority use of the generic term. Its heading “Geographic name protection” sounds broader than its operative text. That text requires the operator to transmit to registrars the list of names prohibited under Specification 5, keep the list aligned with ICANN’s and consult the GAC and ICANN before seeking release. Specification 5 identifies country and territory names from ISO and United Nations lists, along with technical and institutional reservations. It does not establish a schedule of wine appellations.

The remainder of Section 4 reinforces existing rights and abuse channels. It includes WHOIS accuracy work, the Domains Protected Marks List, an extended trademark-claims service, registrant terms against illegal or abusive activity, restrictions on misuse of privacy services and an anti-abuse policy. The operator reserves broad power to deny, suspend, cancel, transfer or lock a registration for registry integrity, applicable law, government or law-enforcement requirements, dispute processes, policy breaches or third-party rights. Those powers could matter in an origin dispute, especially where a claimant also holds a trademark or obtains an authoritative legal order. They still do not amount to a self-contained GI regime.

No published wine-specific list, eligibility test, trustee procedure or GI appeal route appears in either Registry Agreement. The text does not use “geographical indication” as a contractual category. The private arrangement could remain legally meaningful between its parties, and Section 2.6 could provide the operational capacity to reserve names. The agreement’s entire-agreement clause, however, defines the understanding between ICANN and the operator concerning operation of the TLD. Without incorporation or another contractual hook, a third party alleging breach of the private settlement would need to identify a private-law remedy; it could not simply treat an undisclosed promise as a violated PIC. That is a bounded inference from the published instruments, not a conclusion about the unseen settlement’s validity.

One further limit concerns continuity. The operator-specific Section 4 commitments were reviewable beginning in January 2016 and could, in the operator’s sole discretion and on written notice to ICANN, be discontinued for a substantial and compelling business need. The current ICANN detail pages do not display a TLD-specific instrument under their “Amendments” headings, but that does not prove whether a notice under this clause was given, how it would have been recorded or whether later global amendments affected the text. The continuing status of every optional 2015 commitment therefore cannot be established from the original agreement alone.

Delegation made each institutional threshold visible

Contract execution still did not put either string in the root. The .WINE readiness report and .VIN readiness report, both dated 20 July 2015, record completion of background, registry-services, financial, technical and pre-delegation-testing requirements. They also record that neither applied-for string was classified as a “Geographic Name” under the programme’s geographic-name review. That classification concerned the top-level strings wine and vin; it did not decide whether second-level appellations were protected GIs.

The readiness reports are useful because their checklist categories keep different forms of opposition separate. Each says no formal objection was filed under the Applicant Guidebook’s objection process, while also recording GAC participation and use of accountability mechanisms. Each says no accountability decision required the application to stop before contracting. For .WINE, the report separately records that the applicant prevailed in contention through one of the recognised routes but does not identify which; for .VIN, the corresponding report marks contention resolution as not applicable. “No objections” therefore means no formal Legal Rights, Limited Public Interest or Community Objection—not that governments, producer groups or accountability claimants did not oppose the applications.

The root-zone record then supplies the operational dates. IANA’s .WINE delegation record and .VIN delegation record give a registration date of 23 July 2015 and link delegation reports dated 30 July. The sequence was contract on 18 June, readiness confirmation on 20 July, root registration on 23 July and published delegation reports on 30 July. Those acts belonged to the then-IANA root-zone management chain. They verified that programme and technical prerequisites for the contracted operators had been completed; they did not reopen the merits of wine-origin law.

Binky Moon and Identity Digital changed the operator chain, not the contractual baseline

The original applicant entities did not remain the named operators. ICANN’s completed assignment tracker records Holly Shadow’s .VIN agreement and June Station’s .WINE agreement being assigned to Binky Moon, LLC with an effective date of 29 November 2017. Assignment transferred the agreements to the assignee; it did not, without a separate amendment or incorporated undertaking, create new substantive safeguards. The current contract pages consequently show Binky Moon as operator while retaining the 18 June 2015 agreement date.

On 22 June 2022, the group announced that Donuts and Afilias had rebranded as Identity Digital. That corporate change explains the current administrative chain but is not itself an ICANN policy act. As of 31 July 2026, the IANA records for .WINE and .VIN identify Binky Moon as the sponsoring organisation, “c/o Identity Digital Inc.”; both records show a last update of 7 October 2025. Identity Digital Inc. is therefore the relevant linked directory entity, while Binky Moon remains the operator entity shown in the public ICANN and IANA records.

Identity Digital’s public reserved-names policy, last updated on 12 February 2026, says names may be reserved for registry operations or premium use, to meet ICANN requirements, or because they remain pending or otherwise unavailable; registrars may request a reserved list from account managers. The page does not publish a wine-origin list, Domain Name Wine Trustee criteria or an appellation appeal route. That absence does not prove the private arrangement has ended. It shows only that the current public operator policy reviewed here does not let an outside reader map any continuing wine-specific practice to a disclosed rule and remedy.

What the record establishes—and what it leaves open

The record supports a precise conclusion. ICANN processed sustained governmental and GI opposition through an Early Warning, GAC advice, Board holds, independent legal analysis, reconsideration and CEP. Those mechanisms affected attention, sequence and bargaining leverage. They did not, by themselves, decide substantive GI law. The contract was the point at which negotiation could have become an ICANN-enforceable origin regime. The published .WINE and .VIN agreements instead used standard and operator-proposed PICs, applicable-law and rights provisions, Specification 5 country-and-territory reservations and broad operator discretion. Participant-side evidence describes a practical private accommodation, but the available instruments do not incorporate that arrangement into the PICDRP chain.

Several matters should remain open rather than be filled by inference. The full private agreement and its governing law, duration, signatories and remedies are not public in the assembled record. The evidence does not establish whether any element was made enforceable through an ICANN mechanism outside the published agreement. It does not resolve whether the operator later used the January 2016 discontinuation clause for any Section 4 commitment. The official records confirm that .WINE contention ended but do not identify whether the decisive route was private settlement or auction.

The current public operator materials do not disclose how any surviving GI reservation system maps to the contract. Finally, the sources reviewed do not establish a later .WINE- or .VIN-specific ICANN compliance action or PICDRP determination; an exhaustive negative claim would require a complete case-by-case compliance search.

The institutional outcome was therefore neither a judgment that wine-origin claims lacked legal force nor a decision to convert them into a global DNS entitlement. ICANN chose a more limited form of governance: use process to create negotiating time, contract on a general programme baseline and delegate once programme conditions were met. Assignment to Binky Moon and the Identity Digital operator chain carried that baseline forward. What persisted was the contract. What did not appear in it was the sector-specific rule that opponents had asked ICANN to make binding.