Bidrectional Forwarding Detection IETF 62

1
Bidrectional Forwarding Detection IETF 62

• Jeffrey Haas - jhaas_at_nexthop.comDave Ward -
  dward_at_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
• QA

3
Document Status

• Dave

4
Were late

• Most WG Documents were expected to be last called
  in August of 2004.

5
Procedural Status (1)

• Based on Daves 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_s
  earch.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 saysBFD 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 isnt to say that recent proposals arent
  valid problems to solve. It just means that
  while BFD can be used in the solution, BFD cant
  be changed for that solution.

9
Questions/Discussion