No Such Weblog

The GNSO secretariat points to some updated travel information for participants in ICANN's Carthage meetings at http://www.icanncarthage.tn/.

Twomey talking about redelegation of ccTLDs. He emphasizes the importance of having documentation that supports a redelegation request. Notes that redelegation is not just a local issue, but might also affect global interoperability. Emphasizes the need for being extremely conservative with regard to redelegation; characterizes US DoC involvement as fail-safe mechanism, not actual exercise of influence over substance of redelegation decisions.

ICANN has hired its new Vice President, Supporting Organization and Committee Support. That Vice President will operate out of ICANN's new office in Brussels.

Not only is WSIS one of the more important topics of hallway talk -- in a touch of irony, the WSIS logo is featured on the materials distributed at the meeting by the local organizers.

Steve Crocker kicks off the wildcard session in Tunis.

About SECSAC. Evolution of events. Change to registry; redirection of unassigned names to SiteFinder server. SECSAC meetings in DC. Still gathering public input by e-mail. Emphasizes that Sitefinder was change to existing protocols, as opposed to introduction of new protocol (like WWW). Defensive action: Changes to undo the change. Change and counterchange. Has not escalated.

Registries, registrars, registrants -- explains registration system structure. Name resolution; explain mechanism. What happens when name exists, what happens when name doesn't exist? Explain wildcard situation. Broad areas of concern: Abruptness; right thing? competition; lots more. Initial SECSAC advisory: Verisign -- please roll back; tech community -- clarify specs; ICANN -- clarify procedures.

Overview of 10/7 DC meeting. Presentations available on the net. Follow-up meeting on 10/15. Ben Edelman etc.

SECSAC has not yet finished its work; still very interested in receiving comments. Scope of SECSAC work. Will produce report, will then step back and be part of the audience.

Clarification: There is no wildcard in .name. Talk about the non-delegation patch to BIND and its impact on .name. Feature to rewrite authoritative DNS answers containing non-delegation records. 15000+ downloads. Quite a bit more now. Used incorrectly, changes fundamental hierarchy of DNS system. For .name, patch will rewrite valid authoritative MX records returned from registry. root-delegation-only needs explicit list of TLDs that are allowed to return non-delegation records. Explains .name structure. Impact of rewrite: E-Mail to @*.name bounces.

Innovation needs stable basis. New internet services don't interfere with old ones, so no need for expensive and tedious approval process. Important for new applications that infrastructure -- including naming system -- behave predictably.

Easy to write new network applications. Don't have to special-case by TLD when writing software. Keeping tables of TLD behavior is a bad thing and brings you into trouble. host table analogy. Nobody updated them. Idiosyncratic features return us to host table situation.

Impact on users. Attention to backwards compatibility. Let old applications see old behaviour. Don't force old applications to upgrade. Upgrades don't happen. One of the things that killed OSI was need for gatewaying between different versions of X.400. We don't do that on the Internet, that's why we are here.

Example: IDN. DNS spec permits any binary string. Applications told that it's not a good idea. Applications expect letter-digit-hyphen. To old applications, IDNs look like meaningless domain names. Hard problem: Internationalized e-mail. Internationalized addresses: Last step, hard.

Alternative ways to do typo-fixing service. DNS Internationalization in practice. Some letters look like other letters. Have unregistered reserved name -- not possible with wildcards.

Network incredibly robust against many types of nonsense. Robustness depends on stability and predictability. Practical stability, not some lawyer reading contract, finding something defined, and concluding defined = permitted.

Robustness principle.

Wildcards: MX wildcards important when bringing countries with poor communications infrastructure to Internet -- let wildcard MX point to gateway, have gateway convert to legacy protocols. Wildcard then defined generically, but known from the beginning to be harmful when applied across protocols. MX only affects one protocol.

Joost Zuurbier relatively briefly describes what .tk (Tokelau) does with wildcards: Wildcard A points to URL forwarders; wildcard MX points to centralized e-mail forwarding server.

.tw: Using wildcards for IDN support. Plugins.

My presentation is here.

About EPIC. "Where do you want your data to go today?" Impact on privacy tools. Privacy law.

Privacy Issues with Wildcard. Data use -- Techniques -- Laws. E-Mail session. Omniture partnership. Omniture as privacy issue. Looks like doubleclick. No indication to user that data is sent to Omniture; cookie with 5 years lifetime. Information gathered by omniture from wildcard.

