Summary
- LACNIC's current process treats the open Public Policy List as the formal starting and ending point for policy discussion. Proposals that reach consensus move to a four-week last call, after which chairs determine whether consensus is maintained before Board ratification.
- LACNIC describes last call as a final opportunity, especially for people who did not participate earlier. Editorial comments are permitted; an exceptional substantive objection may be raised when it identifies an aspect not considered before the earlier determination.
- The last call should test the resilience of an affirmative prior record: exact text, known objections, chair reasoning and evidence of support. It should not create consensus through silence. No response is compatible with agreement, but also with fatigue, low notice, language barriers, perceived futility and rational delegation.
- Historical rules used a different sequence, including a 45-day post-forum comment period before Board action. Changes in duration and venue demonstrate that last call is an institutional design choice, not an inherent technical fact.
- Chairs should publish delivery and participation evidence: channels used, language availability, independent organisations responding, new readers, known objectors' status, material comments and the reason each did or did not disturb consensus.
- A quiet period can legitimately permit progression when the earlier consensus was well supported and the final text is faithful. The defensible conclusion is “no new substantial objection displaced the prior finding,” not “silence proved that the region agreed.”
Last call comes after a decision, not before one
The timing of last call determines its meaning. In LACNIC's current Policy Development Process, public discussion occurs on an open Policy List, chairs determine whether consensus has been reached after the discussion period, and a successful proposal enters a four-week last call. Within a week after that period, chairs confirm whether consensus is maintained or decide with the authors whether an updated version should return to discussion.
This is not a blank referendum. The proposal arrives with a history: a stated problem, published text, weeks of discussion, chair assessment and a prior consensus finding. Last call exposes that finding to another interval of scrutiny. It asks whether the decision remains safe after people have seen the text and had a final chance to identify something missed.
That sequence gives silence a limited role. If nobody raises a new substantial concern, the prior decision may stand. The institution does not need every earlier supporter to repeat a position. Requiring affirmative reconfirmation from all contributors would reward those with time to post twice and could trap policy in endless revalidation.
But a quiet final period cannot supply evidence that the prior decision lacked. If the original discussion involved few independent organisations, left known objections unanswered or did not expose the final words, a silent last call does not cure those defects. It can fail to reveal another problem; it cannot retroactively broaden the constituency.
The correct logic is conservative. Last call tests whether a justified finding has been displaced. It does not infer a new mandate from absence. That distinction should appear in every chair announcement because the words “consensus maintained” can otherwise sound as though silence itself voted.
LACNIC gives silence a defined procedural setting
The current rules do more than set a duration. They describe the Public Policy List as open and as the formal starting and ending point for policy discussions. They assign chairs duties to announce results within defined periods. They require a new last call when editorial changes produce a new version. They allow an exceptional objection if an aspect appears that was not considered before consensus.
These features make the quiet period more accountable than an informal “speak now” message. Entities know the authoritative channel. A proposal cannot drift from meeting agreement into implementation without another public step. Text changes trigger renewed exposure. Chairs must make a subsequent determination rather than treating the calendar's end as automatic approval.
The design also signals that not every disagreement should restart the process. Last call is not an invitation to repeat every earlier position. Its focus is fidelity and omission: does the final text retain what reached consensus, and has someone found a material aspect the prior discussion did not address? This protects closure while preserving a route for genuine late discovery.
The challenge is evidentiary. Chairs still decide whether a comment is editorial, whether an objection is new, whether it is technically substantiated and whether consensus remains. If the public record states only “no objections” or “consensus maintained,” readers cannot inspect those judgments.
LACNIC's structure is therefore sound but incomplete without a decision record. The existence of an open list and four-week period demonstrates opportunity. Legitimacy also requires showing what evidence arrived, what was already decided and why the final conclusion followed.
Silence has several incompatible meanings
A person who does not post during last call may support the proposal. They may trust the entities who developed it. They may consider their earlier comment sufficient. They may lack time to review another version. They may not have received the notice, or may receive it in a language or format that raises the cost of response. They may believe that chairs will dismiss renewed objection as repetition. They may have no settled view.
These states cannot be distinguished from the list's empty space. Silence is observationally identical across motives. Assigning it one meaning is therefore an inference, not a fact. The inference becomes especially weak when the institution does not know how many people received, opened or understood the call.
This does not make silence useless. In a process with affirmative prior support, faithful text and resolved objections, absence of a new issue is relevant. It indicates that the review channel did not surface a defect during the allotted time. That is a negative finding about the record, not a positive finding about every non-entity's preference.
Governance language should respect the difference. “No new substantial objection was submitted” is precise. “The community supported the proposal in last call” is too strong unless entities affirmatively did so. “Consensus was maintained” can be valid if it points back to the earlier evidence and explains why final comments did not undermine it.
The silence problem is not unique to LACNIC. It appears in standards bodies, association consultations and board notices. LACNIC's clearly defined last-call stage makes it possible to confront the problem directly rather than letting unspoken assumptions hide inside a generic consensus label.
The prior consensus must carry the weight
Because last call cannot manufacture support, the quality of the prior consensus is decisive. Chairs should enter the period with a record of the exact proposal, entity population, major arguments, substantial objections, text changes and reasoning behind the determination. The last call then tests that record against new readers and a stabilised text.
If prior support was broad across independent organisations and the chair explained why objections were resolved, a quiet period can reasonably leave the finding intact. If support came from a small circle but the technical evidence was strong, chairs can also proceed, provided they are candid about limited breadth and show targeted notice to affected groups.
If the earlier record is thin, last call should not be asked to save it. The remedy is more discussion, outreach or clarification before the consensus call. Waiting four weeks for objections from people who never understood the proposal is not equivalent to engaging them.
This allocation of evidentiary burden disciplines both sides. Proponents cannot claim that non-response enlarged their coalition. Objectors cannot demand that every supporter speak again. Chairs must rely on reasons already established and remain open to a genuinely new concern.
The determination after last call should therefore cite the original finding. It should say what evidence established consensus, what changed in the final text, who commented during the final period, whether known objectors participated, and why each new point did or did not affect the result. Silence occupies one line in that explanation, not the whole conclusion.
An open list is not a measured constituency
LACNIC's Policy List is open, which is an important guarantee. Anyone able to subscribe can observe and participate. Openness reduces the risk that policy is developed only among members, staff or meeting attendees. It allows technical expertise and affected experience to enter from across the region.
An open list still selects for attention, language, professional familiarity and time. Network policy may be central to a registry employee and peripheral to an operator whose staff member manages addresses among many duties. A small provider may understand the consequence only when implementation reaches it. People who do not already know LACNIC's stages may not recognise a last-call announcement as a final opportunity.
Subscriber count does not solve the problem. Lists contain inactive addresses, multiple subscriptions, staff accounts and people following only selected threads. Delivery proves that a message reached a server, not that a person read or understood it. An open channel is a procedural condition, not a representative sample.
The institution should therefore avoid claims such as “the entire community had the chance” unless it explains the channels and audience. Better language says that notice was published to the Policy List, website, members and relevant outreach channels in specified languages. This lets readers assess reach.
Formal openness remains valuable even when participation is uneven. It prevents exclusion by rule and preserves a public record. Effective legitimacy adds targeted notice and evidence of independent response, particularly when a proposal concentrates costs on a group unlikely to follow the list routinely.
The region's languages affect usable time
LACNIC serves a region in which Spanish and Portuguese are central, with English and other languages relevant to particular communities. Language affects whether four weeks are four usable weeks. A proposal available first or most clearly in one language gives that audience more time and lower interpretive cost.
Technical terms can be difficult even for fluent readers. A translation must preserve definitions, obligations and exceptions, not merely the general objective. If versions diverge, entities may comment on different propositions. Chairs should identify the authoritative text while ensuring materially equivalent explanations appear together.
Last-call notices should state what changed since the consensus finding in each working language. A reader should not need to compare long texts manually to discover a new condition. Where a translation is delayed, the period should run from availability of the complete set or the deadline should be extended for the affected audience.
Language also shapes public reasoning. A entity may be able to understand a proposal but reluctant to draft a technically substantiated objection in a second language. Chairs can permit comments in supported languages and ensure that summaries travel across them. A concern should not lose weight because it requires translation.
Silence is particularly weak evidence when language delivery is not reported. The institution cannot infer agreement from an audience that received less usable time or an incomplete explanation. Equal elapsed time is not equivalent opportunity.
LACNIC's regional identity gives it a reason to lead on this issue. Last call can be a genuine second look only if the people invited to look receive the same policy in time to act.
Historical design shows that last call is adjustable
An earlier LACNIC Policy Development Process used a different sequence. Version 3 described proposals reaching consensus at the Public Policy Forum and then being published to the Policy List for 45 days of comments before Board consideration. Chairs had duties to issue the call, report results and communicate the Board's ratification. The modern design uses an eight-week list discussion and a four-week last call with chairs confirming whether consensus remains.
The comparison matters because it removes any suggestion that last call has one natural duration or institutional meaning. LACNIC has adjusted the relationship among list, forum, chairs and Board as participation practices changed. The current arrangement places more explicit responsibility on chairs to determine consensus around list discussion rather than relying only on a meeting event.
A 45-day period is not necessarily more legitimate than four weeks. The earlier process may have offered more elapsed time but less clearly defined treatment of new objections. The current process may provide stronger structure and a cleaner restart rule for changed text. Design should be assessed through actual reach, response and correction, not the largest number of days.
Historical comparison also suggests useful evaluation. Did shortening or restructuring last call change participation? Are more independent organisations commenting? Do late objections more often identify issues genuinely missed? How frequently do editorial changes restart the period? How long does Board ratification take after chairs confirm consensus?
An institution that has changed the stage before can change it again. The right standard is whether the final interval gives new readers a real chance, preserves prior deliberation and produces a reasoned transition to ratification.
New readers are the point, but hard to observe
LACNIC explicitly describes last call as an opportunity especially for people who did not participate earlier. This is a crucial justification. Regular entities may share assumptions, and a fresh reader can detect ambiguity or impact that months of debate normalised.
Yet the institution rarely knows who is genuinely new. A first message on the thread may come from a long-time silent reader. A familiar contributor may bring a colleague's concern. Someone who joined the list during last call may never post. Public evidence can identify new speakers, not every new reader.
Chairs can improve the measure through the notice itself. Invite commenters to state whether they participated earlier and which stakeholder experience informs the concern. This should remain optional; no one should have to disclose unnecessary identity. Aggregate reporting can then say how many final-period comments came from first-time contributors or organisations absent from the main discussion.
Targeted outreach can deliberately create new readership. If a proposal affects national Internet registries, small ISPs, content networks or legacy holders, send a concise notice to those groups and record the channels. The point is not to secure endorsements. It is to expose the decision to experience that may be missing.
A last call containing only repeated comments from the same core group can still confirm text fidelity, but it has not strongly performed the new-reader function. The final determination should say so rather than treating every quiet or familiar response as equivalent evidence.
Editorial change is not always small in effect
The current process permits editorial comments during last call and requires a new version and restarted period when editorial changes are made. This rule recognises that the public must review the actual text, not a memory of the forum's intent.
The boundary between editorial and substantive change can be difficult. Moving a comma, replacing “may” with “shall,” changing a defined term or reordering an exception may alter obligations. A translation correction can expose ambiguity in the authoritative text. Even a stylistic simplification can remove a qualification entities relied on.
Chairs and authors should publish a marked comparison and classification for every change. If any entity reasonably argues that meaning changed, the safest response is to restart substantive discussion rather than defend a narrow editorial label. The cost of another period must be balanced against the risk of implementing words that lacked review.
Not every typo requires a full reset. A transparent rule can distinguish corrections that do not affect meaning from edits that change interpretation. The decision and rationale should be public. Text should remain frozen during the final determination so another change does not occur after the review closes.
Silence is particularly unreliable if entities cannot see what changed. A clean replacement page without a comparison imposes the full reading cost again. Some readers will assume continuity and remain quiet. The institution should make attention efficient if it wants non-response to carry even limited evidentiary value.
A late objection should face a clear test
LACNIC allows an exceptional objection during last call when it identifies an aspect not considered before consensus. This balances closure and learning. It prevents the final period from becoming a complete replay while recognising that a material defect can surface late.
The test should ask four questions. Is the issue substantively new rather than a restatement? Could a reasonable entity have identified it from the earlier text? Does it concern technical soundness, fairness, feasibility or another relevant policy principle? What evidence supports the predicted consequence? A concern can be new even if the underlying subject appeared earlier, where the final wording creates a different effect.
Chairs should summarise the objection in its strongest form and invite response. They should not dismiss it merely because one sentence resembles an old thread. Nor should they allow an objector to restart the process by changing labels around an answered claim. A public disposition should identify the prior discussion or explain why new review is required.
Timing matters. An objection submitted on the final day may need analysis beyond the one-week determination window. Chairs should have authority to extend review with reasons. Speed should not force a choice between ignoring a serious issue and announcing uncertainty.
The outcome can be maintained consensus, editorial correction, revised text and restarted last call, or return to the eight-week discussion stage. Each reflects a different finding. Publishing the path teaches entities what counts as useful late evidence and reduces strategic posting.
Known objectors are valuable confirmation evidence
When a proposal enters last call after chairs conclude that objections were resolved or did not prevent consensus, the status of known objectors is informative. Did they acknowledge that revised text addressed the concern? Did they remain opposed on the same grounds? Did they disengage? The answer should be recorded where available.
An objector is not required to bless the result. Rough consensus can exist with continuing dissent. But a direct confirmation that the principal technical concern was cured is stronger than silence. Continued opposition with an answer from chairs is also stronger than pretending no objection exists.
Institutions should avoid privately soliciting withdrawal in exchange for progression. Contact should be public or transparently summarised, and the objector should control whether their personal response is attributed. The purpose is to check understanding, not negotiate legitimacy behind the list.
If known objectors do not respond during last call, chairs should not infer concession. They can say the prior disposition remains and no new evidence was submitted. This protects closure without rewriting silence as agreement.
Tracking objections across versions also prevents a common error: treating the same unresolved concern as new each time or, conversely, assuming a wording change solved it without asking. A concise objection table can show text response and chair conclusion.
Last call is strongest when it verifies that the community's hardest questions travelled into the final text. Known objectors provide one test of that journey, but their assent is neither necessary nor safely inferred.
Independent responses matter more than volume
One active entity can generate a long thread during last call. Ten short messages may come from employees of the same organisation. Raw volume can make a period look vibrant without broadening the evidence. Chairs should count independent organisations and roles alongside messages.
Affiliation is not always clear. People may speak personally, consult for several companies or use addresses unrelated to their current employer. Reporting should preserve uncertainty and avoid attributing a personal view as formal organisational policy. The objective is a reasonable concentration measure, not a legal roll of representatives.
Independent response matters because last call is intended to expose the proposal beyond its development core. A comment from a national registry, small provider or network in a previously absent country may add experience even if it supports the outcome. Affirmative support from ten distinct organisations is different from ten replies inside one institutional circle.
Reasons still outweigh arithmetic. One substantiated compatibility defect can require return despite broad support. A hundred “looks good” messages do not cure it. Counts show reach; dispositions show deliberative quality. Both belong in the final report.
The report can remain concise: number of comments, unique individuals, estimated independent organisations, new organisations relative to discussion, countries or economies represented where reliable, and substantive issues raised. Staff and chair messages should be separated from community responses.
This evidence would make a quiet period interpretable. Zero responses after broad targeted notice means something different from zero responses on a low-traffic list with no outreach, though neither proves assent.
Rational delegation is not a democratic defect
Many operators cannot follow every registry proposal. They rely on experienced entities, trade associations, national registries or LACNIC staff to identify consequential issues. This rational delegation explains why low response need not indicate apathy or exclusion. A specialised policy community can make sound decisions without mass participation in every final period.
The institution should recognise delegation without claiming mandates that were never granted. A frequent contributor may be trusted informally by peers but does not automatically represent them. A national registry may carry local operational experience without speaking for every member. Chairs can credit expertise and breadth while avoiding inflated constituency claims.
Last call supports rational delegation by creating a predictable checkpoint. Intermediaries can alert their communities when a final text contains a concern. Most proposals may pass quietly because trusted observers found no reason to mobilise. This is an efficient form of attention allocation.
Its legitimacy depends on information reaching those observers and on their ability to reopen the issue. If last call is treated as ceremonial, intermediaries stop investing in review. If every late concern restarts months of debate, entities may use the stage strategically. The procedural test must be credible in both directions.
Silence under rational delegation therefore means only that the monitoring network did not produce an objection. It can strengthen confidence where monitors are diverse and the prior process was sound. It cannot be described as individual approval by all who delegated attention informally.
Fatigue can look like agreement
Long policy discussions consume volunteer energy. Entities explain the same concern across versions, meetings and language threads. By last call, even people with unresolved reservations may believe another post will not change the chair's view. Proponents may also remain silent because they assume success. The resulting quiet can reflect exhaustion more than convergence.
Fatigue is difficult to measure, but several signals help. Count how many contributors from the main discussion remain active. Record repeated versions and time elapsed. Survey entities after major proposals about whether they understood the final status and believed further comment could matter. Examine whether late periods routinely attract no response regardless of controversy.
Process design can reduce fatigue. Maintain a clear change log and objection table so contributors do not restate history. Ask focused questions rather than reposting an entire proposal. Enforce decisions against repetitive claims while remaining open to new evidence. Publish chair reasoning promptly so entities know their contribution was considered.
The risk is not that every tired entity must be re-engaged. It is that the institution interprets their withdrawal as endorsement. A final report can say that no new comments were received after extensive prior debate and that known objections were previously answered. That is honest and sufficient where the record supports progression.
Fatigue also argues for periodic review after implementation. A policy that passed through exhausted silence can be tested against outcomes without reopening every historical argument. Learning reduces the stakes of final call by showing that adoption is not irreversible.
Perceived futility can suppress the best objections
People speak when they believe a forum will engage their reason. If chairs have already announced consensus and last call is described as final, a entity may assume that only typographical comments are welcome. LACNIC's exceptional-objection rule permits more, but the notice must communicate that route clearly.
The chair's treatment of past objections shapes future behaviour. Dismissive summaries, unexplained findings or long delays signal futility. Careful restatement and disposition encourage even losing entities to remain. Legitimacy is not measured by whether everyone wins; it is measured partly by whether a entity can recognise their argument in the decision.
Last-call notices should state that a new, substantiated issue can affect progression and explain how chairs will evaluate it. Examples can distinguish a previously answered preference from a newly discovered interoperability problem. The final report should show that this promise was real.
An appeal route is also important. LACNIC permits challenges where entities believe chairs violated the process or erred in judgment, with Board consideration under the published rules. Appeal should not replace last-call engagement, but its availability constrains futility by making chair power reviewable.
Low response cannot demonstrate futility, just as it cannot demonstrate assent. The institution must look at entity experience and the quality of prior dispositions. A quiet process trusted by contributors is efficient. A quiet process viewed as predetermined is brittle. Public reasons are the main evidence separating them.
Board ratification should not borrow silence as a mandate
After chairs confirm maintained consensus, the proposal moves toward LACNIC Board ratification. The Board should receive the full deliberative record: exact text, consensus determination, last-call notice, responses, unresolved dissent, appeals and implementation assessment. Its role is not simply to observe that a deadline passed.
Ratification connects community policy to the organisation responsible for execution. The Board can check process, legal duty and institutional feasibility. It should not claim that a quiet final period gives it a regional political mandate. The authority is narrower: the published community process produced a policy judgment that survived final review.
If the Board finds a material defect, it should return the proposal with reasons. Private modification would break the connection between the text reviewed in last call and the text implemented. If ratification is delayed, the community should know why and whether the policy remains in force as a pending decision.
Board minutes should identify the version and record recusals or material concerns. A bare approval entry may satisfy corporate form but does not show that trustees reviewed the evidence. The stronger the claim attached to community consensus, the more important that trace becomes.
Ratification can strengthen legitimacy by ensuring that no single set of chairs converts silence into policy alone. It weakens legitimacy if the Board uses “community consensus” as a shield while ignoring a poor record. Separate institutions must perform separate judgments.
Last call needs delivery evidence
A defensible final period should begin with a delivery report. List the authoritative page, Policy List message, member notice, social or event channels, languages, publication time and closing time. Identify any delivery failure and extension. This is ordinary administrative evidence, not a surveillance programme.
Where possible, report aggregate delivery and access measures carefully. Email delivery rates and page views can show reach but not understanding or agreement. They should never be converted into votes. Their value is diagnostic: a broken notice or unexpectedly low access may justify renewed communication.
Targeted channels should reflect the proposal. A change affecting transfers may warrant notice to organisations that transfer resources and relevant legal or operational contacts. A routing-security proposal may require network-security communities. Targeting is consultation, not special veto.
The notice itself should be usable. State the problem, exact decision, material changes, known unresolved concerns, what comments are permitted, how to submit, languages accepted and what happens after close. Link to a comparison, not only a clean text.
If no one replies after this effort, chairs can confidently say the review opportunity was real. They still cannot say every recipient agreed. The distinction protects accuracy without paralysing decision.
Chairs need a maintained-consensus statement
Within the period specified after last call, chairs should publish a structured maintained-consensus statement. It should identify the proposal version, original determination date, last-call dates, channels and languages, participation, comments, dispositions, text changes, appeal status and conclusion.
The reasoning should follow a simple standard. First, restate the affirmative evidence supporting consensus before last call. Second, confirm that the final text faithfully expressed that decision. Third, assess whether any final-period comment introduced a substantial unconsidered issue. Fourth, explain why consensus remains or why discussion restarts.
Where no comments arrived, the statement should not be empty. It can say that the earlier record remained controlling, no new issue was submitted through the public channel and no text change occurred. If outreach was limited, acknowledge it. If known objectors remained silent, do not claim withdrawal.
Where comments were affirmative, distinguish endorsement from editorial help. Where objections were repeated, link to the prior disposition. Where a new issue was raised but judged limited public evidence, explain the evidence. This gives an appeal body something concrete to review.
The statement turns last call from a calendar event into a reasoned decision. It also gives the Board and future entities a compact account of what the stage accomplished. The effort is small compared with the authority the conclusion carries.
A response-rate audit should be longitudinal
One proposal cannot show whether LACNIC's last call works. The institution should examine several years of periods using consistent measures: proposal subject, discussion participation, last-call duration, notice channels, unique responders, independent organisations, first-time contributors, comment type, restarts, appeals and Board outcomes.
Patterns would reveal whether silence is normal or topic-specific. If nearly every last call receives no comment, the stage may function mainly as a notice safeguard. That can still be valuable, but the institution should stop describing it as broad confirmation. If high-impact proposals attract new organisations, targeted attention may be working.
The audit should compare the earlier 45-day design where records permit. Did longer periods produce more independent response? Did moving the main decision emphasis from forum to list change who participated? Were substantive late objections more or less frequent? Historical evidence can guide design better than assumptions about ideal duration.
Quality matters alongside rate. One new technical objection that prevents a harmful policy may justify years of quiet periods. A flood of simple endorsements may add little. The audit should code consequences and chair dispositions, not reward volume.
Results should lead to experiments: clearer notices, multilingual change summaries, direct member alerts, targeted sector outreach or adjusted timing. Publish what changed and evaluate again. Last call should be treated as an institution capable of learning.
Silence can permit closure without authorising overclaim
Policy systems need closure. LACNIC cannot require affirmative response from a large share of the service region before every policy proceeds. Such a quorum would entrench current rules and give disengagement a veto. The final period must be able to close quietly.
Closure is defensible when five conditions hold. The prior consensus rests on reasoned evidence. The exact final text is public and faithful. Notice is broad and usable. Known substantial objections have dispositions. No new substantial concern emerges. Under those conditions, chairs may confirm maintained consensus even if last call attracts no message.
What they may not do is inflate the result. The conclusion does not prove universal agreement, representative turnout or a regional mandate beyond the policy process. It proves that an authorised open deliberation reached a finding that survived a defined final review.
This modest language is not a weakness. It makes the decision easier to defend. Critics can challenge a specific condition—perhaps notice failed or a new issue was dismissed—rather than argue against a fictional claim that everyone agreed. Supporters can point to the complete record rather than the mystery of silence.
The difference between closure and overclaim is one sentence: “No new substantial objection displaced the prior consensus” rather than “The community approved through silence.” LACNIC's rules are well suited to the first formulation.
The final opportunity should produce evidence of its own
Last call is often justified as insurance. Most periods will end without a dramatic discovery, just as most safety checks find no fault. The absence of an objection does not make the check pointless. It shows that a defined channel remained open while the final text was visible.
Insurance still requires records. A fire door is not proven by saying no fire occurred; it is inspected for access and operation. Similarly, last call should preserve notice, duration, text, responses and chair determination. This evidence shows that the opportunity existed in practice.
The check can also improve policy without reopening substance. Editorial comments clarify language. A new reader may spot an inconsistent reference. A national registry may confirm operational compatibility. Affirmative comments can reveal that constituencies absent earlier have now examined the text. These outcomes deserve reporting.
The institution should resist treating a silent period as administratively empty. Even zero is a finding when connected to a known invitation and prior record. The public report turns that finding into accountable evidence. Without it, later readers see only dates and a status change.
Last call's value is therefore both preventive and documentary. It gives a final route for correction and creates a boundary after which the Board can act. The better the record, the less pressure there is to assign silence a meaning it cannot carry.
From silence to a defensible decision
LACNIC's final comment design contains the right constitutional intuition. Consensus reached during active discussion should not move directly into corporate ratification. The exact text should remain exposed, new readers should have a chance to identify an omission, and chairs should confirm that the decision still holds.
The problem is not silence itself. Quiet is compatible with an efficient, trusted specialised community. The problem is using quiet as evidence of preferences that were never expressed. A last-call archive records speech; it does not read minds.
The solution is to relocate the burden. Prior deliberation establishes consensus. Last call tests text fidelity, notice and newly discovered objections. Chairs publish delivery and response evidence, count independent organisations where possible, preserve known dissent and explain the maintained-consensus judgment. The Board reviews that record before ratification. Appeals remain available for procedural or judgment error.
Historical variation shows that LACNIC can adjust the stage. Its earlier 45-day post-forum period and current four-week model are institutional choices. Future changes should follow evidence about participation, language, response quality and correction—not a belief that longer silence equals stronger support.
A mature policy community can close a quiet last call confidently if it says exactly what the quiet did and did not establish. It did not show that every operator agreed. It showed that a published proposal, already supported through the authorised process, remained unshaken by another open review. That is a narrower claim, but it is the claim the evidence can bear.

