draft-ietf-bfd-seamless-ip-00.txt   draft-ietf-bfd-seamless-ip-01.txt 
Internet Engineering Task Force N. Akiya Internet Engineering Task Force N. Akiya
Internet-Draft C. Pignataro Internet-Draft C. Pignataro
Intended status: Standards Track D. Ward Intended status: Standards Track D. Ward
Expires: March 18, 2015 Cisco Systems Expires: July 6, 2015 Cisco Systems
September 14, 2014 January 2, 2015
Seamless Bidirectional Forwarding Detection (S-BFD) for Seamless Bidirectional Forwarding Detection (S-BFD) for
IPv4, IPv6 and MPLS IPv4, IPv6 and MPLS
draft-ietf-bfd-seamless-ip-00 draft-ietf-bfd-seamless-ip-01
Abstract Abstract
This document defines procedures to use Seamless Bidirectional This document defines procedures to use Seamless Bidirectional
Forwarding Detection (S-BFD) for IPv4, IPv6 and MPLS environments. Forwarding Detection (S-BFD) for IPv4, IPv6 and MPLS environments.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 18, 2015. This Internet-Draft will expire on July 6, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 2, line 25 skipping to change at page 2, line 25
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 . . 3 5.1. Details of S-BFD Control Packet Sent by SBFDInitiator . . 3
5.2. Target vs. Remote Entity (S-BFD Discriminator) . . . . . 4 5.2. Target vs. Remote Entity (S-BFD Discriminator) . . . . . 4
6. Responder Procedures . . . . . . . . . . . . . . . . . . . . 4 6. Responder Procedures . . . . . . . . . . . . . . . . . . . . 4
6.1. Details of S-BFD Control Packet Sent by SBFDReflector . . 5 6.1. Details of S-BFD Control Packet Sent by SBFDReflector . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
10. Contributing Authors . . . . . . . . . . . . . . . . . . . . 6 10. Contributing Authors . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 7 11.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Seamless Bidirectional Forwarding Detection (S-BFD), Seamless Bidirectional Forwarding Detection (S-BFD),
[I-D.ietf-bfd-seamless-base], defines a generalized mechanism to [I-D.ietf-bfd-seamless-base], defines a generalized mechanism to
allow network nodes to seamlessly perform continuity checks to remote allow network nodes to seamlessly perform continuity checks to remote
entities. This document defines necessary procedures to use S-BFD on entities. This document defines necessary procedures to use S-BFD on
IPv4, IPv6 and MPLS environments. IPv4, IPv6 and MPLS environments.
The reader is expected to be familiar with the IP, MPLS BFD and S-BFD The reader is expected to be familiar with the IP, MPLS BFD and S-BFD
terminologies and protocol constructs. terminologies and protocol constructs.
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 the use of the S-BFD on IPv4, IPv6 and
MPLS environments: TBD1. SBFDReflector session MUST listen for MPLS environments: 7784. SBFDReflector session MUST listen for
incoming S-BFD control packets on the port TBD1. SBFDInitiator incoming S-BFD control packets on the port 7784. SBFDInitiator
sessions MUST transmit S-BFD control packets with destination port sessions MUST transmit S-BFD control packets with destination port
TBD1. The source port of the S-BFD control packets transmitted by 7784. The source port of the S-BFD control packets transmitted by
SBFDInitiator sessions can be of any but MUST NOT be TBD1. The same SBFDInitiator sessions can be of any but MUST NOT be 7784. The same
UDP source port number MUST be used for all S-BFD control packets UDP source port number MUST be used for all S-BFD control packets
associated with a particular SBFDInitiator session. The source port associated with a particular SBFDInitiator session. The source port
number MAY be unique among all SBFDInitiator sessions on the system. number MAY be unique among all SBFDInitiator sessions on the system.
3. S-BFD Echo UDP Port 3. S-BFD Echo UDP Port
A new UDP port is defined for the use of the S-BFD Echo function on The BFD Echo port defined by [RFC5881], port 3785, is used for the
IPv4, IPv6 and MPLS environments: TBD2. SBFDInitiator sessions MUST S-BFD Echo function on IPv4, IPv6 and MPLS environments.
transmit S-BFD echo packets with destination port TBD2. This SBFDInitiator sessions MUST transmit S-BFD echo packets with
document defines only the UDP port value for the S-BFD Echo function. destination port 3785. This document defines only the UDP port value
The source port and the procedures for the S-BFD Echo function are for the S-BFD Echo function. The source port and the procedures for
outside the scope of this document. the S-BFD Echo function are outside the scope of this document.
4. S-BFD Control Packet Demultiplexing 4. S-BFD Control Packet Demultiplexing
Received BFD control packet MUST be demultiplexed with the Received BFD control packet MUST be demultiplexed with the
destination UDP port field. If the port is TBD1, then the packet destination UDP port field. If the port is 7784, then the packet
MUST be looked up to locate a corresponding SBFDReflector session MUST be looked up to locate a corresponding SBFDReflector session
based on the value from the "your discriminator" field in the table based on the value from the "your discriminator" field in the table
describing S-BFD discriminators. If the port is not TBD1, then the describing S-BFD discriminators. If the port is not 7784, then the
packet MUST be looked up to locate a corresponding SBFDInitiator packet MUST be looked up to locate a corresponding SBFDInitiator
session or classical BFD session based on the value from the "your session or classical BFD session based on the value from the "your
discriminator" field in the table describing BFD discriminators. If discriminator" field in the table describing BFD discriminators. If
the located session is an SBFDInitiator, then the destination IP the located session is an SBFDInitiator, then the destination IP
address of the packet SHOULD be validated to be for self. address of the packet SHOULD be validated to be for self.
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 IP header, UDP header and
BFD control header ([RFC5880]). When S-BFD control packets are BFD control header ([RFC5880]). When S-BFD control packets are
skipping to change at page 4, line 6 skipping to change at page 4, line 6
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 * Source IP address field of the IP header MUST be set to a local
IP address that is expected to be routable by the target (i.e. IP address that is expected to be routable by the target (i.e.
not IPv6 link-local address when the target is multiple hops not IPv6 link-local address when the target is multiple hops
away). away).
* UDP destination port MUST be set to a well-known UDP * UDP destination port MUST be set to a well-known UDP
destination port assigned for S-BFD: TBD1. destination port assigned for S-BFD: 7784.
* UDP source port MUST be set to a value that is not TBD1. * UDP source port MUST be set to a value that is not 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 * Destination IP address field of the IP header MUST set to an IP
address of the target. address of the target.
* TTL field of the IP header SHOULD be set to 255. * TTL 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:
skipping to change at page 4, line 52 skipping to change at page 4, line 52
This also requires S-BFD control packets not be dropped by the This also requires 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 TTL expiry
exception path to reach corresponding reflector BFD session. exception path to reach corresponding reflector BFD session.
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 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 UDP source port
as TBD1, the packet MUST be discarded. Necessary values in the BFD as 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 [I-D.ietf-bfd-seamless-base].
Section 6.1 describes necessary values in the IP header and UDP Section 6.1 describes necessary values in the IP header and UDP
header when an SBFDReflector on the responder is sending S-BFD header when an 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 Packet Sent by SBFDReflector
o Destination IP address field of the IP header MUST be copied from o Destination IP address field of the IP header MUST be copied from
source IP address field of received S-BFD control packet. source IP address field of received S-BFD control packet.
skipping to change at page 5, line 43 skipping to change at page 5, line 43
o Implementations MUST NOT act on received S-BFD control packets o Implementations MUST NOT act on received S-BFD control packets
containing Martian addresses as source IP addresses. containing Martian addresses as source IP addresses.
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 to the initiator by the SBFDReflector have a reachable
target (ex: destination IP address). target (ex: destination IP address).
8. IANA Considerations 8. IANA Considerations
A new value TBD1 is requested from the "Service Name and Transport A new value 7784 was allocated from the "Service Name and Transport
Protocol Port Number Registry". The requested registry entry is: 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@tools.ietf.org> BFD Chairs <bfd-chairs@tools.ietf.org>
Description (REQUIRED) Description (REQUIRED)
Seamless Bidirectional Forwarding Detection (S-BFD) Seamless Bidirectional Forwarding Detection (S-BFD)
Reference (REQUIRED) Reference (REQUIRED)
draft-akiya-bfd-seamless-ip draft-akiya-bfd-seamless-ip
Port Number (OPTIONAL) Port Number (OPTIONAL)
TBD1 (Requesting 7784) 7784
A new value TBD2 is requested from the "Service Name and Transport
Protocol Port Number Registry". The requested registry entry is:
Service Name (REQUIRED)
s-bfd-echo
Transport Protocol(s) (REQUIRED)
udp
Assignee (REQUIRED)
IESG <iesg@ietf.org>
Contact (REQUIRED)
BFD Chairs <bfd-chairs@tools.ietf.org>
Description (REQUIRED)
Seamless Bidirectional Forwarding Detection (S-BFD) Echo Function
Reference (REQUIRED)
draft-akiya-bfd-seamless-ip
Port Number (OPTIONAL)
TBD2 (Requesting 7785)
9. Acknowledgements 9. Acknowledgements
Authors would like to thank Marc Binderberger from Cisco Systems for The authors would like to thank the BFD WG members for helping to
providing valuable comments. 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. Contributing Authors 10. Contributing Authors
Tarek Saad Tarek Saad
Cisco Systems Cisco Systems
Email: tsaad@cisco.com Email: tsaad@cisco.com
Siva Sivabalan Siva Sivabalan
Cisco Systems Cisco Systems
Email: msiva@cisco.com Email: msiva@cisco.com
skipping to change at page 7, line 24 skipping to change at page 7, line 11
Networks, "Seamless Bidirectional Forwarding Detection Networks, "Seamless Bidirectional Forwarding Detection
(S-BFD)", draft-ietf-bfd-seamless-base-03 (work in (S-BFD)", draft-ietf-bfd-seamless-base-03 (work in
progress), August 2014. progress), August 2014.
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010. (BFD)", RFC 5880, June 2010.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June
2010.
11.2. Informative References 11.2. Informative References
[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, May 2000. Address Spoofing", BCP 38, RFC 2827, May 2000.
Authors' Addresses Authors' Addresses
Nobo Akiya Nobo Akiya
Cisco Systems Cisco Systems
 End of changes. 17 change blocks. 
45 lines changed or deleted 34 lines changed or added

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