The Volokh Conspiracy
Mostly law professors | Sometimes contrarian | Often libertarian | Always independent
Responding to Reader Comments on The Five Internet Rights
Seven-layer stacks, messy anecdotes, and the conservative case for net neutrality.
I want to thank Eugene again for inviting me to guest-blog last week about my new article, The Five Internet Rights. See Parts I, II, III, IV, and V. I thought I'd follow up with just one more post to respond to some of the reader comments I received on the series.
In the first place, it was certainly an interesting (and educational) experience trying to distill a 100-page, heavily footnoted, academic article into five short-form blog posts. That translation forced me to elide over many important details and caveats that were addressed in the article, some of which readers focused on. For example:
Technical Objections
On the technical side, the savvy DNS practitioner might point out that having one's domain name suspended doesn't amount to getting kicked off the internet (just ask gab.com and ar15.com). Often, when a registrar suspends a domain name, it gives the registrant an opportunity to find another registrar. Given that more than a thousand ICANN-accredited registrars currently offer their services to the public, a registrant faced with a suspension for purely ideological reasons can usually find a substitute. Or a truly beleaguered speaker could theoretically become her own registrar (with a fair amount of money and effort). And even if a top-level domain registry (as distinct from a registrar) permanently deprived you of your domain name (say, example.com), you could probably register another string in a different top-level domain (say, example.xyz or even example.ru).
Likewise, even if a regional internet registry (RIR) revoked your IP addresses, you might manage to procure substitute address space within another RIR's service region. I address these nuances in a section of the article that distinguishes between "strict" and "fuzzy" classes of intermediaries and notes the hierarchy of control from registrars to registries to ICANN. But obviously, that would have been too in the weeds for a blog series (as would have been any description of the seven-layer OSI network stack).
Another important clarification is that even if a person lost her domain name, IP address, and commercial internet connection, those actions would only kick her website off the internet; they wouldn't necessarily kick her off the internet. She could probably continue to leverage the internet to express her viewpoints using non-web technologies, such as email, FTP, peer-to-peer, or video conferencing. I acknowledge as much in the article. But I also argue that websites enjoy a special status when it comes to online expression. Websites alone combine control, social valence, accessibility, discoverability, authority, and permanency. Not so with spoof-able emails, undiscoverable file objects, or ephemeral Zoom-casts. A viewpoint that is denied a home on every website might not be banished from the internet entirely, but it would be effectively banished from the public internet.
Messy Anecdotes
Some readers focused on certain anecdotes I used to illustrate the evolution of content moderation as it has progressed down the internet stack. Did GoDaddy suspend ar15.com simply because GoDaddy disliked lawfully expressed viewpoints on the site, or did GoDaddy find instances of actual (unlawful) incitement to violence? Did LACNIC revoke IP addresses used by Parler because it wanted to take the unpopular social media platform offline, or was it simply enforcing neutral policies?
As I address in the article, instances of deplatforming will often be messy or ambiguous. Take LACNIC, for example, which supposedly revoked IP addresses belonging to DDoS-Guard (Parler's cloud hosting provider) because DDoS-Guard had used a shell company in Belize to obtain the addresses. Yet corporations often create local subsidiaries (with no employees) in foreign jurisdictions solely to obtain licenses or other resources granted only to local entities. And as any telecom lawyer who has incorporated local subsidiaries in different countries to obtain telecom licenses for a global OTT service will tell you, that is a perfectly acceptable practice. Moreover, the provision at issue, § 1.14 of the LACNIC Policy Manual, requires only that address holders be "legally constituted within [the LACNIC] service region"; it contains no requirements as to a minimum of employees.
Perhaps DDoS-Guard lost its IP addresses because it did not use them primarily to serve networks in Latin America, which is also contemplated by LACNIC policy. If DDoS-Guard had violated that principle (and I've seen no reporting stating that it had), then that might indeed have been a viewpoint-neutral reason for the revocation. But the fact that many address holders are likely in a similar position highlights another problem: the opportunity for selective enforcement. If there is any desire to see an unpopular speaker deplatformed, it will often be possible to find some technical violation. Many intermediaries prohibit "objectionable" content (which is usually not defined), GoDaddy may cancel a domain name if it receives an "excessive amount of complaints" from the public, and RIPE, another RIR, reserves the right to revoke IP addresses from any holder that merely "cause[s] damage" to its name, which theoretically could be interpreted to encompass situations where enough people criticize RIPE for enabling an unpopular site to stay online. As one commentator noted, in 2021, GoFundMe demonetized the Canadian trucker protesters based on only three instances of minor illegality while continuing to fund protests in Portland that "set fire to police stations, vandalized city hall, wielded weapons and injured police officers."
And just as concerning, I would argue, was Ukraine's attempt to revoke Russia's IP addresses and top-level domains. That attempt perhaps serves as a cleaner example of the growing interest in using internet architecture as a tactical weapon (not to take anything away from Ukraine's cause, which I otherwise support).
In any event, and circling back to my opening remarks, it's important to understand that The Five Internet Rights is ultimately a theoretical piece. Its point is not to demonize any particular intermediaries or to claim to know their motives. And its thesis doesn't depend on any particular instances of deplatforming or my interpretation of them. Rather, it offers a theory of interventionism—an answer to the thorny question of when, if ever, the state should intervene in private content moderation.
Doesn't your thesis require you to support net neutrality?
For the most part, yes. My thesis is that an intermediary's "content moderation" practices—its decision to revoke a resource used by a third party to publish lawful content on the internet—should be subject to regulation (in the U.S.) if (and perhaps only if) the revocation of that resource presents the risk of viewpoint foreclosure. That is, if (1) that resource class is essential to operating a public website and (2) a person deprived of that resource cannot realistically create a substitute. By my reckoning, three resource classes satisfy this test: networks, IP addresses, and domain names. The "five internet rights" call for non-discrimination protections across these three classes and only these three classes.
That thesis is bound to upset some folks on both the left and the right (no one loves a moderate). Conservatives might complain that it doesn't touch social media (or any other websites), search engines, app stores, or even cloud computing (inclusive of content delivery networks and DDoS mitigation services). Google would remain free to de-index 4chan, Apple could keep Parler out of the App Store, and Amazon could boot Parler off AWS. After all, none of those actions would take the targeted site permanently offline. By contrast, progressives might oppose any policy that would keep the worst kinds of content online, even if that online presence is limited to backwater websites that few visit or link to.
Net neutrality (before it was repealed) guaranteed only a right to "accessibility"—the right not to have one's users blocked from accessing her lawful website by their ISPs (their last-mile networks). But it didn't protect a website operator's ability to connect her website to the internet in the first place, to maintain a static IP address and a resolvable domain name, or to have her website's packets faithfully routed through intermediate backbone networks. For those, you need additional rights of connectivity, addressability, nameability, and routability.
Some have told me that they think of the five internet rights as a kind of expanded net neutrality (perhaps it might be called "internet neutrality" or "infrastructure neutrality"). That's true in a sense, but there's an important distinction. From the beginning, the concerns that motivated the political left to pursue net neutrality were economic in nature. The left wanted to prevent ISPs from leveraging their networks and their access to subscribers (in telecom parlance, their "terminating access monopolies") to extract rents from websites in the form of tolls, paid prioritization, or zero-rating or to advantage their OTT services over those of competitors. By contrast, the concerns that have motivated the political right to pass laws like those in Texas and Florida in recent years have been moral in nature (in the deontological sense and not to make any value judgments about the moral rightness of those efforts). The right has wanted to prevent websites like social media platforms from discriminating against users for ideological reasons. Both are non-discrimination enterprises, but their theoretical foundations differ.
What the right and the left should appreciate is that their interests now align. The FCC's 2015 Open Internet Order prevented ISPs from blocking their subscribers' access to lawful websites and applications. That broad prohibition wasn't conditioned on whether an ISP might block a website for economic reasons (to charge a toll or disadvantage a competitor) or for moral reasons (to counter the viewpoints expressed on the site). If the right is concerned about private "censorship" on the internet, it should consider giving the left the economic neutrality it has long desired in exchange for the ideological neutrality the right now craves. Given that the ISP ecosystem already abides by net neutrality principles (whether because of state net neutrality laws, the EU Open Internet Regulation, or market forces), that seems like a small concession. Ideally, the left and the right could agree on a broad neutrality framework that encompasses all aspects of the network (beyond net neutrality's focus on last-mile, mass market access), as well as DNS and the IP address system, and that protects against both economic and ideological discrimination. (Precisely what the "five internet rights" are designed to do.)
At least, that seems like a sensible compromise to me.
Editor's Note: We invite comments and request that they be civil and on-topic. We do not moderate or assume any responsibility for comments, which are owned by the readers who post them. Comments do not represent the views of Reason.com or Reason Foundation. We reserve the right to delete any comment for any reason at any time. Comments may only be edited within 5 minutes of posting. Report abuses.
Please
to post comments
Thank you for a very thought-provoking series!
Agreed. I really enjoyed the series. Thanks to Prof. Nugent for the articles, and Prof. Volokh, who's been roping in a lot of guest talent these days.
“My thesis is that an intermediary’s “content moderation” practices—its decision to revoke a resource used by a third party to publish lawful content on the internet—should be subject to regulation (in the U.S.) if (and perhaps only if) the revocation of that resource presents the risk of viewpoint foreclosure.”
Why would that not apply to social media?
The major difference I can see is that social media is an oligopoly instead of a monopoly, so if you’re booted off of *only* Facebook and nothing else you still have an outlet. But that allows the same problems piecemeal that booting someone off of domain names allows in one fell swoop. And being kicked off of one social medium is highly correlated with being kicked off of another.
If a state government uses a social medium platform to substitute for a state website (Massachusetts does) and a user has been kicked off the platform, the user may no longer have access to a state public forum or state rules and regulations.
The reason is addressed in the series of posts and presumably in the original article, and I think the tl;dr is that you don't actually need social media sites to speak on the Internet, but if you don't have IP addresses or domain name resolution there's no alternative mechanism to reach you.
Sure there's an alternative mechanism. There just isn't as *good* an alternative mechanism. He even covers this above:
"On the technical side, the savvy DNS practitioner might point out that having one's domain name suspended doesn't amount to getting kicked off the internet ...
Likewise, even if a regional internet registry (RIR) revoked your IP addresses, you might manage to procure substitute address space within another RIR's service region. ...
Another important clarification is that even if a person lost her domain name, IP address, and commercial internet connection, those actions would only kick her website off the internet; they wouldn't necessarily kick her off the internet."
So even if there's an alternative mechanism, if the alternative mechanism is a lot worse than the one you're barred from, it should still count by his own standards.
There's a huge difference between needing to go to a different RIR to get addresses (which you can't actually do unless you are a multi-continent entity since the RIRs only service specific global regions) and setting up some alternative venue to publish whatever screed you want on the Internet.
As proof of this point: notice that we are having this conversation on a platform that is not any of the major social media platforms. Beyond that, the Volokh conspiracy site itself has moved multiple times over the years. In fact, most of the content of the Internet exists outside social media sites so it's quite obvious there's perfectly good alternatives to them for someone to get their message out.
The historical analogy I would use is shortwave radio broadcasts.
We had Voice of America and the Soviet Block had their stations and they would jam ours and I suspect we jammed theirs. I am not sure how that finally wound up but it's the same type of issue.
I have been an avid SW listener since I was 5, in 1973. I am not aware of a single case of the US jamming a single Eastern Bloc nation's broadcasts. Back in the day when they still broadcasted on SW I QSL'ed pretty much every country behind the Iron Curtain. My parents weren't very happy at the time with me getting mail from the USSR, East Germany, Czechoslovakia, etc.
The Internet is not a broadcast medium. A social medium platform has bailment of a message in a backend server. A user only sees the message if he specifically requests message to be transported the user's computing device and to be displayed on the display of the user's computing device.
Web pages aren't essentially broadcast?
Yes, you have to request it, but then you had to tune your radio to a specific frequency to receive a specific broadcast.
Tuning the radio dial is a wholly local operation. The broadcaster is not broadcasting the broadcast specifically to the radio that was tuned to the broadcaster. The social medium platform transmits a requested message specifically to the user that requested the message. The social medium platform provides a service that is email with a niftier service.
I meant niftier user interface and not niftier service.
Once again: "bailment of a message" is word soup. One does not transfer possession of anything when one posts a message on Twitter.
"The internet" isn't anything; it's an abstraction. But social media companies absolutely are broadcast media in the most important ways in their ordinary use. They represent one-to-many communications in which the recipients, not the senders, decide who will view them.
Literary property and bailment of literary property have been recognized in English law since the 17th century. When one borrows a book from a library, one has bailment of literary property, which is embodied in the physical property of the book. A text or message is literary property whatever its substrate. These concepts become important law in the early days of the telegraph when one news organization paid a telegraph company not to carry (by common carriage) a news report (unpublished literary property) to another news organization.
The Internet is as concrete as predecessor packet-switched networks that became part of the Internet. These networks included: GTE Telenet and the Arpanet.
The belief in the abstract nature of the Internet is like a belief in the abstract nature of a telephone network or of a telegraph network.
If I remember correctly the last major revision of copyright law took place in 1976.
SCOTUS last addressed issues of literary property in Harper & Row, Publishers, Inc. v. Nation Enterprises, 471 U.S. 539, 105 S. Ct. 2218 (1985).
Completely wrong. When one borrows a book from a library, one has bailment of a physical object. Not the information in the book. The book itself. The library book is no different than a rock from a property law perspective.
For a copyrighted text, David Nieporent is correct. If the text is not copyrightable, David may not be correct. We have a few libraries in my neighborhood where a scholar can borrow an unpublished manuscript or book. When one borrows an unpublished text, one probably has bailment of the substrate and of the text separately. I only know two US cases on the subject. There are probably more cases on the subject in the UK.
Net Neutrality is more then just not blocking, it is also about the ISPs not intentionally slowing down or degrading the connection unless for legitimate network management. The only ones who don't like Net Neutrality are the ISPs and some large internet companies who wand to slow the connection of their rivals.
Net neutrality is also hated by users who get lousy service because some bandwidth is getting a free pass.
That is not caused by Net Neutrality, that is caused my ISPs not doing proper network management. And no one gets a free pass.
Sorry I didn't arrive in time to comment on your initial post but while I'm broadly sympathetic to the idea I just don't see how it works out in practice.
Ok, I have a right to have a website and an IP address. Can they charge me an arm and a leg for all inbound traffic? Block XHR and websockets connections in the name of security and reduce me to a 90s plain HTML website? What if comcast offers me a website on their shitty braned hosting platform? Can they let me run a website and buy a domain but block all DNS traffic to my IP so I can't connect the two? What if they give me an IPV6 address but then don't allow me to run a DNS server and don't serve IPV6?
The problem is these aren't simple yes/no things but come packaged with certain expectations about a reasonable setup but it's very easy for ISPs to play games with this in the name of security and, at the very least, make it very difficult to use or vindicate these rights.
Finally, as a general problem there is the issue of how you get positive rights enforced. Who do you sue if a bunch of entities (many ISPs) individually fail to accept me as a customer? How do I compel the government to pass laws practically effectuating these rights? Without such compulsion aren't they just a policy prescription.
All good questions, Peter. Here’s how I’d analyze those issues.
First, determine whether a given resource is necessary to maintain a publicly accessible website. ISP access, IP address, domain name (inclusive of both authoritative and recursive resolution), BGP/packet routing, and last-mile access by subscribers? Yes. SSL certificates, CDN, DDoS mitigation? Maybe not. Because they don’t prevent you from operating a public website, strictly speaking, and you could potentially build your own substitutes (maybe you couldn’t realistically build your own SSL/PKI because browsers might not trust your homegrown solution, but you don’t strictly need SSL to maintain a site).
It’s true that losing the latter resources might leave you with a 90s-ish website. That’s the sliding scale and marginalization I’m willing to live with (see Part IV): basic access to the internet but no guarantees when it comes to reach or usability. Others might disagree about which resources are truly essential, or they might have a more generous conception of the basic subsistence level that should be conceded to all websites.
That’s fine. My contribution was to offer viewpoint foreclosure as a limiting principle for how far private “content moderation” should be permitted to go before the law steps in (and implicitly to reject social media regulation because it doesn’t hit that tripwire). Others may come up with different conclusions about which resources fall on which side of the foreclosure line. For example, some might argue that funding is, for all intents and purposes, necessary to maintain a public website (even if it isn’t a true technical dependency). Or that even if a website is theoretically accessible, it won’t be long for the world if it can’t purchase DDoS protection services. They might therefore argue for additional rights of “monetization” and “security” (bringing the total to “seven internet rights,” I suppose). I don’t go that far, but I’m happy for others to use my theoretical framework to come up with different sets of fundamental internet rights. The main thing is the foreclosure line.
Second step: If a resource is fundamental, determine whether a deplatformed person has been disadvantaged in his access to that resource because of ideological animus. Suppose a provider charges you what you think is an unusually high price, provides a crappy service, or cuts ties with you altogether. How do you determine whether the provider is motivated by ideological animus vs. simply being greedy, running its service incompetently, or discarding an unprofitable customer? You would have to sue the provider and ultimately prove animus by a preponderance of evidence. That might sound difficult, but it’s no different from what litigants must do in other anti-discrimination regimes that allow private suits. An employee could be fired (or not hired) for countless reasons, some permissible, some impermissible. Same for a landlord who declines to rent to a prospective tenant or a college that rejects a particular applicant. Proving intent is hard, but litigants do it all the time.
This is where the five internet rights show their deontological stripes. If they were purely economic in nature (like net neutrality), they might require an unwieldy regulatory scheme—perhaps rate regulation. But they’re just another incarnation of anti-discrimination law, similar to Title II, Title VII, the federal Pregnancy Discrimination Act, etc.
That said, where there is true ideological deplatforming, the facts typically aren’t murky. When providers want to distance themselves from a controversial customer, they tend to terminate service altogether; they don’t simply increase the price or reduce service levels. There’s usually a very public pressure campaign that precedes the deplatforming, and the provider typically announces its decision to satisfy the campaigners. All these things help to illuminate intent.
Finally, these aren’t positive rights. They’re negative rights to the same extent that other anti-discrimination regimes establish negative rights against private parties. No one would have any positive right to commercial internet service, IP addresses, or domain names. She’d still have to come up with the cash to purchase each (just as a prospective tenant must have the necessary income to pay the advertised rent). The five internet rights only ensure that if you had the money for those resources, you couldn’t be denied them on account of ideological animus.
Also, I'm really worried about the scope of the notion of 'viewpoint foreclosure'. Looking at first amendment cases we see an amazing elasticity of this notion: if you don't like the content then the viewpoint isn't foreclosed provided they can stand in line for 6 hours to get approval to ask someone if they want to see the content. If you like the content it means 'makes it difficult to share'.
For instance, suppose I have to make my point w/o enough bandwidth for videos and fancy graphics. Is that foreclosure?
Here is a summarizing response comment. Nugent never quite convinced me that his sole interest is low-level internet infrastructure. I think he has his eye on social media too.
One of the greatest obstacles to sorting out current internet user vexations and dissatisfactions has been that too many people want to treat internet publishing as if it were a novel phenomenon, being experienced as a matter of first impression, as it were. Those folks want to tailor without constraint this supposedly new thing, into any form they can imagine.
Problem is, because there are so many different forms being imagined, not much progress gets made. Folks remain at cross purposes, while the vexations and dissatisfactions inflict ever-increasing costs on the public life of the nation.
That view is not only unproductive, it is mistaken. Only at the margins is internet publishing a new thing in the world. Mostly, it is in fact just old-fashioned publishing undergoing one of its periodic technical reformations. If everyone could keep that in mind, they would find that many problems which feel novel now in fact have extensive precedents, and customary solutions already well-known, and proved to work reliably. Those solutions are deeply rooted in the legal tradition developed over more than 2 centuries to defend 1A press freedom.
So my advice is that if you set out to invent whatever number of internet rights you think are needed, the first thing to do is to be sure none of them infringes, vitiates, or displaces 1A press freedom as it has been traditionally understood. The ability to go back to that after the novelty dust settles needs to be preserved.
In principle, I agree, but Kindle Direct Publishing and similar services constitute an upgrade to publishing.
In 1996 AOL, Prodigy, and CompuServe were examples of an ICS. They included "specifically a service or system that provides access to the Internet." They included email and other services. They were quasi-common carriers. Email is a common carriage service.
Xfinity and similar services include "specifically a service or system that provides access to the Internet." Such a service is an ICS.
A social medium platform is email with a niftier user interface. Neither Gmail, Facebook, X, LinkedIn etc include "specifically a service or system that provides access to the Internet." A social medium platform is not an ICS.
Like Gmail and other Email services, a social medium platform is a common carrier just as the FCC decided that ECOM was a common carrier in Federal Communications Commission [CC Docket No. 79-6; FCC 79-465] Electronic Computer Originated Mail (ECOM); Proceeding Terminated, Memorandum Opinion and Order, Federal Register, Vol. 44, No. 181, Monday, September 17, 1979, Notices, pp 53788-53800.
As Stephen Lathrop points, the technology has only been upgraded. The upgrade is in many ways quite minor.
A social media platform is not a common carrier, and is nothing at all like email. It serves a very different function in very a different way.
One logs into an email service or into a social medium platform and sees a number of alerts for available messages. The user may request to see the message, which is associated with the alert. The user may send a response to the message. Or the user may send his own message to be held in bailment at the backend server until a user requests to see it.
How does a social medium platform differ from email service?
The only difference is the user interface.
Function is not part of the definition of common carriage. Common carriers have many different functions.
Incorrect. Function is the core of what a common carrier is.
Carriage is at the core of common carriage, but not every carrier is a common carrier.
For more elaboration, see Frontier Broadcasting Co. v. Laramie Community TV Co., Memorandum Opinion and Order, 24 F.C.C. 251, 254, ¶ 7 (Apr. 2, 1958); see In re Amendment of Parts 2, 91, and 99 of the commission’s Rules Insofar as They Relate to the Industrial Radiolocation Service, Report and Order, 5 F.C.C.2d 197, ¶¶ 19-20 (Oct. 5, 1968) (“[T]he fundamental concept of a communications common carrier is that such a carrier makes a public offering to provide, for hire, facilities by wire or radio whereby all members of the public who choose to employ such facilities may communicate or transmit intelligence of their own design and choosing between points on the system of that carrier and between such points and points on the systems of other carriers connecting with it.”). See also Nat’l Ass’n of Regulatory Util. Comm’rs v. FCC (NARUC I), 525 F.2d 630, 641 (D.C. Cir.), cert. denied, 425 U.S. 992 (1976) (finding that the essential elements of common carriage to be (1) “that the carrier undertakes to carry for all people indifferently”); Nat’l Ass’n of Regulatory Utility Comm’rs v. FCC (NARUC II), 533 F.2d 601, 609 (D.C. Cir. 1976) (finding that a common carrier’s system is “such that customers ‘transmit intelligence of their own design and choosing.’”)
Once again for the kids that rode the short bus: the definition of an ICS is "any information service, system, or access software provider that provides or enables computer access by multiple users to a computer server," which of course gmail, Facebook, twitter, LinkedIn, etc., all do.
Such intellectual dishonesty.
Neither Gmail nor any social medium platform meets the definition of an ICS.
I don't know why they didn't define the Internet as "if you want to provide the inter part of internet, the transmission of other stuff, you can't discriminate."
Like a home owner agreement to keep your grass under 8 feet high, it isn't an issue. Join for profit, just transmit all who come your way.
I enjoyed the series overall and think that the overall conclusions (and Professor Nugent's take on the political valence at the end of this post) seem correct.
I will say, though, that the majority of this post is trying a bit too hard in some ways. Most notably, I think it is quite obvious that the LACNIC withdrawal of DDos-Guard's IP addresses was content neutral. The RIRs serve constituents actually located in their respective regions, and I've seen no evidence that DDos-Guard had anything other than a paper presence in Latin America. The fact that companies routinely use shell entities in other contexts does not detract from the fact that the RIRs expect their customers to actually be operating out of their regions. Rather than trying to promote the misleading idea that the RIRs actually engaged in content-based takedowns, it seems sufficient to acknowledge that pressure is being applied to these foundational intermediaries and that we may want to create a legal structure that would prevent them from making content-based decisions rather than simply relying on them continuing to operate the way they have in the past.
I do think it's true that domain registrars have dropped customers for content-based reasons, but as I noted earlier there's fairly robust competition in the domain name space. I'm less convinced that we need protections there than with, e.g., domain registries or root server operations, but that may be the only place where I might get to a different conclusion than Professor Nugent.
Great points, jb.
You’re right that there’s some heterogeneity in terms of how core intermediaries are involved in viewpoint foreclosure (or attempts at foreclosure). Some (e.g., registrars and some registries) are clearly motivated by ideological animus, some are more ambiguous, and some may be currently only subject to pressure to act for ideological reasons. I’d like to see evidence that DDoS-Guard violated LACNIC’s terms as written (granted that LACNIC currently owes no such duty to publicly explain itself). In any event, yours might have been a better/more nuanced articulation when it comes to RIRs.