Summary

  • Cade warned that “standard,” “guideline” and “mandate” can imply different authority across business, legal, governmental and IETF settings.
  • The minutes preserve her intervention and its limits: the Business Constituency still had to deliberate, and the record does not show that she determined the final wording.

The force hidden in a drafting verb

On 19 June 2010, an open meeting of the GNSO Operations Steering Committee was working through recommendations for how constituencies and stakeholder groups should operate. The discussion was not a theoretical debate over standards bodies. Members were trying to decide which practices should be common, which could remain adaptable, and how words such as “should,” “must” and “shall” would be read.

The committee chair described a compromise: some things should be standardized across groups, while other work should remain flexible. A change in the GNSO’s structure had also made the draft speak about stakeholder groups as well as constituencies. The meeting transcript records that context immediately before Marilyn Cade took the floor.

Cade identified herself as chair of the Business Constituency and made a boundary explicit: she was speaking from that perspective, and the matter would continue to be discussed within the BC. She then asked colleagues to distinguish “a standard versus a guideline versus a mandate.” Those terms, she said, could mean different things in business and legal settings, international government, or the IETF. Her preference was for wording that remained aspirational rather than dictating, because constituencies differed and future smaller constituencies could not yet be predicted.

That caveat about representation matters as much as the headline phrase. The transcript does not present Cade as speaking for every constituency, nor as having authority to settle the committee’s language. It shows a chair putting a concern into a shared drafting process while leaving room for her own constituency to deliberate.

Why the distinction had an operating cost

An organization can use a common baseline to make expectations legible. But when a recommendation is copied across groups that differ in size, membership, funding and administrative capacity, the same verb may impose unequal costs. A “must” can require a group to provide a function it cannot staff. A “should” may set a default yet leave a group room to explain why it cannot comply. A guideline can support consistency without claiming the same authority as a binding rule.

Cade connected that problem to work already underway inside the Business Constituency. The group had completed a membership brochure and was conducting outreach. She argued that a toolkit should give groups choices, even à la carte options, so each could adapt support to its own needs. Her example was volunteer capacity: members had day jobs, while producing membership materials and keeping a checking account amounted to a second, after-hours workload. A recommendation about participation that ignores the means to carry it out can demand more than its authors intend.

The meeting record therefore shows two linked questions. Who is the provision for? And what can that group actually do with it? If the answer is “all groups,” the text has to say whether the requirement is uniform, adaptable or optional, and who decides when an exception is justified.

A comment is not a decision

The minutes of the GNSO Council meeting on 8 December 2010 show that the Operations Steering Committee was still at work. The Council extended its term through the June 2011 ICANN meeting and asked its chairs to identify remaining targets and deadlines. The same minutes report that the Commercial Stakeholder Group had ratified a permanent charter submitted for Board consideration, while other groups were still revising theirs.

This is useful evidence of a process continuing after the June discussion. It does not establish that Cade’s intervention changed a particular sentence, that a mandate was removed, or that the Council adopted her preferred phrasing. During the meeting, the chair pointed participants toward the public-comment period as the next place to raise concerns. The strongest defensible claim is narrower: the distinction was raised in the open, while the recommendations and implementation work were still in motion.

Cade’s documented roles make the intervention intelligible without making it singular. ICANN’s 2005 biography describes her work at the intersection of technology and public policy, her leadership in the Commercial and Business Constituency, and her service on the GNSO Council and task forces. The Business Constituency’s charter history identifies her as chair for its January 2009 version, which aligned its text with GNSO restructuring. A later charter assigns amendment authority to members and an interpretation role to the Executive Committee.

That later document is not evidence of what Cade caused in 2010; it illustrates where internal rules acquire force: through an adopted procedure, a named decision-maker and an available appeal path.

The useful test is operational. A governance document should identify who must act, what support is available, who may adapt a provision, and where a dispute goes. Otherwise “aspirational” can become a promise without an owner, while “mandate” can become a burden without a clear source of authority. Cade’s contribution in this episode was to insist that the drafting team notice that difference before readers did.

Sources

Image identity references