Does this mean the term of agreement will change stating the registrar will be out of the cash but no change on the way the registerar may be refunded or take control of the domain? Lord, I hope your answer is not just the terms change in our agreement to state we can NOT get control for a charge back of non payment. We would be out twice as much and more from the charge back fees. Yet still no domain name to use our selves from it....
-- Mike Allen, 4CheapDomains.Net [EMAIL PROTECTED] http://www.4CheapDomains.Net Need Advertising? Try DeerSearch.Com http://www.DeerSearch.com ----- Original Message ----- From: "Ross Wm. Rader" <[EMAIL PROTECTED]> To: "Andy Coates" <[EMAIL PROTECTED]>; "'Charles Daminato'" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, November 05, 2002 11:42 AM Subject: Re: REFUNDS, ETC... > > How dodgy is the area of registering the domains in your name, but > > "leasing" the adminstration of the domain? i.e. giving them control over > > the domain via tools, but they're not listed anywhere on the domain > > registrar. > > > > I think this is basically what Go Daddy are doing IIRC. > > I/We would be interested in hearing what y'all have to think about a > clarification of policy that we are about to implement. This statement is > basically our existing policy, however we've not really put it down on paper > anywhere except by implication in the contracts. We've changed a few things > internally that will hopefully allow us to efficiently followup this > statement with further clarifications on other existing policies - we've not > really paid a lot of attention to this type of thing in the past because of > a variety of competing interests (like adding new TLDs, tightening up > internal processes in support and sales, etc., etc., etc.), but at the end > of the day realize that you guys can only be as effective in dealing with > customers when we have been exceptionally clear on things like this. Just > sticking things in the contract without fully explaining what they mean > isn't all that helpful. Hopefully this effort will streamline things for > both us and our resellers. > > Our next policy meeting is this Thursday, so if you have any comments, it > would be useful to have them before them. I except that we will adopt this > language as written and publish it to our resellers shortly thereafter. If > any of you have concerns, I will work internally to address them - just drop > me a note off-list. > > POLICY COMMITTEE - DRAFT POLICIES > > > Tucows' Whois Policy > Tucows' standard whois policy states that the following contact information > will typically appear in the whois record. This policy is applicable to the > .com, .net, .org and .info TLD's only. Please note that other TLD's may > adopt alternative definitions. > > 1. Registrant > The individual or organization that registers a specific domain name and is > therefore the Registered Name Holder. This individual or organization holds > the right to use a specific domain name for a specified period of time, > provided certain conditions are met and the registration fees are paid. This > person or organization is the 'legal entity' bound by the terms of the > relevant service agreement with the registry operator for the TLD in > question. > > 2. Administrative Contact > The Administrative Contact is an individual, role or organization authorized > to interact with the registry or registrar on behalf of the Registrant. The > administrative contact should be able to answer non-technical questions > about the domain name's registration and the Registrant. In all cases, the > Administrative Contact is viewed as the authoritative point of contact for > the domain name, second only to the Registrant. > > 3. Technical Contact > The Technical Contact is the individual, role or organization that is > responsible for the technical operations of the delegated zone. This contact > likely maintains the domain name server(s) for the domain. The Technical > Contact should be able to answer technical questions about the domain name, > the delegated zone and work with technically oriented people in other zones > to solve technical problems that affect the domain name and/or zone. > > 4. Registrar > A person or entity that, via contract with Registrants, Resellers and a > Registry, provides front-end domain name registration services to > registrants, providing a public interface to registry services. > > In the situation where a Reseller elects to substitute its information for > the domain Registrant's in the whois service, Tucows has established the > following guidelines. These guidelines will ensure when it is and is not > appropriate for the Reseller to include its information in the organization > field. > > A Reseller may substitute its information for the domain's Registrant of > Record in the whois service when; > > 1. The party requesting the registration of the domain name has expressly > agreed to the Reseller doing so on their behalf. Resellers typically elect > to insert their information in the Registrant field when their customer has > asked them to do so for privacy purposes or when the domain name is offered > free to the customer when they agree to purchase additional services from > the Reseller. The Reseller must provide their customer's agreement as a > condition of an agreement between themselves and their customer, and must > keep a copy of this agreement to demonstrate the requisite consent. > > As such, the Reseller must: > > a) Clearly indicate in the terms of the agreement with their customer(s) > that they are acting on behalf of the Registrant. > b) Provide the Registrant's information upon request from either the > Registrant, the Registrar, from any third party pursuant to a dispute > policy, court action, or for any other lawful purpose. > c) Change the information at the request of the Registrant or Registrar. > d) Have clear policies in place for both transfers and renewals to eliminate > any ambiguity as to what happens to the domain upon its expiration date. > e) Insert the customer's information if and when they are required to do so > pursuant to a dispute policy or for any lawful purpose. > > Please note that, if the Reseller does elect to adopt this practice, from > Tucows' perspective they: > > a) Assume full responsibility and liability for the domain as that domain's > Registrant. This means that the Reseller will be a party to any dispute > that arises with respect to a particular domain name. > b) Clearly communicate to their customer that they are offering to them, the > use of a domain for a specified time period, for which they are the > Registrant of Record. > c) Have clear policies in place for both transfers and renewals to eliminate > any ambiguity as to what happens to the domain upon its expiration date. > > > It is inappropriate for the Reseller to edit the whois information at any > time unless they are doing so on behalf of the Registrant or they are listed > as the Registrant of Record. > > > Tucows' Domain Expiration Policy > From the date of registration, a domain belongs to the Registrant for one > year plus the 'grace' period specified by the respective Registry. During > the 'grace' period or at any time during the registration period, the domain > cannot be purchased, edited, or resold by the Reseller. At the end of these > periods, the domain, if it is not renewed, is returned to the Registry and > only becomes available after the Registry releases it. > > > > -rwr > > > > > "There's a fine line between fishing and standing on the shore like an > idiot." > - Steven Wright > > Got Blog? http://www.byte.org/blog > > Please review our ICANN Reform Proposal: > http://www.byte.org/heathrow > > > > ----- Original Message ----- > From: "Andy Coates" <[EMAIL PROTECTED]> > To: "'Charles Daminato'" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, November 05, 2002 5:00 AM > Subject: RE: REFUNDS, ETC... > > > > > There's another side to this... > > > > > > You cannot "force" yourself to be the Administrative contact. > > > The Registrant must agree to have you as the Administrative > > > contact, and even then you're only empowered (as the Admin > > > contact) to administratively handle the domain. You are not > > > allowed to "steal" the domain away from someone for non-payment > > > (they must still be listed as the legal registrant). > > > > How dodgy is the area of registering the domains in your name, but > > "leasing" the adminstration of the domain? i.e. giving them control over > > the domain via tools, but they're not listed anywhere on the domain > > registrar. > > > > I think this is basically what Go Daddy are doing IIRC. > > > > Andy. > > >
