Segment Routing Header encapsulation for In-situ OAM Data
draft-ali-spring-ioam-srv6-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-07-08
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
On Agenda |
|
spring at IETF-105
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
SPRING Working Group Z. Ali
Internet-Draft R. Gandhi
Intended status: Standards Track C. Filsfils
Expires: January 9, 2020 F. Brockners
N. Nainar
C. Pignataro
Cisco Systems, Inc.
C. Li
M. Chen
Huawei
G. Dawra
LinkedIn
July 8, 2019
Segment Routing Header encapsulation for In-situ OAM Data
draft-ali-spring-ioam-srv6-01
Abstract
OAM and PM information from the SR endpoints can be piggybacked in
the data packet. The OAM and PM information piggybacking in the data
packets is also known as In-situ OAM (IOAM). IOAM records
operational and telemetry information in the data packet while the
packet traverses a path between two points in the network. This
document defines how IOAM data fields are transported as part of the
Segment Routing with IPv6 data plane (SRv6) header.
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 http://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."
Copyright Notice
Copyright (c) 2018 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Ali, et al. Expires January 9, 2020 [Page 1]
Internet-Draft In-situ OAM SRv6 encapsulation July 8, 2019
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. Requirement Language . . . . . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
3. OAM Metadata Piggybacked in Data Packets . . . . . . . . .. . 4
3.1 IOAM Data Field Encapsulation in SRH . . . . . . . . . . . . 4
4. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Ingress Node . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. SR Segment Endpoint Node . . . . . . . . . . . . . . . . . 5
4.3. Egress Node . . . . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
OAM and PM information from the SR endpoints can be piggybacked in
the data packet. The OAM and PM information piggybacking in the data
packets is also known as In-situ OAM (IOAM). IOAM records
OAM information within the packet while the packet traverses a
particular network domain. The term "in-situ" refers to the fact
that the IOAM data fields are added to the data packets rather than
being sent within probe packets specifically dedicated to OAM.
This document defines how IOAM data fields are transported as part of
the Segment Routing with IPv6 data plane (SRv6) header
[I-D.6man-segment-routing-header].
The IOAM data fields carried are defined in
Show full document text