const char *Templates_v[] = {
"The as-block class:\n"
"\n"
"      INSERT as-block description here.\n"
"   ""\n"
"as-block:      [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [optional]   [multiple]   [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"admin-c:       [mandatory]  [multiple]   [inverse key]\n"
"notify:        [optional]   [multiple]   [inverse key]\n"
"mnt-lower:     [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 as-block class are defined below:\n"
"\n"
"as-block\n"
"\n"
"      as-block\n"
"   ""\n"
"      INSERT as-block desc here.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-lower\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      hierarchical authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The as-set class:\n"
"\n"
"      INSERT as-set description here.\n"
"   ""\n"
"as-set:        [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"members:       [optional]   [multiple]   [ ]\n"
"mbrs-by-ref:   [optional]   [multiple]   [inverse key]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"admin-c:       [mandatory]  [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 as-set class are defined below:\n"
"\n"
"as-set\n"
"\n"
"      as-set\n"
"   ""\n"
"      INSERT as-set desc here.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"members\n"
"\n"
"      members\n"
"   ""\n"
"      INSERT members desc here.\n"
"   ""\n"
"mbrs-by-ref\n"
"\n"
"      mbrs-by-ref\n"
"   ""\n"
"      INSERT mbrs-by-ref desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The aut-num class:\n"
"\n"
"      The aut-num object describes the details of the\n"
"      registered owner of an Autonomous System and their\n"
"      routing policy for that AS. See ripe-181 and\n"
"      RFC-BGP4 for details.\n"
"   ""\n"
"aut-num:       [mandatory]  [single]     [primary/look-up key]\n"
"as-name:       [mandatory]  [single]     [ ]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"member-of:     [optional]   [multiple]   [inverse key]\n"
"import:        [optional]   [multiple]   [ ]\n"
"export:        [optional]   [multiple]   [ ]\n"
"default:       [optional]   [multiple]   [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"admin-c:       [mandatory]  [multiple]   [inverse key]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"cross-mnt:     [optional]   [multiple]   [inverse key]\n"
"cross-nfy:     [optional]   [multiple]   [inverse key]\n"
"notify:        [optional]   [multiple]   [inverse key]\n"
"mnt-lower:     [optional]   [multiple]   [inverse key]\n"
"mnt-routes:    [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-num class are defined below:\n"
"\n"
"aut-num\n"
"\n"
"      The autonomous system number.  This must be a uniquely\n"
"      allocated autonomous system number from an AS registry\n"
"      (e.g.RIPE NCC, the Inter-NIC, etc).\n"
"   ""\n"
"      \"AS\"<positive integer between 1 and 65535>\n"
"   ""\n"
"as-name\n"
"\n"
"      A descriptive name associated with an AS.\n"
"   ""\n"
"      Uppercase letters, dashes (\"-\") and digits, no spaces.\n"
"      Must start with a letter.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"member-of\n"
"\n"
"      member-of\n"
"   ""\n"
"       INSERT member-of desc here.\n"
"    ""\n"
"import\n"
"\n"
"      import\n"
"   ""\n"
"      INSERT import desc here.\n"
"   ""\n"
"export\n"
"\n"
"      export\n"
"   ""\n"
"      INSERT export desc here.\n"
"   ""\n"
"default\n"
"\n"
"      default\n"
"   ""\n"
"      INSERT default desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"cross-mnt\n"
"\n"
"      cross-mnt\n"
"   ""\n"
"      INSERT cross-mnt desc here.\n"
"   ""\n"
"cross-nfy\n"
"\n"
"      cross-nfy\n"
"   ""\n"
"      INSERT cross-nfy desc here.\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-lower\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      hierarchical authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"mnt-routes\n"
"\n"
"      An additional maintainer reference can occur through a new attribute,\n"
"      \"mnt-routes\", and is used in aut-num, inetnum and route objects.  The\n"
"      \"mnt-routes\" attribute is an extension to RPSL and is described in\n"
"      detail in Section 10.\n"
"\n"
"      A mnt-routes attribute in an aut-num object allows addition of route\n"
"      objects with that AS number as the origin to the maintainers listed.\n"
"      A mnt-routes attribute in an inetnum object allows addition of route\n"
"      objects with exact matching or more specific prefixes.  A mnt-routes\n"
"      attribute in a route object allows addition of route objects with\n"
"      exact matching or more specific prefixes.  A mnt-routes attribute\n"
"      does not allow changes to the aut-num, inetnum, or route object where\n"
"      it appears.  A mnt-routes may optionally be constrained to only apply\n"
"      to a subset of more specific routes.\n"
"\n"
"      Where \"mnt-routes\" or \"mnt-lower\" are applicable, any maintainer\n"
"      referenced in the \"mnt-by\" still apply.  The set of applicable\n"
"      maintainers for whatever check is being made is the union of the\n"
"      \"mnt-routes\" or \"mnt-lower\" and the \"mnt-by\".  For example, when\n"
"      authorizing a route object software would look at \"mnt-routes\", if it\n"
"      does not exist, look at \"mnt-lower\", if that does not exist look at\n"
"      \"mnt-by\".\n"
"   ""\n"
"      INSERT mnt-routes format here.\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The domain class:\n"
"\n"
"      A domain object represents a Top Level Domain (TLD) or\n"
"      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 domain class are defined below:\n"
"\n"
"domain\n"
"\n"
"      IP domain name.\n"
"   ""\n"
"      Full qualified domain name without trailing \".\".\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"zone-c\n"
"\n"
"      NIC-handle of the person with authority over a zone.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"nserver\n"
"\n"
"      List of nameservers for a domain object; a minimum\n"
"      of two is mandatory .\n"
"   ""\n"
"      <Fully qualified domain name(s) without trailing \".\">\n"
"      OR <IP Address(es) of the nameserver(s)>\n"
"   ""\n"
"sub-dom\n"
"\n"
"      List of the sub-domains of a domain\n"
"   ""\n"
"      <Relative domain name to the domain>\n"
"   ""\n"
"dom-net\n"
"\n"
"      List of IP networks in a domain.\n"
"   ""\n"
"      Dotted quad including trailing 0's.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"mnt-lower\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      hierarchical authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"refer\n"
"\n"
"      Whois referral for domain objects\n"
"   ""\n"
"      <Type> <host> <port>\n"
"      <Type> is one of RIPE, Internic or SIMPLE. Specifies whois\n"
"      query style.\n"
"      <host> specifies the host to be queried.\n"
"      <port> the TCP port number (optional: 43 is the default)\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The inet-rtr class:\n"
"\n"
"      The inet-rtr object represents an internet router\n"
"      within a routing registry. See ripe-122 for details.\n"
"   ""\n"
"inet-rtr:      [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"alias:         [optional]   [multiple]   [ ]\n"
"local-as:      [mandatory]  [single]     [inverse key]\n"
"ifaddr:        [mandatory]  [multiple]   [lookup key]\n"
"peer:          [optional]   [multiple]   [ ]\n"
"member-of:     [optional]   [multiple]   [inverse key]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"admin-c:       [mandatory]  [multiple]   [inverse key]\n"
"tech-c:        [mandatory]  [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 inet-rtr class are defined below:\n"
"\n"
"inet-rtr\n"
"\n"
"      Fully qualified domain name of an internet router.\n"
"   ""\n"
"      Fully qualified domain name without trailing \".\"\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"alias\n"
"\n"
"      alias\n"
"   ""\n"
"      INSERT alias desc here.\n"
"   ""\n"
"local-as\n"
"\n"
"      The autonomous system in which a router belongs.\n"
"   ""\n"
"      AS<positive integer between 1 and 65535>.\n"
"   ""\n"
"ifaddr\n"
"\n"
"      An interface address within an internet router.\n"
"   ""\n"
"      <Interface Address> <Interface Subnet Mask>\n"
"   ""\n"
"peer\n"
"\n"
"      Details of any (interior or exterior) router peerings.\n"
"   ""\n"
"      <Peer address> <Peer AS> <Routing Protocol> [Local AS]\n"
"      [Local AS] is optional.\n"
"   ""\n"
"member-of\n"
"\n"
"      member-of\n"
"   ""\n"
"       INSERT member-of desc here.\n"
"    ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The inet6num class:\n"
"\n"
"      An inet6num object contains information on allocations\n"
"      and assignments of IPv6 address space. \n"
"   ""\n"
"inet6num:      [mandatory]  [single]     [primary/look-up key]\n"
"netname:       [mandatory]  [single]     [lookup 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:        [mandatory]  [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 inet6num class are defined below:\n"
"\n"
"inet6num\n"
"\n"
"      Full IP version 6 address.\n"
"   ""\n"
"      <ip6num>/<prefix length>\n"
"   ""\n"
"netname\n"
"\n"
"      The name of a range of IP address space.\n"
"   ""\n"
"      RPSL object name. An <object-name> made up of letters, digits, the\n"
"      character underscore \"_\", and the character hyphen \"-\"; the first\n"
"      character of a name must be a letter, and the last character of a name\n"
"      must be a letter or digit.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"country\n"
"\n"
"      ATB country DESC Name of the country of the admin-c.\n"
"   ""\n"
"      ATB country FRMT 2 letter uppercase ISO 3166 country code.\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"rev-srv\n"
"\n"
"      Domain name server for a range of IP addresses.\n"
"   ""\n"
"      Fully qualified name without trailing \".\"\n"
"   ""\n"
"status\n"
"\n"
"      status\n"
"   ""\n"
"      INSERT status desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"mnt-lower\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      hierarchical authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The inetnum class:\n"
"\n"
"      An inetnum object contains information on allocations\n"
"      and assignments of IPv4 address space. See ripe-220 for\n"
"      information on requesting IP address space.\n"
"   ""\n"
"inetnum:       [mandatory]  [single]     [primary/look-up key]\n"
"netname:       [mandatory]  [single]     [lookup 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:        [mandatory]  [single]     [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"notify:        [optional]   [multiple]   [inverse key]\n"
"mnt-by:        [mandatory]  [multiple]   [inverse key]\n"
"mnt-lower:     [optional]   [multiple]   [inverse key]\n"
"mnt-routes:    [optional]   [multiple]   [inverse key]\n"
"changed:       [mandatory]  [multiple]   [ ]\n"
"source:        [mandatory]  [single]     [ ]\n"
"\n"
"The content of the attributes of the inetnum class are defined below:\n"
"\n"
"inetnum\n"
"\n"
"      A range of IP address space.\n"
"   ""\n"
"      x.x.x.x - x.x.x.x, where 0 =< x =< 255\n"
"   ""\n"
"netname\n"
"\n"
"      The name of a range of IP address space.\n"
"   ""\n"
"      RPSL object name. An <object-name> made up of letters, digits, the\n"
"      character underscore \"_\", and the character hyphen \"-\"; the first\n"
"      character of a name must be a letter, and the last character of a name\n"
"      must be a letter or digit.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"country\n"
"\n"
"      ATB country DESC Name of the country of the admin-c.\n"
"   ""\n"
"      ATB country FRMT 2 letter uppercase ISO 3166 country code.\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"rev-srv\n"
"\n"
"      Domain name server for a range of IP addresses.\n"
"   ""\n"
"      Fully qualified name without trailing \".\"\n"
"   ""\n"
"status\n"
"\n"
"      status\n"
"   ""\n"
"      INSERT status desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"mnt-lower\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      hierarchical authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"mnt-routes\n"
"\n"
"      An additional maintainer reference can occur through a new attribute,\n"
"      \"mnt-routes\", and is used in aut-num, inetnum and route objects.  The\n"
"      \"mnt-routes\" attribute is an extension to RPSL and is described in\n"
"      detail in Section 10.\n"
"\n"
"      A mnt-routes attribute in an aut-num object allows addition of route\n"
"      objects with that AS number as the origin to the maintainers listed.\n"
"      A mnt-routes attribute in an inetnum object allows addition of route\n"
"      objects with exact matching or more specific prefixes.  A mnt-routes\n"
"      attribute in a route object allows addition of route objects with\n"
"      exact matching or more specific prefixes.  A mnt-routes attribute\n"
"      does not allow changes to the aut-num, inetnum, or route object where\n"
"      it appears.  A mnt-routes may optionally be constrained to only apply\n"
"      to a subset of more specific routes.\n"
"\n"
"      Where \"mnt-routes\" or \"mnt-lower\" are applicable, any maintainer\n"
"      referenced in the \"mnt-by\" still apply.  The set of applicable\n"
"      maintainers for whatever check is being made is the union of the\n"
"      \"mnt-routes\" or \"mnt-lower\" and the \"mnt-by\".  For example, when\n"
"      authorizing a route object software would look at \"mnt-routes\", if it\n"
"      does not exist, look at \"mnt-lower\", if that does not exist look at\n"
"      \"mnt-by\".\n"
"   ""\n"
"      INSERT mnt-routes format here.\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The key-cert class:\n"
"\n"
"      The key certificate object is used to store PGP\n"
"      certificates for use with the maintainer objects\n"
"      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-cert class are defined below:\n"
"\n"
"key-cert\n"
"\n"
"      key-cert\n"
"   ""\n"
"      INSERT key-cert desc here.\n"
"   ""\n"
"method\n"
"\n"
"      method\n"
"   ""\n"
"      INSERT method desc here.\n"
"   ""\n"
"owner\n"
"\n"
"      owner\n"
"   ""\n"
"      INSERT owner desc here.\n"
"   ""\n"
"fingerpr\n"
"\n"
"      fingerpr\n"
"   ""\n"
"      INSERT fingerpr desc here.\n"
"   ""\n"
"certif\n"
"\n"
"      certif\n"
"   ""\n"
"      INSERT certif desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The limerick class:\n"
"\n"
"      The limerick object represents a humourous poem which\n"
"      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]   [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 limerick class are defined below:\n"
"\n"
"limerick\n"
"\n"
"      Title of a limerick.\n"
"   ""\n"
"      LIM-<string>, where string can include\n"
"      alphanumeric characters, \"-\" character.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"text\n"
"\n"
"      Must be humourous, but not malicious\n"
"      or insulting. :-)\n"
"   ""\n"
"      Free Text.\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"author\n"
"\n"
"      Limerick author.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The mntner class:\n"
"\n"
"      The mntner object contains details of who is authorised\n"
"      to make changes to RIPE Database objects and details of\n"
"      a process that actually verifies that the person who\n"
"      makes the changes is authorised to do so.\n"
"      Mntner objects are not created automatically, but are\n"
"      forwarded to RIPE Database Administration (ripe-dbm@ripe.net).\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]   [inverse key]\n"
"mnt-nfy:       [optional]   [multiple]   [inverse key]\n"
"auth:          [mandatory]  [multiple]   [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"notify:        [optional]   [multiple]   [inverse key]\n"
"mnt-by:        [mandatory]  [multiple]   [inverse key]\n"
"auth-override: [optional]   [single]     [ ]\n"
"referral-by:   [mandatory]  [single]     [inverse key]\n"
"changed:       [mandatory]  [multiple]   [ ]\n"
"source:        [mandatory]  [single]     [ ]\n"
"\n"
"The content of the attributes of the mntner class are defined below:\n"
"\n"
"mntner\n"
"\n"
"      The name of a mntner object.  Must be an unique mntner\n"
"      name, but can be identical to AS names, nic-handles.\n"
"   ""\n"
"      <uppercase letter><uppercase alphanumeric, \"-\">\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"upd-to\n"
"\n"
"      The e-mail address to be notified when an object\n"
"      ATB upd-to DESC protected by a mntner is unsuccessfully updated.\n"
"   ""\n"
"      ATB upd-to FRMT RFC-822 address\n"
"   ""\n"
"mnt-nfy\n"
"\n"
"      The e-mail address to be notified when an object\n"
"      protected by a mntner is successfully updated.\n"
"   ""\n"
"      RFC-822 address.\n"
"   ""\n"
"auth\n"
"\n"
"      auth\n"
"   ""\n"
"      INSERT auth desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"auth-override\n"
"\n"
"       An auth-override attribute can be added, deleted, or\n"
"       changed by a transaction submitted by maintainer listed in the\n"
"       referral-by.  An auth-override can only be added to a maintainer\n"
"       if that maintainer has been inactive for the prior 60 days.  The\n"
"       auth-override attribute itself contains only the date when the at-\n"
"       tribute will go into effect which must be at least 60 days from the\n"
"       current date unless there is already authorization to modify the\n"
"       maintainer.  After the date in the auth-override is reached, those\n"
"       identified by the maintainer in the referral-by have authoriza-\n"
"       tion to modify the maintainer.  This attribute exists as a means to\n"
"       clean up should the holder of a maintainer become unresponsive and\n"
"       can only take effect if that maintainer does not remove the auth-\n"
"       override in response to the automatic notification that occurs on\n"
"       changes.\n"
"   ""\n"
"      INSERT auth-override format here.\n"
"   ""\n"
"referral-by\n"
"\n"
"      This attribute is required in the maintainer object.  It\n"
"      may never be altered after the addition of the maintainer.  This\n"
"      attribute refers to the maintainer that created this maintainer.\n"
"      It may be multiple if more than one signature appeared on the\n"
"      transaction creating the object.\n"
"   ""\n"
"      INSERT referral-by format here.\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The person class:\n"
"\n"
"      The person object contains information on how to\n"
"      contact those people who are responsible for\n"
"      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 person class are defined below:\n"
"\n"
"person\n"
"\n"
"      The full name of an adminstrative, technical or zone\n"
"      contact person specified in another object.\n"
"      Do not use titles such as\"Dr.\", \"Prof.\", \"Mv.\",\n"
"      \"Ms.\", \"Mr.\", etc.\n"
"   ""\n"
"      <Personal Name> <Family Name> where each name is\n"
"      composed of alphabetic characters.\n"
"   ""\n"
"address\n"
"\n"
"      Full postal address of a person.\n"
"   ""\n"
"      Free Text.\n"
"   ""\n"
"phone\n"
"\n"
"      Telephone number\n"
"   ""\n"
"      + <Country Code><Area Code><Phone Number>\n"
"      + <Country Code><Area Code><Phone Number> ext. <number>\n"
"      Optional: spaces may be used to split up the phone number\n"
"      into its constituent components. \".\" characters can also\n"
"      be used between to separate the digits.\n"
"   ""\n"
"fax-no\n"
"\n"
"      The fax number of a person or role\n"
"   ""\n"
"      + <Country Code> <Area Code> <Fax Number>\n"
"   ""\n"
"e-mail\n"
"\n"
"      The e-mail address of a person or role.\n"
"   ""\n"
"      RFC-822 address.\n"
"   ""\n"
"nic-hdl\n"
"\n"
"      The NIC handle of a role or person object.\n"
"      This can be a RIPE NIC-handle or a NIC-handle\n"
"      assigned by other regional registries.\n"
"   ""\n"
"      RIPE NIC-handle: <Initials><0-999>-RIPE\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The role class:\n"
"\n"
"      The role object represents a \"help desk\", a network\n"
"      operations centre or a contact point for help or\n"
"      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 role class are defined below:\n"
"\n"
"role\n"
"\n"
"      The full name of a role entity e.g. RIPE DBM.\n"
"   ""\n"
"      Two components, each consisting of alphabetic\n"
"      characters. Note: there is no \"-\" character\n"
"      between the two components of the the name.\n"
"   ""\n"
"address\n"
"\n"
"      Full postal address of a person.\n"
"   ""\n"
"      Free Text.\n"
"   ""\n"
"phone\n"
"\n"
"      Telephone number\n"
"   ""\n"
"      + <Country Code><Area Code><Phone Number>\n"
"      + <Country Code><Area Code><Phone Number> ext. <number>\n"
"      Optional: spaces may be used to split up the phone number\n"
"      into its constituent components. \".\" characters can also\n"
"      be used between to separate the digits.\n"
"   ""\n"
"fax-no\n"
"\n"
"      The fax number of a person or role\n"
"   ""\n"
"      + <Country Code> <Area Code> <Fax Number>\n"
"   ""\n"
"e-mail\n"
"\n"
"      The e-mail address of a person or role.\n"
"   ""\n"
"      RFC-822 address.\n"
"   ""\n"
"trouble\n"
"\n"
"      Information on who to contact when there are problems.\n"
"   ""\n"
"      <Free text>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"nic-hdl\n"
"\n"
"      The NIC handle of a role or person object.\n"
"      This can be a RIPE NIC-handle or a NIC-handle\n"
"      assigned by other regional registries.\n"
"   ""\n"
"      RIPE NIC-handle: <Initials><0-999>-RIPE\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The route class:\n"
"\n"
"      The route object represents a single route injected into\n"
"      the Internet routing mesh.\n"
"   ""\n"
"route:         [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"origin:        [mandatory]  [single]     [primary/inverse key]\n"
"holes:         [optional]   [multiple]   [ ]\n"
"member-of:     [optional]   [multiple]   [inverse key]\n"
"inject:        [optional]   [multiple]   [ ]\n"
"aggr-mtd:      [optional]   [single]     [ ]\n"
"aggr-bndry:    [optional]   [single]     [ ]\n"
"export-comps:  [optional]   [single]     [ ]\n"
"components:    [optional]   [single]     [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"cross-mnt:     [optional]   [multiple]   [inverse key]\n"
"cross-nfy:     [optional]   [multiple]   [inverse key]\n"
"notify:        [optional]   [multiple]   [inverse key]\n"
"mnt-lower:     [optional]   [multiple]   [inverse key]\n"
"mnt-routes:    [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 route class are defined below:\n"
"\n"
"route\n"
"\n"
"      A route being anounced.\n"
"   ""\n"
"      Classless prefix length representation.  <IP num-\n"
"      ber>/<prefix length>\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"origin\n"
"\n"
"      origin\n"
"   ""\n"
"      INSERT origin desc here.\n"
"   ""\n"
"holes\n"
"\n"
"      holes\n"
"   ""\n"
"       INSERT holes desc here.\n"
"    ""\n"
"member-of\n"
"\n"
"      member-of\n"
"   ""\n"
"       INSERT member-of desc here.\n"
"    ""\n"
"inject\n"
"\n"
"      inject\n"
"   ""\n"
"      INSERT inject desc here.\n"
"   ""\n"
"aggr-mtd\n"
"\n"
"      aggr-mtd\n"
"   ""\n"
"      INSERT aggr-mtd desc here.\n"
"   ""\n"
"aggr-bndry\n"
"\n"
"      aggr-bndry\n"
"   ""\n"
"      INSERT aggr-bndry desc here.\n"
"   ""\n"
"export-comps\n"
"\n"
"      export-comps\n"
"   ""\n"
"      INSERT export-comps desc here.\n"
"   ""\n"
"components\n"
"\n"
"      components\n"
"   ""\n"
"      INSERT components desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"cross-mnt\n"
"\n"
"      cross-mnt\n"
"   ""\n"
"      INSERT cross-mnt desc here.\n"
"   ""\n"
"cross-nfy\n"
"\n"
"      cross-nfy\n"
"   ""\n"
"      INSERT cross-nfy desc here.\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-lower\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      hierarchical authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"mnt-routes\n"
"\n"
"      An additional maintainer reference can occur through a new attribute,\n"
"      \"mnt-routes\", and is used in aut-num, inetnum and route objects.  The\n"
"      \"mnt-routes\" attribute is an extension to RPSL and is described in\n"
"      detail in Section 10.\n"
"\n"
"      A mnt-routes attribute in an aut-num object allows addition of route\n"
"      objects with that AS number as the origin to the maintainers listed.\n"
"      A mnt-routes attribute in an inetnum object allows addition of route\n"
"      objects with exact matching or more specific prefixes.  A mnt-routes\n"
"      attribute in a route object allows addition of route objects with\n"
"      exact matching or more specific prefixes.  A mnt-routes attribute\n"
"      does not allow changes to the aut-num, inetnum, or route object where\n"
"      it appears.  A mnt-routes may optionally be constrained to only apply\n"
"      to a subset of more specific routes.\n"
"\n"
"      Where \"mnt-routes\" or \"mnt-lower\" are applicable, any maintainer\n"
"      referenced in the \"mnt-by\" still apply.  The set of applicable\n"
"      maintainers for whatever check is being made is the union of the\n"
"      \"mnt-routes\" or \"mnt-lower\" and the \"mnt-by\".  For example, when\n"
"      authorizing a route object software would look at \"mnt-routes\", if it\n"
"      does not exist, look at \"mnt-lower\", if that does not exist look at\n"
"      \"mnt-by\".\n"
"   ""\n"
"      INSERT mnt-routes format here.\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The route-set class:\n"
"\n"
"      INSERT route-set description here.\n"
"   ""\n"
"route-set:     [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"members:       [optional]   [multiple]   [ ]\n"
"mbrs-by-ref:   [optional]   [multiple]   [inverse key]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"admin-c:       [mandatory]  [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 route-set class are defined below:\n"
"\n"
"route-set\n"
"\n"
"      route-set\n"
"   ""\n"
"      INSERT route-set desc here.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"members\n"
"\n"
"      members\n"
"   ""\n"
"      INSERT members desc here.\n"
"   ""\n"
"mbrs-by-ref\n"
"\n"
"      mbrs-by-ref\n"
"   ""\n"
"      INSERT mbrs-by-ref desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The filter-set class:\n"
"\n"
"       The filter-set object defines a set of filters, which is s a logical\n"
"       expression which when applied to a set of routes returns a subset of\n"
"       these routes.\n"
"   ""\n"
"filter-set:    [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"filter:        [mandatory]  [single]     [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"admin-c:       [mandatory]  [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 filter-set class are defined below:\n"
"\n"
"filter-set\n"
"\n"
"      filter-set\n"
"   ""\n"
"      INSERT filter-set desc here.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"filter\n"
"\n"
"      filter\n"
"   ""\n"
"      INSERT filter desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The peering-set class:\n"
"\n"
"      The peering-set object defines a set of peerings that are listed in its\n"
"      peering attributes.\n"
"   ""\n"
"peering-set:   [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"peering:       [mandatory]  [multiple]   [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"admin-c:       [mandatory]  [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 peering-set class are defined below:\n"
"\n"
"peering-set\n"
"\n"
"      peering-set\n"
"   ""\n"
"      INSERT peering-set desc here.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"peering\n"
"\n"
"      peering\n"
"   ""\n"
"      INSERT peering desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
"The rtr-set class:\n"
"\n"
"      The rtr-set object defines a set of inet-rtr objects.\n"
"   ""\n"
"rtr-set:       [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"members:       [optional]   [multiple]   [ ]\n"
"mbrs-by-ref:   [optional]   [multiple]   [inverse key]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"admin-c:       [mandatory]  [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 rtr-set class are defined below:\n"
"\n"
"rtr-set\n"
"\n"
"      rtr-set\n"
"   ""\n"
"      INSERT rtr-set desc here.\n"
"   ""\n"
"descr\n"
"\n"
"      A short decription of this object.\n"
"   ""\n"
"      All characters possible.\n"
"   ""\n"
"members\n"
"\n"
"      members\n"
"   ""\n"
"      INSERT members desc here.\n"
"   ""\n"
"mbrs-by-ref\n"
"\n"
"      mbrs-by-ref\n"
"   ""\n"
"      INSERT mbrs-by-ref desc here.\n"
"   ""\n"
"remarks\n"
"\n"
"      General remarks. Can include an URL or RFC822\n"
"      address (if preceeded by mailto:).\n"
"   ""\n"
"      <free text>\n"
"   ""\n"
"tech-c\n"
"\n"
"      A technical contact.\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"admin-c\n"
"\n"
"      An on-site contact (person)\n"
"   ""\n"
"      <NIC-handle>\n"
"   ""\n"
"notify\n"
"\n"
"      The e-mail address to which notifications of changes to\n"
"      an object should be sent.\n"
"   ""\n"
"      <RFC-822 address>\n"
"   ""\n"
"mnt-by\n"
"\n"
"      The identifier of a registered mntner object used for\n"
"      authorization and authentication.\n"
"   ""\n"
"      <mntner>\n"
"   ""\n"
"changed\n"
"\n"
"      Who previously changed this object\n"
"      and when this change was made.\n"
"   ""\n"
"      <RFC822 e-mail address> <DATE>\n"
"      E-mail address of person updating the object.\n"
"      DATE in YYYYMMDD or YYMMDD format.\n"
"   ""\n"
"source\n"
"\n"
"      Identifier of the database containing\n"
"      authoritative data for this object.\n"
"      Use RIPE for objects in the RIPE Database.\n"
"   ""\n"
"      Uppercase Text.\n"
"   ""\n"
"\n"
"Further information may be found at:\n"
"\n"
"http://www.ripe.net/docs/ripe-157.html\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.ps\n"
"ftp://ftp.ripe.net/ripe/docs/ripe-157.txt\n"
"\n"
,
NULL
}; /* Templates_v */
