1 / 9

Bidrectional Forwarding Detection IETF 62

Bidrectional Forwarding Detection IETF 62. Jeffrey Haas - jhaas@nexthop.com Dave Ward - dward@cisco.com. Agenda. Agenda bashing – 5 min Document Status, Dave Ward – 20 mins Working Group Status, Jeff Haas – 10 min BFD Focus, Jeff Haas – 5 mins Q&A. Document Status. Dave…. We’re late.

mina
Download Presentation

Bidrectional Forwarding Detection IETF 62

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. Bidrectional Forwarding DetectionIETF 62 Jeffrey Haas - jhaas@nexthop.comDave Ward - dward@cisco.com

  2. Agenda • Agenda bashing – 5 min • Document Status, Dave Ward – 20 mins • Working Group Status, Jeff Haas – 10 min • BFD Focus, Jeff Haas – 5 mins • Q&A

  3. Document Status Dave…

  4. We’re late • Most WG Documents were expected to be last called in August of 2004.

  5. Procedural Status (1) • Based on Dave’s update, we will have at least one more revision of the base protocol document. • Clarifications sought in the 1hopv4v4 document need to be integrated. • The MIB needs to be brought into harmony with the latest changes.

  6. Procedural Status (2) • Cisco and Nortel have filed IPR claims against BFD.See https://datatracker.ietf.org/public/ipr_search.cgi • Document authors are requested to publish all updates to their documents before the end of the month. • WG last call will proceed thereafter. • Call for implementation reports.

  7. BFD Focus • Our WG charter says:“BFD is a protocol intended to detect faults in the bi-directional path between two forwarding engines, including physical interfaces, sub interfaces, data link(s), and to the extent possible the forwarding engines themselves, with potentially very low latency. It operates independently of media, data protocols, and routing protocols. An additional goal is to provide a single mechanism that can be used forliveness detection over any media, at any protocol layer, with a wide range of detection times and overhead, to avoid a proliferation of different methods.”

  8. What this means • We have a very tight focus on the product of the working group. • Proposals meant to solve the problems of any particular media or transport are very likely out of scope. • This isn’t to say that recent proposals aren’t valid problems to solve. It just means that while BFD can be used in the solution, BFD can’t be changed for that solution.

  9. Questions/Discussion

More Related