const char *Templates_v[] = {
"The as-block class:\n"
"\n"
"      An as-block object is needed to delegate a range of AS numbers \n"
"      to a given repository.  This object may be used for authorisation \n"
"      of the creation of aut-num objects within the range specified \n"
"      by the \"as-block:\" attribute.\n"
"    ""\n"
"as-block:      [mandatory]  [single]     [primary/look-up key]\n"
"descr:         [optional]   [multiple]   [ ]\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"
"mnt-lower:     [optional]   [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"
"   Range of AS numbers.\n"
"    ""\n"
"     <as-number> - <as-number>\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-lower\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for hierarchical authorisation.  Protects creation of objects\n"
"   directly (one level) below in the hierarchy of an object type\n"
"   (only for inetnum, inet6num, as-block, aut-num, route or\n"
"   domain objects).  The authentication method of this maintainer\n"
"   object will then be used upon creation of any object directly\n"
"   below the object that contains the \"mnt-lower:\" attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The as-set class:\n"
"\n"
"      An as-set object defines a set of aut-num objects. The\n"
"      attributes of the as-set class are shown in Figure 1.2.2.  The\n"
"      \"as-set:\" attribute defines the name of the set. It is an RPSL\n"
"      name that starts with \"as-\". The \"members:\" attribute lists the\n"
"      members of the set.  The \"members:\" attribute is a list of AS\n"
"      numbers, or other as-set names.\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"
"   Defines the name of the set.\n"
"    ""\n"
"     An as-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"as-\", and the last character of a name must\n"
"     be a letter or a digit.\n"
"\n"
"     An as-set name can also be hierarchical.  A hierarchical set\n"
"     name is a sequence of set names and AS numbers separated by\n"
"     colons \":\".  At least one component of such a name must be\n"
"     an actual set name (i.e. start with \"as-\").  All the set\n"
"     name components of a hierarchical as-name have to be as-set\n"
"     names.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"members\n"
"\n"
"   Lists the members of the set.\n"
"    ""\n"
"     <as-number> or\n"
"     <as-set-name>\n"
"       ""\n"
"mbrs-by-ref\n"
"\n"
"   This attribute can be used in all \"set\" objects; it allows\n"
"   indirect population of a set. If this attribute is used, the\n"
"   set also includes objects of the corresponding type (aut-num\n"
"   objects for as-set, for example) that are protected by one of\n"
"   these maintainers and whose \"member-of:\" attributes refer to\n"
"   the name of the set. If the value of a \"mbrs-by-ref:\"\n"
"   attribute is ANY, any object of the corresponding type\n"
"   referring to the set is a member of the set. If the\n"
"   \"mbrs-by-ref:\" attribute is missing, the set is defined\n"
"   explicitly by the \"members:\" attribute.\n"
"    ""\n"
"     <mntner-name> | ANY \n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The aut-num class:\n"
"\n"
"      An object of the aut-num class is a database representation of \n"
"      an Autonomous System (AS), which is a group of IP networks operated \n"
"      by one or more network operators that has a single and clearly \n"
"      defined external routing policy.\n"
"    ""\n"
"aut-num:       [mandatory]  [single]     [primary/look-up key]\n"
"as-name:       [mandatory]  [single]     [ ]\n"
"descr:         [mandatory]  [multiple]   [ ]\n"
"member-of:     [optional]   [multiple]   [ ]\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.\n"
"    ""\n"
"     An \"AS\" string followed by an integer in the range from 1 to\n"
"     65534\n"
"       ""\n"
"as-name\n"
"\n"
"   A descriptive name associated with an AS.\n"
"      ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"member-of\n"
"\n"
"   This attribute can be used in the route, aut-num and inet-rtr\n"
"   classes. The value of the \"member-of:\" attribute identifies a\n"
"   set object that this object wants to be a member of.  This\n"
"   claim, however, should be acknowledged by a respective\n"
"   \"mbrs-by-ref:\" attribute in the referenced object.\n"
"    ""\n"
"     An as-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"as-\", and the last character of a name must\n"
"     be a letter or a digit.\n"
"\n"
"     An as-set name can also be hierarchical.  A hierarchical set\n"
"     name is a sequence of set names and AS numbers separated by\n"
"     colons \":\".  At least one component of such a name must be\n"
"     an actual set name (i.e. start with \"as-\").  All the set\n"
"     name components of a hierarchical as-name have to be as-set\n"
"     names.\n"
"       ""\n"
"import\n"
"\n"
"   Specifies import policy expression.\n"
"     ""\n"
"     [protocol <protocol-1>] [into <protocol-1>]\n"
"     from <peering-1> [action <action-1>] \n"
"         .\n"
"         .\n"
"         .\n"
"     from <peering-N> [action <action-N>] \n"
"     accept <filter>\n"
"       ""\n"
"export\n"
"\n"
"   Specifies an export policy expression.\n"
"    ""\n"
"     to <peering-1> [action <action-1>] \n"
"         .\n"
"         .\n"
"         .\n"
"     to <peering-N> [action <action-N>] \n"
"     announce <filter>\n"
"       ""\n"
"default\n"
"\n"
"   Specifies default routing policies.\n"
"     ""\n"
"     to <peering> [action <action>] [networks <filter>]\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"cross-mnt\n"
"\n"
"   References mntner(s) to be notified. The \"cross-mnt:\"\n"
"   attribute may be used in:\n"
"\n"
"      * route object - to get a notification for any overlaps\n"
"        with the prefix specified in that route object;\n"
"\n"
"      * aut-num object - to get a notification for overlaps with\n"
"        any of the prefixes announced in route objects in which\n"
"        the given AS number is specified in the \"origin:\"\n"
"        attribute.\n"
"\n"
"   A notification will be sent to mailbox(es) listed in cross-nfy\n"
"   and mailbox(es) listed in the \"mnt-nfy:\" attributes of the\n"
"   maintainers referenced by the cross-mnt whenever an\n"
"   overlapping route is added or removed.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"cross-nfy\n"
"\n"
"   References a NIC-handle pointing to a person or role object,\n"
"   the email address of which will be used for notification about\n"
"   the addition or removal of route objects, which overlap the\n"
"   prefixes of the already registered route objects. \n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-lower\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for hierarchical authorisation.  Protects creation of objects\n"
"   directly (one level) below in the hierarchy of an object type\n"
"   (only for inetnum, inet6num, as-block, aut-num, route or\n"
"   domain objects).  The authentication method of this maintainer\n"
"   object will then be used upon creation of any object directly\n"
"   below the object that contains the \"mnt-lower:\" attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-routes\n"
"\n"
"   This attribute references a maintainer object which is used in\n"
"   determining authorisation for the creation of route objects.\n"
"   After the reference to the maintainer, an optional list of\n"
"   prefix ranges inside of curly braces or the keyword \"ANY\" may\n"
"   follow. The default, when no additional set items are\n"
"   specified, is \"ANY\" or all more specifics. Please refer to\n"
"   RFC-2622 for more information.\n"
"    ""\n"
"     <mnt-name> [ { list of <address-prefix-range> } | ANY ]\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The domain class:\n"
"\n"
"      A domain object represents a Top Level Domain (TLD) or\n"
"      other domain registrations. It is also used for Reverse \n"
"      Delegations.\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"
"   Domain name.\n"
"    ""\n"
"     Domain name as specified in RFC 1034 without trailing dot\n"
"     (\".\").  The total length should not exceed 254 characters\n"
"     (octets).\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"zone-c\n"
"\n"
"   References a zone contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"nserver\n"
"\n"
"   Specifies the nameservers of the domain.\n"
"    ""\n"
"     Domain name as specified in RFC 1034 without trailing dot\n"
"     (\".\").  The total length should not exceed 254 characters\n"
"     (octets).\n"
"       ""\n"
"sub-dom\n"
"\n"
"   Specifies list of sub-domains of a domain.  Domain names are\n"
"   relative to the domain represented by the domain object that\n"
"   contains this attribute.\n"
"    ""\n"
"     Domain name as specified in RFC 1034 without trailing dot\n"
"     (\".\").  The total length should not exceed 254 characters\n"
"     (octets).\n"
"       ""\n"
"dom-net\n"
"\n"
"   List of IP networks in a domain.\n"
"    ""\n"
"     An IPv4 address is represented as a sequence of four\n"
"     integers in the range from 0 to 255 separated by the\n"
"     character dot (\".\").  For example, 128.9.128.5 represents a\n"
"     valid IPv4 address.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-lower\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for hierarchical authorisation.  Protects creation of objects\n"
"   directly (one level) below in the hierarchy of an object type\n"
"   (only for inetnum, inet6num, as-block, aut-num, route or\n"
"   domain objects).  The authentication method of this maintainer\n"
"   object will then be used upon creation of any object directly\n"
"   below the object that contains the \"mnt-lower:\" attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"refer\n"
"\n"
"   Specifies the referral type, hostname and port that the server\n"
"   should use to redirect the query when using referral mechanism\n"
"   for lookups for domain objects.\n"
"    ""\n"
"     <type> <hostname> [<port>]\n"
"\n"
"     <type>  specifies the type of referral to be used.\n"
"     Supported types are SIMPLE, INTERNIC, RIPE, and\n"
"     CLIENTADDRESS.\n"
"\n"
"     <hostname>  is the DNS name or <ipv4 address> of\n"
"     the referred host.\n"
"\n"
"     <port>  is an integer specifying TCP port number at\n"
"     which queries are accepted by the referred host.  If\n"
"     <port> is omitted, the default number of 43 is used.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The inet-rtr class:\n"
"\n"
"      Routers are specified using the inet-rtr class.  The \"inet-rtr:\"\n"
"      attribute is a valid DNS name of the router described. Each\n"
"      \"alias:\" attribute, if present, is a canonical DNS name for the\n"
"      router.  The \"local-as:\" attribute specifies the AS number of\n"
"      the AS that owns/operates this router.\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 DNS name of the inet-rtr without trailing \".\".\n"
"    ""\n"
"     Domain name as specified in RFC 1034 without trailing dot\n"
"     (\".\").  The total length should not exceed 254 characters\n"
"     (octets).\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"alias\n"
"\n"
"   The canonical DNS name for the router.\n"
"     ""\n"
"     Domain name as specified in RFC 1034 without trailing dot\n"
"     (\".\").  The total length should not exceed 254 characters\n"
"     (octets).\n"
"       ""\n"
"local-as\n"
"\n"
"   Specifies the autonomous system that operates the router.\n"
"    ""\n"
"     An \"AS\" string followed by an integer in the range from 1 to\n"
"     65534\n"
"       ""\n"
"ifaddr\n"
"\n"
"   Specifies an interface address within an Internet router.\n"
"    ""\n"
"     <ipv4-address> masklen <integer> [action <action>]\n"
"       ""\n"
"peer\n"
"\n"
"   Details of any (interior or exterior) router peerings.\n"
"    ""\n"
"     <protocol> <ipv4-address> <options>\n"
"     | <protocol> <inet-rtr-name> <options>\n"
"     | <protocol> <rtr-set-name> <options>\n"
"     | <protocol> <peering-set-name> <options>\n"
"       ""\n"
"member-of\n"
"\n"
"   This attribute can be used in the route, aut-num and inet-rtr\n"
"   classes. The value of the \"member-of:\" attribute identifies a\n"
"   set object that this object wants to be a member of.  This\n"
"   claim, however, should be acknowledged by a respective\n"
"   \"mbrs-by-ref:\" attribute in the referenced object.\n"
"    ""\n"
"     A router-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"rtrs-\", and the last character of a name\n"
"     must be a letter or a digit.\n"
"\n"
"     A router-set name can also be hierarchical.  A hierarchical\n"
"     set name is a sequence of set names and AS numbers separated\n"
"     by colons \":\".  At least one component of such a name must\n"
"     be an actual set name (i.e. start with \"rtrs-\").  All the\n"
"     set name components of a hierarchical router-set name have\n"
"     to be router-set names.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\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:        [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-irt:       [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"
"   Specifies a range of IPv6 addresses in prefix notation.\n"
"    ""\n"
"     <ipv6-address>/<prefix>\n"
"       ""\n"
"netname\n"
"\n"
"   The name of a range of IP address space.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"country\n"
"\n"
"   Identifies the country.\n"
"    ""\n"
"     Valid two-letter ISO 3166 country code.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"rev-srv\n"
"\n"
"   Specifies a DNS nameserver for a range of IP addresses\n"
"   represented by the inetnum object that contains this\n"
"   attribute.\n"
"    ""\n"
"     Domain name as specified in RFC 1034 without trailing dot\n"
"     (\".\").  The total length should not exceed 254 characters\n"
"     (octets).\n"
"       ""\n"
"status\n"
"\n"
"   Specifies the status of the address range represented by\n"
"   inetnum or inet6num object.\n"
"    ""\n"
"     Status can have one of these values:\n"
"\n"
"     o ALLOCATED-BY-RIR\n"
"     o ALLOCATED-BY-LIR\n"
"     o ASSIGNED\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-lower\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for hierarchical authorisation.  Protects creation of objects\n"
"   directly (one level) below in the hierarchy of an object type\n"
"   (only for inetnum, inet6num, as-block, aut-num, route or\n"
"   domain objects).  The authentication method of this maintainer\n"
"   object will then be used upon creation of any object directly\n"
"   below the object that contains the \"mnt-lower:\" attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-irt\n"
"\n"
"   May appear in an inetnum or inet6num object. It points to an\n"
"   irt object representing a Computer Security Incident Response\n"
"   Team (CSIRT) that handles security incidents for the address\n"
"   space specified by the inetnum or inet6num object.\n"
"    ""\n"
"     An irt name is made up of letters, digits, the character\n"
"     underscore \"_\", and the character hyphen \"-\"; it must start\n"
"     with \"irt-\", and the last character of a name must be a\n"
"     letter or a digit.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The inetnum class:\n"
"\n"
"      An inetnum object contains information on allocations and\n"
"      assignments of IPv4 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"
"mnt-irt:       [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"
"   Specifies a range of IPv4 that inetnum object presents. The\n"
"   ending address should be greater than the starting one.\n"
"    ""\n"
"     <ipv4-address> - <ipv4-address>\n"
"       ""\n"
"netname\n"
"\n"
"   The name of a range of IP address space.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"country\n"
"\n"
"   Identifies the country.\n"
"    ""\n"
"     Valid two-letter ISO 3166 country code.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"rev-srv\n"
"\n"
"   Specifies a DNS nameserver for a range of IP addresses\n"
"   represented by the inetnum object that contains this\n"
"   attribute.\n"
"    ""\n"
"     Domain name as specified in RFC 1034 without trailing dot\n"
"     (\".\").  The total length should not exceed 254 characters\n"
"     (octets).\n"
"       ""\n"
"status\n"
"\n"
"   Specifies the status of the address range represented by\n"
"   inetnum or inet6num object.\n"
"    ""\n"
"     Status can have one of these values:\n"
"\n"
"     o ALLOCATED PA\n"
"     o ALLOCATED PI\n"
"     o ALLOCATED UNSPECIFIED\n"
"     o LIR-PARTITIONED PA\n"
"     o LIR-PARTITIONED PI\n"
"     o ASSIGNED PA\n"
"     o ASSIGNED PI\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-lower\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for hierarchical authorisation.  Protects creation of objects\n"
"   directly (one level) below in the hierarchy of an object type\n"
"   (only for inetnum, inet6num, as-block, aut-num, route or\n"
"   domain objects).  The authentication method of this maintainer\n"
"   object will then be used upon creation of any object directly\n"
"   below the object that contains the \"mnt-lower:\" attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-routes\n"
"\n"
"   This attribute references a maintainer object which is used in\n"
"   determining authorisation for the creation of route objects.\n"
"   After the reference to the maintainer, an optional list of\n"
"   prefix ranges inside of curly braces or the keyword \"ANY\" may\n"
"   follow. The default, when no additional set items are\n"
"   specified, is \"ANY\" or all more specifics. Please refer to\n"
"   RFC-2622 for more information.\n"
"    ""\n"
"     <mnt-name> [ { list of <address-prefix-range> } | ANY ]\n"
"       ""\n"
"mnt-irt\n"
"\n"
"   May appear in an inetnum or inet6num object. It points to an\n"
"   irt object representing a Computer Security Incident Response\n"
"   Team (CSIRT) that handles security incidents for the address\n"
"   space specified by the inetnum or inet6num object.\n"
"    ""\n"
"     An irt name is made up of letters, digits, the character\n"
"     underscore \"_\", and the character hyphen \"-\"; it must start\n"
"     with \"irt-\", and the last character of a name must be a\n"
"     letter or a digit.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The key-cert class:\n"
"\n"
"      A key-cert object is a database public key certificate \n"
"      that is stored on the server and may be used with a mntner \n"
"      object for authentication when performing updates. \n"
"      Currently only PGP/GnuPG keys are supported.\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"
"   Defines the public key stored in the database.\n"
"    ""\n"
"     PGPKEY-<id>\n"
"\n"
"     <id> is  the PGP key ID of the public key in 8-digit\n"
"     hexadecimal format without \"0x\" prefix.\n"
"       ""\n"
"method\n"
"\n"
"   Defines the type of the public key.\n"
"    ""\n"
"     Currently, only PGP keys are supported.\n"
"       ""\n"
"owner\n"
"\n"
"   Specifies the owner of the public key.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"fingerpr\n"
"\n"
"   A fingerprint of a key certificate generated by the database.\n"
"    ""\n"
"     Attribute generated by server.\n"
"       ""\n"
"certif\n"
"\n"
"   Contains the public key.\n"
"     ""\n"
"     The value of the public key should be supplied either using\n"
"     multiple \"certif:\" attributes, or in one \"certif:\"\n"
"     attribute. In the first case, this is easily done by\n"
"     exporting the key from your local key ring in ASCII armored\n"
"     format and prepending each line of the key with the string\n"
"     \"certif:\". In the second case, line continuation should be\n"
"     used to represent an ASCII armored format of the key. All\n"
"     the lines of the exported key must be included; also the\n"
"     begin and end markers and the empty line which separates the\n"
"     header from the key body.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The limerick class:\n"
"\n"
"      The limerick object represents a humorous poem that has five \n"
"      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"
"   Specifies the title of the limerick.\n"
"    ""\n"
"     LIM-<string>\n"
"\n"
"     <string> can include alphanumeric characters, and \"_\" and \n"
"     \"-\" characters.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"text\n"
"\n"
"   Text of the limerick. Must be humorous, but not malicious or\n"
"   insulting.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"author\n"
"\n"
"   References a limerick author.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The mntner class:\n"
"\n"
"      Objects in the RIPE Database may be protected using mntner\n"
"      (pronounced \"maintainer\") objects.  A mntner object specifies\n"
"      authentication information required to authorise creation,\n"
"      deletion or modification of the objects protected by the mntner.\n"
"      Mntner objects are not created automatically, but are forwarded\n"
"      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"
"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"
"   A unique identifier of the mntner object.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"upd-to\n"
"\n"
"   Specifies the e-mail address to be notified when an object\n"
"   protected by a mntner is unsuccessfully updated.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-nfy\n"
"\n"
"   Specifies the e-mail address to be notified when an object\n"
"   protected by a mntner is successfully updated.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"auth\n"
"\n"
"   Defines an authentication scheme to be used.\n"
"    ""\n"
"<auth-scheme> <scheme-info>       Description\n"
"\n"
"NONE                              No authentication is required to\n"
"                                  make changes to the object protected\n"
"                                  with such authentication scheme.\n"
"\n"
"CRYPT-PW      encrypted           This scheme is our weeakest form\n"
"              password, produced  of authentication.  It is by\n"
"              by UNIX crypt(3)    no means meant to keep out a\n"
"              routine             determined malicious attacker.  The\n"
"                                  crypt function is vulnerable to\n"
"                                  exhaustive search by (lots of) fast\n"
"                                  machines and programs to do the\n"
"                                  searching are widely available. For\n"
"                                  this reason it is strongly\n"
"                                  discouraged to use encrypted\n"
"                                  passwords also used for other\n"
"                                  purposes such as UNIX login accounts\n"
"                                  in this scheme. As you are\n"
"                                  publishing the encrypted password in\n"
"                                  the database, it is open to attack.\n"
"                                  The usual caveats about crypt\n"
"                                  passwords apply, so it is not very\n"
"                                  wise to use words or combinations of\n"
"                                  words found in any dictionary of any\n"
"                                  language.\n"
"\n"
"MD5-PW        encrypted           This scheme is similar to the CRYPT-PW\n"
"              password, produced  scheme, except that it uses an MD5\n"
"              using the FreeBSD   hash rather than DES encryption to\n"
"              crypt_md5           generate the password. The main\n"
"              algorithm           benefit over CRYPT-PW is that pass \n"
"                                  phrases longer than 8 characters may\n"
"                                  be used. All of the dangers of\n"
"                                  CRYPT-PW also apply to MD5-PW.\n"
"\n"
"PGPKEY-<id>                       Strong scheme of authentication.\n"
"                                  <id> is the PGP key ID to be\n"
"                                  used for authentication. This string\n"
"                                  is the same one that is used in the\n"
"                                  corresponding key-cert object's\n"
"                                  \"key-cert:\" attribute.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"referral-by\n"
"\n"
"   This attribute is required in the maintainer object.  It may\n"
"   never be altered after the addition of the maintainer.  This\n"
"   attribute refers to the maintainer that created this\n"
"   maintainer.  It may be multiple if more than one signature\n"
"   appeared on the transaction creating the object.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The person class:\n"
"\n"
"       A person object contains information about technical or\n"
"       administrative contact responsible for the object where it is\n"
"       referenced.  Once the object is created, the value of the\n"
"       \"person:\" attribute cannot be changed.\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"
"   Specifies the full name of an administrative, technical or\n"
"   zone contact person for other objects in the database.  Person\n"
"   name cannot contain titles such as \"Dr.\", \"Prof.\", \"Mv.\",\n"
"   \"Ms.\", \"Mr.\", etc.  It is composed of alphabetic characters.\n"
"    ""\n"
"     A list of at least 2 words separated by white space. The\n"
"     first and the last word cannot end with dot (\".\"). The\n"
"     following words are not allowed: \"Dr\", \"Prof\", \"Mv\", \"Ms\",\n"
"     \"Mr\", no matter whether they end with dot (\".\") or not. A\n"
"     word is made up of letters, digits, the character underscore\n"
"     \"_\", and the character hyphen \"-\"; the first character of a\n"
"     name must be a letter, and the last character of a name must\n"
"     be a letter or a digit.\n"
"       ""\n"
"address\n"
"\n"
"      Full postal address of a contact.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"phone\n"
"\n"
"   Specifies a telephone number of the contact.\n"
"    ""\n"
"     Contact telephone number. Can take one of the forms:\n"
"\n"
"     '+' <integer-list>\n"
"     '+' <integer-list> \"(\" <integer-list> \")\" <integer-list>\n"
"     '+' <integer-list> ext. <integer list>\n"
"     '+' <integer-list> \"(\" integer list \")\" <integer-list> ext. <integer-list>\n"
"       ""\n"
"fax-no\n"
"\n"
"   The fax number of a contact.\n"
"    ""\n"
"     Contact telephone number. Can take one of the forms:\n"
"\n"
"     '+' <integer-list>\n"
"     '+' <integer-list> \"(\" <integer-list> \")\" <integer-list>\n"
"     '+' <integer-list> ext. <integer list>\n"
"     '+' <integer-list> \"(\" integer list \")\" <integer-list> ext. <integer-list>\n"
"       ""\n"
"e-mail\n"
"\n"
"   The e-mail address of a person or role.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"nic-hdl\n"
"\n"
"   Specifies the NIC handle of a role or person object.  When\n"
"   creating an object, one can also specify an \"AUTO\" NIC handle\n"
"   by setting the value of the attribute to \"AUTO-1\" or \n"
"   AUTO-1<Initials>.  In such case the database will assign\n"
"   the NIC handle automatically.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The role class:\n"
"\n"
"      The role class is similar to the person class.  However, instead\n"
"      of describing a human being, it describes a role performed by\n"
"      one or more human beings.  Examples include help desks, network\n"
"      monitoring centres, system administrators, etc.  A role object\n"
"      is particularly useful since often a person performing a role\n"
"      may change; however the role itself remains. The \"nic-hdl:\"\n"
"      attributes of the person and role classes share the same name\n"
"      space. Once the object is created, the value of the \"role:\"\n"
"      attribute cannot be changed.\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"
"   Specifies the full name of a role entity, e.g. RIPE DBM.\n"
"    ""\n"
"     A list of at least 2 words separated by white space. The\n"
"     first and the last word cannot end with dot (\".\"). The\n"
"     following words are not allowed: \"Dr\", \"Prof\", \"Mv\", \"Ms\",\n"
"     \"Mr\", no matter whether they end with dot (\".\") or not. A\n"
"     word is made up of letters, digits, the character underscore\n"
"     \"_\", and the character hyphen \"-\"; the first character of a\n"
"     name must be a letter, and the last character of a name must\n"
"     be a letter or a digit.\n"
"       ""\n"
"address\n"
"\n"
"      Full postal address of a contact.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"phone\n"
"\n"
"   Specifies a telephone number of the contact.\n"
"    ""\n"
"     Contact telephone number. Can take one of the forms:\n"
"\n"
"     '+' <integer-list>\n"
"     '+' <integer-list> \"(\" <integer-list> \")\" <integer-list>\n"
"     '+' <integer-list> ext. <integer list>\n"
"     '+' <integer-list> \"(\" integer list \")\" <integer-list> ext. <integer-list>\n"
"       ""\n"
"fax-no\n"
"\n"
"   The fax number of a contact.\n"
"    ""\n"
"     Contact telephone number. Can take one of the forms:\n"
"\n"
"     '+' <integer-list>\n"
"     '+' <integer-list> \"(\" <integer-list> \")\" <integer-list>\n"
"     '+' <integer-list> ext. <integer list>\n"
"     '+' <integer-list> \"(\" integer list \")\" <integer-list> ext. <integer-list>\n"
"       ""\n"
"e-mail\n"
"\n"
"   The e-mail address of a person or role.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"trouble\n"
"\n"
"   Contains information on who to contact when there are problems.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"nic-hdl\n"
"\n"
"   Specifies the NIC handle of a role or person object.  When\n"
"   creating an object, one can also specify an \"AUTO\" NIC handle\n"
"   by setting the value of the attribute to \"AUTO-1\" or \n"
"   AUTO-1<Initials>.  In such case the database will assign\n"
"   the NIC handle automatically.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The route class:\n"
"\n"
"      Each interAS route (also referred to as an interdomain route) \n"
"      originated by an AS is specified using a route object. The \"route:\" \n"
"      attribute is the address prefix of the route and the \"origin:\" \n"
"      attribute is the AS number of the AS that originates the route \n"
"      into the interAS routing system. \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]   [ ]\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"
"   Specifies the prefix of the interAS route. Together with the\n"
"   \"origin:\" attribute,  constitutes a primary key of the route\n"
"   object.\n"
"    ""\n"
"     An address prefix is represented as an IPv4 address followed\n"
"     by the character slash \"/\" followed by an integer in the\n"
"     range from 0 to 32.  The following are valid address\n"
"     prefixes: 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the\n"
"     following address prefixes are invalid: 0/0, 128.9/16 since\n"
"     0 or 128.9 are not strings containing four integers.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"origin\n"
"\n"
"   Specifies the AS that originates the route. The corresponding\n"
"   aut-num object should be registered in the database.\n"
"    ""\n"
"     An \"AS\" string followed by an integer in the range from 1 to\n"
"     65534\n"
"       ""\n"
"holes\n"
"\n"
"   Lists the component address prefixes that are not reachable\n"
"   through the aggregate route (perhaps that part of the address\n"
"   space is unallocated).\n"
"    ""\n"
"     An address prefix is represented as an IPv4 address followed\n"
"     by the character slash \"/\" followed by an integer in the\n"
"     range from 0 to 32.  The following are valid address\n"
"     prefixes: 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the\n"
"     following address prefixes are invalid: 0/0, 128.9/16 since\n"
"     0 or 128.9 are not strings containing four integers.\n"
"       ""\n"
"member-of\n"
"\n"
"   This attribute can be used in the route, aut-num and inet-rtr\n"
"   classes. The value of the \"member-of:\" attribute identifies a\n"
"   set object that this object wants to be a member of.  This\n"
"   claim, however, should be acknowledged by a respective\n"
"   \"mbrs-by-ref:\" attribute in the referenced object.\n"
"    ""\n"
"     An route-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"rs-\", and the last character of a name must\n"
"     be a letter or a digit.\n"
"\n"
"     A route-set name can also be hierarchical.  A hierarchical\n"
"     set name is a sequence of set names and AS numbers separated\n"
"     by colons \":\".  At least one component of such a name must\n"
"     be an actual set name (i.e. start with \"rs-\").  All the set\n"
"     name components of a hierarchical route-name have to be\n"
"     route-set names.\n"
"       ""\n"
"inject\n"
"\n"
"   Specifies which routers perform the aggregation and when they\n"
"   perform it.\n"
"    ""\n"
"     [at <router-expression>]\n"
"     [action <action>]\n"
"     [upon <condition>]\n"
"       ""\n"
"aggr-mtd\n"
"\n"
"   Specifies how the aggregate is generated.\n"
"      ""\n"
"     inbound | outbound [<as-expression>]\n"
"       ""\n"
"aggr-bndry\n"
"\n"
"   Defines a set of ASes, which form the aggregation boundary.\n"
"      ""\n"
"     [<as-expression>]\n"
"       ""\n"
"export-comps\n"
"\n"
"   Defines the set's policy filter, a logical expression which\n"
"   when applied to a set of routes returns a subset of these\n"
"   routes.\n"
"    ""\n"
"     Logical expression which when applied to a set of routes\n"
"     returns a subset of these routes. Please refer to RFC 2622\n"
"     for more information.\n"
"       ""\n"
"components\n"
"\n"
"   The \"components:\" attribute defines what component routes are\n"
"   used to form the aggregate.  \n"
"    ""\n"
"     [ATOMIC] [[<filter>] [protocol <protocol> <filter> ...]]\n"
"\n"
"     <protocol> is a routing routing protocol name such as\n"
"     BGP4, OSPF or RIP\n"
"\n"
"     <filter> is a policy expression\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"cross-mnt\n"
"\n"
"   References mntner(s) to be notified. The \"cross-mnt:\"\n"
"   attribute may be used in:\n"
"\n"
"      * route object - to get a notification for any overlaps\n"
"        with the prefix specified in that route object;\n"
"\n"
"      * aut-num object - to get a notification for overlaps with\n"
"        any of the prefixes announced in route objects in which\n"
"        the given AS number is specified in the \"origin:\"\n"
"        attribute.\n"
"\n"
"   A notification will be sent to mailbox(es) listed in cross-nfy\n"
"   and mailbox(es) listed in the \"mnt-nfy:\" attributes of the\n"
"   maintainers referenced by the cross-mnt whenever an\n"
"   overlapping route is added or removed.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"cross-nfy\n"
"\n"
"   References a NIC-handle pointing to a person or role object,\n"
"   the email address of which will be used for notification about\n"
"   the addition or removal of route objects, which overlap the\n"
"   prefixes of the already registered route objects. \n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-lower\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for hierarchical authorisation.  Protects creation of objects\n"
"   directly (one level) below in the hierarchy of an object type\n"
"   (only for inetnum, inet6num, as-block, aut-num, route or\n"
"   domain objects).  The authentication method of this maintainer\n"
"   object will then be used upon creation of any object directly\n"
"   below the object that contains the \"mnt-lower:\" attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"mnt-routes\n"
"\n"
"   This attribute references a maintainer object which is used in\n"
"   determining authorisation for the creation of route objects.\n"
"   After the reference to the maintainer, an optional list of\n"
"   prefix ranges inside of curly braces or the keyword \"ANY\" may\n"
"   follow. The default, when no additional set items are\n"
"   specified, is \"ANY\" or all more specifics. Please refer to\n"
"   RFC-2622 for more information.\n"
"    ""\n"
"     <mnt-name> [ { list of <address-prefix-range> } | ANY ]\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The route-set class:\n"
"\n"
"      A route-set object defines a set of routes that can be\n"
"      represented by route objects or by address prefixes. In the\n"
"      first case, the set is populated by means of the \"mbrs-by-ref:\"\n"
"      attribute, in the latter, the members of the set are explicitly\n"
"      listed in the \"members:\" attribute. The \"members:\" attribute is\n"
"      a list of address prefixes or other route-set names.  Note that\n"
"      the route-set class is a set of route prefixes, not of database\n"
"      route objects.\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"
"   Specifies the name of the route set. It is a primary key for\n"
"   the route-set object.\n"
"    ""\n"
"     An route-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"rs-\", and the last character of a name must\n"
"     be a letter or a digit.\n"
"\n"
"     A route-set name can also be hierarchical.  A hierarchical\n"
"     set name is a sequence of set names and AS numbers separated\n"
"     by colons \":\".  At least one component of such a name must\n"
"     be an actual set name (i.e. start with \"rs-\").  All the set\n"
"     name components of a hierarchical route-name have to be\n"
"     route-set names.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"members\n"
"\n"
"   Lists the members of the set.\n"
"    ""\n"
"     <address-prefix-range> or\n"
"     <route-set-name> or\n"
"     <route-set-name><range-operator>.\n"
"       ""\n"
"mbrs-by-ref\n"
"\n"
"   This attribute can be used in all \"set\" objects; it allows\n"
"   indirect population of a set. If this attribute is used, the\n"
"   set also includes objects of the corresponding type (aut-num\n"
"   objects for as-set, for example) that are protected by one of\n"
"   these maintainers and whose \"member-of:\" attributes refer to\n"
"   the name of the set. If the value of a \"mbrs-by-ref:\"\n"
"   attribute is ANY, any object of the corresponding type\n"
"   referring to the set is a member of the set. If the\n"
"   \"mbrs-by-ref:\" attribute is missing, the set is defined\n"
"   explicitly by the \"members:\" attribute.\n"
"    ""\n"
"     <mntner-name> | ANY \n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The filter-set class:\n"
"\n"
"       A filter-set object defines a set of routes that are matched by\n"
"       its filter.  The \"filter-set:\" attribute defines the name of\n"
"       the filter.  It is an RPSL name that starts with \"fltr-\".  The\n"
"       \"filter:\" attribute defines the set's policy filter.   A policy\n"
"       filter is a logical expression which when applied to a set of\n"
"       routes returns a subset of 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"
"   Defines the name of the filter. \n"
"    ""\n"
"     A filter-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"fltr-\", and the last character of a name\n"
"     must be a letter or a digit.\n"
"\n"
"     A filter-set name can also be hierarchical.  A hierarchical\n"
"     set name is a sequence of set names and AS numbers separated\n"
"     by colons \":\".  At least one component of such a name must\n"
"     be an actual set name (i.e. start with \"fltr-\").  All the\n"
"     set name components of a hierarchical filter-name have to be\n"
"     filter-set names.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"filter\n"
"\n"
"   Defines the set's policy filter.\n"
"    ""\n"
"     Logical expression which when applied to a set of routes\n"
"     returns a subset of these routes. Please refer to RFC 2622\n"
"     for more information.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The peering-set class:\n"
"\n"
"      A peering-set object defines a set of peerings that are listed \n"
"      in its \"peering:\" attributes.  The \"peering-set:\" attribute \n"
"      defines the name of the set. \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"
"   Specifies the name of the peering-set.\n"
"    ""\n"
"     A peering-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"prng-\", and the last character of a name\n"
"     must be a letter or a digit.\n"
"\n"
"     A peering-set name can also be hierarchical.  A hierarchical\n"
"     set name is a sequence of set names and AS numbers separated\n"
"     by colons \":\".  At least one component of such a name must\n"
"     be an actual set name (i.e. start with \"prng-\").  All the\n"
"     set name components of a hierarchical peering-set name have\n"
"     to be peering-set names.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"peering\n"
"\n"
"   Defines a peering that can be used for importing or exporting\n"
"   routes.\n"
"    ""\n"
"     <peering>\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The rtr-set class:\n"
"\n"
"      A rtr-set object defines a set of routers. A set may be described \n"
"      by the \"members:\" attribute, which is a list of inet-rtr names, \n"
"      IPv4 addresses or other rtr-set names. A set may also be populated \n"
"      by means of the \"mbrs-by-ref:\" attribute, in which case it is \n"
"      represented by 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"
"   Defines the name of the rtr-set.\n"
"    ""\n"
"     A router-set name is made up of letters, digits, the\n"
"     character underscore \"_\", and the character hyphen \"-\"; it\n"
"     must start with \"rtrs-\", and the last character of a name\n"
"     must be a letter or a digit.\n"
"\n"
"     A router-set name can also be hierarchical.  A hierarchical\n"
"     set name is a sequence of set names and AS numbers separated\n"
"     by colons \":\".  At least one component of such a name must\n"
"     be an actual set name (i.e. start with \"rtrs-\").  All the\n"
"     set name components of a hierarchical router-set name have\n"
"     to be router-set names.\n"
"       ""\n"
"descr\n"
"\n"
"   A short decription related to the object.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"members\n"
"\n"
"   Lists the members of the set.\n"
"    ""\n"
"     <inet-rtr-name> or\n"
"     <rtr-set-name> or\n"
"     <ipv4-address>\n"
"       ""\n"
"mbrs-by-ref\n"
"\n"
"   This attribute can be used in all \"set\" objects; it allows\n"
"   indirect population of a set. If this attribute is used, the\n"
"   set also includes objects of the corresponding type (aut-num\n"
"   objects for as-set, for example) that are protected by one of\n"
"   these maintainers and whose \"member-of:\" attributes refer to\n"
"   the name of the set. If the value of a \"mbrs-by-ref:\"\n"
"   attribute is ANY, any object of the corresponding type\n"
"   referring to the set is a member of the set. If the\n"
"   \"mbrs-by-ref:\" attribute is missing, the set is defined\n"
"   explicitly by the \"members:\" attribute.\n"
"    ""\n"
"     <mntner-name> | ANY \n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
"The irt class:\n"
"\n"
"       An irt object is used to define a Computer Security Incident\n"
"       Response Team (CSIRT).\n"
"    ""\n"
"irt:           [mandatory]  [single]     [primary/look-up key]\n"
"address:       [mandatory]  [multiple]   [ ]\n"
"phone:         [optional]   [multiple]   [ ]\n"
"fax-no:        [optional]   [multiple]   [ ]\n"
"e-mail:        [mandatory]  [multiple]   [lookup key]\n"
"signature:     [mandatory]  [multiple]   [ ]\n"
"encryption:    [mandatory]  [multiple]   [ ]\n"
"admin-c:       [mandatory]  [multiple]   [inverse key]\n"
"tech-c:        [mandatory]  [multiple]   [inverse key]\n"
"auth:          [mandatory]  [multiple]   [ ]\n"
"remarks:       [optional]   [multiple]   [ ]\n"
"irt-nfy:       [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 irt class are defined below:\n"
"\n"
"irt\n"
"\n"
"   Specifies the name of the irt object. The name should start\n"
"   with the prefix \"IRT-\", reserved for this type of object.\n"
"    ""\n"
"     An irt name is made up of letters, digits, the character\n"
"     underscore \"_\", and the character hyphen \"-\"; it must start\n"
"     with \"irt-\", and the last character of a name must be a\n"
"     letter or a digit.\n"
"       ""\n"
"address\n"
"\n"
"      Full postal address of a contact.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"phone\n"
"\n"
"   Specifies a telephone number of the contact.\n"
"    ""\n"
"     Contact telephone number. Can take one of the forms:\n"
"\n"
"     '+' <integer-list>\n"
"     '+' <integer-list> \"(\" <integer-list> \")\" <integer-list>\n"
"     '+' <integer-list> ext. <integer list>\n"
"     '+' <integer-list> \"(\" integer list \")\" <integer-list> ext. <integer-list>\n"
"       ""\n"
"fax-no\n"
"\n"
"   The fax number of a contact.\n"
"    ""\n"
"     Contact telephone number. Can take one of the forms:\n"
"\n"
"     '+' <integer-list>\n"
"     '+' <integer-list> \"(\" <integer-list> \")\" <integer-list>\n"
"     '+' <integer-list> ext. <integer list>\n"
"     '+' <integer-list> \"(\" integer list \")\" <integer-list> ext. <integer-list>\n"
"       ""\n"
"e-mail\n"
"\n"
"   The e-mail address of a person or role.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"signature\n"
"\n"
"   References a key-cert object representing a CSIRT public key\n"
"   used by the team to sign their correspondence.\n"
"    ""\n"
"     PGPKEY-<id>\n"
"\n"
"     <id> is  the PGP key ID of the public key in 8-digit\n"
"     hexadecimal format without \"0x\" prefix.\n"
"       ""\n"
"encryption\n"
"\n"
"   References a key-cert object representing a CSIRT public key\n"
"   used to encrypt correspondence sent to the CSIRT.\n"
"    ""\n"
"     PGPKEY-<id>\n"
"\n"
"     <id> is  the PGP key ID of the public key in 8-digit\n"
"     hexadecimal format without \"0x\" prefix.\n"
"       ""\n"
"admin-c\n"
"\n"
"   References an on-site administrative contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"tech-c\n"
"\n"
"   References a technical contact.\n"
"    ""\n"
"     From 2 to 4 characters optionally followed by up to 5 digits\n"
"     optionally followed by a source specification.  Source\n"
"     specification starts with \"-\" followed by source name up to\n"
"     9-character length.\n"
"       ""\n"
"auth\n"
"\n"
"   Defines an authentication scheme to be used.\n"
"    ""\n"
"<auth-scheme> <scheme-info>       Description\n"
"\n"
"NONE                              No authentication is required to\n"
"                                  make changes to the object protected\n"
"                                  with such authentication scheme.\n"
"\n"
"CRYPT-PW      encrypted           This scheme is our weeakest form\n"
"              password, produced  of authentication.  It is by\n"
"              by UNIX crypt(3)    no means meant to keep out a\n"
"              routine             determined malicious attacker.  The\n"
"                                  crypt function is vulnerable to\n"
"                                  exhaustive search by (lots of) fast\n"
"                                  machines and programs to do the\n"
"                                  searching are widely available. For\n"
"                                  this reason it is strongly\n"
"                                  discouraged to use encrypted\n"
"                                  passwords also used for other\n"
"                                  purposes such as UNIX login accounts\n"
"                                  in this scheme. As you are\n"
"                                  publishing the encrypted password in\n"
"                                  the database, it is open to attack.\n"
"                                  The usual caveats about crypt\n"
"                                  passwords apply, so it is not very\n"
"                                  wise to use words or combinations of\n"
"                                  words found in any dictionary of any\n"
"                                  language.\n"
"\n"
"MD5-PW        encrypted           This scheme is similar to the CRYPT-PW\n"
"              password, produced  scheme, except that it uses an MD5\n"
"              using the FreeBSD   hash rather than DES encryption to\n"
"              crypt_md5           generate the password. The main\n"
"              algorithm           benefit over CRYPT-PW is that pass \n"
"                                  phrases longer than 8 characters may\n"
"                                  be used. All of the dangers of\n"
"                                  CRYPT-PW also apply to MD5-PW.\n"
"\n"
"PGPKEY-<id>                       Strong scheme of authentication.\n"
"                                  <id> is the PGP key ID to be\n"
"                                  used for authentication. This string\n"
"                                  is the same one that is used in the\n"
"                                  corresponding key-cert object's\n"
"                                  \"key-cert:\" attribute.\n"
"       ""\n"
"remarks\n"
"\n"
"   Contains remarks.\n"
"    ""\n"
"     A sequence of ASCII characters.\n"
"       ""\n"
"irt-nfy\n"
"\n"
"   Specifies the e-mail address to be notified when a reference\n"
"   to the irt object is added or removed.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"notify\n"
"\n"
"   Specifies the e-mail address to which notifications of changes\n"
"   to an object should be sent.\n"
"    ""\n"
"     An e-mail address as defined in RFC 2822.\n"
"       ""\n"
"mnt-by\n"
"\n"
"   Specifies the identifier of a registered mntner object used\n"
"   for authorisation of operations performed with the object\n"
"   that contains this attribute.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a name\n"
"     must be a letter, and the last character of a name must be a\n"
"     letter or a digit.  The following words are reserved by\n"
"     RPSL, and they can not be used as names:\n"
"   \n"
"      any as-any rs-any peeras and or not atomic from to at\n"
"      action accept announce except refine networks into inbound\n"
"      outbound\n"
"   \n"
"     Names starting with certain prefixes are reserved for\n"
"     certain object types.  Names starting with \"as-\" are\n"
"     reserved for as set names.  Names starting with \"rs-\" are\n"
"     reserved for route set names.  Names starting with \"rtrs-\"\n"
"     are reserved for router set names. Names starting with\n"
"     \"fltr-\" are reserved for filter set names. Names starting\n"
"     with \"prng-\" are reserved for peering set names. Names\n"
"     starting with \"irt-\" are reserved for irt names.\n"
"       ""\n"
"changed\n"
"\n"
"   Specifies who submitted the update, and when the object was\n"
"   updated. \n"
"    ""\n"
"     An e-mail address as defined in RFC 2822, followed by a date\n"
"     in the format YYYYMMDD.\n"
"       ""\n"
"source\n"
"\n"
"   Specifies the registry where the object is registered.  Should\n"
"   be \"RIPE\" for the RIPE Database.\n"
"    ""\n"
"     Made up of letters, digits, the character underscore \"_\",\n"
"     and the character hyphen \"-\"; the first character of a \n"
"     registry name must be a letter, and the last character of a\n"
"     registry name must be a letter or a digit.\n"
"       ""\n"
,
NULL
}; /* Templates_v */
