Antony Antony antonyripe.net

1
Routing Information Service (RIS)

• Antony Antony ltantony_at_ripe.netgt
• Henk Uijterwaal lthenk_at_ripe.netgt
• RIPE-34, Amsterdam. Sep. 1999

2
Overview

• Goals of the RIS
• Prototype
• Proposed Final setup
• HW SW
• Open Questions

3
Where to find the slides

• RIS home page
• http//www.ripe.net/ris
• Discussions
• ltrouting-wg_at_ripe.netgt
• Questions about RIS
• Antony Antony ltantony_at_ripe.netgt
• Henk Uijterwaal lthenk_at_ripe.netgt

4
Why Collect BGP Updates ?

• Routing problems are instantaneous
• need to be recorded to track
• BGP announcements originate from independent
  sources
• Follow back to origin from remote ends
• NOCs can offer better service to customers
  using RIS
• Network operators can track usage of IP addresses
  and AS
• Check past routing table against RRs

5
Goals of the RIS

• Past BGP updates between AS available to RIPE
  community
• Interactive query of past routing table for RIPE
  community
• Prefix, AS Path, Origin AS
• other BGP Attributes for IPv4
• Check real routing data against policies IRR
  reality check
• Reports like- IP address AS in use
• Raw data

6
Why RIPE NCC is doing This Project ?

• RIPE NCC is a neutral body
• Experience from Test Traffic project.

7
Prototype
8
Proposed Final Setup
9
Data collection

• RRC Peer AS12654 with all possible peers at IX
• Few multi hop EBGP with remote Border router
• up to 10 Exchange Points
• Up to 70 peers at each IX
• Each peer announces the whole routing table
  (about 64 K prefixes)

10
Remote Route Collector

• BGP4 IPv4 announcements between AS
• AS path Origin AS
• Route prefix and length
• Any additional BGP attributes which are
  propagated through the system
• Errors in the BGP announcements
• Snapshots of routing table 3/day

11
Software

• BGP Listener
• Multi-threaded Routing Toolkit (MRT)
• GNU-Zebra
• Possible to extend to IPv6
• Central data collector
• User interface
• Command line query tool
• Web interface
• Reports Statistics

12
Possible Queries to the RIS

• 193.0.0.0/22 updates since yesterday
• announcements from AS3333 at 600
• who announced 193.0.0.0/22 yesterday
• flap statistics of a prefix/AS for a period

13
Database Considerations

• About 110 M prefix updates / day
• 700 snapshots / day
• Insert data collected from RRC
• Should Answer queries O (10) sec

14
Updates in first 3 min from Prototype6,500
prefix updates / sec / peer
Time in seconds
15
Raw Data Volume G Bytes
16
Hardware Considerations

• RRCs Memory and IO intensive
• Typically 256 Mbytes RAM
• 20 GB Disk space
• NCC RIS
• Raw data for analysis 600 G bytes Indexes
• Tape storage 1.2 T Bytes

17
Related Projects

• Bgp Updates IPMA/Merit
• http//www.merit.edu/ipma/
• Route views U Oregorn
• http//moat.nlanr.net/
• ASExplorer
• http//www.merit.edu/ipma/docs/Manual/asexplorer.h
  tml
• CAIDA
• http//www.caida.org

18
Open Questions for this Project

• Define potential user base
• Setting up peerings at IXs
• Data collection from RRC
• Data handling
• Turning the RIS into a regular service
• Late 2000

19
Next Steps

• Design draft document (ripe-200)
• Final project proposal Oct 01, 1999
• Before RIPE-35
• Setup first RRC
• Make Raw data available and present extracted
  statistics
• Prototype UI for ? testing
• Hardware proposal for NCC RIS server
• RIPE35
• Present answers to the open questions

20
More Information

• RIS home page
• http//www.ripe.net/ris
• Discussions ltrouting-wg_at_ripe.netgt
• Questions about the RIS
• Antony Antony ltantony_at_ripe.netgt
• Henk Uijterwaal lthenk_at_ripe.netgt

21
Questions?