Summary
- ARIN offered the Legacy Registration Services Agreement from 11 October 2007 through 31 December 2023, with an unresolved-ticket grace period ending 31 December 2024, so the consent question spans several contract eras rather than one fixed text.
- Signature was not formally mandatory: ARIN's public account says holders could remain outside the LRSA and keep basic legacy registration, while holders under agreement received fuller services, transfer recognition and a long-lived fee cap.
- Practical pressure still mattered. As accurate registry records, transfers, routing-security services and buyer confidence became more valuable, the unsigned option could be real in law yet weaker in use.
- The Nortel transaction illuminates the difference between sale, registry recognition and contract entry: 666,624 IPv4 addresses sold for about US$7.5 million, while Microsoft's LRSA with ARIN came from the purchaser side and did not make the seller a party to that agreement.
The right unit of analysis is the bargain, not the slogan
The phrase "contractual consent" sounds cleaner than the record allows. So does "administrative ultimatum." The LRSA was neither a pure private bargain between equal actors nor a simple order backed by an admitted public sanction. It sat in the space where a registry's database, recognition practices and service menu can make a voluntary form carry unusually high operational weight.
A legacy holder began from a distinctive position. It held or used Internet number resources that had been allocated before the modern ARIN service relationship. It did not begin with an ordinary ARIN Registration Services Agreement covering those resources. Its record still had to live somewhere, be maintained by someone, and be trusted by parties that needed registry confirmation. That starting position is not the same as a new applicant asking ARIN for fresh resources under ordinary conditions. It is also not the same as a property owner dealing with a land registry under a complete statutory code.
The legacy holder's practical power came from history. ARIN's practical power came from the live registry.
The LRSA offered to bridge that gap. ARIN's current service history says the agreement was available from 11 October 2007 through 31 December 2023, with unresolved LRSA tickets expiring on 31 December 2024. The cited 16 August 2011 v3.0 draft is only one draft version, not proof that every holder signed identical terms or that the 2007 text had the same wording. Even within a stable institutional program, version matters. A clause can change. A fee schedule can change. A service list can change. A promise that looks protective in one draft can interact differently with later policy or transfer practice.
The better method is a bargaining ledger. On one side sits the holder's starting position: existing legacy registration, historical reliance, absence of a standard ARIN contract for the covered resources, and a desire to keep records accurate. On the other side sits ARIN's offer: defined registry services, documented recognition, transfer treatment, routing-security services, policy incorporation and a fee structure that included a long-lived cap for eligible legacy resources.
Across the middle sit the costs: contract obligations, fees, acceptance of future policy interaction, limits on unilateral claims and the practical fact that refusal could leave the holder with a thinner service relationship.
This ledger does not decide legal duress. It asks a more precise governance question: was the unsigned state a real, usable alternative for the services that mattered, or did dependency on registry recognition make signature function like an ultimatum in practice? The answer differs by service. Basic record preservation is not transfer approval. Transfer approval is not routing-security enablement. Routing-security enablement is not an abstract claim about ownership. A holder may be free to refuse one service while being heavily pressured to sign for another.
The LRSA should therefore be judged across three states. The first is unsigned basic legacy registration. The second is a legacy holder under an LRSA. The third is the later regular Registration Services Plan for legacy resources brought under ordinary treatment after the end of new LRSAs and the fee-cap path. That comparison shows why the same act of signing can look like a contract in one column and a registry choke point in another.
State one: unsigned basic legacy registration
The strongest evidence against the ultimatum framing is the existence of an outside option. ARIN's public legacy-resource account distinguishes holders receiving full registry services under RSA or LRSA from those receiving basic legacy services. That distinction matters. If a holder could remain outside the LRSA and retain basic legacy registration, signature was not an absolute condition for every form of recognition. The holder did not have to sign merely to avoid disappearance from the registry.
Basic legacy registration is not trivial. It preserves continuity for resources that predate ARIN's ordinary contractual model. It tells the world that a registry record exists. It reduces the risk that an unsigned holder is treated as if it has no history at all. In a debate about consent, that fact must be given full weight. A contract is less coercive when refusal leaves a service relationship in place.
But the outside option must be measured by use, not just by label. "Basic" can mean enough for a holder whose only aim is to keep a static record. It can mean too little for a holder that needs a transfer, wants stronger routing-security service, faces a buyer demanding registry recognition, or must maintain confidence among lenders, counterparties, customers and technical partners. A holder that never changes its use of addresses may experience basic legacy registration as adequate. A holder selling, acquiring, pledging, reorganising, securing or cleaning records may experience the same basic status as a narrow hallway.
That difference should prevent two mistakes. The first mistake is to say refusal was meaningless just because ARIN controlled the live registry. The record does not support that. ARIN described continuing basic service outside agreement. The second mistake is to say refusal was fully voluntary because a basic record remained. A registry service can be formally available yet economically or operationally limited public evidence for important uses. A market entity often needs more than survival. It needs a record that other parties will accept.
The unsigned state is therefore a real baseline, but not a complete answer. It proves that the LRSA was not a blanket precondition for all legacy registration. It does not prove that all valuable services stayed equally available to nonsigners.
State two: the LRSA as a service contract with institutional benefits
The pro-contract case is not cosmetic. The LRSA offered benefits that a rational holder could value. The 2011 v3.0 draft identifies covered number resources, sets out services, addresses fees, incorporates policy, and deals with registration and use rights as well as transfer treatment. Because it is a draft, it cannot be used as every holder's executed contract. Still, it shows the kind of exchange ARIN was presenting: not merely "obey us," but "enter a defined service relationship with recognised rights and duties."
That distinction matters. A holder under an LRSA gained a clearer written basis for dealing with ARIN. The agreement could give the holder a better account of what ARIN would do, which resources were covered, how fees would be handled, and how the holder's status would be treated in registry services. The long-lived fee cap was especially important. In a world where IPv4 scarcity increased the value of legacy address blocks, predictable registry fees were not a minor concession. They reduced uncertainty and made the agreement more than a burden.
Transfer recognition also had substantial value. A legacy holder contemplating a sale, merger, internal reallocation or other transaction needed registry records to be accepted. A buyer did not only want a private promise from the seller. It wanted a registry outcome that would be visible, durable and compatible with ARIN's service practice. The LRSA could make that outcome more legible. It could reduce friction and give parties a shared route through ARIN's requirements.
Routing-security services added another layer. The more that resource certification and related trust mechanisms matter to network operations, the more a registry service relationship can become a technical asset. A holder may sign not because a human official threatened it, but because the services needed to keep routing records trusted have become tied to being under agreement. That still may be a valid bargain. It is not the same as buying a discretionary luxury.
The LRSA also moved obligations onto the holder. Policy incorporation matters because it connects historical resources to an evolving policy environment. Fees matter because they convert a legacy relationship into a priced service. Contract representations and operational duties matter because they can narrow a holder's ability to keep every prior claim outside ARIN's framework. A fair assessment must keep both sides visible: enforceable value and submitted constraint.
Under this second state, the LRSA looks like a real contract. The question is whether the holder's consent to that contract was shaped by a strong enough outside option.
State three: the regular Registration Services Plan after the LRSA path closed
The end of new LRSAs changes the comparison. ARIN's later notice recorded that unresolved LRSA tickets would expire on 31 December 2024 and that the LRSA and fee-cap path had ended for new entrants after 31 December 2023. Legacy resources later brought under agreement would be handled under the regular Registration Services Plan. That is not just housekeeping. It closes one institutional compromise and moves later signers toward ordinary treatment.
The LRSA was a transitional instrument for legacy resources. It acknowledged that legacy holders were not situated like new recipients of number resources. It offered a special contractual bridge, including fee treatment that made the bridge more palatable. Once that bridge closed, the consent question did not vanish. It changed form. A holder seeking full services later had a different menu, with a different price and fewer legacy-specific concessions.
This matters for fairness because the passage of time can change the value of refusal. A holder in 2007 faced a new agreement, live disagreement about legacy rights, and a registry still defining the legacy-service boundary. A holder in 2023 faced a more mature transfer market, more developed registry practice, and greater operational importance for clean records and security services. A holder after the LRSA closing faces a further shift: the special legacy contract is no longer the same available offer.
That sequence should prevent anachronism. It would be wrong to judge a 2007 decision solely by later routing-security expectations. It would also be wrong to judge a late decision as if the holder still had the same special fee-cap path that existed earlier. Consent quality is time-specific. The relevant outside option is the service menu at the moment the holder had to decide.
The three-state comparison produces a restrained finding. The LRSA was not simply the ordinary RSA under another name. It was a special legacy agreement. Basic legacy services were not the same as full services under LRSA. Later regular-plan treatment was not the same as the earlier LRSA bargain. A serious consent analysis must hold these states apart.
The service-pressure gradient
Practical pressure was not uniform across the service menu. It should be ranked.
At the low-pressure end sits static record continuity. If an unsigned holder needed only the continued existence of a basic legacy record, the pressure to sign was weaker. ARIN's distinction between basic legacy service and full services supports that conclusion. A holder that did not need transfer recognition, enhanced services or a more developed written relationship had a plausible reason to stay outside.
Next sits record maintenance. Basic legacy service may preserve a record, but the details of contact accuracy, organisational changes and confidence in the registry file can become more important over time. If a holder could keep records accurate without signing, pressure stays lower. If significant updates became difficult or less trusted outside agreement, pressure rises. The fixed record does not supply a complete service-by-service denial table, so this column remains a hypothesis rather than a proved injury.
Higher still sits transfer recognition. Transfers are where registry dependence becomes visible. A seller and buyer can agree privately, but a buyer wants ARIN's registry record to reflect the result. Without registry recognition, the buyer's risk rises. If ARIN's transfer treatment was much clearer or more accessible under LRSA, then signature had substantial practical value. That does not make signature legally compelled. It means the holder's choice was made under strong service pressure.
Routing-security services sit in the same high-pressure range. If a holder needs registry-backed security services to support trust in the use of resources, an agreement can become the route to operational confidence. A holder that signs for those services may be acting prudently, not reluctantly. But prudence and pressure can coexist. A costly outside option can make consent real and constrained at the same time.
The highest-pressure point is the combined transaction. A holder trying to transfer legacy resources may face a buyer that demands registry recognition, a financing or diligence process that demands clean records, and operational parties that care about security services. In that case, the holder does not merely compare contract clauses. It compares a recognised transaction with a transaction that may be harder to close. That is where the administrative-ultimatum claim has its strongest practical force.
The gradient also protects ARIN's strongest point. The existence of pressure in transfer or security services does not prove that basic registration was withheld. It does not prove that all nonsigners suffered operational harm. It does not prove that every LRSA was accepted under comparable conditions. Pressure must be shown at the service level.
How to test dependency pressure without overstating it
Dependency pressure should be treated as a mechanism, not a conclusion. For each asserted pressure point, the test needs three parts: predicted behaviour, alternative explanation and disconfirming evidence.
For counterparties, the predicted behaviour is that buyers, lenders or corporate transaction parties would prefer or require LRSA-covered status before closing. They might treat an unsigned legacy record as a diligence risk even if ARIN still maintained basic registration. The alternative explanation is ordinary caution. Counterparties often prefer written registry contracts because they reduce uncertainty, not because ARIN forced them. Disconfirming evidence would include completed transactions outside LRSA with comparable pricing, no added delay and no buyer discount for unsigned status.
For trusted records, the predicted behaviour is that holders with changing corporate names, contacts or internal reorganisations would sign in order to get clearer updates and greater confidence that registry records would be accepted. The alternative explanation is administrative housekeeping. A holder may sign because the written service path is easier, not because the unsigned path is broken. Disconfirming evidence would include reliable, timely, comparable record updates for unsigned holders across similar cases.
For transfers, the predicted behaviour is that sellers or buyers would enter LRSA or related agreements around the transfer event, especially where substantial value is at stake. The alternative explanation is that scarce IPv4 resources made parties prefer maximum certainty regardless of ARIN's pressure. Disconfirming evidence would include a mature market of unsigned legacy transfers that ARIN recognised on predictable terms without material extra cost.
For routing-security services, the predicted behaviour is that holders needing enhanced trust functions would sign even if they preferred to avoid broader contractual submission. The alternative explanation is that security services are a genuine extra service for which agreement is normal. Disconfirming evidence would include equivalent routing-security access for nonsigners, with no practical difference in trust, processing or recognition.
This method is deliberately narrow. It avoids using the word "coercion" as a substitute for evidence. It also avoids the opposite error, which is to declare voluntariness merely because a refusal box existed. A registry can exert pressure through the architecture of services. The question is whether that pressure is documented, whether it differs by service, and whether a holder's outside option was commercially and operationally usable.
The 2007 publication dispute shows the problem was visible early
The LRSA was not introduced into a silent field. The October 2007 posting of the Legacy RSA and FAQ, and the immediate public discussion that followed, preserved live disagreement about rights, revocability and fairness. Those messages are not legal holdings. They do not settle what a court would decide. They do not prove that every holder shared the same view. But they show that the consent problem was visible from the start.
That early dispute matters because it shows the LRSA was not only an administrative form. Entities understood that legacy resources carried contested assumptions. Some saw ARIN as offering a reasonable written service bargain for resources that needed stable records. Others worried that ARIN was using registry dependence to draw older allocations into a contractual framework. Both concerns were rational enough to require analysis.
The fairness issue was not simply whether ARIN could charge a fee. It was whether the fee and policy obligations were attached to a genuinely optional service upgrade or to services that holders needed in order to preserve the practical value of their legacy resources. If the agreement was only a route to additional, optional services, the pro-contract case strengthens. If the agreement became the practical route to recognised transfer and trusted operation, the pressure case strengthens.
The 2007 record also helps separate voice from consent. Public discussion allowed objections to be heard. It did not create a measured denominator of eligible holders, signers, nonsigners, refusals or negotiated modifications. A mailing-list dispute can show contested legitimacy. It cannot quantify how many holders felt compelled or how many accepted the agreement as a fair bargain.
That distinction remains important for the later record. ARIN's own public reporting can distinguish resources under agreement from basic legacy services, but status counts do not reveal motive. A holder under agreement may have signed because the deal was good. It may have signed because a buyer demanded recognition. It may have signed because counsel preferred written certainty. It may have signed because the fee cap was attractive. It may have signed because a transfer could not otherwise be completed on acceptable terms. Public status alone cannot choose among those explanations.
Nortel shows transaction sequence, not a universal rule
The Nortel transaction is useful because it places legacy resources, private sale value and registry recognition in one sequence. The 2017 legal scholarship on IP address control describes a bankruptcy sale involving 666,624 IPv4 addresses for about US$7.5 million and an LRSA between Microsoft and ARIN. The seller was not party to that LRSA. That bounded sequence is more instructive than a broad slogan about ownership.
The transaction shows first that legacy resources could be valued in a private sale setting. It also shows that registry recognition mattered to the purchaser. Microsoft did not merely rely on the seller's transfer document. It entered an LRSA with ARIN. That does not prove that ARIN owned the addresses. It does not prove that the bankruptcy order resolved all legacy title questions. It does not prove that every future transfer required the same path. It shows that for a high-value transfer, the buyer's relationship with the registry was part of making the transaction usable.
The seller not being party to Microsoft's LRSA is especially important. It prevents a simple story in which the seller's legacy rights were directly transformed by signing ARIN's contract. The contract that mattered in the sequence was on the purchaser side. That supports a more precise claim: registry recognition can become indispensable to the buyer's practical enjoyment of the acquired resources even if the seller's legal posture remains disputed or unadjudicated.
Nortel also illustrates the difference between private ordering and registry ordering. A bankruptcy sale can approve a transaction among parties before the registry's service relationship is complete. But a buyer still needs registry records to reflect and support use. The market can produce a deal; the registry can make the deal administratively durable. That makes ARIN's role powerful without requiring the conclusion that ARIN had comprehensive property ownership.
For the LRSA consent question, Nortel strengthens both sides. The pro-contract side can say the buyer received concrete service value and clearer registry recognition for a valuable asset. The pressure side can say the transaction demonstrates why registry agreement could become practically necessary for value realisation. The balanced lesson is that the LRSA was a real instrument of recognition in a market where private sale documents alone were not enough to eliminate risk.
The strongest pro-contract case
The best defence of the LRSA begins with institutional responsibility. ARIN maintained a registry whose accuracy affected operators beyond the immediate holder. It could not simply accept every private claim about legacy resources without conditions. It needed a service relationship to know who was responsible, what resources were covered, how disputes would be handled, and how policy would apply.
From that perspective, the LRSA was a governance improvement. It converted informal historical reliance into a written service relationship. It supplied a defined contact surface. It made services and fees more predictable. It offered a fee cap that recognised the special position of legacy holders. It helped align legacy records with transfer practice and registry policy. It could reduce disputes by putting terms in writing.
The pro-contract case also treats refusal as meaningful. If an unsigned holder kept basic legacy registration, then ARIN was not erasing legacy records to force agreement. It was offering a fuller set of services in exchange for contract. Many institutions do this. A baseline service may remain free or limited, while a more complete service requires agreement. That model is not inherently abusive.
The LRSA's enforceable character also benefits holders. A written agreement can bind the registry as well as the holder. It can make service expectations clearer than institutional goodwill. It can support planning by limiting fees through a cap. It can provide a recognised route for transaction counsel, network operators and business parties who need certainty.
The fact that a holder signs because an agreement is useful does not make the agreement suspect. Scarce resources, large values and technical dependence make certainty valuable. A holder may rationally accept obligations because the benefits exceed the cost. That is consent in a practical commercial sense, even if the parties are not equal in structural power.
This case should be taken seriously. If ARIN had offered no documented services, no fee cap, no baseline outside option and no public recognition distinction, the ultimatum argument would be stronger. The actual record is more mixed. The agreement supplied value.
The strongest dependency-pressure case
The best critique begins from the registry choke point. ARIN was not an ordinary vendor competing to serve legacy holders. It maintained the recognised registry records for its region. A holder that wanted a record update, a transfer or a security-related service could not simply choose a different regional registry for the same resources. That structural position made ARIN's offer different from a normal service contract.
The outside option was also thinner than the word "option" suggests. Basic legacy registration could preserve an existing record, but it did not necessarily provide the full bundle needed for modern use. If counterparties discounted unsigned status, if transfer recognition depended on agreement, or if routing-security services required agreement, a holder's ability to refuse declined as soon as it needed those services. The more valuable the resources became, the more expensive refusal could be.
The dependency critique is strongest when it focuses on value realisation rather than bare existence. ARIN did not need to threaten removal of a record to create pressure. It only needed to make full recognition, transfer durability and enhanced services materially easier under agreement. A holder could remain outside and still face a degraded ability to sell, reorganise or secure its resources.
This is why formal voluntariness cannot be the only test. A person can be free to decline a contract and still face a practical compulsion created by a monopolistic service point. In registry governance, the relevant loss is not only immediate cancellation. It can be delay, uncertainty, buyer discount, inability to satisfy diligence, weaker security service or reduced confidence in the record.
The critique remains bounded. The fixed record does not prove that ARIN denied all significant services to nonsigners. It does not quantify refusal rates. It does not show all executed terms or side letters. It does not provide a final appellate holding that defines legacy address title, ARIN authority and contract pressure for all cases. Therefore, the pressure case should not be written as a completed legal verdict. It is a strong governance concern supported by the structure of dependency and the service distinctions visible in the record.
Fee caps can be both concession and lever
The LRSA fee cap deserves separate treatment because price can carry more than one meaning. For legacy holders, a cap was a concession. It recognised that old allocations had a different history from newly issued resources. It reduced fear that signing would open the door to ordinary fee growth without limit. It made the agreement more predictable and therefore more attractive.
That concession strengthens consent. A party offered a favourable price term is not merely being burdened. It receives value. The cap can be viewed as ARIN paying an institutional price for bringing legacy resources into a clearer contractual relationship. Holders who signed early could rationally value that bargain.
At the same time, the cap could function as a time-sensitive lever. If holders believed the special treatment might end, they had an incentive to sign before the path closed. Later, when ARIN ended new LRSAs and the fee-cap path, the choice changed. A holder could no longer compare basic legacy service with the same capped LRSA offer. It had to compare basic legacy service with regular-plan treatment. That shift makes the timing of consent important.
The cap therefore cannot be reduced to either fairness or pressure. It was both a benefit and an inducement. Whether that inducement was benign depends on the service alternatives. If unsigned holders could obtain needed services on comparable terms, the cap looks like a voluntary discount. If needed services were meaningfully tied to signing, the cap looks more like a limited-time settlement offer in front of a choke point.
This is one reason versioned evidence matters. A fee term in a 2011 draft does not prove the same economic offer for all years. The period from 2007 through 2023 was long enough for scarcity, transfer value and operational expectations to change. A cap that looked generous in one phase may have had different strategic force later. The terms and service context have to be matched by date.
Policy incorporation and the legacy-holder fear
Policy incorporation is another double-edged term. ARIN needed policies to run a coherent registry. Without a policy framework, transfers and services could become inconsistent, opaque or unfair to other operators. A holder entering LRSA could reasonably accept that some registry policies should govern services connected to the covered resources.
For legacy holders, however, policy incorporation could look like a change in the original bargain. Their resources predated ARIN's ordinary contractual model. They might have believed that future community policy should not rewrite their historical position without consent. By signing, they could be seen as accepting a channel through which later policy changes might matter.
This concern does not make policy incorporation illegitimate. A registry cannot administer scarce, globally relevant resources as if each historical allocation lives in isolation. Transfers affect others. Record accuracy affects others. Security services affect others. The registry's policy environment has a public coordination function.
The consent question is whether the holder accepted that environment freely enough. If the holder signed mainly to obtain an optional benefit, policy incorporation is part of the price of that benefit. If the holder signed because the alternative impaired transfer value or trusted operation, policy incorporation carries more pressure. The clause may be formally agreed and still institutionally sensitive.
The v3.0 draft helps identify this issue but cannot settle every version. It shows that policy and contract were connected in the LRSA architecture. It does not show the precise negotiation history for each holder. It does not show whether some holders received modifications. It does not show how ARIN described policy effects at the moment of each signature.
The fair governance remedy is not to pretend policy incorporation had no force. It is to make its force explicit, version by version, so holders and observers can see exactly what was accepted and what services were tied to that acceptance.
What the public data can show and cannot show
ARIN's public resources-under-agreement reporting is useful because it distinguishes organisations receiving full registry services under RSA or LRSA from those receiving basic legacy services. That distinction confirms the three-state framework. It shows that agreement status is not merely historical trivia; it maps to service treatment.
The same reporting cannot explain motive. It does not tell us why an organisation signed. It does not identify whether the holder faced a pending transfer, a buyer demand, an internal governance requirement, a security need, a counsel recommendation or a simple preference for certainty. It does not show rejected terms, negotiation power, refusals or terminations. It is status data, not consent-quality data.
The missing evidence is specific. A complete assessment would need all executed LRSA versions, any side letters and negotiated modifications, signatory counts by version, the denominator of eligible legacy holders, signer and refusal counts over time, service access comparisons for nonsigners, evidence of actual operational harm where service was unavailable, and a final appellate holding addressing property, registry authority and contract pressure across legacy resources. Without those materials, confidence should stay bounded.
That limit cuts both ways. It prevents critics from proving a universal administrative ultimatum. It also prevents defenders from proving robust consent across the whole legacy population. The record supports a mixed finding: formal choice existed, defined benefits existed, and practical pressure likely varied with the holder's service needs.
A stronger public audit would not need to reveal private commercial details. It could publish version histories, service matrices, aggregate counts and examples stripped of sensitive party information. It could distinguish "basic record maintained," "record update available," "transfer recognised," "routing-security service available," and "fee cap applicable" by agreement status and date. That would convert the argument from slogans into measured outside-option analysis.
Why the LRSA was not the ordinary RSA
The LRSA must not be collapsed into the ordinary RSA. The ordinary RSA was the standard contractual relationship for resources issued through ARIN's normal service model. The LRSA addressed a different legacy population: holders whose resources came from earlier arrangements and whose records had to be reconciled with ARIN's live registry.
The difference explains the special fee treatment and the special consent debate. A new resource recipient asks ARIN for something under ARIN's existing terms. A legacy holder already has a historical allocation and may need ARIN's recognition to preserve, update or transfer it. The holder is not simply applying for a new benefit. It is deciding whether to bring an old position into a modern contract.
Collapsing the LRSA into the RSA hides that asymmetry. It makes the legacy holder look like any other customer. Collapsing basic legacy service into the LRSA hides the opposite point: not every registry recognition service required the same agreement status. Collapsing post-2023 regular-plan treatment into the LRSA hides the fact that ARIN's offer changed after the legacy path closed.
The institutional legitimacy question depends on those distinctions. A registry may reasonably require a standard RSA for newly issued resources. It may reasonably offer a special LRSA for older resources. It may reasonably end that special offer after many years. But each step has its own consent profile. The fact that one step is legitimate does not automatically validate the next.
A ranked finding
The most defensible finding is ranked, not binary.
First, the LRSA was formally optional for legacy holders who were willing to remain within basic legacy registration. That point is supported by ARIN's distinction between full services under agreement and basic legacy services outside agreement. It means the agreement should not be described as an absolute order to sign.
Second, the LRSA offered real value. Defined services, clearer recognition, transfer treatment, routing-security access and a long-lived fee cap were not decorative. They gave holders reasons to sign that were consistent with voluntary commercial judgment. The agreement could protect holders as well as bind them.
Third, the practical pressure was substantial for holders needing transfers, enhanced trust services or counterparty confidence. The more a holder needed value realisation rather than static record survival, the weaker the unsigned outside option became. In those settings, the LRSA could function like a practical requirement without being formally mandatory.
Fourth, the public record is not strong enough to declare a universal legal conclusion about coercion, property title or ARIN's authority over every legacy resource. The Nortel sequence, the 2007 dispute, the 2011 draft and ARIN's service descriptions illuminate the structure. They do not supply all executed terms, all motives or a final universal holding.
That ranked finding is less dramatic than either title label. It is also more accurate. The LRSA was a contractual exchange built around a registry choke point.
The contract remedy, the outside-option test and the archival test
The best remedy is not to relitigate every LRSA in the abstract. It is to improve the evidence that lets holders and observers assess future registry bargains.
The contract remedy is modular clarity. Every legacy-facing agreement should identify, in plain service terms, what the holder receives, what it gives up, what policies apply, what fees are capped or uncapped, what happens to transfers, what security services depend on agreement, and what rights remain if the holder declines. The document should not rely on a general sense that the registry is important. It should state the service exchange directly.
The outside-option measurement test is practical. For each major service, ARIN should be able to answer four questions by date and agreement status: Can an unsigned holder obtain the service? Is the service equivalent in timing, reliability and recognition? Do counterparties treat the unsigned result as usable? Is there evidence of material discount, delay or failed transaction due to unsigned status? If the answer shows parity, consent looks stronger. If the answer shows degraded value, pressure must be acknowledged.
The versioned-contract archival test is historical. A governance record should preserve the 2007 form, later drafts, executed-form variants where disclosure is possible, fee schedules, service matrices and closure notices. It should distinguish draft text from executed text and special legacy terms from ordinary Registration Services Plan terms. The 2011 v3.0 draft is helpful; it is not enough to stand for every year and every signer.
The LRSA's legitimacy ultimately depends on whether the registry can show that it offered more than a thin choice. A real contract asks for obligations in exchange for defined value. An administrative ultimatum makes refusal so costly that the form of choice hides dependence. The record supports neither extreme as a universal description. It shows a legacy-service bargain whose voluntariness rose or fell with the service being sought, the version being signed and the practical strength of basic legacy registration at that moment.
For static records, contractual consent is the better description. For high-value transfers and trust-dependent services, dependency pressure is the better warning. For the institution as a whole, the answer is conditional: the LRSA was legitimate to the extent that ARIN preserved a usable outside option and documented the service value of signing; it became ultimatum-like wherever the unsigned path existed on paper but failed the practical test of recognition, transferability and trusted operation.