Multi-Layer Active OAM for Service Function Chains in Networks
draft-wang-sfc-multi-layer-oam-10
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-09-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
SFC WG G. Mirsky
Internet-Draft ZTE Corp.
Intended status: Standards Track W. Meng
Expires: March 25, 2018 ZTE Corporation
B. Khasnabish
ZTE TX, Inc.
C. Wang
September 21, 2017
Multi-Layer Active OAM for Service Function Chains in Networks
draft-wang-sfc-multi-layer-oam-10
Abstract
A multi-layer approach to the task of Operation, Administration and
Maintenance (OAM) of Service Function Chains (SFCs) in networks is
presented. Based on the requirements towards active OAM for SFC, a
multi-layer model is introduced. A mechanism to detect and localize
defects using the multi-layer model is also described.
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 March 25, 2018.
Copyright Notice
Copyright (c) 2017 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
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Mirsky, et al. Expires March 25, 2018 [Page 1]
Internet-Draft Multi-Layer Active OAM for SFC September 2017
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. Multi-layer Model of SFC OAM . . . . . . . . . . . . . . . . 4
4. Requirements for Multi-layer Model of Active OAM . . . . . . 4
5. Active OAM Identification in SFC NSH . . . . . . . . . . . . 6
6. SFC OAM multi-layer model . . . . . . . . . . . . . . . . . . 6
7. Echo Request/Echo Reply for SFC in Networks . . . . . . . . . 7
7.1. SFC Echo Request Transmission . . . . . . . . . . . . . . 9
7.2. SFC Echo Request Reception . . . . . . . . . . . . . . . 9
7.3. SFC Echo Reply Transmission . . . . . . . . . . . . . . . 9
7.4. Overlay Echo Reply Reception . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
9.1. SFC Active OAM Protocol . . . . . . . . . . . . . . . . . 11
9.2. SFC Active OAM Message Type . . . . . . . . . . . . . . . 11
9.3. SFC Echo Request/Echo Reply Parameters . . . . . . . . . 12
9.4. SFC Echo Request/Echo Reply Message Types . . . . . . . . 12
9.5. SFC Echo Reply Modes . . . . . . . . . . . . . . . . . . 12
9.6. SFC TLV Type . . . . . . . . . . . . . . . . . . . . . . 13
9.7. SFC OAM UDP Port . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . 14
10.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
[RFC7665] defines components necessary to implement Service Function
Chain (SFC). These include a classifier which performs
classification of incoming packets. A Service Function Forwarder
(SFF) is responsible for forwarding traffic to one or more connected
Show full document text