CURRENT_MEETING_REPORT_

Reported by Mark Kosters/InterNIC

Minutes of the RWhois Operational Development Working Group (RWHOIS)


Agenda

   o Review issues raised at BOF
   o Discuss proposed charter
   o Status of InterNIC version 1.0
      -  Client
      -  Server
      -  Tools
   o Protocol issues
   o Minimum requirements for an RWhois registration server
   o Required object and attribute set
      -  SOA objects
      -  Network objects
      -  Domain objects
      -  Host objects
      -  AS objects
      -  Role account objects
      -  Individual objects
      -  Maintainer objects
   o Discussion of operational deployment schedule
      -  InterNIC (NIC for the Americas and Global IR)
      -  US service providers
      -  AP region
      -  European region
      -  US domain


Discussion

Scott Williamson started the session with a review of the issues raised
at the previous BOF in San Jose.  The first issue was reducing the
complexity of the server with display types being moved to the client.
It was noted that additional protocol elements may be needed if this was
to happen.  The second issue was placing the supported directives within
the %RWhois identification header.  This would be accomplished with
hexadecimal codes.

Additional discussion ensued about security, and the recommendation was
made to follow the appropriate working group's output.  It was noted
that RWhois can follow any type of security protocol since it has been
left open for specific implementations.

Server administration was then discussed.  The group recommended the
following secondary server requirements:


   o At least two secondaries with one being the parent.

   o If queried for a secondary's information and a parent, it will not
     answer unless explicitly mentioned.

   o The SOA record should have a last update time attribute.


It was agreed that the RWhois attributes should follow the RIPE model
whenever possible.  There are attributes within the RIPE specification
that need to be added.  Mark Kosters will make a recommendation to the
RIPE working groups for the additional attributes.

At closing, the working group discussed deployments of RWhois within the
Internet.  There are servers within the AP region, the US and South
Africa.  RIPE is to modify their server to be at least minimally
conformant.


Action Items

   o Scott Williamson and Mark Kosters will release version 1.0Beta as
     soon as it becomes relatively stable.

   o Mark Kosters to work with the RIPE working groups on additional
     optional and mandatory attributes.