OECD privacy principles. Try to apply to service as offered by Verisign. Purpose specification principle. Collection limitation principle. Use limitation principle. Openness. Make known to users what is happening to their information. Ability for community to participate in decision-making.

Core legal question -- is it legal? Interesting question. Maybe it is legal. Consent, lots of notice, learn typing! Maybe it is not legal. Go to classical communications: Have to keep them confidential, either deliver as intended, or return. Essential problem from privacy perspective: Not giving information to person originating communication on where communication ends up.

Privacy issues in various categories. Keep in mind while developing policy for wildcard DNS.

Vittorio Bertola: Many don't speak English. Many aren't even able to deal with latin scripts. Not everything that's technically allowable should be practically done. Users like it? Correct architecture? Build wildcard in competition-friendly way? Controlled innovation? No. But only by respecting competitive environment. Long-term point. Most unpleasant thing see parts of community fight; fragmentation. IP-addresses hardwired. Protocols agnostic. Collateral damage such as effect on .name worrisome for future of Internet.

Nobody else speaks up.

Sebastian Bachollet speaks to the registrars' meeting. Has given presentations to different constituencies. Conducting interviews. 7 new gTLDs. 6 launched, .pro in the middle of the river. Address 12 questions; priority questions set up by NTEPPTF. Evaluation team: Summit Strategies Intl. (Miriam Sapiro); Solucom (?; Michel Briche); Bachollet supervising. Goal: Draft evaluation report at middle January / end January. Draft to TEAC (TLD Evaluation Advisory Committee); final report to TEAC around Rome meeting. Rough overview of questions. For some questions, input from registrars needed since they were between end customers and registry. Would like input about process with different new gTLDs. Difficulties faced? Technologies used by registries? Initial trademark protection? Startup issues? Implementation of registration restrictions? WHOIS and how it was implemented? Competition -- how did new gTLD change market, if at all? Effect on scope and competitiveness of domain name market? Effect on existing TLDs and registrants? Service continuity? Legal framework?

If anyone wants to be interviewed, please contact Bachollet.

Question: Evaluation process further delaying new gTLDs? SB: Question to board, can't answer that. Dan Halloran points out formal deadline from MoU -- September 2004.

Bachollet asks that r'ar constituency identify a small, but diverse set of registrars that might serve as interview partners.

Bruce Tonkin: Twomey response to sitefinder -- no documented procedure for dealing with new services. Special meeting of council. policy-development process; issues report requested by council. During meeting, Twomey and Jeffreys read letter that clarifies scope. Subtle wording.

Not just registry services as defined in contracts -- also other services that could have impact on internet stability. Not purely looking at registry services.

Other issue towards end of letter: Industry participants might be concerned because of competition issues. In end of Twomey letter, indicated that ICANN should seek external advice from competition authorities.

Barbara Roseman in charge of preparing issues report. Questions?

Elana Broitman: GNSO to look at definition of service or process? Tonkin: Early discussions with ICANN GC. Want to get away from what a service is, but rather look at impact and effect.

...

Process not about determining good service or not, but about impact on security and stability. GNSO developing process that staff applies on case-by-case basis. Q: Meet 15 January deadline? BT: probably not. But shouldn't take a year either. Miss 15 january by bit, not much. Q: Look at old requests? BT: Question to board, not to GNSO Council.

Barbara Roseman joins the meeting. Bruce Tonkin points out Twomey's broadly-worded core question. Barbara. Have talked to comm. user constituencies; will let GC figure out what's in scope for ICANN. Will go to outside entity asking about competition/confidentiality aspects; expertise available to GNSO.

Should new services or significant changes be reviewed before or after introduction?
Contract changes re stabililty/security?
Dominant vs. non-dominant registries? Comm. users had asked about differentiation between sponsored/non-sponsored?
Who should initiate process? Registry? Notification to ICANN, ICANN initiates? GNSO initiates? External party?
Desire to have definition of services provided?
Comm. users requested briefing what contracts say today.
Discussion ofo time frames? What time scales?
Involve other advisory bodies/SOs? Considerations from these overriding?
Concern about time frame for this PDP.
Time frame concerns?

Additional input from registrars?

Check or review for determination that something is registry service?
Review of anti-trust implications? Roseman: ICANN intends to make experts available.

Issues report will be posted CoB Friday, California time.

