draft-ietf-bfd-seamless-ip-06.txt   rfc7881.txt 
Internet Engineering Task Force C. Pignataro Internet Engineering Task Force (IETF) C. Pignataro
Internet-Draft D. Ward Request for Comments: 7881 D. Ward
Intended status: Standards Track Cisco Category: Standards Track Cisco
Expires: November 7, 2016 N. Akiya ISSN: 2070-1721 N. Akiya
Big Switch Networks Big Switch Networks
May 6, 2016 July 2016
Seamless Bidirectional Forwarding Detection (S-BFD) for Seamless Bidirectional Forwarding Detection (S-BFD)
IPv4, IPv6 and MPLS for IPv4, IPv6, and MPLS
draft-ietf-bfd-seamless-ip-06
Abstract Abstract
This document defines procedures to use Seamless Bidirectional This document defines procedures for using Seamless Bidirectional
Forwarding Detection (S-BFD) for IPv4, IPv6 and MPLS environments. Forwarding Detection (S-BFD) in 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 Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on November 7, 2016. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7881.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction ....................................................2
2. S-BFD UDP Port . . . . . . . . . . . . . . . . . . . . . . . 2 2. S-BFD UDP Port ..................................................2
3. S-BFD Echo UDP Port . . . . . . . . . . . . . . . . . . . . . 3 3. S-BFD Echo UDP Port .............................................3
4. S-BFD Control Packet Demultiplexing . . . . . . . . . . . . . 3 4. S-BFD Control Packet Demultiplexing .............................3
5. Initiator Procedures . . . . . . . . . . . . . . . . . . . . 3 5. Initiator Procedures ............................................3
5.1. Details of S-BFD Control Packet Sent by SBFDInitiator . . 4 5.1. Details of S-BFD Control Packets Sent by SBFDInitiator .....4
5.1.1. Target vs. Remote Entity (S-BFD Discriminator) . . . 4 5.1.1. Target versus Remote Entity (S-BFD Discriminator) ...4
6. Responder Procedures . . . . . . . . . . . . . . . . . . . . 5 6. Responder Procedures ............................................5
6.1. Details of S-BFD Control Packet Sent by SBFDReflector . . 5 6.1. Details of S-BFD Control Packets Sent by SBFDReflector .....5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations .........................................6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations .............................................6
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 9. References ......................................................7
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 9.1. Normative References .......................................7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 9.2. Informative References .....................................7
11.1. Normative References . . . . . . . . . . . . . . . . . . 7 Acknowledgements ...................................................8
11.2. Informative References . . . . . . . . . . . . . . . . . 7 Contributors .......................................................8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses .................................................8
1. Introduction 1. Introduction
Seamless Bidirectional Forwarding Detection (S-BFD), Seamless Bidirectional Forwarding Detection (S-BFD) [RFC7880] defines
[I-D.ietf-bfd-seamless-base], defines a generalized mechanism to a generalized mechanism to allow network nodes to seamlessly perform
allow network nodes to seamlessly perform continuity checks to remote continuity checks to remote entities. This document defines
entities. This document defines necessary procedures to use S-BFD on necessary procedures for using S-BFD in IPv4, IPv6, and MPLS
IPv4, IPv6 and MPLS environments. environments.
The reader is expected to be familiar with the IP [RFC0791] The reader is expected to be familiar with the IP [RFC791] [RFC2460],
[RFC2460], BFD [RFC5880], MPLS BFD [RFC5884], and S-BFD BFD [RFC5880], MPLS BFD [RFC5884], and S-BFD [RFC7880] terms and
[I-D.ietf-bfd-seamless-base] terminologies and protocol constructs. protocol constructs.
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].
2. S-BFD UDP Port 2. S-BFD UDP Port
A new UDP port is defined for the use of the S-BFD on IPv4, IPv6 and A new UDP port is defined for use by S-BFD in IPv4, IPv6, and MPLS
MPLS environments: 7784. environments: 7784.
On S-BFD control packets from the SBFDInitiator to the SBFDReflector, In S-BFD Control packets from the SBFDInitiator to the SBFDReflector,
the SBFDReflector session MUST listen for incoming S-BFD control the SBFDReflector session MUST listen for incoming S-BFD Control
packets on the port 7784. SBFDInitiator sessions MUST transmit S-BFD packets on port 7784. SBFDInitiator sessions MUST transmit S-BFD
control packets with destination port 7784. The source port of the Control packets with destination port 7784. The source port of the
S-BFD control packets transmitted by SBFDInitiator sessions can be S-BFD Control packets transmitted by SBFDInitiator sessions can be
any but MUST NOT be 7784. The same UDP source port number MUST be any port, with one exception: it MUST NOT be 7784. The same UDP
used for all S-BFD control packets associated with a particular source port number MUST be used for all S-BFD Control packets
SBFDInitiator session. The source port number is unique among all associated with a particular SBFDInitiator session. The source port
SBFDInitiator sessions on the system. number is unique among all SBFDInitiator sessions on the system.
On S-BFD control packets from the SBFDReflecto to the SBFDInitiator, In S-BFD Control packets from the SBFDReflector to the SBFDInitiator,
the SBFDInitiator MUST listen for reflected S-BFD control packets at the SBFDInitiator session MUST listen for reflected S-BFD Control
its source port. packets at its source port.
3. S-BFD Echo UDP Port 3. S-BFD Echo UDP Port
The BFD Echo port defined by [RFC5881], port 3785, is used for the The BFD Echo port defined by [RFC5881], port 3785, is used for the
S-BFD Echo function on IPv4, IPv6 and MPLS environments. S-BFD Echo function in IPv4, IPv6, and MPLS environments.
SBFDInitiator sessions MUST transmit S-BFD echo packets with SBFDInitiator sessions MUST transmit S-BFD Echo packets with
destination port 3785. The setting of the UDP source port [RFC5881] destination port 3785. The setting of the UDP source port [RFC5881]
and the procedures [I-D.ietf-bfd-seamless-base] for the S-BFD Echo and the procedures [RFC7880] for the S-BFD Echo function are outside
function are outside the scope of this document. the scope of this document.
4. S-BFD Control Packet Demultiplexing 4. S-BFD Control Packet Demultiplexing
The S-BFD Control Packet demultiplexing follows the procedure S-BFD Control packet demultiplexing follows the procedure specified
specified in Section 7.1. of [I-D.ietf-bfd-seamless-base]. Received in Section 7.1 of [RFC7880]. A received S-BFD Control packet MUST be
S-BFD control packet MUST be demultiplexed with the destination UDP demultiplexed with the destination UDP port field.
port field.
This procedure for an S-BFD packet is executed on both the initiator This procedure for an S-BFD packet is executed on both the initiator
and the reflector. If the port is 7784 (i.e., S-BFD packet for and the reflector. If the port is 7784 (i.e., an S-BFD packet for
S-BFDReflector), then the packet MUST be looked up to locate a the SBFDReflector), then the packet MUST be looked up to locate a
corresponding SBFDReflector session based on the value from the "your corresponding SBFDReflector session based on the value from the
discriminator" field in the table describing S-BFD discriminators. Your Discriminator field in the table describing S-BFD
If the port is not 7784, but the packet is demultiplexed to be for an Discriminators. If the port is not 7784 but the packet is
SBFDInitiator, then the packet MUST be looked up to locate a demultiplexed to be for an SBFDInitiator, then the packet MUST be
corresponding SBFDInitiator session based on the value from the "your looked up to locate a corresponding SBFDInitiator session based on
discriminator" field in the table describing BFD discriminators. In the value from the Your Discriminator field in the table describing
that case, then the destination IP address of the packet SHOULD be BFD Discriminators. In that case, the destination IP address of the
validated to be for itself. If the packet demultiplexes to a packet SHOULD be validated to be for itself. If the packet
classical BFD session, then the procedures from [RFC5880] apply. demultiplexes to a classical BFD session, then the procedures from
[RFC5880] apply.
5. Initiator Procedures 5. Initiator Procedures
S-BFD control packets are transmitted with IP header, UDP header and S-BFD Control packets are transmitted with an IP header, UDP header,
BFD control header ([RFC5880]). When S-BFD control packets are and BFD Control packet ([RFC5880]). When S-BFD Control packets are
explicitly label switched (i.e. not IP routed which happen to go over explicitly label switched (i.e., not IP routed and forwarded over a
an LSP, but explicitly sent on a specific LSP), the former is Label Switched Path (LSP), but explicitly sent on a specific LSP),
prepended with a label stack. Note that this document does not make the former is prepended with a label stack. Note that this document
a distinction between a single-hop S-BFD scenario and a multi-hop does not make a distinction between a single-hop S-BFD scenario and a
S-BFD scenario, both scenarios are supported. multi-hop S-BFD scenario; both scenarios are supported.
The necessary values in the BFD control headers are described in The necessary values in the BFD control headers are described in
[I-D.ietf-bfd-seamless-base]. Section 5.1 describes necessary values [RFC7880]. Section 5.1 describes necessary values in the MPLS
in the MPLS header, IP header and UDP header when an SBFDInitiator on header, IP header, and UDP header when an SBFDInitiator on the
the initiator is sending S-BFD control packets. initiator is sending S-BFD Control packets.
5.1. Details of S-BFD Control Packet Sent by SBFDInitiator 5.1. Details of S-BFD Control Packets Sent by SBFDInitiator
o Specifications common to both IP routed S-BFD control packets and o Specifications common to both IP-routed S-BFD Control packets and
explicitly label switched S-BFD control packets: explicitly label-switched S-BFD Control packets:
* Source IP address field of the IP header MUST be set to a local * The Source IP Address field of the IP header MUST be set to a
IP address that is expected to be routable by the target (i.e. local IP address that is expected to be routable by the target
not IPv6 link-local address when the target is multiple hops (i.e., not an IPv6 link-local address when the target is
away). multiple hops away).
* UDP destination port MUST be set to a well-known UDP * The UDP destination port MUST be set to a well-known UDP
destination port assigned for S-BFD: 7784. destination port assigned for S-BFD, i.e., 7784.
* UDP source port MUST NOT be set to 7784. * The UDP source port MUST NOT be set to 7784.
o Specifications for IP routed S-BFD control packets: o Specifications for IP-routed S-BFD Control packets:
* Destination IP address field of the IP header MUST set to an IP * The Destination IP Address field of the IP header MUST be set
address of the target. to an IP address of the target.
* The TTL/Hop Limit field of the IP header SHOULD be set to 255. * The TTL / Hop Limit field of the IP header SHOULD be set
to 255.
o Specifications for explicitly label switched S-BFD control o Specifications for explicitly label-switched S-BFD Control
packets: packets:
* S-BFD control packets MUST have the label stack that is * S-BFD Control packets MUST have the label stack that is
expected to reach the target. expected to reach the target.
* TTL field of the top most label SHOULD be 255. * The TTL field of the topmost label SHOULD be 255.
* The destination IP address MUST be chosen from the 127/8 range * The destination IP address MUST be chosen from the 127/8 range
for IPv4 and from the 0:0:0:0:0:FFFF:7F00:0/104 range for IPv6, for IPv4 and from the 0:0:0:0:0:ffff:7f00:0/104 range for IPv6,
as with [RFC5884]. as per [RFC5884].
* The TTL/Hop Limit field of the IP header MUST be set to 1. * The TTL / Hop Limit field of the IP header MUST be set to 1.
5.1.1. Target vs. Remote Entity (S-BFD Discriminator) 5.1.1. Target versus Remote Entity (S-BFD Discriminator)
Typically, an S-BFD control packet will have "your discriminator" Typically, an S-BFD Control packet will have the Your Discriminator
field corresponding to an S-BFD discriminator of the remote entity field corresponding to an S-BFD Discriminator of the remote entity
located on the target network node defined by the destination IP located on the target network node defined by the destination IP
address or the label stack. It is, however, possible for an address or the label stack. It is, however, possible for an
SBFDInitiator to carefully set the "your discriminator" and TTL SBFDInitiator to carefully set the Your Discriminator and TTL fields
fields to perform a continuity test in the direction towards a to perform a continuity test in the direction towards a target, but
target, but destined to a transit network node and not to the target destined to a transit network node and not to the target itself.
itself.
Section 5.1 intentionally uses the word "target", instead of "remote Section 5.1 intentionally uses the word "target" instead of "remote
entity", to accommodate this possible S-BFD usage through TTL expiry. entity" to accommodate this possible S-BFD usage through TTL expiry.
This also requires S-BFD control packets not be dropped by the This also requires that S-BFD Control packets not be dropped by the
responder node due to TTL expiry. Thus implementations on the responder node due to TTL expiry. Thus, implementations on the
responder MUST allow received S-BFD control packets taking TTL expiry responder MUST allow received S-BFD Control packets taking a TTL
exception path to reach corresponding reflector BFD session. This is expiry exception path to reach the corresponding SBFDReflector
an existing packet processing exception practice for OAM packets, session. This is an existing packet-processing exception practice
where the control plane further identifies the type of OAM by the for Operations, Administration, and Maintenance (OAM) packets, where
protocol and port numbers. the control plane further identifies the type of OAM by the protocol
and port numbers.
6. Responder Procedures 6. Responder Procedures
S-BFD control packets are IP routed back to the initiator, and will S-BFD Control packets are IP routed back to the initiator and will
have IP header, UDP header and BFD control header. If an have an IP header, UDP header, and BFD control header. If an
SBFDReflector receives an S-BFD control packet with UDP source port SBFDReflector receives an S-BFD Control packet with a UDP source port
as 7784, the packet MUST be discarded. Necessary values in the BFD of 7784, the packet MUST be discarded. Necessary values in the BFD
control header are described in [I-D.ietf-bfd-seamless-base]. control header are described in [RFC7880]. Section 6.1 describes
Section 6.1 describes necessary values in the IP header and UDP necessary values in the IP header and UDP header when an
header when an SBFDReflector on the responder is sending S-BFD SBFDReflector on the responder is sending S-BFD Control packets.
control packets.
6.1. Details of S-BFD Control Packet Sent by SBFDReflector 6.1. Details of S-BFD Control Packets Sent by SBFDReflector
o Destination IP address field of the IP header MUST be copied from o The Destination IP Address field of the IP header MUST be copied
source IP address field of received S-BFD control packet. from the Source IP Address field of the received S-BFD Control
packet.
o Source IP address field of the IP header MUST be set to a local IP o The Source IP Address field of the IP header MUST be set to a
address that is expected to be visible by the initiator (i.e. not local IP address that the initiator expects to be visible (i.e.,
IPv6 link-local address when the initiator is multiple hops away). not an IPv6 link-local address when the initiator is multiple hops
The source IP address SHOULD be copied from the destination IP away). The source IP address SHOULD be copied from the
address field of the received S-BFD control packet, except when it Destination IP Address field of the received S-BFD Control packet,
is from the 127/8 range for IPv4 or from the except when it is from the 127/8 range for IPv4 or from the
0:0:0:0:0:FFFF:7F00:0/104 range for IPv6. 0:0:0:0:0:ffff:7f00:0/104 range for IPv6.
o The TTL/Hop Limit field of the IP header MUST be set to 255. o The TTL / Hop Limit field of the IP header MUST be set to 255.
o UDP destination port MUST be copied from received UDP source port. o The UDP destination port MUST be copied from the received UDP
source port.
o UDP source port MUST be copied from received UDP destination port. o The UDP source port MUST be copied from the received UDP
destination port.
7. Security Considerations 7. Security Considerations
Security considerations for S-BFD are discussed in Security considerations for S-BFD are discussed in [RFC7880].
[I-D.ietf-bfd-seamless-base]. Additionally, implementing the Additionally, implementing the following measures will strengthen
following measures will strengthen security aspects of the mechanism security aspects of the mechanism described by this document:
described by this document:
o Implementations MUST provide filtering capability based on source o Implementations MUST provide filtering capability based on source
IP addresses of received S-BFD control packets: [RFC2827]. IP addresses of received S-BFD Control packets; see [RFC2827].
o Implementations MUST NOT act on received S-BFD control packets o Implementations MUST NOT act on received S-BFD Control packets
containing source Martian IP addresses (i.e., address that, by containing source Martian IP addresses (i.e., addresses that, by
application of the current forwarding tables, would not have its application of the current forwarding tables, would not have their
return traffic routed back to the sender.) return traffic routed back to the sender).
o Implementations MUST ensure that response S-BFD control packets o Implementations MUST ensure that response S-BFD Control packets
generated to the initiator by the SBFDReflector have a reachable generated by the SBFDReflector and sent to the initiator have a
target (ex: destination IP address). reachable target (e.g., destination IP address).
8. IANA Considerations 8. IANA Considerations
A new value 7784 was allocated from the "Service Name and Transport A new port number value, 7784, was allocated from the "Service Name
Protocol Port Number Registry". The allocated registry entry is: and Transport Protocol Port Number Registry". The allocated registry
entry is:
Service Name (REQUIRED) Service Name (REQUIRED)
s-bfd s-bfd
Transport Protocol(s) (REQUIRED) Transport Protocol(s) (REQUIRED)
udp udp
Assignee (REQUIRED) Assignee (REQUIRED)
IESG <iesg@ietf.org> IESG <iesg@ietf.org>
Contact (REQUIRED) Contact (REQUIRED)
BFD Chairs <bfd-chairs@ietf.org> IETF Chair <chair@ietf.org>
Description (REQUIRED) Description (REQUIRED)
Seamless Bidirectional Forwarding Detection (S-BFD) Seamless Bidirectional Forwarding Detection (S-BFD)
Reference (REQUIRED) Reference (REQUIRED)
RFC.this (RFC Editor, please update at publication) RFC 7881
Port Number (OPTIONAL) Port Number (OPTIONAL)
7784 7784
9. Acknowledgements 9. References
The authors would like to thank the BFD WG members for helping to
shape the contents of this document. In particular, significant
contributions were made by following people: Marc Binderberger,
Jeffrey Haas, Santosh Pallagatti, Greg Mirsky, Sam Aldrin, Vengada
Prasad Govindan, Mallik Mudigonda and Srihari Raghavan.
10. Contributors
The following are key contributors to this document:
Tarek Saad, Cisco Systems, Inc.
Siva Sivabalan, Cisco Systems, Inc.
Nagendra Kumar, Cisco Systems, Inc.
11. References
11.1. Normative References
[I-D.ietf-bfd-seamless-base] 9.1. Normative References
Akiya, N., Pignataro, C., Ward, D., Bhatia, M., and J.
Networks, "Seamless Bidirectional Forwarding Detection
(S-BFD)", draft-ietf-bfd-seamless-base-09 (work in
progress), April 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<http://www.rfc-editor.org/info/rfc5880>. <http://www.rfc-editor.org/info/rfc5880>.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881,
DOI 10.17487/RFC5881, June 2010, DOI 10.17487/RFC5881, June 2010,
<http://www.rfc-editor.org/info/rfc5881>. <http://www.rfc-editor.org/info/rfc5881>.
11.2. Informative References [RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S.
Pallagatti, "Seamless Bidirectional Forwarding Detection
(S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016,
<http://www.rfc-editor.org/info/rfc7880>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 9.2. Informative References
DOI 10.17487/RFC0791, September 1981,
[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC791, September 1981,
<http://www.rfc-editor.org/info/rfc791>. <http://www.rfc-editor.org/info/rfc791>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/rfc2460>. December 1998, <http://www.rfc-editor.org/info/rfc2460>.
[RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering: [RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering:
Defeating Denial of Service Attacks which employ IP Source Defeating Denial of Service Attacks which employ IP Source
Address Spoofing", BCP 38, RFC 2827, DOI 10.17487/RFC2827, Address Spoofing", BCP 38, RFC 2827, DOI 10.17487/RFC2827,
May 2000, <http://www.rfc-editor.org/info/rfc2827>. May 2000, <http://www.rfc-editor.org/info/rfc2827>.
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
"Bidirectional Forwarding Detection (BFD) for MPLS Label "Bidirectional Forwarding Detection (BFD) for MPLS Label
Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884, Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884,
June 2010, <http://www.rfc-editor.org/info/rfc5884>. June 2010, <http://www.rfc-editor.org/info/rfc5884>.
Acknowledgements
The authors would like to thank the BFD WG members for helping to
shape the contents of this document. In particular, significant
contributions were made by the following people: Marc Binderberger,
Jeffrey Haas, Santosh Pallagatti, Greg Mirsky, Sam Aldrin, Vengada
Prasad Govindan, Mallik Mudigonda, and Srihari Raghavan.
Contributors
The following are key contributors to this document:
Tarek Saad, Cisco Systems, Inc.
Siva Sivabalan, Cisco Systems, Inc.
Nagendra Kumar, Cisco Systems, Inc.
Authors' Addresses Authors' Addresses
Carlos Pignataro Carlos Pignataro
Cisco Systems, Inc. Cisco Systems, Inc.
Email: cpignata@cisco.com Email: cpignata@cisco.com
Dave Ward Dave Ward
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 59 change blocks. 
196 lines changed or deleted 198 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/