Network Service Header (NSH) Encapsulation for In-situ OAM (IOAM) Data
draft-ietf-sfc-ioam-nsh-03
SFC F. Brockners, Ed.
Internet-Draft S. Bhandari, Ed.
Intended status: Standards Track Cisco
Expires: September 20, 2020 March 19, 2020
Network Service Header (NSH) Encapsulation for In-situ OAM (IOAM) Data
draft-ietf-sfc-ioam-nsh-03
Abstract
In-situ Operations, Administration, and Maintenance (IOAM) records
operational and telemetry information in the packet while the packet
traverses a path between two points in the network. This document
outlines how IOAM data fields are encapsulated in the Network Service
Header (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 September 20, 2020.
Copyright Notice
Copyright (c) 2020 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
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.
Brockners & Bhandari Expires September 20, 2020 [Page 1]
Internet-Draft NSH encapsulation for In-situ OAM March 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. IOAM data fields encapsulation in NSH . . . . . . . . . . . . 3
4. Considerations . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Discussion of the encapsulation approach . . . . . . . . 4
4.2. IOAM and the use of the NSH O-bit . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
In-situ OAM (IOAM), as defined in [I-D.ietf-ippm-ioam-data], records
OAM information within the packet while the packet traverses a
particular network domain. The term "in-situ" refers to the fact
that the OAM data is added to the data packets rather than is being
sent within packets specifically dedicated to OAM. This document
defines how IOAM data fields are transported as part of the Network
Service Header (NSH) [RFC8300] encapsulation for the Service Function
Chaining (SFC) [RFC7665]. The IOAM-Data-Fields are defined in
[I-D.ietf-ippm-ioam-data]. An implementation of IOAM which leverages
NSH to carry the IOAM data is available from the FD.io open source
software project [FD.io].
2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Abbreviations used in this document:
IOAM: In-situ Operations, Administration, and Maintenance
NSH: Network Service Header
OAM: Operations, Administration, and Maintenance
SFC: Service Function Chaining
Brockners & Bhandari Expires September 20, 2020 [Page 2]
Internet-Draft NSH encapsulation for In-situ OAM March 2020
TLV: Type, Length, Value
3. IOAM data fields encapsulation in NSH
The NSH is defined in [RFC8300]. IOAM-Data-Fields are carried in NSH
using a next protocol header which follows the NSH MD context
Show full document text