More conference call observations

Some brief observations about yesterday’s WHOIS conference call (for those who find my earlier notes too lengthy ;): The discussions on the call were clearly dominated by IP interests and registrars. Registries were on the call, but silent. Variou…

Some brief observations about yesterday’s WHOIS conference call (for those who find my earlier notes too lengthy ;): The discussions on the call were clearly dominated by IP interests and registrars. Registries were on the call, but silent. Various parts of the USG were represented on the call and participated; other governments or governmental entities didn’t even listen in (or didn’t announce themselves during the role call).

Notes from the WHOIS telephone conference.

The agenda of today’s conference: Reasons we are here / history; a view of the problem; uses and users; the registrar proposal; can we get there from here? Extensive notes inside; errors, typos and misunderstandings are mine. (Update: Fixed some t…

The agenda of today’s conference: Reasons we are here / history; a view of the problem; uses and users; the registrar proposal; can we get there from here? Extensive notes inside; errors, typos and misunderstandings are mine. (Update: Fixed some typos. Also, a formal transcript will be made available by the call’s organizers. — 030530, 9pm CEST, tlr. Update 2: Thomas Barret from Encirca writes to make some corrections to a comment by him which I had wrongly attributed to Robert Connelly. — 030602)

An open conference call on WHOIS.

Writes Ross Rader: Next week, there will be a community sponsored, open teleconference to discuss how we can work within the ICANN process to start implementing first steps towards a Whois that more appropriately suits the needs of all affected st…

Writes Ross Rader: Next week, there will be a community sponsored, open teleconference to discuss how we can work within the ICANN process to start implementing first steps towards a Whois that more appropriately suits the needs of all affected stakeholders. … a group of registrars, business leaders, intellectual property interests, generic and country registry operators, consumer rights and other related parties are in the process of putting together an open forum that will occur next week. Our goal is to start an open and honest dialogue between impacted parties and identify points of agreement that we can start building on. I must stress that this will be an open forum with an agenda.

GNSO Council adopts resolution on new gTLDs.

The GNSO Council has, unanimously, adopted this resolution on today’s call: Expansion of the gTLD namespace should be a bottom-up approach with names proposed by the interested parties to ICANN. Expansion should be demand-driven. Furthermore, ther…

The GNSO Council has, unanimously, adopted this resolution on today’s call: Expansion of the gTLD namespace should be a bottom-up approach with names proposed by the interested parties to ICANN. Expansion should be demand-driven. Furthermore, there should be a set of objective criteria to be met in any future expansion. The development of this set of objective criteria should be the subject of a new Policy Development Process (PDP). These ideas are expanded in the a report together with the responses of the GNSO Constituencies and the ALAC which will be forwarded to the Board in June.

The “report” referred to will be a revised version of what has been circulated on the gtld-com list, and is supposed to be a summary of the discussions the Council had on that list. There will be no public comment process on this particular document, since it’s expected to be used as input into a formal policy-development process.

List RSS feeds now with message bodies.

The mailing-list-archive-based RSS feeds I provide now include messages’ bodies. Thanks for the patch; the code is available on request. (As a side effect, mailing list postings which contain URLs can now appear as “related stories” in this blog.)

The mailing-list-archive-based RSS feeds I provide now include messages’ bodies. Thanks for the patch; the code is available on request.

(As a side effect, mailing list postings which contain URLs can now appear as “related stories” in this blog.)