GA summary 2002-02

This summary covers the DNSO GA mailing list’s discussions during the second week of 2002. List archives are available online at [www.dnso.org]. Note that a new volume of the archive has been begun. Votes The election for the GA representative to …

This summary covers the DNSO GA mailing list’s discussions during the second week of 2002. List archives are available online at [www.dnso.org]. Note that a new volume of the archive has been begun.

Votes

The election for the GA representative to the NC Transfer Task Force ended on Thursday 10 January 2002. The candidates were Dan Steinberg, Eric Dierker, and Jeff Williams. Dan Steinberg was elected. Details on the vote are available from [www.dnso.org].

The vote for the GA chair and alternative chair began Saturday 5 January 2002, and was finished on 12 January 2002. The candidates were Kristy McKee, Thomas Roessler, Alexander Svensson, and Eric Dierker. Thomas Roessler and Alexander Svensson were elected. Details on the vote are available from [www.dnso.org].

Topics

(i) domain-policy archives. According to a message from Chuck Gomes, in reply to a question from Patrick Corliss, the domain-policy mailing list was shut down by Verisign for legal reasons in May 2001. [www.dnso.org]

There was some debate on whether or not this had actually been said before in public.

(ii) .org divestiture. Marc Schneiders posted the final version of the final draft of the .org NC task force report, plus a supplemental report from the GA representative which lists remaining concerns with the current text. [www.dnso.org], [www.dnso.org].

(iii) Deleted domain name handling. This was certainly the week’s dominant topic.

Genie Livingstone gave a summary of data gathered from tracking of expiring domains. According to him, “most dropped domains in 2001 were originally registered at Netsol Registrar. 99.9% of dropped domains were NOT re-registered at Netsol Registrar.” “This might be one interesting premise motivating Verisign to try to recapture the monopoly,” he writes. His message goes on to list some more concerns he has with practices of Verisign’s registrar division. [www.dnso.org].

Don Brown summarized what he believes to be “a few fundamental hurdles which need to be met before anything else is important” with respect to the waiting list proposal: “1. The WLS proposal essentially puts monopolistic power in the hands of one entity (the Registrar) and thwarts all competition.” (I suppose this should have been “the registry”.) “2. The theory behind this WLS proposal is that it addresses technical issues, which cannot otherwise be addressed on a technical level.” Don then demands that the technical difficulties be solved in a way which does not affect the business model. As his third point, he notes that “the name space belongs to the public – not the registrars”. [www.dnso.org]

In a more fundamental part of the thread, Chuck Gomes asks whether or not it is “okay for a property manager to have a waiting list”. To this, George Kirikos replies: “IF the LANDLORD allowed such a thing in their contract with the property manager, it would be perfectly legitimate. HOWEVER (and read this part, as it’s important), it is NOT OK for the property manager to create a waiting list on their own volition and keep all the money for themselves, behind the back of the landlords!” He also notes that “in most cases where there’s a waiting list, though, there’s a definite end to the lease term.” To this, William Walsh follows up to say that “Verisign is creating a situation in which a domain name has more value to the Registry and Registrar if the registrant does NOT renew the domain, and creates a problem in that the Registrar will be incentivized to not provide as strong a renewal notification service as they would otherwise be under incentive to do.” [www.dnso.org], [www.dnso.org], [www.dnso.org].

However, Verisign’s proposal wasn’t the only one to draw criticism: In fact, the “registry re-circulation system” (RRS), proposed by Peter Girard of Afternic.com, forwarded to the GA on Monday, and covered in the last summary, drew some criticism, too: George Kirikos complains that replacing “one monopoly (Verisign’s WLS) with another (a cartel of registrars doing an auction) isn’t a solution which promotes competition”. He also notes that the proposal “gives all the value of the domains that are auctioned to the registrars”, who have however done nothing to create that value (he says). He then introduces the “Let’s make George Kirikos a Multi-Millionaire” proposal. After all, he didn’t do anything to contribute to domains’ value, just like registrars….

