const char *Templates_v[] = {
"The aut-num class:\n\
\n\

      The aut-num object describes the details of the
      registered owner of an Autonomous System and their
      routing policy for that AS. See ripe-181 and
      RFC-BGP4 for details.
   \n\
\n\
aut-num:     [mandatory]  [single]     [primary/look-up key]\n\
as-name:     [optional]   [single]     [ ]\n\
descr:       [mandatory]  [multiple]   [ ]\n\
as-in:       [optional]   [multiple]   [ ]\n\
as-out:      [optional]   [multiple]   [ ]\n\
cross-nfy:   [optional]   [multiple]   [inverse key]\n\
cross-mnt:   [optional]   [multiple]   [inverse key]\n\
interas-in:  [optional]   [multiple]   [ ]\n\
interas-out: [optional]   [multiple]   [ ]\n\
as-exclude:  [optional]   [multiple]   [ ]\n\
default:     [optional]   [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
tech-c:      [mandatory]  [multiple]   [inverse key]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [mandatory]  [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the aut-numclass are defined below:\n\
\n\
aut-num
      The autonomous system number.  This must be a uniquely
      allocated autonomous system number from an AS registry
      (e.g.RIPE NCC, the Inter-NIC, etc).
    
      "AS"&lt;positive integer between 1 and 65535&gt;
    \n\
as-name
      A descriptive name associated with an AS.
    
      Uppercase letters, dashes ("-") and digits, no spaces.
      Must start with a letter.
    \n\
descr
      A short decription of this object.
    
      All characters possible.
    \n\
as-in
      as-in
    
      INSERT as-in desc here.
    \n\
as-out
      as-out
    
      INSERT as-out desc here.
    \n\
cross-nfy
      cross-nfy
    
      INSERT cross-nfy desc here.
    \n\
cross-mnt
      cross-mnt
    
      INSERT cross-mnt desc here.
    \n\
interas-in
      interas-in
    
      INSERT interas-in desc here.
    \n\
interas-out
      interas-out
    
      INSERT interas-out desc here.
    \n\
as-exclude
      as-exclude
    
      INSERT as-exclude desc here.
    \n\
default
      default
    
      INSERT default desc here.
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
tech-c
      A technical contact.
    
      &lt;NIC-handle&gt;
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The domain class:\n\
\n\

      A domain object represents a Top Level Domain (TLD) or
      other domain registrations. It is for information only.
   \n\
\n\
domain:      [mandatory]  [single]     [primary/look-up key]\n\
descr:       [mandatory]  [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
tech-c:      [mandatory]  [multiple]   [inverse key]\n\
zone-c:      [mandatory]  [multiple]   [inverse key]\n\
nserver:     [optional]   [multiple]   [inverse key]\n\
sub-dom:     [optional]   [multiple]   [inverse key]\n\
dom-net:     [optional]   [multiple]   [ ]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [optional]   [multiple]   [inverse key]\n\
mnt-lower:   [optional]   [multiple]   [inverse key]\n\
refer:       [optional]   [single]     [ ]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the domainclass are defined below:\n\
\n\
domain
      IP domain name.
    
      Full qualified domain name without trailing ".".
    \n\
descr
      A short decription of this object.
    
      All characters possible.
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
tech-c
      A technical contact.
    
      &lt;NIC-handle&gt;
    \n\
zone-c
      NIC-handle of the person with authority over a zone.
    
      &lt;NIC-handle&gt;
    \n\
nserver
      List of nameservers for a domain object; a minimum
      of two is mandatory .
    
      &lt;Fully qualified domain name(s) without trailing "."&gt;
      OR &lt;IP Address(es) of the nameserver(s)&gt;
    \n\
sub-dom
      List of the sub-domains of a domain
    
      &lt;Relative domain name to the domain&gt;
    \n\
dom-net
      List of IP networks in a domain.
    
      Dotted quad including trailing 0's.
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
mnt-lower
      The identifier of a registered mntner object used for
      hierarchical authorization and authentication.
    
      &lt;mntner&gt;
    \n\
refer
      Whois referral for domain objects
    
      &lt;Type&gt; &lt;host&gt; &lt;port&gt;
      &lt;Type&gt; is one of RIPE, Internic or SIMPLE. Specifies whois
      query style.
      &lt;host&gt; specifies the host to be queried.
      &lt;port&gt; the TCP port number (optional: 43 is the default)
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The inet6num class:\n\
\n\

      An experimental object for IP Version 6 addresses.
   \n\
\n\
inet6num:    [mandatory]  [single]     [primary/look-up key]\n\
netname:     [mandatory]  [single]     [primary/look-up key]\n\
descr:       [mandatory]  [multiple]   [ ]\n\
country:     [mandatory]  [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
tech-c:      [mandatory]  [multiple]   [inverse key]\n\
rev-srv:     [optional]   [multiple]   [inverse key]\n\
status:      [generated]  [single]     [ ]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [optional]   [multiple]   [inverse key]\n\
mnt-lower:   [optional]   [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the inet6numclass are defined below:\n\
\n\
inet6num
      Full IP version 6 address.
    
      &lt;ip6num&gt;/&lt;prefix length&gt;
    \n\
netname
      The name of a range of IP address space.
    
      &lt;uppercase letter&gt;&lt;uppercase alphanumeric, "-"&gt;
    \n\
descr
      A short decription of this object.
    
      All characters possible.
    \n\
country
      ATB country DESC Name of the country of the admin-c.
    
      ATB country FRMT 2 letter uppercase ISO 3166 country code.
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
tech-c
      A technical contact.
    
      &lt;NIC-handle&gt;
    \n\
rev-srv
      Domain name server for a range of IP addresses.
    
      Fully qualified name without trailing "."
    \n\
status
      status
    
      INSERT status desc here.
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
mnt-lower
      The identifier of a registered mntner object used for
      hierarchical authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The inetnum class:\n\
\n\

      An inetnum object contains information on allocations
      and assignments of IP address space. See ripe-142 for
      information on requesting IP address space.
   \n\
\n\
inetnum:     [mandatory]  [single]     [primary/look-up key]\n\
netname:     [mandatory]  [single]     [primary/look-up key]\n\
descr:       [mandatory]  [multiple]   [ ]\n\
country:     [mandatory]  [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
tech-c:      [mandatory]  [multiple]   [inverse key]\n\
rev-srv:     [optional]   [multiple]   [inverse key]\n\
status:      [generated]  [single]     [ ]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [optional]   [multiple]   [inverse key]\n\
mnt-lower:   [optional]   [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the inetnumclass are defined below:\n\
\n\
inetnum
      A range of IP address space.
    
      x.x.x.x - x.x.x.x, where 0 =&lt; x =&lt; 255
    \n\
netname
      The name of a range of IP address space.
    
      &lt;uppercase letter&gt;&lt;uppercase alphanumeric, "-"&gt;
    \n\
descr
      A short decription of this object.
    
      All characters possible.
    \n\
country
      ATB country DESC Name of the country of the admin-c.
    
      ATB country FRMT 2 letter uppercase ISO 3166 country code.
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
tech-c
      A technical contact.
    
      &lt;NIC-handle&gt;
    \n\
rev-srv
      Domain name server for a range of IP addresses.
    
      Fully qualified name without trailing "."
    \n\
status
      status
    
      INSERT status desc here.
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
mnt-lower
      The identifier of a registered mntner object used for
      hierarchical authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The inet-rtr class:\n\
\n\

      The inet-rtr object represents an internet router
      within a routing registry. See ripe-122 for details.
   \n\
\n\
inet-rtr:    [mandatory]  [single]     [primary/look-up key]\n\
local-as:    [mandatory]  [single]     [ ]\n\
ifaddr:      [mandatory]  [multiple]   [ ]\n\
peer:        [optional]   [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
tech-c:      [mandatory]  [multiple]   [inverse key]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [mandatory]  [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the inet-rtrclass are defined below:\n\
\n\
inet-rtr
      Fully qualified domain name of an internet router.
    
      Fully qualified domain name without trailing "."
    \n\
local-as
      The autonomous system in which a router belongs.
    
      AS&lt;positive integer between 1 and 65535&gt;.
    \n\
ifaddr
      An interface address within an internet router.
    
      &lt;Interface Address&gt; &lt;Interface Subnet Mask&gt;
    \n\
peer
      Details of any (interior or exterior) router peerings.
    
      &lt;Peer address&gt; &lt;Peer AS&gt; &lt;Routing Protocol&gt; [Local AS]
      [Local AS] is optional.
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
tech-c
      A technical contact.
    
      &lt;NIC-handle&gt;
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The key-cert class:\n\
\n\

      The key certificate object is used to store PGP
      certificates for use with the maintainer objects
      as a means of authentication.
   \n\
\n\
key-cert:    [mandatory]  [single]     [primary/look-up key]\n\
method:      [generated]  [single]     [ ]\n\
owner:       [generated]  [multiple]   [ ]\n\
fingerpr:    [generated]  [single]     [ ]\n\
certif:      [mandatory]  [multiple]   [ ]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [mandatory]  [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the key-certclass are defined below:\n\
\n\
key-cert
      key-cert
    
      INSERT key-cert desc here.
    \n\
method
      method
    
      INSERT method desc here.
    \n\
owner
      owner
    
      INSERT owner desc here.
    \n\
fingerpr
      fingerpr
    
      INSERT fingerpr desc here.
    \n\
certif
      certif
    
      INSERT certif desc here.
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The limerick class:\n\
\n\

      The limerick object represents a humourous poem which
      has five lines and the rhyme scheme "aabba".
   \n\
\n\
limerick:    [mandatory]  [single]     [primary/look-up key]\n\
descr:       [optional]   [multiple]   [ ]\n\
text:        [mandatory]  [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
author:      [mandatory]  [multiple]   [ ]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [mandatory]  [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the limerickclass are defined below:\n\
\n\
limerick
      Title of a limerick.
    
      LIM-&lt;string&gt;, where string can include
      alphanumeric characters, "-" character.
    \n\
descr
      A short decription of this object.
    
      All characters possible.
    \n\
text
      Must be humourous, but not malicious
      or insulting. :-)
    
      Free Text.
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
author
      Limerick author.
    
      &lt;NIC-handle&gt;
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The mntner class:\n\
\n\

      The mntner object contains details of who is authorised
      to make changes to RIPE Database objects and details of
      a process that actually verifies that the person who
      makes the changes is authorised to do so.
      Mntner objects are not created automatically, but are
      forwarded to RIPE NCC staff.
   \n\
\n\
mntner:      [mandatory]  [single]     [primary/look-up key]\n\
descr:       [mandatory]  [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
tech-c:      [optional]   [multiple]   [inverse key]\n\
upd-to:      [mandatory]  [multiple]   [ ]\n\
mnt-nfy:     [optional]   [multiple]   [ ]\n\
auth:        [mandatory]  [multiple]   [ ]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [mandatory]  [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the mntnerclass are defined below:\n\
\n\
mntner
      The name of a mntner object.  Must be an unique mntner
      name, but can be identical to AS names, nic-handles.
    
      &lt;uppercase letter&gt;&lt;uppercase alphanumeric, "-"&gt;
    \n\
descr
      A short decription of this object.
    
      All characters possible.
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
tech-c
      A technical contact.
    
      &lt;NIC-handle&gt;
    \n\
upd-to
      The e-mail address to be notified when an object
      ATB upd-to DESC protected by a mntner is unsuccessfully updated.
    
      ATB upd-to FRMT RFC-822 address
    \n\
mnt-nfy
      The e-mail address to be notified when an object
      protected by a mntner is successfully updated.
    
      RFC-822 address.
    \n\
auth
      auth
    
      INSERT auth desc here.
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The person class:\n\
\n\

      The person object contains information on how to
      contact those people who are responsible for
      network operations or RIPE Database objects.
   \n\
\n\
person:      [mandatory]  [single]     [lookup key]\n\
address:     [mandatory]  [multiple]   [ ]\n\
phone:       [mandatory]  [multiple]   [ ]\n\
fax-no:      [optional]   [multiple]   [ ]\n\
e-mail:      [optional]   [multiple]   [lookup key]\n\
nic-hdl:     [mandatory]  [single]     [primary/look-up key]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [optional]   [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the personclass are defined below:\n\
\n\
person
      The full name of an adminstrative, technical or zone
      contact person specified in another object.
      Do not use titles such as"Dr.", "Prof.", "Mv.",
      "Ms.", "Mr.", etc.
    
      &lt;Personal Name&gt; &lt;Family Name&gt; where each name is
      composed of alphabetic characters.
    \n\
address
      Full postal address of a person.
    
      Free Text.
    \n\
phone
      Telephone number
    
      + &lt;Country Code&gt;&lt;Area Code&gt;&lt;Phone Number&gt;
      + &lt;Country Code&gt;&lt;Area Code&gt;&lt;Phone Number&gt; ext. &lt;number&gt;
      Optional: spaces may be used to split up the phone number
      into its constituent components. "." characters can also
      be used between to separate the digits.
    \n\
fax-no
      The fax number of a person or role
    
      + &lt;Country Code&gt; &lt;Area Code&gt; &lt;Fax Number&gt;
    \n\
e-mail
      The e-mail address of a person or role.
    
      RFC-822 address.
    \n\
nic-hdl
      The NIC handle of a role or person object.
      This can be a RIPE NIC-handle or a NIC-handle
      assigned by other regional registries.
    
      RIPE NIC-handle: &lt;Initials&gt;&lt;0-999&gt;-RIPE
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The role class:\n\
\n\

      The role object represents a "help desk", a network
      operations centre or a contact point for help or
      information on network operations.
   \n\
\n\
role:        [mandatory]  [single]     [lookup key]\n\
address:     [mandatory]  [multiple]   [ ]\n\
phone:       [optional]   [multiple]   [ ]\n\
fax-no:      [optional]   [multiple]   [ ]\n\
e-mail:      [mandatory]  [multiple]   [lookup key]\n\
trouble:     [optional]   [multiple]   [ ]\n\
admin-c:     [mandatory]  [multiple]   [inverse key]\n\
tech-c:      [mandatory]  [multiple]   [inverse key]\n\
nic-hdl:     [mandatory]  [single]     [primary/look-up key]\n\
remarks:     [optional]   [multiple]   [ ]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [optional]   [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the roleclass are defined below:\n\
\n\
role
      The full name of a role entity e.g. RIPE DBM.
    
      Two components, each consisting of alphabetic
      characters. Note: there is no "-" character
      between the two components of the the name.
    \n\
address
      Full postal address of a person.
    
      Free Text.
    \n\
phone
      Telephone number
    
      + &lt;Country Code&gt;&lt;Area Code&gt;&lt;Phone Number&gt;
      + &lt;Country Code&gt;&lt;Area Code&gt;&lt;Phone Number&gt; ext. &lt;number&gt;
      Optional: spaces may be used to split up the phone number
      into its constituent components. "." characters can also
      be used between to separate the digits.
    \n\
fax-no
      The fax number of a person or role
    
      + &lt;Country Code&gt; &lt;Area Code&gt; &lt;Fax Number&gt;
    \n\
e-mail
      The e-mail address of a person or role.
    
      RFC-822 address.
    \n\
trouble
      Information on who to contact when there are problems.
    
      &lt;Free text&gt;
    \n\
admin-c
      An on-site contact (person)
    
    &lt;NIC-handle&gt;
    \n\
tech-c
      A technical contact.
    
      &lt;NIC-handle&gt;
    \n\
nic-hdl
      The NIC handle of a role or person object.
      This can be a RIPE NIC-handle or a NIC-handle
      assigned by other regional registries.
    
      RIPE NIC-handle: &lt;Initials&gt;&lt;0-999&gt;-RIPE
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
"The route class:\n\
\n\

      The route object represents a single route injected into
      the Internet routing mesh.
   \n\
\n\
route:       [mandatory]  [single]     [primary/look-up key]\n\
descr:       [mandatory]  [multiple]   [ ]\n\
origin:      [mandatory]  [single]     [primary key]\n\
hole:        [optional]   [multiple]   [ ]\n\
withdrawn:   [optional]   [single]     [ ]\n\
comm-list:   [optional]   [multiple]   [ ]\n\
advisory:    [optional]   [multiple]   [ ]\n\
remarks:     [optional]   [multiple]   [ ]\n\
cross-nfy:   [optional]   [multiple]   [inverse key]\n\
community:   [optional]   [multiple]   [ ]\n\
cross-mnt:   [optional]   [multiple]   [inverse key]\n\
notify:      [optional]   [multiple]   [inverse key]\n\
mnt-by:      [mandatory]  [multiple]   [inverse key]\n\
changed:     [mandatory]  [multiple]   [ ]\n\
source:      [mandatory]  [single]     [ ]\n\
\n\
The content of the attributes of the routeclass are defined below:\n\
\n\
route
      A route being anounced.
    
      Classless prefix length representation.  &lt;IP num-
      ber&gt;/&lt;prefix length&gt;
    \n\
descr
      A short decription of this object.
    
      All characters possible.
    \n\
origin
      origin
    
      INSERT origin desc here.
    \n\
hole
      hole
    
       INSERT holes desc here.
     \n\
withdrawn
      withdrawn
    
      INSERT withdrawn desc here.
    \n\
comm-list
      comm-list
    
      INSERT comm-list desc here.
    \n\
advisory
      advisory
    
      INSERT advisory desc here.
    \n\
remarks
      General remarks. Can include an URL or RFC822
      address (if preceeded by mailto:).
    
      &lt;free text&gt;
    \n\
cross-nfy
      cross-nfy
    
      INSERT cross-nfy desc here.
    \n\
community
      community
    
      INSERT community desc here.
    \n\
cross-mnt
      cross-mnt
    
      INSERT cross-mnt desc here.
    \n\
notify
      The e-mail address to which notifications of changes to
      an object should be sent.
    
      &lt;RFC-822 address&gt;
    \n\
mnt-by
      The identifier of a registered mntner object used for
      authorization and authentication.
    
      &lt;mntner&gt;
    \n\
changed
      Who previously changed this object
      and when this change was made.
    
      &lt;RFC822 e-mail address&gt; &lt;DATE&gt;
      E-mail address of person updating the object.
      DATE in YYYYMMDD or YYMMDD format.
    \n\
source
      Identifier of the database containing
      authoritative data for this object.
      Use RIPE for objects in the RIPE Database.
    
      Uppercase Text.
    \n\

Further information may be found at:

http://www.ripe.net/docs/ripe-157.html
ftp://ftp.ripe.net/ripe/docs/ripe-157.ps
ftp://ftp.ripe.net/ripe/docs/ripe-157.txt


",
NULL
}; /* Templates_v */
