RIPE handles
                                  and
                        the 'status' attribute
                          in the RIPE-database


                           Document: ripe-126       
                         
                Updated by: ripe-127 ('status:' attribute)              
                


                                RIPE-126


Introduction

   This document describes two additions to the RIPE database, which
   were implemented during the last weeks that Marten Terpstra
   maintained the RIPE database software: RIPE-handles, and the
   status-attribute.


RIPE-handles

   The design of the RIPE-database stores contact info on networks in
   separate 'person' objects:
      inetnum:     193.0.1.0
      netname:     RIPE-EXP
      descr:       Sample database-assignment, RIPE NCC
      descr:       Amsterdam, Netherlands
      country:     NL
      admin-c:     Anne Lord
      tech-c:      Mirjam Kuehne
      changed:     GeertJan.deGroot@ripe.net 950310
      source:      RIPE

      person:      Anne Lord
      address:     RIPE Network Coordination Centre (NCC)
      address:     Kruislaan 409
      address:     NL-1098 SJ Amsterdam
      address:     Netherlands
      phone:       +31 20 592 5065
      fax-no:      +31 20 592 5090
      e-mail:      anne@ripe.net
      changed:     anne@ripe.net 941207
      source:      RIPE
   This works only if the name of the person is unique, as the name of
   the person is used as search key to locate the person-object.  With
   the growth of the Internet, this gives problems as it becomes more
   and more likely that person names are no longer unique.





                              May 19, 1995





                                 - 2 -


   To overcome this problem, handles are introduced as unique search key
   to locate person-objects:
      inetnum:     193.0.1.0
      netname:     RIPE-EXP
      descr:       Sample database-assignment, RIPE NCC
      descr:       Amsterdam, Netherlands
      country:     NL
      admin-c:     AL12-RIPE      <------
      tech-c:      MK16-RIPE      <------
      changed:     GeertJan.deGroot@ripe.net 950310
      source:      RIPE

      person:      Anne Lord
      address:     RIPE Network Coordination Centre (NCC)
      address:     Kruislaan 409
      address:     NL-1098 SJ Amsterdam
      address:     Netherlands
      phone:       +31 20 592 5065
      fax-no:      +31 20 592 5090
      e-mail:      anne@ripe.net
      nic-hdl:     AL12-RIPE
      notify:      anne@ripe.net
      changed:     ripe-dbm@ripe.net 920826
      changed:     anne@ripe.net 941207
      source:      RIPE

   A RIPE-handle consists of 3 parts:
   - prefix
     the prefix is built from the first letters of each word of a
     person's name, e.g. John Doe would yield JD as prefix.
   - index
     the index is used to make the handle unique. It consists of a
     decimal number that is incremented to obtain a letter/digit
     combination that is unique.  If JD1 is already assigned, then the
     next available handle would be JD2, JD3, et cetera.
   - suffix
     the suffix is used to avoid clashes between the regional
     registries, without the need to check if a handle is already
     assigned on a global scale.  The suffix has the fixed value '-RIPE'
     for new handles that are generated by the RIPE community.  (handles
     generated by APNIC have a two-letter country code suffix
     (e.g. '-JP'), and the Internic does not use a suffix for historical
     reasons).

   For example, John Doe could yield JD1-RIPE. If this handle is already
   assigned, then JD2-RIPE is a candidate, or JD3-RIPE, until a free
   slot is found. Note that the actual value of the handle is not
   important as long as it is unique.



                              May 19, 1995





                                 - 3 -


   It is perfectly legal to use