< draft-ietf-mpls-bfd-directed-10.txt   draft-ietf-mpls-bfd-directed-11.txt >
MPLS Working Group G. Mirsky MPLS Working Group G. Mirsky
Internet-Draft ZTE Internet-Draft ZTE
Intended status: Standards Track J. Tantsura Intended status: Standards Track J. Tantsura
Expires: April 1, 2019 Nuage Networks Expires: October 5, 2019 Nuage Networks
I. Varlashkin I. Varlashkin
Google Google
M. Chen M. Chen
Huawei Huawei
September 28, 2018 April 3, 2019
Bidirectional Forwarding Detection (BFD) Directed Return Path Bidirectional Forwarding Detection (BFD) Directed Return Path
draft-ietf-mpls-bfd-directed-10 draft-ietf-mpls-bfd-directed-11
Abstract Abstract
Bidirectional Forwarding Detection (BFD) is expected to be able to Bidirectional Forwarding Detection (BFD) is expected to be able to
monitor a wide variety of encapsulations of paths between systems. monitor a wide variety of encapsulations of paths between systems.
When a BFD session monitors an explicitly routed unidirectional path When a BFD session monitors an explicitly routed unidirectional path
there may be a need to direct egress BFD peer to use a specific path there may be a need to direct egress BFD peer to use a specific path
for the reverse direction of the BFD session. for the reverse direction of the BFD session.
Status of This Memo Status of This Memo
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 April 1, 2019. This Internet-Draft will expire on October 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 6, line 41 skipping to change at page 6, line 41
Table 1: New BFD Reverse Type TLV Table 1: New BFD Reverse Type TLV
5.2. Return Code 5.2. Return Code
The IANA is requested to assign a new Return Code value from the The IANA is requested to assign a new Return Code value from the
"Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs) "Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs)
Ping Parameters" registry, "Return Codes" sub-registry, as follows Ping Parameters" registry, "Return Codes" sub-registry, as follows
using a Standards Action value. using a Standards Action value.
+--------+------------------------------------------+---------------+ +--------+----------------------------------------------+-----------+
| Value | Description | Reference | | Value | Description | Reference |
+--------+------------------------------------------+---------------+ +--------+----------------------------------------------+-----------+
| (TBD3) | Inappropriate Target FEC Stack sub-TLV | This document | | (TBD3) | Inappropriate Target FEC Stack sub-TLV | This |
| | present. | | | | present. | document |
| (TBD4) | Failed to establish the BFD session. The | This document | | (TBD4) | Failed to establish the BFD session. The | This |
| | specified reverse path was not found. | | | | specified reverse path was not found. | document |
+--------+------------------------------------------+---------------+ +--------+----------------------------------------------+-----------+
Table 2: New Return Code Table 2: New Return Code
6. Security Considerations 6. Security Considerations
Security considerations discussed in [RFC5880], [RFC5884], [RFC7726], Security considerations discussed in [RFC5880], [RFC5884], [RFC7726],
and [RFC8029], apply to this document. and [RFC8029], apply to this document.
7. Normative References 7. Normative References
 End of changes. 6 change blocks. 
13 lines changed or deleted 13 lines changed or added

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