Add. questions: What's time table when service is not considered as registry service? "Registry service" covered by contract. But for non-registry service change, no contract requirement. Review of stability implications after the fact?

Tonkin: Add that issues report is starting point, not end point.

...

Suggestions to Barbara welcome, done by Friday.

John Klensin points out that whois data in strange languages may quite well kill port 43 whois, and notes that that protocol has outlived its useful life. Some panel discussion about what languages should be where, and about experience in China.

I was on the data element review panel of today's WHOIS Workshop. Unfortunately, that panel was chartered to look at things from a data user point of view only, without space for the data subject perspective.

The brief summary is that the usual statements were made.

The slightly longer summary: Bruce Tonkin reported about the current data element situation. Jane Mutimear gave the IP perspective, recycling some slides from the Montreal workshop. Marilyn Cade told a story about an abuse case. David Maher noted that registries don't need personal WHOIS information. I complained a bit about the lack of registrant perspective, pointed to the ALAC's new WHOIS statement, and noted that individual Internet users really don't have essential WHOIS uses, and that existing uses can easily be covered by some kind of person directory where information is entered voluntarily. Tom Keller noted that registrar mostly need WHOIS for transfers. Brian Cute confirmed that, and gave some customer quotes on WHOIS privacy.

The NCUC's Kathy Kleiman made the case for registrant privacy, and suggested that a technical contact should essentially be the only thing published in the WHOIS; this technical contact could then be someone at an ISP, not the individual itself.

We're two almost three hours into the GNSO Council session now. After long debate, the GNSO Council has adopted moderately updated versions of the Terms of Reference that the WHOIS Steering Committee had generated, and has also agreed to kick off all three Task Forces at this time.

Ultimately, all council members except the ISPCP representatives voted in favor.

new gTLDs (PDP initiation moved by Milton Mueller) unanimously deferred until next meeting.

Lengthy discussion of STLD (non-) RFP under AOB, and how sharply the Council should phrase a possible resolution on that topic. "Concern and ask for clarification" or more? Wording suggestions. Dan Halloran at the microphone. Points to oct 13 board minutes. Emphasize bottom-up nature. Commitment?^*

Resolution is drafted on the fly and adopted unanimously: Council requests clarification and is concerned that board may have made decision in gTLD policy area without consulting council.

UDRP is deferred for the time being. Expenditure authorization to GNSO secretariat. Enforcement of contracts scheduled for another meeting.

Disclosure: I participated in the council session as the ALAC liaison to the council.

^*) Stricken on 2003-11-02.

Twomey gives his report to the public forum.

Vision becoming clearer. Commitment to global outreach. Have gTLD registrars in 26 countries. Agreements with 15 ccTLD managers. ccNSO. Increased cooperation with relevant intergovernmental organizations. IDN introduction as important part of outreach. Local focus and commitment and key stewardship for integrity, security, stability of single Internet. Multi-lingual communications. ALAC as part of international outreach.

Commitment to innovation in the Domain Name System. Clear understanding of commitment to integrity, stability, security of single Internet. Keeping and building community. Work closely with other bodies -- ISOC, IETF, others.

Move from vision to how to achieve it. MoU extension. Strategic plan. Some headings: How build sustainable business operation. Management controls. Building capable staff. VP Biz ops: Kurt Pritz. VP SOs and ACs: Paul Verhoef (Brussels). GC: John Jeffreys. Focus around business unit model, key accountabilities. Measurement, make performance more accountable. Performance of IANA function. Share more statistics. Automation of operative processes. Stable, adequate, fair funding. Open small targeted offices in regions. Verhoef in Brussels office. "Lean and mean" offices, target on cooperation with regional communities and organizations.

Potential risks. Community consensus on key issues. WHOIS. WIPO2 implementation issues. Bring community together, work together to find pragmatic solutions going forward. Don't work in silos, interact. Heavily involved in WSIS. Working with many member states, attending prepcomm meetings. Want to leave report at this level today.

Detailed reporting on some function areas available. Will be posted later during the day.

Sharil Tamizi is delivering the GAC's communique.

Standard preamble. ccTLD redelegation, IANA function. Pending redelegations for some GAC members. Priority. Review ccNSO progress. Encourage continued work. Move forward on GAC principles. WIPO2: Welcome creation ofo joint working group. Mandate of WG limited to analyzing the practical and technical aspects of implementing wipo2 recs. GAC regrets that the working group has not presented an outliljne and timetable for its work on the GAC meeting at carthage, welcomes request from president of ICANN that wg report to board at Rome meeting.