In another reply to the Afternic proposal, Darryl (Dassa) Lynch writes: “I can’t see any reason for Registrars or the Registry to be benefiting from the consumer market value for renewed/deleted domains.”

[www.dnso.org], [www.dnso.org], [www.dnso.org].

A comment from Ron Wiener of Snapnames.com (the folks who own the technology Verisign has licensed for the WLS) was forwarded by Ross Wm. Rader. One of his points is this: “It seems to me that there is a distinction between the WLS (as proposed) and the RRS (as proposed), in that the WLS allows registrars to capture “backup demand” for any name throughout the entire year. The RRS only allows the capture of demand during a portion of the 45-day grace period window, which inherently means it would be primarily of interest to, and accessible to, speculators, not mainstream consumers.” [www.dnso.org]

Rick Wesson has asked the community to develop a “concise list of requirements for proposals to solve the issues with a registry deleting domains in batch”. He hopes for a consensus document on the requirements to be used when proposals are evaluated. [www.dnso.org]

In reply to this, George Kirikos lists various requirements, two of which are these: 1. Equal opportunity for any registrar to acquire a deleted name. “No current business model that is in place must be forcibly required to change […], unless it can be proven that they have caused the abuse through their choice of business models.” 2. “Registrants should continue to have the ability to register an expired name at a registrar’s normal price for a brand new registration for ALL deleted names.” [www.dnso.org]

From a registrant point of view, Bret Fausett lists six requirements, including: Registrants shouldn’t need to pay fees to more than one registrar to get a deleted domain; registrants should be able to place the order with one visit of the registrar’s web site; expiration dates listed in the whois should have some meaning; “the current registrant should make his or her decision to renew blind to the value placed on that domain name by prospective registrants”. (I find the last one particularly interesting.) [www.dnso.org]

Elliot Noss of Tucows sent a long message to the GA list in which he looks at various aspects of the deleted domains issue. First, he considers who may claim the right to expired or expiring names. He concludes that “the competing claims of registries and registrars are likely subordinate to those of registrants,” in the end of the day. “Accordingly, any solution should start with this underpinning,” he says. In the second section of his document, Noss emphasizes that he believes that the issues of registry load and expired/expiring domain allocation should be considered separately, and that the technical side of the problem can be (and actually mostly has been) solved without touching the allocation question. He then elaborates on “the inefficiency of flat pricing”, and argues that the combination of flat-priced supply and variable-priced demand has lead to a robust secondary market, and to a “significant amount of the current CNO namespace sitting unused”. He warns that these effects should not be magnified by solutions for the “expiring market”. Noss concludes by stating that the WLS proposal is unacceptable to him, and then suggests what he calls “two important modifications” to Afternic’s RRS proposal: Make all names available for bidding, and give the existing registrant an opportunity to accept bids at any time (with registrars and registries getting their share of the money, too). [www.dnso.org]

In follow-ups, George Kirikos and Don Brown argue that, if there’s no technical need for changing the “expiring market”, this market should be left alone for the moment, and more pressing problems should be addressed first. As Don puts it: “I am in favor of ‘healthy’ change, but I don’t view any change with respect to the after-market to be either healthy or warranted at this time.” [www.dnso.org]

In another follow-up to Elliot Noss’ message, Don Brown points out that part of the process “to introduce more efficiency into the systems and procedures” concerning deleted domain names should be “the adoption of specifications or policy” in the sense of 3.7.5 of the RAA (Registry-Registrar-Agreement): Such policy does not currently exist. [www.dnso.org]

In his comments on Elliot Noss’ proposal, Chuck Gomes of Verisign agrees with most of the points Elliot made. In particular, he “definitely confirms” that the WLS proposal and the technical problems the registry has with deleted domain names are not directly connected, and can be dealt with separately. However, he believes that the WLS could “still make some positive impact in this regard, but it certainly does not solve the whole problem”. He also points out that, while the registry problems do not affect day-to-day business of registrars anymore, “there has been and continues to be a growing impact on registry operations and registry costs”.

