About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
RIPE NCC Mail Archives
     
Mailing Lists:
RIPE NCC Navigation Ends
Link to NCC Lists Archive NCC Lists Archive
Link to RIPE Lists Archive RIPE Lists Archive
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

mntner object

  • From: Frank Bohnsack < >
  • Date: Mon, 29 Jan 2001 15:13:14 +0100 (MET)
  • Organization: UUNET Deutschland GmbH
  • Reply-to:

Dear RIPE DB colleagues,

follow is attracted attention me:

fb@localhost 268>  whois -h rpsl.ripe.net -v mntner
% This is the RIPE Whois server v3.0 beta.
% This server mirrors the RIPE Database in RPSL format.

The mntner class:

      The mntner object contains details of who is authorised
      to make changes to RIPE Database objects and details of
      a process that actually verifies that the person who
      makes the changes is authorised to do so.
      Mntner objects are not created automatically, but are
      forwarded to RIPE NCC staff.
   
mntner:        [mandatory]  [single]     [primary/look-up key]
descr:         [mandatory]  [multiple]   [ ]
admin-c:       [mandatory]  [multiple]   [inverse key]
tech-c:        [optional]   [multiple]   [inverse key]
upd-to:        [mandatory]  [multiple]   [inverse key]
mnt-nfy:       [optional]   [multiple]   [inverse key]
auth:          [mandatory]  [multiple]   [ ]
remarks:       [optional]   [multiple]   [ ]
notify:        [optional]   [multiple]   [inverse key]
mnt-by:        [mandatory]  [multiple]   [inverse key]
auth-override: [optional]   [single]     [ ]
referral-by:   [mandatory]  [single]     [inverse key]
changed:       [mandatory]  [multiple]   [ ]
source:        [mandatory]  [single]     [ ]

The content of the attributes of the mntner class are defined below:

...
   
referral-by

      This attribute is required in the maintainer object.  It
      may never be altered after the addition of the maintainer.  This
      attribute refers to the maintainer that created this maintainer.
      It may be multiple if more than one signature appeared on the
      transaction creating the object.
   
      INSERT referral-by format here.


The "referral-by" and "auth-override" objects are missing in the last RPSL
meeting (monday) at RIPE 38 by Andrei Robachevsky. 

The "referral-by" attribute is mandatory, but not set in all mntner object on rpsl.ripe.net. 
In my understanding it should be point to it self.

comments ?


cheers
Frank






  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE NCC | Service Announcements | Site Map | LIR Portal | About RIPE | Contact | Legal | © RIPE NCC. All rights reserved.
RIPE NCC Homepage Go to the RIPE NCC LIRPortal Go to the RIPE Community pages