GAC whois and gTLD working groups met GNSO Council, discussed gnso PDP. WHOIS use by govt authorities, GAC will share with GNSO.

IPv6. New registry services: GAC follows debate on use of DNS wildcards. Received briefing from ICANN president and CEO, and secsac chair. GAC recognizes that many interests have raised concerns about competition, technicasl and user issues. GAC recognizes ongoing review. GNSO PDP on review of registry services. GAC will continue monitoring.

Root servers; GAC recognizes efforts to increase security and stability of root server system.

Outreach: GAC workshop dedicated to arab and african regions with participation from 17 countries.

Future of GAC organization and financing. Agreed a procedure for updating operating principles, and election of vice chairs later this year. Working group to consider structure, organization, financing of GAC.

Thanks to local organizers. Next GAC meeting in Rome.

Suzanne Woolf. Anycasting root servers. AAAA records. Input on renumbering ofo B.root-servers.net. No objections raised. Renumbering in the next few months. GAC named liaison to RSSAC.

See www.root-servers.org for public information about committee's work.

Cerf asks about discussions re improving security of root system information by using DNSSEC. Answer: Active discussion. Not concern directly for committee, not yet ready for deployment. Waiting on IETF standardization. IETF is getting close, making progress, but not ready yet.

Cerf: AAAA records significant introduction. Test environment for such things? RSSAC does not operate test environment, but some participants do. RIRs and several root name server operators do participate in experimental activities of that kind. Have input.

Steve Crocker at the microphone.

Quiet group without much to do until recently. SECSAC membership. Technical people, not political people. Committee activity in last month dominated by wildcard. Sitefinder generated complaints and problem reports. Preliminary advisory. Information gathering. Still gathering input on substantive technical input, thoughtful commentary and analysis: secsac-comment@icann.org.

October 7 and October 15 meetings in Washington DC. Information posted on web site. SECSAC is writing report; part of larger process. SECSAC is strong on technical aspect. Also policy issues and economic impacts. Appreciate being an advisory committee. Not a decision-making body.

Back to wildcard: What happened? Wildcard. Some things broke. Some took defensive action. BIND patches, ISPs blocking sitefinder.

Areas of concern: no notice. Is it the thing right? Competition and contracts.

Just don't do wildcards? But: Existing registries; ccTLDs, .museum, but world has not come apart. Why is it a problem now if it wasn't a problem then? Issue of size?

Initial Advisory. Three recommendations. To Verisign: Please roll back, and provide time for everyone to think hard about this. To tech community: Ambiguous specifications / best practices? To ICANN: Please clarify procedures. More to say when finished with writing.

October 7 and October 15 meetings. Transcripts are available.

Tentative Issues: Abruptness, rightness, systemic stability, confidence, technical clarity, process clarity, displaced costs, innovation at core v. edge, future architecture, role of standards (do RFCs say everything?), existing wildcards, scope/size.

Will finish work over month or so. Will release report.

Cerf: Wildcards in general? Crocker: Yes, look at it in general. One step further: Wildcard is internal device for how you implement a broad set of reswponses or response to broad set of queries. Look at wire protocol -- doesn't matter what's in zone. Other kinds of synthesis. General questions: What are expectations in this area? What is impact of change? Align specs with practice? Align practice with specs? Live with a certain degree of discrepancy?

Vittorio is giving the ALAC's report. Key points: We start getting applications; we have sent Roberto Gaetano to the board. Organizing in regions starts moving. Recent statements and activities: Wildcard. New gTLDs: no harm principle. WHOIS: Raised data elements collected and displayed as issue with GNSO.

Activities in Carthage: Sitefinder workshop on Monday, WSIS workshop.

Slides here.

Jonathan Cohen reports for the wipo2 working group. Small meeting in Carthage as only few members are here. Set up tight telephone conference schedule. Document sharing phase. Have produced book with the materials on this.

Meetings every three weeks, first one on November 25th. Possibly meeting before Rome. Issue areas: Exclusionary lists, amending UDRP, independent UDRP, sunset provisions, treaty. Look at each of these under number of headings.

Vint Cerf: Large issue universe.