He then suggests that WLS would still be “a valuable service for consumers”, and that a 12-month test could be useful. [www.dnso.org]

Also on the deleted domains topic, the registrars’ constituency held a conference call. Various draft notes of the conference call are available. [www.lextext.com], [www.dnso.org], [www.dnso.org].

(iv) Working groups, sublists, etc. As a spin-off from the deleted domains thread (which, bad enough, seems to have mostly killed that thread), some discussion on working groups and sublists came up, including on-list straw polls on whether or not the GA should start a working group on the deletion issue, or whether people like the WLS. David Farrar writes about these: “Could I suggest both this poll and the previous one while well intentioned lead to the GA being more dysfunctional. Many do not subscribe here to see 40 people vote on a list.” [www.dnso.org]

Announcements from the new Chair and Co-Chair

In two short messages to the GA list, the new Chair and Alt.Chair have pointed out what their immediate plans are. These include:

  • Enforce list rules, including the posting limit. (Alexander will be the list monitor.)
  • Try to attract discussions and participants from various constituencies to the GA.
  • Concerning GA working groups and sublists, a “show traffic, get group” policy will be followed for the moment: If sustained discussions on some topic become too much, and participants desire it, the chairs will try to organize a new mailing list for these.
  • Concerning task forces, there’s nothing which prevents the GA members from discussing topics. According to the “show traffic, get group” policy, “mirror working groups” may be established. The GA rep to task forces has the responsibility to inform task force members of the GA’s discussions.

[www.dnso.org], [www.dnso.org].

GA summary 2002-01.

This summary covers the DNSO GA mailing list’s discussions during the first week of 2002. List archives are available online at [www.dnso.org]. Criticism and suggestions for improvement are welcome. Votes The election for the GA representative to …

This summary covers the DNSO GA mailing list’s discussions during the first week of 2002. List archives are available online at [www.dnso.org].

Criticism and suggestions for improvement are welcome.

Votes

The election for the GA representative to the NC Transfer Task Force, began on Thursday 3 January 2002, and will end on Thursday 10 January 2002. The candidates are Dan Steinberg, Eric Dierker, and Jeff Williams. Details on the vote are available from [www.dnso.org].

The call for endorsement for the election of the GA Chair and Alternate Chair closed on Friday, 04 January 2002. The vote began Saturday 5 January 2002, and will end on 12 January 2002. The candidates are Kristy McKee, Thomas Roessler, Alexander Svensson, and Eric Dierker. Details on the vote are available from [www.dnso.org].

Topics

(i) .org divestiture. Jeff Williams forwarded a draft (version 5.2, from Jan 4, 2002) of the Task Force’s report on the .org divestiture [www.dnso.org]. Marc Schneiders (the GA’s representative to this task force) followed up, noting that it’s not clear whether the draft posted is the final version, but that it was posted to the NCDNHC list. He noted that he believes that the key points he stands for are “quite well represented in the text”, and that he’s happy with it. [www.dnso.org]

There was little discussion on this text. It should, however, be noted that the .org divestiture TF is currently the subject of active discussions on the names council list, see various threads at [www.dnso.org].

(ii) Structure task force. Dave P. Farrar (the GA representative to the DNSO Structure Task Force) provided a summary of options and discussions on the task force. See [www.dnso.org].

(iii) UDRP task force: The time line for the UDRP questionnaire has been extended until February 6. [www.dnso.org]

(iv) Deleted domain name handling. On December 30, 2001, a PDF document circulated on the registrars constituency mailing list detailed plans on a waiting list service. [www.lextext.com], [www.dnso.org].

