Route Flap Damping Deployment Status Survey draft-shishio-grow-isp-rfd-implement-survey Shishio Tsuchiya Seiichi Kawamura.

Slides:



Advertisements
Similar presentations
71 th IETF meeting Experience of implementing NETCONF over SOAP ( draft-iijima-netconf-soap-implementation-06) Tomoyuki Iijima, Yoshifumi Atarashi, Hiroyasu.
Advertisements

© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—5-1 MPLS VPN Implementation Configuring BGP as the Routing Protocol Between PE and CE Routers.
Design Guidelines for IPv6 Networks draft-matthews-v6ops-design-guidelines-01 Philip Matthews Alcatel-Lucent.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public Presentation_ID 1 BGP Diverse Paths draft-ietf-grow-diverse-bgp-paths-dist-02 Keyur Patel.
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
BGP Scaling Techniques Scalable Infrastructure Workshop AfNOG 2010.
Delayed Internet Routing Convergence due to Flap Dampening Z. Morley Mao Ramesh Govindan, Randy Katz, George Varghese
Part V: BGP Beacons -- A n Infrastructure for BGP Monitoring.
1 BGP Anomaly Detection in an ISP Jian Wu (U. Michigan) Z. Morley Mao (U. Michigan) Jennifer Rexford (Princeton) Jia Wang (AT&T Labs)
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—7-1 Optimizing BGP Scalability Limiting the Number of Prefixes Received from a BGP Neighbor.
BGP Scaling Techniques Philip Smith E2 Workshop, AfNOG 2006.
Making Route Servers Aware of Data Link Failure at IXPs Dr. Thomas King Manager R&D Discussion: Internet Draft.
An Operational Perspective on BGP Security Geoff Huston GROW WG IETF 63 August 2005.
1 Finding a Needle in a Haystack: Pinpointing Significant BGP Routing Changes in an IP Network Jian Wu (University of Michigan) Z. Morley Mao (University.
Comments Where do I go from here?. Types of Studies. Meta Case Study Historical ( not hysterical) Descriptive i.e. Survey Comparing one population Comparing.
BGP Wedgies ---- Bad Policy Interactions that Cannot be Debugged JaNOG / Kyushu
BMP(BGP Monitoring Protocol) Testing by *JANOGers
Performance-based BGP Routing Mechanism draft-xu-idr-performance-routing-00 Xiaohu Xu (Huawei) Hui Ni (Huawei) Mohamed Boucadair (France.
DMM Framework based on Functional Elements draft-liebsch-dmm-framework-analysis-02 M. Liebsch, P. Seite, G. Karagiannis IETF88, Vancouver DMM WG 08 th.
IPv6 Site Renumbering Gap Analysis draft-ietf-6renum-gap-analysis-02 draft-ietf-6renum-gap-analysis-02 Bing Liu (speaker), Sheng Jiang, Brian.E.Carpenter,
APNIC eLearning: Intro to RPKI 10 December :30 PM AEST Brisbane (UTC+10)
Policy Implementation and Experience Report Leslie Nobile.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Addressing in an Enterprise Network Introducing Routing and Switching in the.
Advertising Equal Cost Multi-Path Routes in BGP Manav Bhatia Samsung India Software Operations, Bangalore – India July 17, th IETF - Vienna draft-ecmp-routes-in-bgp-00.txt.
Interconnectivity Density Compare number of AS’s to average AS path length A uniform density model would predict an increasing AS Path length (“Radius”)
Error reports as a source for SPI Tor Stålhane Jingyue Li, Jan M.N. Kristiansen IDI / NTNU.
BEHAVE BOF (Behavior Engineering for Hindrance AVoidancE) Cullen Jennings Jiri Kuthan.
APNIC Policy Update 1 st TWNIC Open Policy Meeting 3 December, 2003 Taipei, Taiwan.
1 IPv6 Deployment Scenarios in (e) Networks draft-ietf-v6ops deployment-scenarios-01 Myung-Ki Shin, ETRI Youn-Hee Han, KUT Sang-Eon Kim, KT.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Addressing in an Enterprise Network Introducing Routing and Switching in the.
Recommendations of Unique Local Addresses Usages draft-ietf-v6ops-ula-usage-recommendations-02 draft-ietf-v6ops-ula-usage-recommendations-02 Bing Liu(speaker),
BGP operations and security draft-jdurand-bgp-security-02.txt Jerome Durand Gert Doering Ivan Pepelnjak.
Proposal for new Working Group Item: Core Router Software Accelerated Life Testing (draft-poretsky-routersalt-term-00.txt) Authors: Scott Poretsky, Avici.
OSPFv3 Stub Router Advertisement
Route Flap Damping Deployment Status Survey draft-shishio-grow-isp-rfd-implement-survey Shishio Tsuchiya Seiichi Kawamura.
BGP4 - Border Gateway Protocol. Autonomous Systems Routers under a single administrative control are grouped into autonomous systems Identified by a 16.
ERS Update Plus Revisions to Proposed Changes for ERS Time Periods Presented to: Demand Side Working Group November 5, 2014.
NMI End-to-End Diagnostic Advisory Group BoF Fall 2003 Internet2 Member Meeting.
IANA Stewardship Transition Process Session Update Izumi Okutani Chair, The CRISP Team.
By, Matt Guidry Yashas Shankar.  Analyze BGP beacons which are announced and withdrawn, usually within two hour intervals.  The withdraws have an effect.
1 MPLS: Progress in the IETF Yakov Rekhter
CONEX BoF. Welcome to CONEX! Chairs: –Leslie Daigle –Philip Eardley Scribe Note well.
81st IETF - Quebec, Canada IJsbrand Yiqun draft-wijnands-pim-neighbor-reduction-01.
BLACKHOLE BGP Community for Blackholing T. King, C. Dietzel, J. Snijders, G. Doering, G. Hankins.
© 2001, Cisco Systems, Inc. 1-1 Introduction Configuring BGP on Cisco Routers.
Policies for ASN Management in the Asia Pacific Region – Revised Draft Address Policy SIG APNIC14, Kitakyushu, Japan 4 Sept 2002.
4 Byte AS Number Update Geoff Huston August 2008.
Magnus Westerlund 1 The RTSP Core specification draft-ietf-mmusic-rfc2326bis-06.txt Magnus Westerlund Aravind Narasimhan Rob Lanphier Anup Rao Henning.
MEXT Deliverable status IETF 71. Deliverables (I) Dec 2007Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG –draft-ietf-mip6-nemo-v4traversal-06 –WGLC.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—5-1 Customer-to-Provider Connectivity with BGP Connecting a Multihomed Customer to a Single Service.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—7-1 Optimizing BGP Scalability Using BGP Route Dampening.
RPSEC WG Issues with Routing Protocols security mechanisms Vishwas Manral, SiNett Russ White, Cisco Sue Hares, Next Hop IETF 63, Paris, France.
Doc.: IEEE sru Submission 11 November 2013 M Ariyoshi, S Kitazawa (ATR)Slide 1 Project: IEEE P Working Group for Wireless Personal.
IDR WG Document Status Update Sue Hares, Yakov Rekhter November 2005.
Draft-li-idr-cc-bgp-arch-00IETF 88 IDR1 An Architecture of Central Controlled Border Gateway Protocol (BGP) draft-li-idr-cc-bgp-arch-00 Zhenbin Li, Mach.
 How to Reach Us  Service Support Levels  Support Definitions & Standards  Response Levels  Point of Contact  Our Escalation Processes  Expect a.
IPv6 Working Group IETF55 Atlanta November URL for Thermometer
6TSCH Webex 07/05/2013. Reminder: This call is recorded the record is public Minutes are taken and published to the ML.
AS Numbers - Again Geoff Huston APNIC October 2009
Benchmarking for CoPP draft-shishio-bmwg-copp-00 Shishio Tsuchiya
BGP Deployment & Scalability
BCOP Taskforce Administrative Matters
draft-white-i2rs-use-case-02
Jian Wu (University of Michigan)
APNIC Open Address Policy Meeting
Stateless IPv4 over IPv6 report draft-janog-softwire-report-00
draft-lts-pim-hello-mtu-01
Geoff Huston APNIC August 2009
Network Monitoring Protocol (NMP)
Levels of involvement Consultation Collaboration User control
Presentation transcript:

Route Flap Damping Deployment Status Survey draft-shishio-grow-isp-rfd-implement-survey Shishio Tsuchiya Seiichi Kawamura Randy Bush Cristel Pelsser

abstract BGP Route Flap Damping [RFC2439] is a mechanism that targets route stability. It penalizes routes that flap with the aim of reducing CPU load on the routers. But it has side-effects. Thus, in 2006, RIPE recommended not to use Route Flap Damping (see RIPE-378). Now, some researchers is proposing to turn RFD with less aggressive parameters. [draft-ymbk-rfd-usable] When Randy did presentation the report on JANOG meeting,there were different opinions about RFD among ISP operators. We took a survey on JANOG to analyze current RFD operational practices. The purposes of this draft are to share the results of the current practice survey, and to get more opinions on where to go with the solution space.

from [draft-ymbk-rfd-usable] Propose to raise implementation/configuration – the suppress threshold to no less than 6000 – the maximum threshold to 50K only 3% prefix are responsible 36% bgp update mice even “mice” was damped

RFD documentation summary RIPE-378 RFC2439 draft-ymbk-rfd-usable Parameter Consideration / Recommendation Architecture Definition Route Flap Damping Deployme nt Status Survey USE/Not USE Refer/Not Refer What do you think? RIPE-178 RIPE-210 RIPE-229 Parameter Consideration / Recommendation Revised Feedback

Survey's target and period Japan Network Operator Group (+4000 subscibrers) Jan 28, Feb 12, and future All operators Already announced to Please open the following url and answer the questionaire. - May 25,2011

Q1.Do you use Route Flap Damping ? 27.8%(5) 72.2%(13)

Q2.If you select No on Q1,why? 21.4%(3) 14.3%(2) 21.4%(3) 7.1%(1) 14.3%(2) 21.4%(3)

Q3.If you select Yes on Q1,what parameter do you use? 50.0%(3)

Q4.Do you know Randy Bush et. al's report ''Route Flap Damping Considered Usable?'' 63.2%(12) 36.8%(7)

Q5.IOS's max-penalty is currently limited to 20K. Do you need this limitation to be relaxed to over 50K? 52.6%(10) 47.4%(9)

Q6.If you have any comments, please fill this box. Our peer seems to have damping enabled, and our prefix gets damped sometimes. We do not enable damping because we think that customers want a non-damped route. From the perspective of a downstream ISP, if our upstream told us that an outage occurred because a route was damped, I may call an ask "is it written in the agreement that you will do this?“ We use damping pretty heavily I had RFD turned on until this morning when I discovered our router has CSCtd26215 issues. I would like to turn on a "useful" RFD.

Summary of data From the survey we see that there are many service providers with RFD disabled. The reason varies among providers, but it is clear that there are those who wish that RFD was made useful. there are still some providers who turn on RFD with default settings.

difference between Japanese and English of survey Added a question to understand what operators want. – Which is the best description of your job role? – According to [draft-ymbk-rfd-usable], Suppress Threshold should be set to 6K.Do you think the default value on implementations should be changed to 6K?

next step.. please forward questionnaire to operators or NOGs you know will publish 02 to reflect survey results after the May cutoff grow or idr – grow is in ops, which can do requirements/surveys/..., but not protocol. so this fits right in. – idr is in routing which do protocols.