I'm taking a break from notetaking, while the ccNSO, GNSO, and ASO reports go through; there's now open microphone time for comments regarding these reports.

Ivan Campos speaks; Alejandro Pisanty chairs the committee, but is not here.

Review of the committee's charter. Unanimous recommendation for a slate for chair and vice chair of the board: Vint Cerf as chairman, Alejandro Pisanty as vice chairman. Discussed IDN Committee evolution. Masanobu Katoh speaks about the IDN committee and recent IDN developments. Proposal: Terminate the existing two committees that deal with IDNs, and create some sort of discussion forum.

The results from yesterday's Council meeting are now online: The text of the resolution regarding the sTLD RFP has been posted to the council list; the Terms of Reference for the three Task Forces that were kicked off yesterday are linked from the GNSO's WHOIS Privacy issue page.

The real-time captioning's output is available from the ICANN web page, too. Kudos to ICANN staff for this!

At the open microphone, Wolfgang Kleinwächter asks what has happened to the Privacy Committee that was initiated in Montreal. The initiative for the committee had come from Andy Müller-Maguhn at the time, who is now one of its three members.

Twomey's response: The committee has been asked to present a work program, but has not yet done so.

We're now hearing the summary from the ccTLD meetings.

Documents used for these meetings are available online, including Stephan Welzel's analysis of legal issues regarding the ccNSO set-up. This presentation is particularly interesting to read in the light of the argument structure used in Paul Twomey's recent letter to the GNSO on new registry services.

Redemption Grace Period for .info: No discussion. Palage abstains; all others in favor.

GNSO deletes: No discussion. Approved unanimously.

GNSO Council seats: GNSO Council has asked for three reps; evolution and reform process had two representatives by the end of this meeting. If no action, GNSO has to name two candidates for council. No discussion. All in favor.

RegistryPro, second level registrations: No discussion, approved unanimously.

New gTLDs. Lots of whereases that outline what is to be done; no chance to take notes on these. President directed to begin expeditious and targeted development of strategy and policy leading to a streamlined process for the introduction of new TLDs; president directed to seek community input on this strategy; report on new TLD policy should be completed by September 30, 2004; implementation begin before December 31, 2004. Palage abstains; all others in favor. Cerf: Is Palage channeling Karl or Andy? Palage: Conflict of interest.

New sTLD RFP: Board was hesitant at last meeting about doing sTLD round at same time with "generic" process. Lots of community input both via e-mail and in Carthage. Board has concluded that it should proceed. Open opportunity to apply in sTLD space; not limited to failed Y2k applicants; not limited to non-profit sponsors. Resolution: Open RFP no later than 15 December 2003; "limited number." Have not picked number. Want to keep this from being out-of-control landslide. Upon completion of sTLD selection process, agreement reflecting commercial and technical terms shall be negotiated. Selection process and implementation for sTLDs shall be evaluated and results utilized in new gTLD process. Cerf moves; Chapin seconds.

Discussion: Even while new TLD process runs, there might be results from it that have implications for sTLD contracts. Reasons for moving forward quickly. Keep in mind protection of registrant. Vote. Palage abstains, all others approve.

IDN Committee changes. Close existing IDN committee and President's IDN Registry Implementation Committee. Continue to participate and provide guidance on community's work with objective to achieve coordinated implementation of IDN. Brief discussion. Accepted unanimously.

Thanks to Masanobu Katoh who leaves the board today. Cerf moves. 17 seconds. "All those in favor please clap." Katoh: On way back from Berlin meeting, wrote "ICANN is a place of anarchists. It's a wild west." Improved tremendously now. Can focus on substantive issues. When running for election in 2000, five key issues: Continue work of ICANN to make it more stable. Promote multilingual communications. Establish local ICANN supporting organizations. Formalize multilingual DNS. Have closed two committees today, but work not yet done. Last issue: Review election system. Three years ago, said ICANN can be 21st ctry model for intl organization dealing with technology and new economy. Bottom-up. Private-sector leadership. Good coordination with government. Don't be too bureaucratic. Believe in ICANN. Believe ICANN can be that model. Good luck.

Palage: Katoh demonstrates what direct at-large voting can put on the board.

