GROW WORKING GROUPIETF 78

MAASTRICHT

draft-manderson-grow-geomrt-00

Summary

Research is underway that analyzes the network behavior of routing protocol transactions from routing information base snapshots in relation to geographical coordinates. Specifically the BGP routing protocol is the subject of study and the analysis has been significantly aided by the availability and extension of the "MRT format" [I-D.ietf-grow-mrt] originally defined in the MRT Programmer's Guide [MRT PROG GUIDE].

Summary

Documents an extension to the "MRT format” [I-D.ietf-grow-mrt] and introduces an additional definition of a MRT Type field and related Subtype fields.

Current Drafts / Dependency

Blunk, L., Karir, M., and C. Labovitz, "MRT routing information export format", draft-ietf-grow-mrt-11 (work in progress), March 2010

Feedback

So far all off-list emails positiveBUT, No discussion on the MLOne suggestion (privately) to escalate the

collector GPS Coordinates outside of the BGP format. still open to the idea, however decouples the first class nature of the location data

from the BGP dump potential issues of historical collection

Question to WG

Table type number Currently documented 65, requires IETF review Or use different number? (FCFS, or other?)

Implementation (zebra)

! Zebra configuration saved from vty! 2010/07/05 21:16:11!hostname bgpdpassword XXXXenable password XXXXlog file /opt/bgpd-log/error.log!router bgp 64512bgp router-id 208.77.191.17bgp geo 33.980198 -118.440033network 208.77.191.17/32neighbor 192.0.35.254 remote-as 40528neighbor geo 33.980198 -118.440033neighbor 192.0.35.254 ebgp-multihop 255neighbor 192.0.35.254 distribute-list all inneighbor 192.0.35.254 distribute-list zero outneighbor 2620:0:2d0:ffff::254 remote-as 40528neighbor 2620:0:2d0:ffff::254 geo 33.980198 -118.440033neighbor 2620:0:2d0:ffff::254 ebgp-multihop 255!address-family ipv6network 2620:0:2d0:3::17/128neighbor 2620:0:2d0:ffff::254 activateneighbor 2620:0:2d0:ffff::254 distribute-list all6 inneighbor 2620:0:2d0:ffff::254 distribute-list zero6 outexit-address-family!

Implementation (cont)

Code/diffs will be made available insert usual set of disclaimers modulo a rework of some acquired IP issues.

Next step

Believe it is of valueRequest adoption as a Work Group item