From memsvcs at arin.net Tue Nov 2 10:34:04 1999 From: memsvcs at arin.net (Member Services) Date: Tue, 2 Nov 1999 10:34:04 -0500 (EST) Subject: Database Implementation WG - Notes from Denver Message-ID: <199911021534.KAA23528@ops.arin.net> As promised, here are the notes for the Database Implementation Working Group discussion held October 19th, 1999 at the Denver Marriott City Center as part of ARIN's Public Policy Meeting: Topics of Discussion: --------------------- 1. SWIP and in-addr.arpa authentication procedures 2. RWHOIS technology 3. Improvements to SWIP 4. Potential re-use of historically-unique network registration handles 5. Publically-accessible customer information/reassignments 6. Possible additions to POC fields in ARIN's WHOIS Attendee List: -------------- petrovic at corp.earthlink.net (Mark Petrovic) martind at uu.net (Dawn Martin) dploher at level3.net (Darren Loher) kjh at cert.org (Kevin Houle) pwilson at apnic.net (Paul Wilson) jason at pathwaynet.com (Jason Smith) mike at coloradocomputing.com (Mike Booco) Fran.Lamerson at eds.com Tanya.Hinman at cwusa.com Ron.Muir at corp.bellsouth.net gene at netreach.net (Gene Jakominich) algold at co.rnp.br (Alexandre Grojsgold) mike at netwright.net (Michael Lieberman) repete at cncx.com (Pete Bowden) awm at cv.net (Aram Mirzadeh) david at qwest.net (David Kessens) markk at netsol.com (Mark Kosters) dcheline at telocity.net (Doug Cheline) linda at sat-tel.com (Linda Werner) rogerh at arin.net (Roger Halls) kerr at arin.net (Shane Kerr) michaelo at arin.net (Michael O'Neill) 1. Improvements to SWIP & reverse server security ------------------------------------------------- * Right now ARIN's systems and analysts review only * Discussion and suggestions for password storage and web-based updates * Any improvements to ARIN's authorization and authentication system would facilitate ISPs' control over reassigments (SWIPs) and in-addr information in network records * ARIN staff will communicate a proposal to: 1. change (based on RIPE-121 and RIPE-189 authentication and authorization) for ARIN maintainer database 2. request input from dbwg e-mail list and membership on these changes 3. send RIPE document links to DBWG. 4. post a link to relevant RIPE documents on ARIN web-site 2. RWHOIS --------- * The group discussed RWHOIS mirroring and client functions * Mark Kosters reported on the state of RWHOIS development, bug fixes, and progress toward version 2.0 of the software by Network Solutions engineer David Blacka * Shane Kerr will propose a list of near-term fixes to ARIN RWHOIS contributions to include 1. checking up on root.rwhois.net forwarding 2. impact of registering external RWHOIS servers with ARIN RWHOIS 3. publish RWHOIS information and links on ARIN web page 4. initiate ARIN RWHOIS web page 5. incorporate information about future updates to RWHOIS client from www.rwhois.net developers into ARIN web page 6. investigate any updates to mirrored server capabilities 7. request input from broader ARIN membership to determine level of interest and priority in future ARIN RWHOIS efforts 3. SWIP (Shared WHOIS Project) ------------------------------ * ARIN members reported problems with deletion failures * ARIN staff to investigate a new parser to allow members to parse with "on-demand" error reporting - Pete Bowden has forwarded ARIN staff with some older code to do some SWIP parsing. ARIN staff will investigate the utility of this program. * ARIN staff to fix a problem with subject line changes that attach only "Re: Your Mail" when auto-replying to SWIP 4. Potential re-use of historically-unique network registration handles ----------------------------------------------------------------------- * Group supported a change to database to allow re-use of network handles * ARIN staff to investigate impact on registration software and report back via e-mail to dbwg e-mail list 5. Public registration of reassignments --------------------------------------- * RFC 2050 information for assignments required in both SWIP and RWHOIS * Policy group and members need to address concerns about ISPs' need for customer data protection * Revisions to RFC 2050 should account for privacy, competition, and operational concerns 6. Extend POC information ------------------------- * ARIN staff will investigate extension of POC information associated with network number records to include abuse and NOC contacts * ARIN staff will also investigate how any new POC information would impact templates and existing contact database If you have any addition to these notes, please feel free to post them to this dbwg mailing list or e-mail them to: member-services at arin.net Don't forget: if you are looking for a complete listing of those subscribed to dbwg at arin.net, you can send an e-mail to majordomo at arin.net with "who dbwg" in the body of the e-mail (without the quotes). Regards, David R Huberman, Membership Services Coordinator American Registry for Internet Numbers