Proposed process to keep track of IDN restriction tables. Klensin: Original model comes out of work by joint team consisting of jpnic, twnic, cnnic, hknic. Working on languages and scripts which derive from Chinese characters. ... Tables designed to be applied by a registry for a language. There might be different tables for the same language, depending on which registry you are using. IDN c'tees have proposed that ICANN ask IANA to create registry of these tables, so they can easily be accessed. Qian: Minor correction: Not HKNIC, but KRNIC. Most difficult variant table is the Chinese. Jointly done by CNNIC, TWNIC, HKNIC, MONIC (?); SGNIC doing some work. Klensin: Apologies, not enough sleep. Magnificant set of jobs done on the Chinese tables. Great harmony with which group managed to work. Hope that smaller, but more overlapping scripts which occur in Western alphabetic languages do not cause great deal more problems and confusion than harmony demonstrated for chinese characters and languages. Twomey: Instructions for staff working on IANA functions will be done by Monday.

Katoh: Short report of Conflict of Interest committee. Not proposal for resolution. Discussed current CoI policy. Propose to review policy to include board liaisons. First reminder: Disclosures of potential conflicts by supporting organizations. Disclosure of conflicts that SO Council members might have. Second reminder for board members: Provide annual statement regarding conflict of interest issues. Tricia Drakes: Constructive input, cooperation from the community. Engagement of all sectors. Still work to be done on ccNSO. Deliver. Constructive Input! Chance that Katoh-san's expectations can be achieved.

Roberto Gaetano: Couple of words. Underline two resolultions passed today. Importance of what has been achieved with these -- talking about new gTLDs. Strategically progressing in careful analysis of the situation for the expansion of domain name space with study. Recognize need for quick action. Board at the same time showing strategic thought in terms of medium-, long-term strategy, also attention to basic needs and provide quick solution in short term.

Meeting adjourned.

Katoh-san leaves board, Hagen Hultzsch joins. Deutsche Telekom. Splendid addition to the board.

Convene new board for organizational meeting. Re-elect board, reconfirm officers. Agenda items for new board to complete. Election of new board chairman -- proposed by board governance ctee: Cerf. Lyman Chapin moves. Pisanty seconds. Unanimously approved.

Second recommendation: Pisanty vice-chairman of board. Cerf moves. Tricia Drakes seconds. Pisanty makes remarks about governance committee. Unanimously adopted. (Cerf does not let Pisanty abstain.)

Election of corporate officers. Twomey, Pritz, Jeffreys, Schroeder. Unanimously accepted.

Thanks for meeting assistance. Accepted by acclamation.

Rememberance of Jon Postel who passed away in October 1998. Place letter from Postel's family in record. Cerf reads letter.

Meeting called to a close.

In Carthage, I posted two blog items from the GNSO Council session in which I participated as the ALAC's liaison.

The first one announced that the Council had kicked off three WHOIS Task Forces; the second "covered" subsequent administrative decisions, and the council's work on a resolution regarding the sTLD RFP.

After the session, I had a discussion with several council members who had issues with this, and found my blogging activities inappropriate for various reasons.

There are two main directions from which objections can come. One, blogging should never take priority over participating in the meeting, and it must not distract from focusing on council work. Two, an acting person is taking the journalist's role and reporting about the council session, which is inherently a conflict of interest; also, the quality of the reporting suffers from the priorities an acting person has to set.

With a little bit of distance to the Carthage Council meeting, I believe that the only way for me to take these objections into account is to refrain from blogging Council discussions. In the future, I'll limit any real-time blogging from GNSO Council sessions to giving a terse account of resolutions adopted, to the extent time and attention permit.

Later: I just notice that Amadeu Abril i Abril (who sat next to me on the council) has blogged some thoughts about the same debate.

To begin with, Carthage was an extremely well-organized ICANN meeting. Participants were picked up by the local organizers at the airport and brought to the hotels with buses; wireless was up as early as Friday in the main meeting area (no Internet access was available in the rooms, though).

The social events left room for improvement: It's important that these give meeting participants enough possibility to network and talk to many others who are also at the conference. Gala diners (and similar fixed-place events) with loud music aren't very helpful for that purpose.

Meeting bags are another topic: They should be light, it should be possible to carry them over the shoulder, and they should be useful for carrying a laptop including its power adapter around.

It seems like Richard Henderson didn't hear the answer to his public forum question about proof-of-concept reports.

The answer was: http://www.icann.org/tlds /agreements/info /poc-afilias-082702.pdf.

(In other words, these reports are added to the TLD contract overview page.)