The proposal goes like this (from Verisign’s document): “WLS is a service whereby potential registrants (‘subscribers’) through their selected, participating registrar, may purchase a subscription tied to a domain name currently registered. […] All current processes would remain unchanged with one exception. A domain name registration that is subscribed to on WLS will be registered to the subscriber when the current domain name registration is deleted through normal operational procedures. Initially, a domain name registration could only have one subscription pending at a time.”

Note, in particular, that according to this proposal the registrar would still be the only one who does business with registrants directly. This includes the process of fulfilling a subscription: When this process is done, the domain in question will be registered for the (now former) subscriber through the registrar which was used to place the subscription.

Pricing at the registrar level is at US $ 40 (wholesale) for a one-year subscription.

Feedback on the proposal is expected from the registrars’ constituency by January 18, 2002.

To implement the proposal, Verisign has licensed technology from Snapnames. [www.lextext.com]

The proposal provoked ample, and sometimes heated, discussions on the GA list, which is still going on.

The discussion included fears that the deal may already be done (which was denied by Ross Rader “if the registrars have anything to do with it”). Ross also pointed to a message discussing the proposal which he sent to the registrars list [www.dnso.org].

Some (WX Walsh, DP Farrar) doubted that the proposal may have any benefit for the internet community as a whole, as opposed to Verisign’s stakeholders. To this, Chuck Gomes of Verisign responded that requests for a wait list service have been there since 1996.

Bret Fausett noted that putting the service at the registry level would mean an improvement to registrants: You’d just buy one subscription through your favorite registrar, and you’d be guaranteed that you get a domain name if and when it lapses. With a purely registrar-based system, you’d pay various services, and that just for improving the chance that you may get the domain when it’s dropped. [www.dnso.org], [www.dnso.org].

In a message forwarded by WXW from some other list (the registrars list?), George Kirikos elaborates on various points of criticism on the proposal. In particular, George asks why Verisign registry has not implemented any of the simple technical fixes proposed earlier. Suggestions include “rate-limiting connections, pushing out lists of candidate drop names, and returning richer error codes”. He also lists “numerous competing firms and registrars attempting to register expired domains, using the existing fair and transparent system” (besides Snapnames). [www.dnso.org]

In a follow-up, Chuck Gomes points out that “every registrar would have equal opportunity to participate or not participate”. George Kirikos replies that his problem is “leveraging the monopoly power of the registry, to enter a ‘new business’, which puts existing market participants out of business”.

Finally, Ross Rader has forwarded an alternative proposal from the icann-deletes mailing list. The proposal from Afternic.com, called Registry Re-circulation System, basically boils down to an auction of expired domain names during a finite amount of time after they have been dropped. [www.dnso.org]

mutt-1.2.5.1 and mutt-1.3.25 have just been simultaneously released.

These releases both fix a security hole which can be remotely exploited. The problem was found and a fix suggested by Joost Pol

These releases both fix a security hole which can be remotely exploited. The problem was found and a fix suggested by Joost Pol <joost(at)contempt.nl>. Thanks for that.

mutt-1.2.5.1 is released as an update to the last stable version of mutt, mutt-1.2.5. The ONLY relevant change in this version is the fix mentioned above. No other bugs present in 1.2.5 have been fixed. You only want to upgrade to this version of mutt if you absolutely have to stick with the mutt-1.2 series.

mutt-1.3.25 is the latest BETA version of mutt, and very close to what will eventually become mutt-1.4. Personally, I’d recommend that you download and use this version.

The tar balls, with detached PGP signatures, will be available from ftp.mutt.org within some minutes.

As an alternative, you can apply this patch to any 1.2 or 1.3 series mutt source code, and rebuild.

I apologize for the problem, and wish all of you a happy new year.

new.net and Tiscali

According to this item on Heise’s news ticker, and this press release from new.net, Tiscali – one of the larger European ISPs – has joined the club of those who will add new.net’s domains.

According to this item on Heise’s news ticker, and this press release from new.net, Tiscali – one of the larger European ISPs – has joined the club of those who will add new.net‘s domains.

D??sseldorf: Another press release

