draft-ietf-bfd-on-lags-01.txt   draft-ietf-bfd-on-lags-02.txt 
Network Working Group M. Bhatia, Ed. Network Working Group M. Bhatia, Ed.
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Standards Track M. Chen, Ed. Intended status: Standards Track M. Chen, Ed.
Expires: December 15, 2013 Huawei Technologies Expires: May 15, 2014 Huawei Technologies
S. Boutros, Ed. S. Boutros, Ed.
M. Binderberger, Ed. M. Binderberger, Ed.
Cisco Systems Cisco Systems
J. Haas, Ed. J. Haas, Ed.
Juniper Networks Juniper Networks
June 13, 2013 November 11, 2013
Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG)
Interfaces Interfaces
draft-ietf-bfd-on-lags-01 draft-ietf-bfd-on-lags-02
Abstract Abstract
This document proposes a mechanism to run BFD on Link Aggregation This document proposes a mechanism to run BFD on Link Aggregation
Group (LAG) interfaces. It does so by running an independent Group (LAG) interfaces. It does so by running an independent
Asynchronous mode BFD session on every LAG member link. Asynchronous mode BFD session on every LAG member link.
This mechanism allows the verification of member link continuity, This mechanism allows the verification of member link continuity,
either in combination with, or in absence of, LACP. It provides a either in combination with, or in absence of, LACP. It provides a
shorter detection time than what LACP offers. The continuity check shorter detection time than what LACP offers. The continuity check
skipping to change at page 2, line 8 skipping to change at page 2, line 8
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 December 15, 2013. This Internet-Draft will expire on May 15, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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
skipping to change at page 7, line 48 skipping to change at page 7, line 48
from the IPv4 load balance table only but remains forwarding in the from the IPv4 load balance table only but remains forwarding in the
IPv6 load balance table. IPv6 load balance table.
6. Security Consideration 6. Security Consideration
This document does not introduce any additional security issues and This document does not introduce any additional security issues and
the security mechanisms defined in [RFC5880] apply in this document. the security mechanisms defined in [RFC5880] apply in this document.
7. IANA Considerations 7. IANA Considerations
IANA assigned a dedicated MAC address 01-00-5E-90-00-01 as well as IANA assigned a dedicated MAC address 01-00-5E-90-00-01 (see
UDP port 6784 for UDP encapsulated micro BFD sessions.
[RFC7042]) as well as UDP port 6784 for UDP encapsulated micro BFD
sessions.
8. Acknowledgements 8. Acknowledgements
We would like to thank Dave Katz, Alexander Vainshtein, Greg Mirsky We would like to thank Dave Katz, Alexander Vainshtein, Greg Mirsky
and Jeff Tantsura for their comments. and Jeff Tantsura for their comments.
The initial event to start the current discussion was the The initial event to start the current discussion was the
distribution of draft-chen-bfd-interface-00. distribution of draft-chen-bfd-interface-00.
9. Contributing authors 9. Contributing authors
skipping to change at page 9, line 35 skipping to change at page 9, line 36
Bidirectional Forwarding Detection (BFD)", RFC 5882, Bidirectional Forwarding Detection (BFD)", RFC 5882,
June 2010. June 2010.
10.2. Informative References 10.2. Informative References
[IEEE802.1AX] [IEEE802.1AX]
IEEE Std. 802.1AX, "IEEE Standard for Local and IEEE Std. 802.1AX, "IEEE Standard for Local and
metropolitan area networks - Link Aggregation", metropolitan area networks - Link Aggregation",
November 2008. November 2008.
[RFC5342] Eastlake, D., "IANA Considerations and IETF Protocol Usage [RFC7042] Eastlake, D. and J. Abley, "IANA Considerations and IETF
for IEEE 802 Parameters", BCP 141, RFC 5342, Protocol and Documentation Usage for IEEE 802 Parameters",
September 2008. BCP 141, RFC 7042, October 2013.
Appendix A. Considerations when using BFD on member links Appendix A. Considerations when using BFD on member links
If the BFD over LAG feature were provisioned on an aggregated link If the BFD over LAG feature were provisioned on an aggregated link
member after the link was already active within a LAG, BFD session member after the link was already active within a LAG, BFD session
state SHOULD NOT influence the load balance algorithm until the BFD state SHOULD NOT influence the load balance algorithm until the BFD
session state transitions to Up. If the BFD session never session state transitions to Up. If the BFD session never
transitions to Up but the LAG becomes inactive, the previously transitions to Up but the LAG becomes inactive, the previously
documented procedures would then normally apply. documented procedures would then normally apply.
 End of changes. 6 change blocks. 
9 lines changed or deleted 11 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/