draft-ietf-sfc-multi-layer-oam-00.txt   draft-ietf-sfc-multi-layer-oam-01.txt 
SFC WG G. Mirsky SFC WG G. Mirsky
Internet-Draft ZTE Corp. Internet-Draft ZTE Corp.
Updates: 8300 (if approved) W. Meng Updates: 8300 (if approved) W. Meng
Intended status: Standards Track ZTE Corporation Intended status: Standards Track ZTE Corporation
Expires: May 8, 2019 B. Khasnabish Expires: August 1, 2019 B. Khasnabish
ZTE TX, Inc. Individual contributor
C. Wang C. Wang
November 4, 2018 January 28, 2019
Active OAM for Service Function Chains in Networks Active OAM for Service Function Chains in Networks
draft-ietf-sfc-multi-layer-oam-00 draft-ietf-sfc-multi-layer-oam-01
Abstract Abstract
A set of requirements for active Operation, Administration and A set of requirements for active Operation, Administration and
Maintenance (OAM) of Service Function Chains (SFCs) in networks is Maintenance (OAM) of Service Function Chains (SFCs) in networks is
presented. Based on these requirements an encapsulation of active presented. Based on these requirements an encapsulation of active
OAM message in SFC and a mechanism to detect and localize defects OAM message in SFC and a mechanism to detect and localize defects
described. Also, this document updates RFC 8300 in the definition of described. Also, this document updates RFC 8300 in the definition of
O (OAM) bit in the Network Service Header (NSH) and defines how the O (OAM) bit in the Network Service Header (NSH) and defines how the
active OAM message identified in SFC NSH. active OAM message identified in SFC NSH.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 May 8, 2019. This Internet-Draft will expire on August 1, 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 2, line 21 skipping to change at page 2, line 21
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements for Active OAM in SFC Network . . . . . . . . . 4 3. Requirements for Active OAM in SFC Network . . . . . . . . . 4
4. Active OAM Identification in SFC NSH . . . . . . . . . . . . 5 4. Active OAM Identification in SFC NSH . . . . . . . . . . . . 5
5. Echo Request/Echo Reply for SFC in Networks . . . . . . . . . 7 5. Echo Request/Echo Reply for SFC in Networks . . . . . . . . . 7
5.1. SFC Echo Request Transmission . . . . . . . . . . . . . . 8 5.1. SFC Echo Request Transmission . . . . . . . . . . . . . . 8
5.2. SFC Echo Request Reception . . . . . . . . . . . . . . . 8 5.2. SFC Echo Request Reception . . . . . . . . . . . . . . . 9
5.3. SFC Echo Reply Transmission . . . . . . . . . . . . . . . 8 5.3. SFC Echo Reply Transmission . . . . . . . . . . . . . . . 9
5.4. Overlay Echo Reply Reception . . . . . . . . . . . . . . 9 5.4. Overlay Echo Reply Reception . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8.1. SFC Active OAM Protocol . . . . . . . . . . . . . . . . . 10 8.1. SFC Active OAM Protocol . . . . . . . . . . . . . . . . . 10
8.2. SFC Active OAM Message Type . . . . . . . . . . . . . . . 10 8.2. SFC Active OAM Message Type . . . . . . . . . . . . . . . 11
8.3. SFC Echo Request/Echo Reply Parameters . . . . . . . . . 11 8.3. SFC Echo Request/Echo Reply Parameters . . . . . . . . . 11
8.4. SFC Echo Request/Echo Reply Message Types . . . . . . . . 11 8.4. SFC Echo Request/Echo Reply Message Types . . . . . . . . 12
8.5. SFC Echo Reply Modes . . . . . . . . . . . . . . . . . . 12 8.5. SFC Echo Reply Modes . . . . . . . . . . . . . . . . . . 12
8.6. SFC TLV Type . . . . . . . . . . . . . . . . . . . . . . 12 8.6. SFC TLV Type . . . . . . . . . . . . . . . . . . . . . . 13
8.7. SFC OAM UDP Port . . . . . . . . . . . . . . . . . . . . 13 8.7. SFC OAM UDP Port . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
[RFC7665] defines components necessary to implement Service Function [RFC7665] defines components necessary to implement Service Function
Chain (SFC). These include a classifier which performs the Chain (SFC). These include a classifier which performs the
classification of incoming packets. A Service Function Forwarder classification of incoming packets. A Service Function Forwarder
(SFF) is responsible for forwarding traffic to one or more connected (SFF) is responsible for forwarding traffic to one or more connected
skipping to change at page 6, line 8 skipping to change at page 6, line 8
O bit: Setting this bit indicates an OAM command and/or data in O bit: Setting this bit indicates an OAM command and/or data in
the NSH Context Header or packet payload the NSH Context Header or packet payload
Active SFC OAM defined as a combination of OAM commands and/or data Active SFC OAM defined as a combination of OAM commands and/or data
included in a message that immediately follows the NSH. To identify included in a message that immediately follows the NSH. To identify
the active OAM message the value on the Next Protocol field MUST be the active OAM message the value on the Next Protocol field MUST be
set to Active SFC OAM (TBA1) according to Section 8.1. The rules of set to Active SFC OAM (TBA1) according to Section 8.1. The rules of
interpreting the values of O bit and the Next Protocol field are as interpreting the values of O bit and the Next Protocol field are as
follows: follows:
o O bit set and the Next Protocol value is not one of identifying o O bit set, and the Next Protocol value is not one of identifying
active or hybrid OAM protocol (per [RFC7799] definitions), e.g., active or hybrid OAM protocol (per [RFC7799] definitions), e.g.,
defined in this specification Active SFC OAM - TLVs contain OAM defined in this specification Active SFC OAM - a Fixed-Length
command or data, and the type of payload determined by the Next Context Header or Variable-Length Context Header(s) contain OAM
command or data. and the type of payload determined by the Next
Protocol field; Protocol field;
o O bit set and the Next Protocol value is one of identifying active o O bit set, and the Next Protocol value is one of identifying
or hybrid OAM protocol - the payload that immediately follows SFC active or hybrid OAM protocol - the payload that immediately
NSH contains OAM command or data; follows SFC NSH contains OAM command or data;
o O bit is clear - no OAM in TLV and the payload determined by the o O bit is clear - no OAM in a Fixed-Length Context Header or
value of the Next Protocol field. Variable-Length Context Header(s) and the payload determined by
the value of the Next Protocol field;
o O bit is clear and the Next Protocol value is one of identifying
active or hybrid OAM protocol MUST be identified and reported as
the erroneous combination. An implementation MAY have control to
enable processing of the OAM payload.
From the above-listed rules follows the recommendation to avoid
combination of OAM in a Fixed-Length Context Header or Variable-
Length Context Header(s) and in the payload immediately following the
SFC NSH because there is no unambiguous way to identify such
combination using the O bit and the Next Protocol field.
Several active OAM protocols will be needed to address all the Several active OAM protocols will be needed to address all the
requirements listed in Section 3. Destination UDP port number may requirements listed in Section 3. Destination UDP port number may
identify protocols if IP/UDP encapsulation used. But extra IP/UDP identify protocols if IP/UDP encapsulation used. But extra IP/UDP
headers, especially in the case of IPv6, add noticeable overhead. headers, especially in the case of IPv6, add noticeable overhead.
This document defines Active OAM Header Figure 2 to demultiplex This document defines Active OAM Header Figure 2 to demultiplex
active OAM protocols on an SFC. active OAM protocols on an SFC.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 15, line 21 skipping to change at page 15, line 26
Wei Meng Wei Meng
ZTE Corporation ZTE Corporation
No.50 Software Avenue, Yuhuatai District No.50 Software Avenue, Yuhuatai District
Nanjing Nanjing
China China
Email: meng.wei2@zte.com.cn,vally.meng@gmail.com Email: meng.wei2@zte.com.cn,vally.meng@gmail.com
Bhumip Khasnabish Bhumip Khasnabish
ZTE TX, Inc. Individual contributor
55 Madison Avenue, Suite 160
Morristown, New Jersey 07960
USA
Email: bhumip.khasnabish@ztetx.com Email: vumip1@gmail.com
Cui Wang Cui Wang
Email: lindawangjoy@gmail.com Email: lindawangjoy@gmail.com
 End of changes. 16 change blocks. 
27 lines changed or deleted 37 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/