1 / 9

draft-manderson-grow-geomrt-00

draft-manderson-grow-geomrt-00. GROW Working Group IETF 78 Maastricht. Summary.

vilina
Download Presentation

draft-manderson-grow-geomrt-00

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-manderson-grow-geomrt-00 GROW Working Group IETF 78 Maastricht

  2. 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].

  3. 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.

  4. 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

  5. Feedback • So far all off-list emails positive • BUT, No discussion on the ML • One 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

  6. Question to WG • Table type number • Currently documented 65, requires IETF review • Or use different number? (FCFS, or other?)

  7. Implementation (zebra) ! Zebra configuration saved from vty ! 2010/07/05 21:16:11 ! hostname bgpd password XXXX enable password XXXX log file /opt/bgpd-log/error.log ! router bgp 64512 bgp router-id 208.77.191.17 bgp geo 33.980198 -118.440033 network 208.77.191.17/32 neighbor 192.0.35.254 remote-as 40528 neighbor geo 33.980198 -118.440033 neighbor 192.0.35.254 ebgp-multihop 255 neighbor 192.0.35.254 distribute-list all in neighbor 192.0.35.254 distribute-list zero out neighbor 2620:0:2d0:ffff::254 remote-as 40528 neighbor 2620:0:2d0:ffff::254 geo 33.980198 -118.440033 neighbor 2620:0:2d0:ffff::254 ebgp-multihop 255 ! address-family ipv6 network 2620:0:2d0:3::17/128 neighbor 2620:0:2d0:ffff::254 activate neighbor 2620:0:2d0:ffff::254 distribute-list all6 in neighbor 2620:0:2d0:ffff::254 distribute-list zero6 out exit-address-family !

  8. Implementation (cont) • Code/diffs will be made available • insert usual set of disclaimers • modulo a rework of some acquired IP issues.

  9. Next step Believe it is of value Request adoption as a Work Group item

More Related