In-situ OAM IPv4 Options
draft-gafni-ippm-ioam-ipv4-options-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-03-09
|
|
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)
|
ippm B. Gafni
Internet-Draft A. Kfir
Intended status: Standards Track Mellanox Technologies, Inc.
Expires: September 10, 2019 S. Bhandari
F. Brockners
R. Sivakolundu
Cisco
T. Mizrahi
Huawei Network.IO Innovation Lab
March 09, 2019
In-situ OAM IPv4 Options
draft-gafni-ippm-ioam-ipv4-options-00
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 IPv4.
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 10, 2019.
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
publication of this document. Please review these documents
Gafni, et al. Expires September 10, 2019 [Page 1]
Internet-Draft In-situ OAM IPv4 encapsulation March 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 . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
3. In-situ OAM Metadata Transport in IPv4 . . . . . . . . . . . 3
3.1. Considerations for in-situ OAM in IPv4 options . . . . . 4
3.1.1. Alignment . . . . . . . . . . . . . . . . . . . . . . 4
3.1.2. Total available length . . . . . . . . . . . . . . . 5
3.1.3. Pre-allocation vs. Incremental trace types . . . . . 5
3.1.4. Checksum considerations . . . . . . . . . . . . . . . 5
3.1.4.1. IP checksum . . . . . . . . . . . . . . . . . . . 5
3.1.4.2. TCP checksum . . . . . . . . . . . . . . . . . . 6
3.1.4.3. UDP checksum . . . . . . . . . . . . . . . . . . 6
3.1.5. Fragmentation . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
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 IPv4 [RFC0791].
2. Conventions
2.1. Requirements Language
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.
Gafni, et al. Expires September 10, 2019 [Page 2]
Internet-Draft In-situ OAM IPv4 encapsulation March 2019
2.2. Abbreviations
Show full document text