Seamless Bidirectional Forwarding Detection (S-BFD) for IPv4, IPv6 and MPLS
draft-ietf-bfd-seamless-ip-00
Internet Engineering Task Force N. Akiya
Internet-Draft C. Pignataro
Intended status: Standards Track D. Ward
Expires: March 18, 2015 Cisco Systems
September 14, 2014
Seamless Bidirectional Forwarding Detection (S-BFD) for
IPv4, IPv6 and MPLS
draft-ietf-bfd-seamless-ip-00
Abstract
This document defines procedures to use Seamless Bidirectional
Forwarding Detection (S-BFD) for IPv4, IPv6 and MPLS environments.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 18, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Akiya, et al. Expires March 18, 2015 [Page 1]
Internet-Draft Seamless BFD for IP September 2014
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. S-BFD UDP Port . . . . . . . . . . . . . . . . . . . . . . . 2
3. S-BFD Echo UDP Port . . . . . . . . . . . . . . . . . . . . . 3
4. S-BFD Control Packet Demultiplexing . . . . . . . . . . . . . 3
5. Initiator Procedures . . . . . . . . . . . . . . . . . . . . 3
5.1. Details of S-BFD Control Packet Sent by SBFDInitiator . . 3
5.2. Target vs. Remote Entity (S-BFD Discriminator) . . . . . 4
6. Responder Procedures . . . . . . . . . . . . . . . . . . . . 4
6.1. Details of S-BFD Control Packet Sent by SBFDReflector . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
10. Contributing Authors . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
Seamless Bidirectional Forwarding Detection (S-BFD),
[I-D.ietf-bfd-seamless-base], defines a generalized mechanism to
allow network nodes to seamlessly perform continuity checks to remote
entities. This document defines necessary procedures to use S-BFD on
IPv4, IPv6 and MPLS environments.
The reader is expected to be familiar with the IP, MPLS BFD and S-BFD
terminologies and protocol constructs.
2. S-BFD UDP Port
A new UDP port is defined for the use of the S-BFD on IPv4, IPv6 and
MPLS environments: TBD1. SBFDReflector session MUST listen for
incoming S-BFD control packets on the port TBD1. SBFDInitiator
sessions MUST transmit S-BFD control packets with destination port
TBD1. The source port of the S-BFD control packets transmitted by
SBFDInitiator sessions can be of any but MUST NOT be TBD1. The same
UDP source port number MUST be used for all S-BFD control packets
associated with a particular SBFDInitiator session. The source port
number MAY be unique among all SBFDInitiator sessions on the system.
Akiya, et al. Expires March 18, 2015 [Page 2]
Internet-Draft Seamless BFD for IP September 2014
3. S-BFD Echo UDP Port
Show full document text