We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAngie Talton
Modified over 5 years ago
© 2003 Public Interest Registry Whois Workshop Introduction to Registry/Registrar Issues Presented by Bruce W. Beckwith VP, Operations June 23, 2003 Serving the Public Interest
© 2003 Public Interest Registry Serving the Public Interest Background In the “early days”, whois was used by network operators (ISPs, web-hosters, infrastructure providers) to identify domain holders – in case of email problems, DOS attacks, etc. The data collected in whois was rudimentary – registrant, administrative, technical and billing contacts
© 2003 Public Interest Registry Serving the Public Interest Background (continued) Data elements historically collected in whois: –Registrant (though no telephone number or email address) –Administrative Contact (usually web- hoster or ISP) –Technical Contact (usually ISP) –Billing Contact (sometimes registrant, sometimes web-hoster, depended on retail model used to register domain)
© 2003 Public Interest Registry Serving the Public Interest Background (continued) In 1999, ICANN required registrars to provide both web-based and Port 43 access to whois –Not all registrars have an operational whois – the requirement is detailed in the RAA –Most of top 10 gTLD registrars limit queries per IP address – maintain that this protects customers & system overload Bulk Whois access also required –Registrars must make available their list of registrants (who do not “opt-out”) for a fee “not to exceed US $10,000” –Of the top 10 TLD registrars, only a fraction offer bulk whois with contracts that conform to the ICANN contractual requirements (most include provisions that are not “in the spirit” of the contracts)
© 2003 Public Interest Registry Serving the Public Interest Background (continued) In 2001, ICANN required registries to provide both web-based and Port 43 whois –Registries with “thin” data – VCNR and PIR (at start) only show minimal data PIR is converting from “thin” to “thick” throughout 2003 –Registries with “thick” data show full registrant record – same as registrars –GNR (.name) was able to change ICANN contracts to offer minimal data (to protect their registrants – individuals)
© 2003 Public Interest Registry Serving the Public Interest The Data Registrars manage the registrant (customer) relationship –Collect domain name record details at registration –Manage the updating of the data –Furnish it to “thick” registries –Provide access via Whois Registries simply provide access via Whois –if.com/.net, then “thin” display –if.org (in transition),.info,.biz, new sponsored gTLDs, then “thick” display
© 2003 Public Interest Registry Serving the Public Interest Issues Many interests now want to keep whois status quo: –IP community – to protect marks –Law Enforcement – to help investigations –Network Operators – in case of attacks Many interests want to restrict whois data: –Privacy Advocates – protect PII –European Union - protect PII and data export –Registrars – retain customers/market share –Registries – PII concerns, not to violate EU restrictions
© 2003 Public Interest Registry Serving the Public Interest Some Misconceptions Spam is only based on domain registrations –If you post to public mailing lists, “bots” harvest your email address –If you purchase anything on-line and the retailer does not have a policy against spam, your email address will be sold Bulk Whois is the major source of email addresses for spammers –Since so few registrars offer Bulk Whois files, spammers use other methods to harvest email addresses
© 2003 Public Interest Registry Serving the Public Interest Some Realities The registry zone files are used to identify changes to each TLD –The best source for spammers & others Via contractual requirements, registrars and registries must make data freely available to anyone –Enables data mining/harvesting of Whois records
© 2003 Public Interest Registry Serving the Public Interest For Further Discussion Allow zone files to be restricted to legitimate uses –Necessary for IP, ISPs, network operators, etc. –Today, registries must comply with any request – cannot decline a request for free zone file access Limit whois access for legitimate purposes –Most queries can be addressed by “domain available” or “domain not available” response –Requires education to community –Requires interested parties to define “legitimate purposes” Engage community in refining the purposes for whois in this changed world and environment –Much has changed since “the early days”, registrar competition in 1999, registry competition in 2000
© 2003 Public Interest Registry Whois Workshop Introduction to Registry/Registrar Issues Contact: firstname.lastname@example.org June 23, 2003 Serving the Public Interest
© 2003 Public Interest Registry Whois Workshop Registrant/User Classification & Current Practices Panel Presented by Bruce W. Beckwith VP, Operations October.
Generic Names Supporting Organisation Bruce Tonkin Chair, GNSO Council.
Whois Task Force GNSO Public Forum Wellington March 28, 2006.
Update on Whois TF March 25, Objectives of the Task Force 1)Define the purpose of the Whois service. [complete] 2)Define the purpose of the Registered.
KnujOn Review of Registrar Obligations, Compliance, and Permitted Illicit Activity.
CcTLD Meetings Rome 2004 WHOIS & Data Privacy Jean-Christophe Vignes Registry Liaison Manager.
Governmental Advisory Committee New gTLD Program Briefing 19 June 2010.
Handling Internet Network Abuse Reports at APNIC 21 October 2010 LAP-CNSA Workshop, Melbourne George Kuo.
A Next Generation Registration Directory Service (RDS) EWG Briefing for the IETF by Chris Disspain Monday Nov 4, 2013.
Addressing spam and enforcing a Do Not Registry using a Certified Electronic Mail System Information Technology Advisory Group, Inc.
Bangkok October 2005 Slide 1 Whois Services Jaap Akkerhuis
Registrar experiences with WHOIS Bruce Tonkin Melbourne IT Ltd.
Slide 1 Whois Workshop, ICANN Montreal Meeting Topic, June 2003 Privacy and Data protection consideration of the Whois directories discussion Diana ALONSO.
June 24, 2003 Montréal, Public Forum Whois and ccTLD naming policy Whois and ccTLD naming policy Bart Boswinkel SIDN.
.| The Trusted Channel Centric Marketplace Domain Name Transfers & Domain Delegation.
Domain Name Registrant Data: The Privacy Questions Alan Davidson Center for Democracy and Technology
Introduction to ICANN’s new gTLD program. A practical example: the Dot Deloitte case. Jan Corstens, Partner, Deloitte WIPO Moscow, 9 Dec 2011.
Implementation Recommendation Team (IRT) Proposal Comments Sue Todd, Director, Product Management Monday 11 May 2009, San Francisco.
Domain Name System | DNSSEC. 2 Internet Protocol address uniquely identifies laptops or phones or other devices The Domain Name System matches IP.
#ICANN51 1 Translation and Transliteration of Contact Information PDP Working Group Activities Update ICANN Los Angeles Meeting October 2014 Chris Dillon.
© 2020 SlidePlayer.com Inc. All rights reserved.