[registrars] Ballot Request: Adopt as Constituency Position

[Ross Rader]

For future reference, only one endorsement is required to validate an 
amendment for consideration in the balloting process.

Jay Westerdal wrote:
> Thanks Maxine,
> I believe that makes three.
>  
> Jay Westerdal
> Name Intelligence, Inc.
> http://www.nameintelligence.com <http://www.nameintelligence.com/>   
> 
> 
>   _____  
> 
> From: Maxine Appleby [mailto:mappleby at Hosting.com] 
> Sent: Thursday, October 06, 2005 11:32 AM
> To: Jay Westerdal
> Cc: registrars at dnso.org
> Subject: Re: [registrars] Ballot Request: Adopt as Constituency Position
> 
> 
> I second this amendment 
> Maxine Appleby
> 
> www.Hosting.com
> 
> Toll free 1-800-455-1795 or  +1 (781)478-1673
> 
> 
> 
> "Few are those who see with their own eyes and feel with their own hearts."
> - Albert Einstein
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Jay Westerdal wrote:
> 
> 
> I propose an amendment to the motion:
> 
> 
> 
> Keep Expiration Date in the registry output.
> 
> 
> 
> I propose Registries follow a documented procedure for showing expiration
> 
> date since they are not authoritative instead of just hiding the field flat
> 
> out:
> 
> 
> 
> On expiration:
> 
> A) if Auto-renewed by Registry
> 
>    1) Hide Expiration date with the words "Pending Registrar Action".
> 
>    2) After 45 days, set expiration date to be a year from initial
> 
> Expiration Date.
> 
> B) if Explicitly renewed by Registrar
> 
>    1) Show new date  
> 
> 
> 
> Thanks,
> 
> 
> 
> Jay Westerdal
> 
> Name Intelligence, Inc.
> 
> http://www.nameintelligence.com 
> 
> 
> 
> -----Original Message-----
> 
> From: owner-registrars at gnso.icann.org
> 
> [mailto:owner-registrars at gnso.icann.org] On Behalf Of Bruce Tonkin
> 
> Sent: Wednesday, October 05, 2005 6:30 PM
> 
> To: registrars at dnso.org
> 
> Subject: RE: [registrars] Ballot Request: Adopt as Constituency Position
> 
> 
> 
> Hello All,
> 
> 
> 
> For the purposes of ensuring that we can eventually converge on an
> 
> agreed version of a position paper on WHOIS, I second this motion from
> 
> Ross Rader so that the formal discussion period can commence as per our
> 
> bylaws.
> 
> 
> 
> I am of course open to suggestions from the constituency to improve the
> 
> motion or make changes to ensure its support.
> 
> 
> 
> I think it is important at this stage to get registrars agreement around
> 
> the core purpose of WHOIS in the context of ICANN's mission.
> 
> 
> 
> Regards,
> 
> Bruce Tonkin
> 
> 
> 
>   
> 
> -----Original Message-----
> 
> From: owner-registrars at gnso.icann.org 
> 
> [mailto:owner-registrars at gnso.icann.org] On Behalf Of Ross Rader
> 
> Sent: Wednesday, 5 October 2005 3:37 AM
> 
> To: registrars at dnso.org
> 
> Subject: [registrars] Ballot Request: Adopt as Constituency Position
> 
> 
> 
> Registrars;
> 
> 
> 
> Per Whois Task Force 123's Terms of Reference, we are 
> 
> required to adopt a position concerning the purpose of the 
> 
> Whois service and the purpose of the Registered Name Holder, 
> 
> Technical and Administrative contacts (see below for an 
> 
> excerpt of the terms of reference for the task force).
> 
> 
> 
> As a representative to this task force and with the input and 
> 
> assistance of the other representatives to this task force, I 
> 
> have prepared a policy position that I seek to have adopted 
> 
> by the constituency. This position statement is attached.
> 
> 
> 
> I therefore would like to make a motion as follows;
> 
> 
> 
> ***MOTION
> 
> Whereas, the Registrar Constituency has considered a range of 
> 
> issues related to the intended and appropriate purpose of the 
> 
> gTLD Whois System, and;
> 
> 
> 
> Whereas, the Registrar Constituency has considered a range of 
> 
> issues related to the intended and appropriate purpose of the 
> 
> Registered Name Holder, Administrative and Technical Contacts, and;
> 
> 
> 
> Whereas, the Registrar Constituency seeks timely resolution 
> 
> of these matters in a consensus-based manner that takes into 
> 
> account the needs of all stakeholders including individual 
> 
> and corporate domain name registrants, the internetworking 
> 
> community and gTLD Registries and Registrars, therefore;
> 
> 
> 
> Be it resolved that the Registrar formally adopts the 
> 
> position statement entitled "The Purpose of the gTLD Whois 
> 
> System and Specific Contact Records" and require its task 
> 
> force representatives to advocate these positions within the 
> 
> Task Force and other ICANN fora as appropriate.
> 
> ***ENDofMOTION
> 
> 
> 
> I have attached both Word and PDF versions of this document 
> 
> to this message. I will also be forwarding this draft 
> 
> document to the Task Force
> 
>   as a heads up concerning our deliberations.
> 
> 
> 
> If you have any questions, please let me know. Your support 
> 
> for this motion would be sincerely appreciated.
> 
> 
> 
> -ross
> 
> 
> 
> 
> 
> Excerpt from WhoisTF123 Terms of Reference;
> 
> (1) ...the purpose of the WHOIS service in the context of 
> 
> ICANN's mission and relevant core values, international and 
> 
> national laws protecting privacy of natural persons, 
> 
> international and national laws that relate specifically to 
> 
> the WHOIS service, and the changing nature of Registered Name Holders.
> 
> 
> 
> (2) ...the purpose of the Registered Name Holder, technical, 
> 
> and administrative contacts, in the context of the purpose of 
> 
> WHOIS, and the purpose for which the data was collected. Use 
> 
> the relevant definitions from Exhibit C of the Transfers Task 
> 
> force report as a starting point (from 
> 
> http://www.icann.org/gnso/transfers-tf/report-exhc-12feb03.htm):
> 
> 
> 
> "Contact: Contacts are individuals or entities associated 
> 
> with domain name records. Typically, third parties with 
> 
> specific inquiries or concerns will use contact records to 
> 
> determine who should act upon specific issues related to a 
> 
> domain name record. There are typically three of these 
> 
> contact types associated with a domain name record, the 
> 
> Administrative contact, the Billing contact and the Technical contact.
> 
> 
> 
> Contact, Administrative: The administrative contact is an 
> 
> individual, role or organization authorized to interact with 
> 
> the Registry or Registrar on behalf of the Domain Holder. The 
> 
> administrative contact should be able to answer non-technical 
> 
> questions about the domain name's registration and the Domain 
> 
> Holder. In all cases, the Administrative Contact is viewed as 
> 
> the authoritative point of contact for the domain name, 
> 
> second only to the Domain Holder.
> 
> 
> 
> Contact, Billing: The billing contact is the individual, role 
> 
> or organization designated to receive the invoice for domain 
> 
> name registration and re-registration fees.
> 
> 
> 
> Contact, Technical: 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.
> 
> 
> 
> Domain Holder: The individual or organization that registers 
> 
> a specific domain name. This individual or organization holds 
> 
> the right to use that 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."
> 
> 
> 
>     
> 
> 
> 
> 
> 
>   
> 
> 
>