RADB Web Update Help

About RADB Web Update

The RADB Web Update interface allows one to easily create, modify, and delete RADB objects from their web browser. Web Update requires the use of a password to authorize updates. New users automatically create this password when registering their maintainer account. If you have forgotten your password or have not yet created a password, you will need to follow these procedures to replace or add a password.

Creating objects

The RADB Web Update form can be used to create new objects in the RADB by selecting the object type in the "Specify object type" field and then clicking on "Create". You will be presented with a web form where you can fill in the object attributes. For many users, the only objects they will likely wish to create are "route" and "aut-num" objects. The "aut-num" object contains the routing policy for your autonomous system (AS) number. There is only one "aut-num" object created per AS number. Route objects correspond to the IP address blocks (prefixes) which you wish to announce and are used primarily to specifiy the origin AS number. A basic tutorial on creating these two types of objects can be found here.

Modify or delete an existing object

To update an existing object, enter the object in the "Search String" field and click on "Search". Any existing objects will be displayed in a web form which will allow you to either update the existing object or entirely delete it. Another option is to enter your maintainer id in the "Maintainer name" field to show all objects belonging to your maintainer. You will then be able to individually update or delete these objects.

RPSL Object class types:

Below is a list of the RPSL Object classes supported by RADB Web Update. Each Object class has a number of attributes associated with it. These attributes are also documented below. This documentation presents only a brief overview of the RPSL standard. For a full reference on the standard, please refer to RFC 2622: Routing Policy Specification Language.

as-set

Example:
  as-set: as-foo
  members: AS1, AS2, as-bar

aut-num

Example:
  aut-num: AS1
  as-name: ACMECORP
  import: from AS2 action pref = 1; accept { 128.9.0.0/16 }

filter-set

Example:
   filter-set: fltr-foo
   filter:     { 5.0.0.0/8, 6.0.0.0/8 }

inet-rtr

Example:
   inet-rtr: Amsterdam.ripe.net
   alias:    amsterdam1.ripe.net
   local-as: AS3333
   ifaddr:   192.87.45.190 masklen 24
   ifaddr:   193.0.0.158   masklen 27
   peer:     BGP4 192.87.45.195 asno(AS3334), flap_damp()

key-cert

mntner

peering-set

Example:
   peering-set:  prng-bar
   peering:      AS1 at 9.9.9.1

person

Example:
   person:      Daniel Karrenberg
   address:     RIPE Network Coordination Centre (NCC)
   address:     Singel 258
   address:     NL-1016 AB  Amsterdam
   address:     Netherlands
   phone:       +31 20 535 4444
   fax-no:      +31 20 535 4445
   e-mail:      Daniel.Karrenberg@ripe.net
   nic-hdl:     DK58
   changed:     Daniel.Karrenberg@ripe.net 19970616
   source:      RIPE

role

Example:
   role:        RIPE NCC Operations
   address:     Singel 258
   address:     1016 AB Amsterdam
   address:     The Netherlands
   phone:       +31 20 535 4444
   fax-no:      +31 20 545 4445
   e-mail:      ops@ripe.net
   nic-hdl:     OPS4-RIPE
   notify:      ops@ripe.net
   changed:     roderik@ripe.net 19970926
   source:      RIPE

route

Example:
   route:  128.9.0.0/16
   origin: AS226

route6

Example:
   route6: 2001:0DB8::/32
   origin: AS65001

route-set

Examples:
   route-set: rs-foo
   members:   128.9.0.0/16, 128.9.0.0/24

   route-set: rs-bar
   members:   128.7.0.0/16, rs-foo

rtr-set

Examples:
   rtr-set: rtrs-foo                   
   members: rtr1.isp.net, rtr2.isp.net 

   rtr-set: rtrs-bar
   members: rtr3.isp.net, rtrs-foo

RPSL Attributes:

descr

tech-c

admin-c

remarks

notify

mnt-by

changed

   changed:  <RFC822 e-mail address>  <DATE>

source

upd-to

mnt-nfy

auth

as-name

import

   import: from <peering-1> [action <action-1>]
            . . .
            from <peering-N> [action <action-N>]
            accept <filter>

export

   export: from <peering-1> [action <action-1>]
            . . .
            from <peering-N> [action <action-N>]
            announce <filter>

    default: to <peering> [action <action>] [networks <filter>]

alias

local-as

ifaddr

  ifaddr: <ipv4-address> masklen <integer> [action <action>]

peer

  peer:  <protocol> <ipv4-address>      <options>
       | <protocol> <inet-rtr-name>     <options>
       | <protocol> <rtr-set-name>      <options>
       | <protocol> <peering-set-name>  <options>

origin

  origin:  AS237

components

aggr-bndry

aggr-mtd

 aggr-mtd: inbound
         | outbound [<as-expression>]

export-comps

holes

inject

 inject: [at <router-expression>] ...
          [action <action>]
          [upon <condition>]

filter

address

phone

fax-no

e-mail

nic-hdl

trouble

member-of

members

mbrs-by-ref

method

owner

fingerpr

certif