Active OAM for Service Function Chains in Networks
draft-ietf-sfc-multi-layer-oam-04
SFC WG G. Mirsky
Internet-Draft ZTE Corp.
Updates: 8300 (if approved) W. Meng
Intended status: Standards Track ZTE Corporation
Expires: May 21, 2020 B. Khasnabish
C. Wang
Individual contributor
November 18, 2019
Active OAM for Service Function Chains in Networks
draft-ietf-sfc-multi-layer-oam-04
Abstract
A set of requirements for active Operation, Administration and
Maintenance (OAM) of Service Function Chains (SFCs) in networks is
presented. Based on these requirements an encapsulation of active
OAM message in SFC and a mechanism to detect and localize defects
described. Also, this document updates RFC 8300 in the definition of
O (OAM) bit in the Network Service Header (NSH) and defines how the
active OAM message identified in SFC NSH.
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 https://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 May 21, 2020.
Copyright Notice
Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of
Mirsky, et al. Expires May 21, 2020 [Page 1]
Internet-Draft Active OAM for SFC November 2019
publication of this document. Please review these documents
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. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements for Active OAM in SFC Network . . . . . . . . . 4
4. Active OAM Identification in SFC NSH . . . . . . . . . . . . 5
5. Echo Request/Echo Reply for SFC in Networks . . . . . . . . . 7
5.1. Return Codes . . . . . . . . . . . . . . . . . . . . . . 9
5.2. SFC Echo Request Transmission . . . . . . . . . . . . . . 9
5.3. SFC Echo Request Reception . . . . . . . . . . . . . . . 9
5.3.1. Errored TLVs TLV . . . . . . . . . . . . . . . . . . 10
5.4. SFC Echo Reply Transmission . . . . . . . . . . . . . . . 10
5.5. SFC Echo Reply Reception . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8.1. SFC Active OAM Protocol . . . . . . . . . . . . . . . . . 13
8.2. SFC Active OAM Message Type . . . . . . . . . . . . . . . 13
8.3. SFC Echo Request/Echo Reply Parameters . . . . . . . . . 14
8.4. SFC Echo Request/Echo Reply Message Types . . . . . . . . 14
8.5. SFC Echo Reply Modes . . . . . . . . . . . . . . . . . . 14
8.6. SFC Echo Return Codes . . . . . . . . . . . . . . . . . . 15
8.7. SFC TLV Type . . . . . . . . . . . . . . . . . . . . . . 15
8.8. SFC OAM UDP Port . . . . . . . . . . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
[RFC7665] defines components necessary to implement Service Function
Chain (SFC). These include a classifier which performs the
classification of incoming packets. A Service Function Forwarder
Show full document text