January 2005 - Test - lists.nanog.org

Re: Registrars serve no useful purpose
by Fergie (Paul Ferguson) 19 Jan '05

19 Jan '05

And, on this point, I believe Karl was right. $.02, - ferg -- "David M. Besonen" <davidb(a)panix.com> wrote: Auerbach: The public interest is not being served. -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(a)netzero.net or fergdawg(a)sbcglobal.net

1 0

Re: Registrars serve no useful purpose
by David M. Besonen 19 Jan '05

19 Jan '05

[a dated, biased (what isn't?), insightful, and relevant interview] Published on Policy DevCenter (http://www.oreillynet.com/policy/) http://www.oreillynet.com/pub/a/policy/2002/12/05/karl.html Karl Auerbach: ICANN "Out of Control" by Richard Koman 12/05/2002 Editor's note: Strong forces are reshaping the Internet these days. To understand these forces-- governmental, business, and technical--Richard Koman interviews the people in the midst of the changes. This month, Richard talks to Karl Auerbach, a public board member of ICANN and one of the Internet governing body's strongest critics. October's distributed, denial-of-service attack against the domain name system--the most serious yet, in which seven of the thirteen DNS roots were cut off from the Internet--put a spotlight on ICANN, the nongovernmental corporation responsible for Internet addressing and DNS. The security of DNS is on ICANN's watch. Why is it so susceptible to attack, when the Internet as a whole is touted as being able to withstand nuclear Armageddon? It's religious dogma, says Karl Auerbach, a public representative to ICANN's board. There's no reason DNS shouldn't be decentralized, except that ICANN wants to maintain central control over this critical function. Worse, Auerbach said in a telephone interview with O'Reilly Network, ICANN uses its domain name dispute resolution process to expand the rights of trademark holders, routinely taking away domains from people with legitimate rights to them, only to reward them to multinational corporations with similar names. Auerbach--who successfully sued ICANN over access to corporate documents (ICANN wanted him to sign a nondisclosure agreement before he could see the documents)--will only be an ICANN director for a few more weeks. As part of ICANN's "reform" process, the ICANN board voted last month to end public representation on the board. As of December 15, there will be zero public representatives on the ICANN board. How does ICANN justify banishing the public from its decision-making process? Stuart Lynn, president and CEO of ICANN, said the change was needed to make ICANN's process more "efficient." In a Washington Post online discussion, Lynn said: "The board decided that at this time [online elections] are too open to fraud and capture to be practical, and we have to look for other ways to represent the public interest. It was also not clear that enough people were really interested in voting in these elections to create a large enough body of voters that could be reflective of the public interest. This decision could always be reexamined in the future. In the meantime, we are encouraging other forms of at-large organizations to self-organize and create and encourage a body of individuals who could provide the user input and public interest input into the ICANN process." Former ICANN president Esther Dyson is also supporting the move away from public representation on the board. "I did believe that it was a good idea to have a globally elected executive board, [but] you can't have a global democracy without a globally informed electorate," Dyson told the Post. "What you really need [in order] to have effective end-user representation is to have them in the bowels (of the organization) rather than on the board." Auerbach isn't buying. "ICANN is pursuing various spin stories to pretend that they haven't abandoned the public interest," he says in this interview. "ICANN is trying to create a situation where individuals are not allowed in and the only organizations that are allowed in are those that hew to ICANN's party line." In this interview, Auerbach makes a number of strong criticisms of ICANN, beyond the issue of public access: * ICANN uses its domain name dispute resolution process to expand the rights of trademark holders, routinely taking away domains from people with legitimate rights to them, only to reward them to multinational corps with similar names, Auerbach says. * ICANN unnecessarily maintains the domain name system as a centralized database, making it vulnerable to attack. * ICANN has failed to improve network security since September 11 and has ignored Auerbach's suggestions for improving DNS security. * ICANN staff takes actions without consulting the board, withholds information from the board, and misleads board members. * Finally, Auerbach charges that ICANN is guilty of corporate malfeasance. Koman: On October 21, there was a denial-of-service attack on DNS, which was widely reported as the most serious yet. Something like seven of the thirteen root servers were unavailable for as long as three hours. What is ICANN's responsibility for DNS, and how vulnerable is it to attack? Auerbach: On the Internet, there are a couple of areas that arguably need some centralized authority. One of these is IP address allocation--addresses need to handed out with some notion of how they comport to the physical topology of the network. A lot of people look at the domain name system as equally in need of centralized control. They look at DNS and see there's a root on top and some number of names underneath and they say, "Whoa, we need an organization to manage that." From a technical point of view, that's completely untrue. The DNS is really an optional service on top of the basic functionality of the Internet. We could have many different versions of DNS. The only concern is they be consistent with one another. People have elevated this argument for consistency to the idea that we can only have one, catholic source of names. That's a leap of logic that does not exist in reality; nevertheless ICANN uses that leap to justify its existence. By some religious dogma, we have come to the conclusion that there must be one ICANN sitting on top of the domain name space. It's a false conclusion but many people believe it, and it's a very useful conclusion for trademark interests, who have found that enforcing trademarks through the court system is just plain expensive. They found ICANN to be a very convenient tool to expand the law of trademarks, so trademark holders can exert control over non-trademark holders in a much less expensive way, and in a way that happens to lack all the protections of due process and judicial review. That's a dream for the trademark holders; they love ICANN. Koman: Let's talk about the recent denial-of-service attack. Auerbach: The interesting thing is, September 11 was more than a year ago and ICANN formed this high-level plenary committee to go and deal with DNS security, and to date not a single peep has come out of that committee. Yet I proposed in early October 2001 a set of several concrete, specific things that people could do to protect DNS, and more importantly, to recover from a DNS outage. And also to go after the bad guys to deter others from doing it. ICANN, because they refuse to admit I exist, deep- sixed the entire set of suggestions and hasn't even admitted that they exist. ICANN has intentionally disregarded things it could have done to protect DNS security, which possibly, had they been adopted, would have either slowed, prevented, or more quickly deflected this most recent attack. ICANN does not have the public interest at heart. ICANN isn't doing a diddly thing about network security. The committee itself has great people on it, but they're great people in a very narrow sense. They're technical experts but they know nothing about how to recover from a disaster. How do you lock a door? They know nothing about collection of evidence. They know nothing about how to recover from a disaster. Koman: How insecure is DNS; how susceptible is it to attack? Auerbach: Well, I don't disagree with the assessment of Bruce Schneier that DNS is probably the most vulnerable point of the Internet. ICANN has proclaimed as a matter of religious dogma--and it's nothing more-- that there shall be but one DNS root. Well that means ICANN is declaring the Internet shall have one single point of failure and here it is. ICANN has by that dogma condemned the Internet to vulnerability. Koman: The whole Internet is based on its decentralized nature, on redundancy, on the lack of single points of failure. Auerbach: Except in the domain name system. And the domain name system need not be that way. ICANN is making a lot of assertions that are not justified by technology and are not consistent with the public's desire to control its own Internet experience. Public Representation on ICANN Koman: On October 31, ICANN approved new bylaws that removed the five publicly elected board members, leaving no public representation on the board, as of December 15. Auerbach: That's right. Now ICANN is pursuing various spin stories to pretend that they haven't abandoned the public interest. One is that they have governments participating in ICANN and the governments represent the people of their nations, and because governments are an advisory group within ICANN, we don't need mere people. That argument is fallacious; governments not only represent their citizens; they also represent businesses and other entities within their borders. But ICANN gives special privileges to those businesses in its forums, and businesses still do get to elect board members. They've also created these so-called at- large advisory committees (ALACs)--note that they're called "at-large" as if the public could join, but membership is not open to the public; membership is only open to organizations. ICANN is trying to create a situation where individuals are not allowed in and the only organizations that are allowed in are those that hew to ICANN's party line. You have no way to vote against ICANN directors. You have as much right to vote against ICANN directors as the peasants in France had of voting against Louis XIV. Koman: What is ICANN's attitude to the idea that the Internet is a public resource and that the public has some justifiable interest in being involved in its governance? Auerbach: ICANN is an oligarchy. ICANN claims it's a private organization yet it claims immunity from things like antitrust because it derives its powers via contracts with the government. It has decided that things like decentralizing the domain name space should not be done because the public should not be confused. ICANN has made all these decisions based on the concept of what the public should have and what it should not without ever asking the public what it wants or allowing the public to have its representatives among those who decide these issues. Koman: So doesn't the public have a reasonable right of governance of this critical public resource? Auerbach: The public does have an expectation--ICANN's purpose is to benefit the public and yet ICANN has done nothing but promote business. There are public interests that are really important on the Internet. Like making sure the domain name system works reliably day in and day out, that it's reasonably protected and stable. ICANN has not done any of that. The public's expectations of what ICANN ought to be doing have been unfilled and the public's expectation of what ICANN ought not to be doing have been quite well fulfilled. ICANN is squishing out of the seams in jobs it ought not to be doing. Corporate Malfeasance? Koman: Stuart Lynn says they made this change to streamline the efficiency of the organization. Auerbach: Since when has efficiency of ICANN been an important goal? ICANN has been the most inefficient organization in the world; it's only created seven top- level domains in its four years of existence. And it only had elected members for half of that period, and only a partially elected membership. ICANN doesn't need efficiency; it needs to examine itself and discover, for example, that its staff is utterly out of control. Stuart Lynn in Shanghai got up and announced to the world that ICANN is going to have three new top-level domains of the sponsored type. Who decided that's what we need or that we need only three of them? Stuart Lynn did. He didn't consult with the community yet he declared the future business landscape of the Internet. He decided who is going to be on the main street of the Internet and who is going to be forced into the back alley. That's not a decision that arose out of elections and non- elections; that arose out of the fact that ICANN has an irresponsible staff that doesn't account to the board, much less to the public, and the board doesn't do anything about it. Insubordination is rife throughout ICANN and the board simply chooses to be powerless and not do anything about it. Elections are a non sequiteur. They have nothing to do with this issue. In terms of corporate governance, ICANN makes Enron look like a saint. I had to sue them to look at the most basic information a board member should look at, and what's amazing is that out of the lawsuit, we discovered that no other board member had bothered to do it, including ICANN's own audit committee. I can't even believe the auditors signed off on ICANN's annual report because I looked at the raw data and it's unauditable. You can't verify that an expense that was paid was actually tied to an expense requisition--they were just paying random invoices. Koman: But there's a congressional committee that oversees ICANN, is there not? Auerbach: No. ICANN plays this shell game--it claims to be a private corporation but it's not really private because it's a public benefit corporation of California. ICANN is in fact, a 501(c)3, which means it's exempt from federal taxes. ICANN is not a governmental organization so Congress's role is not to oversee ICANN but rather to look at it and then determine whether or not Congress needs to pass legislation that controls how the executive branch-- the Department of Commerce--acts in situations like this. Yes, Congress can put pressure on the Department of Commerce, but it's indirect pressure. Commerce has chosen to blind itself to the foibles of ICANN. Commerce has not held ICANN to its commitments. It has not audited ICANN to see that ICANN is doing the job it's supposed to do. As far the financial aspects go, Commerce has really no role because ICANN is a private organization. That's what the directors' role is, to oversee the finances, yet ICANN's management has tried to make it so the directors can't do that. Koman: So in the absence of ICANN directors asking for accountability ... Auerbach: There is none. Koman: There is no other layer? Auerbach: Well, there is one other person who can hold ICANN accountable, but his name is rarely mentioned-- Bill Lockyer, the attorney general for the state of California. He can hold ICANN accountable if the board members do not. I imagine the IRS can as well. I've pointed out certain problems in ICANN whereby the board members may be personally liable for millions of dollars for certain acts of ICANN; and even with that sort of sword of Damocles hanging over ICANN and its directors and their pocketbooks, they're not willing to take action. It's an organization that's just unbelievable. Koman: Karl: In testimony to Congress, you said, if ICANN ceased to exist ... Auerbach: The Internet would run perfectly. The Internet addressing is now being administered by four groups called the RIRs (Regional Internet Address Registries), and they issued what amounts to a declaration of independence from ICANN--they presented it in Shanghai. That's the critical function. Addresses would continue to be allocated by these groups even if ICANN were to disappear. Verisign takes care of the DNS part--it still prepares the root zone file every day and publishes it--that's where it comes from. ICANN does not have its fingers on the keyboard editing that file--that's still inside Verisign. And that would still happen if ICANN disappeared. Koman: So the existence of ICANN is in fact a threat to the Net? Auerbach: Well, as we've seen in the security case, had they not been there we might have reacted more quickly to the threats coming out of September 11. But ICANN has said, "Oh huff and puff, we'll establish these grand glorious committees that will solve the problem. And because so many other things are happening, people have a sense of complacency; they say, "Oh, ICANN's handling that." But ICANN's not. ICANN's far more willing to give .com to Verisign in perpetuity, and deal with reassigning .org, than it is in dealing with what it needs to do to make sure the DNS root level runs responsibly and reliably. For example, my first day on the board I suggested ICANN put in place a monitoring system so that we can learn when DNS servers at the root start to go south. They simply didn't want to consider it. Verisign does that on their own. The security stuff--they don't want to hear about it. Public Action Koman: What can people do? No amount of public agitation will bring about change? Auerbach: No, agitation will work. The Department of Commerce might realize, hey, their little baby is out of control. More congresspeople might realize something's rotten in Denmark and start accumulating the pressure on Commerce. And, of course, there are people outside the U.S. who might realize that ICANN is, for example, advocating wholesale violations of privacy by publishing the whois databases to anybody and anyone, with preference to trademark people, and that includes your personal ID; you've entered into a contract to buy a domain name; you didn't enter into a contract to publish your name, address, phone number, company affiliation, and email address to everybody in the world, including spammers. But ICANN says it has to be that way. Privacy is a balance between somebody's need to know and your need for privacy. There are a lot of principles that have come up over the years about how this balance is to be struck, and ICANN has disregarded all of those, because the trademark people- -in their race to accuse people of being trademark violators and obtain their names, addresses, and phone numbers--have insisted that ICANN make all this stuff widely available. I know a woman who's been stalked because her name was listed in the whois database; it's not that uncommon. And all of us have received spam and phone calls. Koman: What can outraged citizens do about this? Auerbach: Well, be outraged, first of all. Participate in ICANN. I displayed a photo showing that the meetings were empty, and they said, "here we are in the most populous nation in the world and the fact that nobody shows up means that we're doing a good job!" Wait a minute, maybe it's that people have become totally disenchanted with you and have figured out that showing up doesn't make any difference. But we can't give them that excuse; people still have to participate in ICANN and ensure that we have a firm record of ICANN constantly and repeatedly going against the demonstrated consensus of opinion; also what the public needs to do is keep up constant pressure on their representatives, and also on Don Evans in the Department of Commerce. I'd make noises; if you're in California, write to the attorney general, and ask how come we have this public benefit corporation in California that receives all these benefits yet seems to operate in complete defiance of the principal of benefitting the public. Koman: When ICANN demands that DNS be centralized when it could very well be decentralized; when P2P technologies themselves, rather than "pirate users" are attacked by the record companies and Hollywood ... doesn't it seem that there is a battle for control of the infrastructure of the Net, and that the battle is drawn on lines of how centralized or decentralized the Internet shall be? Auerbach: There's definitely a battle for control. A lot of people are fearful of chaos. ICANN's attitude is that we are technologists; we know better about how the world should run than you do. And these are people who can't even run a small business and keep it afloat. Yes, they're smart people and they are very condescending to other people who have other backgrounds and other points of view. But you know, technology isn't everything; dispute resolution is important; knowing how to keep finances is important. Koman: Were some directors filled in and others left in the dark? Auerbach: There was definitely an inner circle. Very definitely. I hear from the budget committee, "Oh, we're watching that." Yet I have never been able to find out whether there's information to be watched. There's some information flowing that I've not yet found. When Stuart Lynn announced his grand plan for change--I don't want to call it "reform" because it's not reform--several board members had already heard it, had seen it; I was just appalled that members had sent people around the world to talk to outsiders, without validating that the board wanted this. And Stuart Lynn gets up there and announces we're going to have three new top-level domains. He never asked the board for that. He just did it. He has given me and the whole board information that he knew was false. I believe that his intent was to mislead. I have instances where he's knowingly made false statements to the board. I think he should be fired for insubordination, as well as incompetence. And the same for their law firm. Joe Sims--he's the secret director--he's unelected but he's party to everything. He's made more money through ICANN than anyone else. Koman: Through his law firm? Auerbach: Yes, and he's a partner. Auerbach: He's the one who brokered the gift of .com to Verisign in perpetuity, privately. And he went to ICANN and said, "here's what I've done--adopt it." And ICANN said OK. Even over the advice of its own advisory group. Koman: Amazing. Auerbach: The public interest is not being served. Richard Koman is a freelance writer and editor, and former O'Reilly editor. Read his blog [http://rkoman.blogspot.com/]

1 1

NANOG via RSS
by Mike Callahan 19 Jan '05

19 Jan '05

By any chance is this list available via xml/rss? Thanks, Mike

9 11

RE: NANOG via RSS
by Hannigan, Martin 19 Jan '05

19 Jan '05

> -----Original Message----- > From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of > Paul Vixie > Sent: Wednesday, January 19, 2005 11:59 AM > To: nanog(a)merit.edu > Subject: Re: NANOG via RSS > > > > rs(a)seastrom.com (Robert E.Seastrom) writes: > > > > By any chance is this list available via xml/rss? > > ... > > Due to different ways of looking at data than one would > usually think > > of when designing a mail or usenet reader, all RSS readers of my > > admittedly fairly narrow acquaintance are lacking in one critical > > (imnsho) feature for reading NANOG-L: "kill thread". > > we gateway nanog@ (it's not called NANOG-L, really, plz stop > saying that) > into a local usenet newsgroup here. the netnews feature i > use most often > isn't actually "kill by thread", but rather "kill by author". i can't > imagine how any of you read this forum using a normal e-mail tool. Merit could treat the mailing list as an asset and not allow redistribution and instead offer multiple formats for readers to "peruse" or "react in near real time". RSS, NNTP, and SMTP are all options in my mind. It's about choices. More is better. -M<

1 0

209.225.34.161 (vsc.gsa.gov)
by Richard J. Sears 19 Jan '05

19 Jan '05

Can someone from this network contact me offlist - we are having routing issues with your network. Thanks ****************************************** Richard J. Sears Vice President American Internet Services ---------------------------------------------------- rsears(a)adnc.com http://www.adnc.com ---------------------------------------------------- 858.576.4272 - Phone 858.427.2401 - Fax INOC-DBA - 6130 ---------------------------------------------------- I fly because it releases my mind from the tyranny of petty things . . "Work like you don't need the money, love like you've never been hurt and dance like you do when nobody's watching."

1 0

NYTimes: Purloined Domain Name Is an Unsolved Mystery
by Hank Nussbacher 19 Jan '05

19 Jan '05

http://www.nytimes.com/2005/01/18/technology/18domain.html -Hank

6 6

Gtld transfer process
by Bruce Tonkin 19 Jan '05

19 Jan '05

Hello All, Given the recent panix.com hijacking, I will give an outline of the current ICANN transfers process for gtlds. In the case of panix.com, evidence so far indicates that a third party that holds an account with a reseller of Melbourne IT, fraudulently initiated the transfer. The third party appears to have used stolen credit cards to establish this account and pay for the transfer. That reseller is analysing its logs and cooperating with law enforcement. There was an error in the checking process prior to initiating the transfer, and thus the transfer should never have been initiated. The loophole that led to this error has been closed. The transfer process has several checks and balances that are described below. It seems that in this case none of these worked. I can only comment on those from our end. Note also that panix.com was held in the .com registry, that does not use the new EPP protocol which incorporates the facility to store a separate password (called auth_info) for each domain name that must be checked before completing a transfer. Transfers process ================= (see http://www.icann.org/transfers/policy-12jul04.htm for full details) (1) A person initiates a transfer for a domain name via a reseller or registrar (1a) For registries (e.g org, biz, info, name) that use the EPP protocol, the person also needs a password that is held in the registry for each domain name (called auth_info in EPP protocol) (2) The gaining registrar is responsible for obtaining approval from the registrant (using the contact details available in the WHOIS of the losing registrar) using a standardised form (http://www.icann.org/transfers/foa-auth-12jul04.htm) In some cases registrars delegate the obtaining of the approval from a reseller that has direct contact with the registrant. A gaining registrar is not permitted by the policy to initiate a transfer without approval from the registrant. (3) The registrar initiates the transfer. (4) The registry checks to see if the name is on Registrar-LOCK, if so, the transfer request is rejected. Registrants may choose to put domain names on registrar-lock. Many registrars now put names on lock by default, and give the registrant the opportunity to remove a lock prior to transfer. (4a) For registries (e.g org, biz, info, name) that use the EPP protocol, the registry checks the auth_info supplied by the gaining registrar against the record in the registry. If there is no match, the transfer request is rejected. (5) The registry will send a message to the losing registrar confirming that a transfer has been initiated. (6) [OPTIONAL] A losing registrar may send a standard confirmation message (http://www.icann.org/transfers/foa-conf-12jul04.htm) to the registrant. A registrant may cancel a transfer at this point. A registrant may also immediately confirm a transfer at this point and the transfer will be immediately completed. (7) If the registry receives no response from the losing registrar after a 5 day period, the transfer will be completed. (8) A registrant may not further transfer a name for a period of 60 days (apart from back to the original registrar). (9) If the losing registrar believes that a transfer was unauthorised, the losing registrar may contact the gaining registrar for a copy of the authorisation in step 2 to arrange for the transfer to be reversed. (10) If the registrars cannot resolve a dispute, the losing registrar may initiate a dispute process with the registry operator. (11) If the registry operator cannot resolve a dispute, the losing registrar may initiate a dispute process with an external dispute resolution provider (http://www.icann.org/dndr/tdrp/approved-providers.htm) In the case of panix.com, the step (2) failed at the gaining registrar. I can't comment on steps taken by the losing registrar. The principle of the process, is that a registrant can move to another domain name provider (registrar or reseller) at any time, and can initiate a transfer from the new provider. This relies on the new provider authenticating the request. Losing registrars can incorporate registrar lock and transfer confirmation messages to minimise the risk in this process. The integrity of the process is greatly improved through the use of the auth_info password in the EPP protocol. This has been operating effectively in .org, .info., .biz and .name. The alternative to the process could be for the losing registrar to authenticate and initiate a transfer away. This may be more secure, but has a downside in that a losing registrar has an incentive to make this process as difficult and slow as possible. The current transfers policy was a result of over 2 years of work, but can always be improved. Thus ICANN is currently conducting a review of the policy http://www.icann.org/announcements/announcement-12jan05.htm. My personal view is that the current transfers policy WITH the use of auth_info and WITH the use of registrar-LOCK is a reasonable balance between security and allowing registrants to easily move their name. Areas for further improvement include having an expedited process for managing a fraudulent transfer - including the ability to quickly revert back to the previous DNS information while a dispute is investigated, and having mechanisms to ensure that 24/7 emergency contacts are available for all registrars at the registry. I am interested to hear what members of the NANOG list believe would be a better transfers process. Regards, Bruce Tonkin

10 11

Re: EPP minutia (was: Re: Gtld transfer process)
by George William Herbert 19 Jan '05

19 Jan '05

>I want a "transfer process" that is inherently difficult, if not >broken, for domain names that are business assets. I don't care about >"competition" between registrars, or how much I get soaked for by the >registrar and registry, or how evil and/or retarded one or both are. The problem that got us here was that registrars have historically been not flexible enough at releasing domains when the owners *did* want to transfer them. What you are saying, is that you want to have either a level of service at registrars, or a new registrar with the additional level of service, that instead of being easy to deal with in moves, is designed to maximally ensure safe handling of your important corporate identity. I think this is a clear and wonderful business opportunity. Just expect to pay more for it... -george william herbert gherbert(a)retro.com

3 2

Was panix.com in registrar-lock?
by Richard Parker 18 Jan '05

18 Jan '05

Does anyone know if the panix.com domain did, in fact, have an RRP status of registrar-lock in the .com registry sometime before it was hijacked? According to a couple of articles Panix officials insist that the panix.com domain had been registrar locked while George DeCarlo, vice president of marketing at Dotster (Panix's registrar), is reported saying that Panix did not sign onto Dotster's domain-locking service. If we ignore the serious issue of potential notification failures and look at just the registrar-lock issue, there are several possible scenarios: 1) Panix never requested that the panix.com domain be locked. 2) Panix requested the lock, but their registrar did not pass this request to the .com registry. 3) Panix's registrar requested the lock, but the .com registry failed to set the lock status. 4) The registrar-lock status was set at the registry, but it was fraudulently cleared prior to the domain transfer. 5) The registrar-lock status was set at the registry, but the domain was transferred despite the lock. Did I miss a scenario? I'd like to know which scenario occurred in the panix.com hijack, hence my interest in whether the .com registry was reporting the status of panix.com as registrar-lock prior to the hijack. -Richard

3 3

RE: Gtld transfer process
by Bruce Tonkin 18 Jan '05

18 Jan '05

Hello William, Thanks for your suggestions. Comments below. > > I would propose the following: > > 1. Keep existing model but make it "SHOULD" for old registrar > to inform > of upcoming transfer (I still don't understand how that failed in > panix.com case BTW, because I'm pretty certain dotster does it, the > only thing I can think of is that they did but answer was > lost among > all the spam that hostmaster account received). Sounds reasonable. > > 2. Allow for fast way to reverse the domain transfer for old register. > I'd propose the following: > a. Old registrar can use special registry function to request > reversal within 5 days of the transfer and that is immediatly > granted (no questions asked at that time) with > immediate restoration > of old NS servers Might be better to simply revert the NS records at the request of the original registrar, and then place the name on registry lock until the dispute is resolved. Note for URDP disputes a name is typically locked by a registrar (although the current NS record state is retained). Most of the other steps regarding provision of evidence and full-rollback to the original registrar are covered under the existing transfer dispute policies. The detailed process is documented here: http://www.icann.org/transfers/dispute-policy-12jul04.htm Regards, Bruce

1 0