UWho and CRISP: Status Update for the Whois Task Force

1
UWho and CRISPStatus Update for the Whois Task
Force

• Andew Newton
• Mark Kosters
• VeriSign Labs
• August 20, 2002

2
UWhat?

• Universal Whois
• UWho is the name of the work VeriSign has
  committed to in agreement with ICANN (Appendix
  W.)
• http//uwho.verisignlabs.com/
• Formal public consultations
• business, intellectual property holders (Aug/01)
• civil liberties, other ngos (Nov/01)
• international input (Nov/01)
• Informal public consultations/presentations
• RIPE 40 (Oct/01)
• NANOG 23 (Oct/01)
• RIPE 41 (Jan/02)
• NANOG 24 (Feb/02)
• CENTR (Feb/02)
• APRICOT 2002 (Mar/02)
• APNIC 13 (Mar/02)
• ARIN IX (Apr/02)

3
CRISP?

• Cross Registry Information Service Protocol
• IETF Applications Area Working Group
• First meeting held at IETF 54, Yokohama, Japan,
  in July, 2002.
• http//www.ietf.org/html.charters/crisp-charter.ht
  ml
• What is VeriSigns role here?
• Appendix W. requires Universal Whois to be an
  open starndard.
• VeriSign is contributing UWho work to the IETF as
  a starting point.
• The IETF process is open and anybody can
  participate.

4
CRISP Goals

• A better whois.
• Not a science project.
• Universal means distributed, not centralized.
• Support policy decisions, not define them.
• To be unencumbered by the shackles of port 43.

5
The Requirements Process

• The process to refine the requirements
• Identify the community of users
• Decide on scope
• List needs
• Determine features
• The requirements are still being derived and
  participation is welcome.
• draft-ietf-crisp-requirements-00.txt

6
The Benefits of Unity

• While the data contained in the different
  registries isnt the same, they all have common
  base requirements.
• Data mining prevention
• Need for machine consumable data
• Access control
• Etc
• One standard, not 3 or 4 or 5.
• A common understanding.

7
The Benefits of An Open Standard

• Provides a known direction for implementers.
• Allows input from end-users.
• Helps with the development of common code bases.
• Encourages ideas not yet imagined.

8
The State of CRISP

• CRISP is in the early stages.
• Requirements draft in-progress.
• draft-ietf-crisp-requirements-00.txt
• Two protocol solutions submitted.
• LDAP-Whois
• IRIS (XML-based)
• Early participation would be nice.

9
Conclusion

• Your comments, opinions, and ideas are welcome.
• CRISP web page http//www.ietf.org/html.charters/
  crisp-charter.html
• CRISP mailing list ietf-not43_at_lists.verisignlabs.
  com
• To subscribe
• https//lists.verisignlabs.com/mailman/listinfo/ie
  tf-not43