[rfc-dist] RFC 5881 on Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)

rfc-editor at rfc-editor.org (rfc-editor at rfc-editor.org) Tue, 01 June 2010 19:38 UTC

From: "rfc-editor at rfc-editor.org"
Date: Tue, 01 Jun 2010 12:38:54 -0700
Subject: [rfc-dist] RFC 5881 on Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)
Message-ID: <20100601193854.C367BE06A3@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5881

        Title:      Bidirectional Forwarding Detection (BFD) for 
                    IPv4 and IPv6 (Single Hop) 
        Author:     D. Katz, D. Ward
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2010
        Mailbox:    dkatz at juniper.net, 
                    dward at juniper.net
        Pages:      7
        Characters: 14307
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bfd-v4v6-1hop-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5881.txt

This document describes the use of the Bidirectional Forwarding
Detection (BFD) protocol over IPv4 and IPv6 for single IP hops.
[STANDARDS TRACK]

This document is a product of the Bidirectional Forwarding Detection Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC