migration to the new ripe database
Download
Skip this Video
Download Presentation
Migration to the new RIPE Database

Loading in 2 Seconds...

play fullscreen
1 / 15

Migration to the new RIPE Database - PowerPoint PPT Presentation


  • 159 Views
  • Uploaded on

Migration to the new RIPE Database. Andrei Robachevsky RIPE NCC <[email protected]>. Outline. Current status of the RIPE Database New version of the Database Migration timeline More information. RIPE Database Status. Contains IP allocations/assignments Domain registry Routing registry

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Migration to the new RIPE Database' - brygid


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
migration to the new ripe database

Migration to the new RIPE Database

Andrei Robachevsky

RIPE NCC

outline
Outline
  • Current status of the RIPE Database
  • New version of the Database
  • Migration timeline
  • More information
ripe database status
RIPE Database Status
  • Contains
    • IP allocations/assignments
    • Domain registry
    • Routing registry
  • 3.7 Million objects
    • 75% person, 10% inetnum, 0.65% route
  • 6,700 updates/day
  • 770,000 queries/day (9 queries/s)
    • 38% IP addresses, 1% IP prefixes
ripe routing registry
RIPE Routing Registry
  • 24500 routes, 4000 aut-num’s
    • 13500 routes are not announced
    • 6454 routes are not registered
    • 60% of all registered routes are “foreign” (non-RIPE ASN or IP space)
  • Routing Registry Consistency Check Project
    • identify bad data
    • help to correct it
    • keep it up-to-date
    • http://www.ripe.net/ripencc/pub-services/rrcc
new version of the database
New version of the Database
  • Supports RPSL (RFC2622)
    • Extended syntax
    • New objects and attributes
  • Supports RPS-auth (RFC2725)
    • New authorization rules
  • Supports RAToolset
  • Code is completely rewritten
    • New database format
    • New version of mirroring protocol
    • New access control
rpsl support
RPSL Support
  • Extended syntax rules are applied to all object types
  • New objects
    • as-set (as-macro), route-set (community)
    • peering-set
    • filter-set
    • rtr-set
  • New attributes
    • member-of
    • mbrs-by-ref
rps sec support
RPS-SEC support
  • New authorization rules
    • route creation
    • aut-num
    • hierarchical names
  • New object
    • as-block
  • New attributes
    • mnt-routes: [ rpsl list of prefixes | ANY]
    • referral-by:
    • auth-override: YYYYMMDD
ratoolset support
RAToolset Support
  • New queries
    • -l
    • -x
    • -K
  • RtConfig -protocol bird
  • Patch is available
    • to parse RIPE-style comments (%)
new software
New software
  • Mainly in C
  • RDBMS as a back-end
    • MySQL
    • Transaction support
  • In-memory radix tree for IP lookups
    • also more and less specific lookups for reverse delegation domains
  • Automatic access control
    • separate accounting for public and contact data
  • New version of NRTM protocol
who will be affected
Who will be affected ?
  • Query users
      • new query flags
  • Update users
      • new syntax rules
      • new authorization rules
  • Scripts
      • new object format and syntax
      • new/modified objects and attributes
      • access control
  • NRTM clients
      • new software
      • new version of the mirroring protocol
transition timeline updates
Production

Prototype/Compatibility

Transition timeline - Updates

Updates in RIPE-181

to

Updates in RIPE-181

to

Updates in RPE-181

to

RIPE181

Updates in RPSL

to

Updates in RPSL

to

RPSL

Updates in RPSL

to

Updates in RPSL

to

TEST

Proposed dates:

X=23 April

Day X

Y=14 May

Day Y

Z=15 October

Day Z

transition timeline queries
Production

Prototype

Transition timeline - Queries

Querying RIPE DB in RIPE-181

at whois.ripe.net :43

RIPE-181

v2.x

Querying RIPE DB in RPSL

at rpsl.ripe.net :43

Additional flags available

Querying RIPE DB in RPSL

at whois.ripe.net : 43

Additional flags available

RPSL

v3.0

Day X

transition timeline nrtm
Production

Prototype

Transition timeline - NRTM

Mirroring RIPE DB in RIPE-181

at whois.ripe.net :43

RIPE181

v2.x

Mirroring RIPE DB in RPSL

at rpsl.ripe.net :4444

Mirroring RIPE DB in RPSL

at whois.ripe.net : 4444

RPSL

v3.0

Day X

prototype servers
Prototype servers
  • Near real-time mirror of the RIPE Database
    • whois -h rpsl.ripe.net
    • contains live RIPE Database in RPSL format
  • Test server for submissions
    • mail
    • whois -h rpsl.ripe.net -p 4343
  • NRTM
    • rpsl.ripe.net, port 4444
    • discuss with
more information
More Information
  • RIPE-181 to RPSL Migration page
    • http://www.ripe.net/rpsl
  • Documentation
    • Transition to the RIPE DB v3.0
    • Whois Queries in the RIPE DB v3.0
    • Updates in the RIPE DB v3.0
    • Error codes in the RIPE DB v3.0
  • Software
    • New whois client ftp://ftp.ripe.net/ripe/dbase/reimp/whoisRIP-1.0.tar.gz
    • Server software v3.0http://www.ripe.net/ripencc/pub-services/db/reimp/latestbeta.html
ad