IS-IS BFD-Enabled TLV
draft-ietf-isis-bfd-tlv-03

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>,
    isis mailing list <isis-wg@ietf.org>,
    isis chair <isis-chairs@tools.ietf.org>
Subject: Protocol Action: 'IS-IS BFD Enabled TLV' to Proposed Standard (draft-ietf-isis-bfd-tlv-03.txt)

The IESG has approved the following document:
- 'IS-IS BFD Enabled TLV'
  (draft-ietf-isis-bfd-tlv-03.txt) as a Proposed Standard

This document is the product of the IS-IS for IP Internets Working Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-isis-bfd-tlv/

Ballot Text

Technical Summary

    This specification provides a solution for when there is an 
    IP forwarding failure as detected by BFD, but IS-IS control packets
    continue to be delivered and so the adjacency stays up. The original
    BFD specification allows for IGP adjacencies to form without paired
    BFD sessions to allow for mixed-use of BFD on a link. This
    specification adds a hello TLV that advertises BFD use so that 
    adjacency state to participating routers can depend on the state of 
    a paired BFD session.


Working Group Summary

    There consensus was strong for this specification.

Document Quality

    There are currently no implementations of this specification.


Personnel

   The Document Shepherd for this document is David Ward
   (dward@juiper.net)

   The Responsible Area Director is Stewart Bryant (stbryant@cisco.com)

RFC Editor Note