current status
  overview of whois port 43, single command line ended in CRLF, closes
  connection when output is finished

  whois users RIRs, routing registries, domain registries, registrars
  #1 and #2 are close #3 is a bit different
  
How flexible are users to change? - different user outputs ARIN, RIPE,
   registry are examples. free text vs tagged formats

enhancements
  database referrals for id - keep data in one place
  fixed set of minimal data, common format, server to server communication
    issues

Andy Newton on rldap
  taken whois and placed in ldap, uses acls to allow people private
  access, structured data
  registrar, registry data split into separate sets of servers
  registry ldap server and its function - lists domains and nameservers
    if you bind with userid and passwd you can see the registration date
  registrar ldap server and its function
    lists contacts, org info, and nameservers
    if you bind has a contact, you can see more specific info
  web site is a sample ldap client and shows how you can use this system
  what we will do
    transition ldap service to VGRS
    open source openldap whois-> ldap gateway
    open source gui for ldap client that uses ldap

Rick: how will this gateway will work?
Karl: why xml and ldap 
Andy: it is a different use
Karl: privacy concernt
Andy: acls can provide for this
Rick: does it support ip registries
Andy: no it does not
Paul: waste of time
Rick: problem of not knowing scope
Patrick: good idea to show example
Rick: whois - use whois for various authentication means it is broken
Dave Crocker: public info - always been this way
Karl: privacy is a issue
Paul: whois is stupid - is it info or port
Joao: it is a small info and works off of 43
Patrick: two things need a directory service and second is service off of
   port 43
John: expand on Hoffman's comment - need to procisely define the protocol
  many will break if do anything
Patrick: whois has a well defined 
John: whois is the second most simple protocol
Joao: description of RIPE's implementation of referral
John: as soon as the client sees anything like a referral, it will break
Karl: need a new protocol
Patrick: have urgency to fix what we have now
register.com: need a few twitches to make it works
Rick: just normalize what we have here
Eric: was optomistic but am no longer with privacy issue
Paul: don't put in referrals but don't use port 43
register.com: most common use is for domain related info
John: can you prove this with internal use by other whois services
Karl: how much is speculation?
Patrick: whois is not ascii - it is stuff ended with <CRLF>
Joao: instruct with what the server is what to do
John: need to avoid clients dying a bad death - need a new port
Rick: propose an alternate - specify what the command parameter set is
John: difficulty is error handling  - let it die
Dave Crocker: believe it does not require heuristics to make it right
Unknown: let it be or move on - consensus
Paul: make a new port or modify whois
Karl: invent a new protocol?
Patrick: background on this bof - parse attribute value pairs, follow referrals,
  character set info, and problems with non-uniq handles
  call to invent a new protocol? consensus is to invent a new protocol
  consensus on forma
Shockey: fix things in whois or move on
Patrick: create mailing list in attempt to solve both - fix current whois
  or create a new protocol - have another bof at the next ietf
Rick: Scope of mailing list is for RIPE only
Joao: this is appropriate, mailing list will be db-wg@ripe.net