120 likes | 236 Vues
Whois Services. Jaap Akkerhuis jaap@nlnetlabs.nl. Overview. The whois protocol The whois function Whois and databases Privacy concerns Thick and Thin registries New: Crisp. The Whois Protocol. Nicname/whois on port 43 RFC 812 (Very Obsolete) RFC 954 (Obsolete) RFC 3912 Protocol:
E N D
Whois Services Jaap Akkerhuis jaap@nlnetlabs.nl
Overview • The whois protocol • The whois function • Whois and databases • Privacy concerns • Thick and Thin registries • New: Crisp
The Whois Protocol • Nicname/whois on port 43 • RFC 812 (Very Obsolete) • RFC 954 (Obsolete) • RFC 3912 • Protocol: • Client opens TCP connection at port 43, sends ASCII, ends with CRLF • Server sends reaction, ends with CRLF, close connection
Protocol Characteristics • Now authentication • No authorization • 1 Question, 1 response • Like the finger protocol (RFC 1288)
Whois Function • Contents of whois is undefined • Information about anything • people • addresses • conference room scheduling • In ccTLD world • publishing of social data • registrant, • registrar • billing contact
Whois and database • Most RIRs: Whois information is the database information • Lots of ccTLD's: Whois information is alimitedview of database contents • only for interest of ''the public'' • details left out: • Why should the world know about the billing contact?
Privacy concerns (1) • Some privacy laws forbid some data to be public • Motivate why you publish what • just ''because others do it'' won't work
Privacy concerns (2) • Data mining prevention • is outside the protocol! • query rate limiting by IP # • No public whois service is an option • Just a web server with whois like info • Detailed info will be asked anyway • More work for the helpdesk • Define that process
Thin and Thick Model • Thin • Registry: Minimum data • name server delegation info • Some registrar data • Registrar: All other data • registrant info (social data) • Runs the whois • Tick • Registry has all data and provides whois service • controls format and info • Registrar often still responsible for the data
Thin model Problems • Multiple whois formats • Different info per registrar • Where is the whois server anyway? • Methods: • SRV records in DNS helps a bit • FreeBSD whois • based on silly DNS tricks
New: CRISP • Cross Registry Information Sharing Protocol • Global entry point for a World Wide whois • Local policy for access • Work in process • RFC 3707 (requirements) • Levels of Authentication • users • ä lawyers • law enforcement • Regular expression look up