There’s another press release concerning the blocking of extremist content on the web ordered by the D??sseldorf district authority. According to this press release, providers will do everything that’s feasible to make access to incriminated conten…

There’s another press release concerning the blocking of extremist content on the web ordered by the Düsseldorf district authority. According to this press release, providers will do everything that’s feasible to make access to incriminated content more difficult.

D??sseldorf, again.

The struggle about the web blockings ordered (or not?) by the D??sseldorf district authority continues on various online fora, and in another (somewhat older) press release by the authority. Today, the head of the authority is going to hold a chat …

The struggle about the web blockings ordered (or not?) by the Düsseldorf district authority continues on various online fora, and in another (somewhat older) press release by the authority. Today, the head of the authority is going to hold a chat session between 14:00 and 15:00 GMT +0100.

Mutt-1.3.24 is out.

I’ve just released the next mutt beta, version 1.3.24i. Some of the more interesting changes against mutt-1.3.23i: New and improved threading code from Daniel Eisenbud. See also $duplicate_threads, $hide_missing, $thread_received. ANSI colors in t…

I’ve just released the next mutt beta, version 1.3.24i.

Some of the more interesting changes against mutt-1.3.23i:

  • New and improved threading code from Daniel Eisenbud. See also $duplicate_threads, $hide_missing, $thread_received.
  • ANSI colors in the builtin pager are now controlled by a variable $allow_ansi, and are turned OFF by default. The colorization of attachment markers (and PGP output messages) in the pager is done a bit different, and more difficult to cheat. In particular, it’s not possible to consistently trick two instances of mutt which were started at different points of time.
  • There’s a $wrapmargin variable which gives users some control over mutt’s wrapping in the pager, and in the text/plain; format=flowed handler. The default value of this variable is 0.
  • Of course, bug fixes.

There’s an outstanding mail loss problem with this version: On system where write(2) lies about the success of an operation (for instance, with NFS folders or when quotas are enabled), mutt may not detect such errors when writing to mbox folders, possibly even losing mail. The bug is mutt’s, and will be fixed next week (I hope). Since it’s present in all mutt versions, there’s no point in holding up this release due to the problem. See the bug tracking system for details.

Mutt 1.3.24i can be found here.

Another press release from the D??sseldorf district authority

Since Friday, another news release from the D??sseldorf district authority has been available. In this release, the authority justifies the blocking attempts by referring to disgusting content on the pages blocked. The allegation that the authority…

Since Friday, another news release from the Düsseldorf district authority has been available. In this release, the authority justifies the blocking attempts by referring to disgusting content on the pages blocked. The allegation that the authority has been wrongly declaring the authors of protest e-mails to be right-wing extremists is rebutted: “There may be many e-mail senders who want to defend the Internet’s liberty on principle. But the content of many other Internet messages clearly demonstrates – by style and content – that the authors show right-wing extremist thinking. In those cases in which my employees have been threatened directly […], the prosecuting attorney will investigate.” For some discussions on this press release, have a look at the authority’s web forum.

ISIS press release on the blocking

In a press release published in the evening, ISIS gives its version of the day’s events: According to this press release, a technician had been experimenting with blocking the relevant web sites since the beginning of the week, despite the fact th…

In a press release published in the evening, ISIS gives its version of the day’s events: According to this press release, a technician had been experimenting with blocking the relevant web sites since the beginning of the week, despite the fact that the ISP originally didn’t want to implement the block (the district government had originally called for the block in early October). This experiment was then stopped in the morning, and reactivated in the late afternoon after an ISIS executive had met the head of the district government to discuss the issue. ISIS then complains about the situation of ISPs which are either perceived as censors, or as fostering right-wing radicalism. It is emphasized that ISIS maintains its criticism of the technical solution used to block the sites – in particular because the solution leaves so many back doors that the effort can’t actually be justified. According to the press release, ISIS will meet the district government in December, in order to discuss further activities and work on a political solution.