Migration to the new ripe database
This presentation is the property of its rightful owner.
Sponsored Links
1 / 15

Migration to the new RIPE Database PowerPoint PPT Presentation


  • 112 Views
  • Uploaded on
  • Presentation posted in: General

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

Download Presentation

Migration to the new RIPE Database

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

<[email protected]>


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: <mnt_name> [ rpsl list of prefixes | ANY]

    • referral-by: <mnt_name>

    • auth-override: YYYYMMDD


Ratoolset support

RAToolset Support

  • New queries

    • -l <ip range>

    • -x <ip range>

    • -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 <[email protected]>

    Updates in RIPE-181

    to <[email protected]>

    Updates in RPE-181

    to <[email protected]>

    RIPE181

    Updates in RPSL

    to <[email protected]>

    Updates in RPSL

    to <[email protected]>

    RPSL

    Updates in RPSL

    to <[email protected]>

    Updates in RPSL

    to <[email protected]>

    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 <[email protected]>

      • whois -h rpsl.ripe.net -p 4343

    • NRTM

      • rpsl.ripe.net, port 4444

      • discuss with <[email protected]>


    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


  • Login