< draft-ietf-ippm-ioam-data-00.txt   draft-ietf-ippm-ioam-data-01.txt >
ippm F. Brockners ippm F. Brockners
Internet-Draft S. Bhandari Internet-Draft S. Bhandari
Intended status: Standards Track C. Pignataro Intended status: Standards Track C. Pignataro
Expires: March 8, 2018 Cisco Expires: May 3, 2018 Cisco
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
J. Leddy J. Leddy
Comcast Comcast
S. Youell S. Youell
JPMC JPMC
T. Mizrahi T. Mizrahi
Marvell Marvell
D. Mozes D. Mozes
Mellanox Technologies Ltd. Mellanox Technologies Ltd.
P. Lapukhov P. Lapukhov
Facebook Facebook
R. Chang R. Chang
Barefoot Networks Barefoot Networks
D. Bernier D. Bernier
Bell Canada Bell Canada
September 4, 2017 October 30, 2017
Data Fields for In-situ OAM Data Fields for In-situ OAM
draft-ietf-ippm-ioam-data-00 draft-ietf-ippm-ioam-data-01
Abstract Abstract
In-situ Operations, Administration, and Maintenance (IOAM) records In-situ Operations, Administration, and Maintenance (IOAM) records
operational and telemetry information in the packet while the packet operational and telemetry information in the packet while the packet
traverses a path between two points in the network. This document traverses a path between two points in the network. This document
discusses the data fields and associated data types for in-situ OAM. discusses the data fields and associated data types for in-situ OAM.
In-situ OAM data fields can be embedded into a variety of transports In-situ OAM data fields can be embedded into a variety of transports
such as NSH, Segment Routing, Geneve, native IPv6 (via extension such as NSH, Segment Routing, Geneve, native IPv6 (via extension
header), or IPv4. In-situ OAM can be used to complement OAM header), or IPv4. In-situ OAM can be used to complement OAM
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 March 8, 2018. This Internet-Draft will expire on May 3, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
4. IOAM Data Types and Formats . . . . . . . . . . . . . . . . . 5 4. IOAM Data Types and Formats . . . . . . . . . . . . . . . . . 5
4.1. IOAM Tracing Options . . . . . . . . . . . . . . . . . . 6 4.1. IOAM Tracing Options . . . . . . . . . . . . . . . . . . 6
4.1.1. Pre-allocated Trace Option . . . . . . . . . . . . . 8 4.1.1. Pre-allocated Trace Option . . . . . . . . . . . . . 8
4.1.2. Incremental Trace Option . . . . . . . . . . . . . . 11 4.1.2. Incremental Trace Option . . . . . . . . . . . . . . 11
4.1.3. IOAM node data fields and associated formats . . . . 14 4.1.3. IOAM node data fields and associated formats . . . . 14
4.1.4. Examples of IOAM node data . . . . . . . . . . . . . 19 4.1.4. Examples of IOAM node data . . . . . . . . . . . . . 19
4.2. IOAM Proof of Transit Option . . . . . . . . . . . . . . 21 4.2. IOAM Proof of Transit Option . . . . . . . . . . . . . . 21
4.3. IOAM Edge-to-Edge Option . . . . . . . . . . . . . . . . 23 4.3. IOAM Edge-to-Edge Option . . . . . . . . . . . . . . . . 23
5. IOAM Data Export . . . . . . . . . . . . . . . . . . . . . . 23 5. IOAM Data Export . . . . . . . . . . . . . . . . . . . . . . 23
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
6.1. Creation of a New In-Situ OAM 6.1. Creation of a new In-Situ OAM Protocol Parameters
(IOAM) Protocol Parameters IANA registry . . . . . . . . 24 Registry (IOAM) Protocol
Parameters IANA registry . . . . . . . . . . . . . . . . 24
6.2. IOAM Trace Type Registry . . . . . . . . . . . . . . . . 24 6.2. IOAM Trace Type Registry . . . . . . . . . . . . . . . . 24
6.3. IOAM Trace Flags Registry . . . . . . . . . . . . . . . . 24 6.3. IOAM Trace Flags Registry . . . . . . . . . . . . . . . . 24
6.4. IOAM POT Type Registry . . . . . . . . . . . . . . . . . 25 6.4. IOAM POT Type Registry . . . . . . . . . . . . . . . . . 25
6.5. IOAM E2E Type Registry . . . . . . . . . . . . . . . . . 25 6.5. IOAM E2E Type Registry . . . . . . . . . . . . . . . . . 25
7. Manageability Considerations . . . . . . . . . . . . . . . . 25 7. Manageability Considerations . . . . . . . . . . . . . . . . 25
8. Security Considerations . . . . . . . . . . . . . . . . . . . 25 8. Security Considerations . . . . . . . . . . . . . . . . . . . 25
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.1. Normative References . . . . . . . . . . . . . . . . . . 25 10.1. Normative References . . . . . . . . . . . . . . . . . . 25
10.2. Informative References . . . . . . . . . . . . . . . . . 26 10.2. Informative References . . . . . . . . . . . . . . . . . 26
skipping to change at page 10, line 42 skipping to change at page 10, line 42
Bit 11 When set indicates presence of the Checksum Complement Bit 11 When set indicates presence of the Checksum Complement
node data. node data.
Bit 12-15 Undefined in this draft. Bit 12-15 Undefined in this draft.
Section 4.1.3 describes the IOAM data types and their formats. Section 4.1.3 describes the IOAM data types and their formats.
Within an in-situ OAM domain possible combinations of these bits Within an in-situ OAM domain possible combinations of these bits
making the IOAM-Trace-Type can be restricted by configuration making the IOAM-Trace-Type can be restricted by configuration
knobs. knobs.
Node Data Length: 4-bit unsigned integer. This field specifies the NodeLen: 4-bit unsigned integer. This field specifies the length of
length of data added by each node in multiples of 4-octets. For data added by each node in multiples of 4-octets. For example, if
example, if 3 IOAM-Trace-Type bits are set and none of them is 3 IOAM-Trace-Type bits are set and none of them is wide, then the
wide, then the Node Data Length would be 3. If 3 IOAM-Trace-Type NodeLen would be 3. If 3 IOAM-Trace-Type bits are set and 2 of
bits are set and 2 of them are wide, then the Node Data Length them are wide, then the NodeLen would be 5.
would be 5.
Flags 5-bit field. Following flags are defined: Flags 5-bit field. Following flags are defined:
Bit 0 "Overflow" (O-bit) (most significant bit). This bit is set Bit 0 "Overflow" (O-bit) (most significant bit). This bit is set
by the network element if there is not enough number of octets by the network element if there is not enough number of octets
left to record node data, no field is added and the overflow left to record node data, no field is added and the overflow
"O-bit" must be set to "1" in the header. This is useful for "O-bit" must be set to "1" in the header. This is useful for
transit nodes to ignore further processing of the option. transit nodes to ignore further processing of the option.
Bit 1 "Loopback" (L-bit). Loopback mode is used to send a copy Bit 1 "Loopback" (L-bit). Loopback mode is used to send a copy
skipping to change at page 13, line 38 skipping to change at page 13, line 38
Bit 10 When set indicates presence of app_data wide in the node Bit 10 When set indicates presence of app_data wide in the node
data. data.
Bit 11 When set indicates presence of the Checksum Complement Bit 11 When set indicates presence of the Checksum Complement
node data. node data.
Bit 12-15 Undefined in this draft. Bit 12-15 Undefined in this draft.
Section 4.1.3 describes the IOAM data types and their formats. Section 4.1.3 describes the IOAM data types and their formats.
Node Data Length: 4-bit unsigned integer. This field specifies the NodeLen: 4-bit unsigned integer. This field specifies the length of
length of data added by each node in multiples of 4-octets. For data added by each node in multiples of 4-octets. For example, if
example, if 3 IOAM-Trace-Type bits are set and none of them is 3 IOAM-Trace-Type bits are set and none of them is wide, then the
wide, then the Node Data Length would be 3. If 3 IOAM-Trace-Type NodeLen would be 3. If 3 IOAM-Trace-Type bits are set and 2 of
bits are set and 2 of them are wide, then the Node Data Length them are wide, then the NodeLen would be 5.
would be 5.
Flags 5-bit field. Following flags are defined: Flags 5-bit field. Following flags are defined:
Bit 0 "Overflow" (O-bit) (least significant bit). This bit is Bit 0 "Overflow" (O-bit) (most significant bit). This bit is set
set by the network element if there is not enough number of by the network element if there is not enough number of octets
octets left to record node data, no field is added and the left to record node data, no field is added and the overflow
overflow "O-bit" must be set to "1" in the header. This is "O-bit" must be set to "1" in the header. This is useful for
useful for transit nodes to ignore further processing of the transit nodes to ignore further processing of the option.
option.
Bit 1 "Loopback" (L-bit). This bit when set indicates to the Bit 1 "Loopback" (L-bit). This bit when set indicates to the
transit nodes processing this option to send a copy of the transit nodes processing this option to send a copy of the
packet back to the source of the packet while it continues to packet back to the source of the packet while it continues to
forward the original packet towards the destination. The L-bit forward the original packet towards the destination. The L-bit
MUST be cleared in the copy of the packet before sending it. MUST be cleared in the copy of the packet before sending it.
Bit 2-4 Reserved. Must be zero. Bit 2-4 Reserved. Must be zero.
Maximum Length: 7-bit unsigned integer. This field specifies the Maximum Length: 7-bit unsigned integer. This field specifies the
maximum length of the node data list in multiples of 4-octets. maximum length of the node data list in multiples of 4-octets.
Given that the sender knows the minimum path MTU, the sender can Given that the sender knows the minimum path MTU, the sender can
set the maximum length according to the number of node data bytes set the maximum length according to the number of node data bytes
allowed before exceeding the MTU. Thus, a simple comparison allowed before exceeding the MTU. Thus, a simple comparison
between "Opt data Len" and "Max Length" allows to decide whether between "NodeLen" and "Max Length" allows to decide whether or not
or not data could be added. data could be added.
Node data List [n]: Variable-length field. The type of which is Node data List [n]: Variable-length field. The type of which is
determined by the OAM Type representing the n-th node data in the determined by the OAM Type representing the n-th node data in the
node data list. The node data list is encoded starting from the node data list. The node data list is encoded starting from the
last node data of the path. The first element of the node data last node data of the path. The first element of the node data
list (node data list [0]) contains the last node of the path while list (node data list [0]) contains the last node of the path while
the last node data of the node data list (node data list[n]) the last node data of the node data list (node data list[n])
contains the first node data of the path traced. contains the first node data of the path traced.
4.1.3. IOAM node data fields and associated formats 4.1.3. IOAM node data fields and associated formats
skipping to change at page 16, line 15 skipping to change at page 16, line 15
when the nodes are time synchronized. When this field is part of when the nodes are time synchronized. When this field is part of
the data field but a node populating the field is not able to fill the data field but a node populating the field is not able to fill
it, the field position in the field must be filled with value it, the field position in the field must be filled with value
0xFFFFFFFF to mean not populated. 0xFFFFFFFF to mean not populated.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp nanoseconds | | timestamp nanoseconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
transit delay: 4-octet unsigned integer in the range 0 to 2^30-1. transit delay: 4-octet unsigned integer in the range 0 to 2^31-1.
It is the time in nanoseconds the packet spent in the transit It is the time in nanoseconds the packet spent in the transit
node. This can serve as an indication of the queuing delay at the node. This can serve as an indication of the queuing delay at the
node. If the transit delay exceeds 2^30-1 nanoseconds then the node. If the transit delay exceeds 2^31-1 nanoseconds then the
top bit 'O' is set to indicate overflow. When this field is part top bit 'O' is set to indicate overflow and value set to
of the data field but a node populating the field is not able to 0x80000000. When this field is part of the data field but a node
fill it, the field position in the field must be filled with value populating the field is not able to fill it, the field position in
0xFFFFFFFF to mean not populated. the field must be filled with value 0xFFFFFFFF to mean not
populated.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|O| transit delay | |O| transit delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
app_data: 4-octet placeholder which can be used by the node to add app_data: 4-octet placeholder which can be used by the node to add
application specific data. App_data represents a "free-format" application specific data. App_data represents a "free-format"
4-octet bit field with its semantics defined by a specific 4-octet bit field with its semantics defined by a specific
deployment. deployment.
skipping to change at page 19, line 29 skipping to change at page 19, line 29
4.1.4. Examples of IOAM node data 4.1.4. Examples of IOAM node data
An entry in the "node data list" array can have different formats, An entry in the "node data list" array can have different formats,
following the needs of the deployment. Some deployments might only following the needs of the deployment. Some deployments might only
be interested in recording the node identifiers, whereas others might be interested in recording the node identifiers, whereas others might
be interested in recording node identifier and timestamp. The be interested in recording node identifier and timestamp. The
section defines different types that an entry in "node data list" can section defines different types that an entry in "node data list" can
take. take.
0x002B: IOAM-Trace-Type is 0x2B then the format of node data is: 0xD400: IOAM-Trace-Type is 0xD400 then the format of node data is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop_Lim | node_id | | Hop_Lim | node_id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ingress_if_id | egress_if_id | | ingress_if_id | egress_if_id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp nanoseconds | | timestamp nanoseconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| app_data | | app_data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0x0003: IOAM-Trace-Type is 0x0003 then the format is: 0xC000: IOAM-Trace-Type is 0xC000 then the format is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop_Lim | node_id | | Hop_Lim | node_id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ingress_if_id | egress_if_id | | ingress_if_id | egress_if_id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0x0009: IOAM-Trace-Type is 0x0009 then the format is: 0x9000: IOAM-Trace-Type is 0x9000 then the format is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop_Lim | node_id | | Hop_Lim | node_id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp nanoseconds | | timestamp nanoseconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0x0021: IOAM-Trace-Type is 0x0021 then the format is: 0x8400: IOAM-Trace-Type is 0x8400 then the format is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop_Lim | node_id | | Hop_Lim | node_id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| app_data | | app_data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0x0029: IOAM-Trace-Type is 0x0029 then the format is: 0x9400: IOAM-Trace-Type is 0x9400 then the format is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop_Lim | node_id | | Hop_Lim | node_id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp nanoseconds | | timestamp nanoseconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| app_data | | app_data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0x018C: IOAM-Trace-Type is 0x104D then the format is: 0x3180: IOAM-Trace-Type is 0x3180 then the format is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp seconds | | timestamp seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp nanoseconds | | timestamp nanoseconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Schema Id | | Length | Schema Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
skipping to change at page 24, line 9 skipping to change at page 24, line 9
process the information further and export the information using process the information further and export the information using
e.g., IPFIX. e.g., IPFIX.
The discussion of IOAM data processing and export is left for a The discussion of IOAM data processing and export is left for a
future version of this document. future version of this document.
6. IANA Considerations 6. IANA Considerations
This document requests the following IANA Actions. This document requests the following IANA Actions.
6.1. Creation of a New In-Situ OAM (IOAM) Protocol Parameters IANA 6.1. Creation of a new In-Situ OAM Protocol Parameters Registry (IOAM)
registry Protocol Parameters IANA registry
IANA is requested to create a new protocol registry for "In-Situ OAM IANA is requested to create a new protocol registry for "In-Situ OAM
(IOAM) Protocol Parameters". This is the common registry that will (IOAM) Protocol Parameters". This is the common registry that will
include registrations for all IOAM namespaces. Each Registry, whose include registrations for all IOAM namespaces. Each Registry, whose
names are listed below: names are listed below:
IOAM Trace Type IOAM Trace Type
IOAM Trace flags IOAM Trace flags
skipping to change at page 26, line 47 skipping to change at page 26, line 47
(work in progress), July 2017. (work in progress), July 2017.
[I-D.hildebrand-spud-prototype] [I-D.hildebrand-spud-prototype]
Hildebrand, J. and B. Trammell, "Substrate Protocol for Hildebrand, J. and B. Trammell, "Substrate Protocol for
User Datagrams (SPUD) Prototype", draft-hildebrand-spud- User Datagrams (SPUD) Prototype", draft-hildebrand-spud-
prototype-03 (work in progress), March 2015. prototype-03 (work in progress), March 2015.
[I-D.ietf-nvo3-geneve] [I-D.ietf-nvo3-geneve]
Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic
Network Virtualization Encapsulation", draft-ietf- Network Virtualization Encapsulation", draft-ietf-
nvo3-geneve-04 (work in progress), March 2017. nvo3-geneve-05 (work in progress), September 2017.
[I-D.ietf-nvo3-vxlan-gpe] [I-D.ietf-nvo3-vxlan-gpe]
Maino, F., Kreeger, L., and U. Elzur, "Generic Protocol Maino, F., Kreeger, L., and U. Elzur, "Generic Protocol
Extension for VXLAN", draft-ietf-nvo3-vxlan-gpe-04 (work Extension for VXLAN", draft-ietf-nvo3-vxlan-gpe-04 (work
in progress), April 2017. in progress), April 2017.
[I-D.ietf-sfc-nsh] [I-D.ietf-sfc-nsh]
Quinn, P., Elzur, U., and C. Pignataro, "Network Service Quinn, P., Elzur, U., and C. Pignataro, "Network Service
Header (NSH)", draft-ietf-sfc-nsh-19 (work in progress), Header (NSH)", draft-ietf-sfc-nsh-27 (work in progress),
August 2017. October 2017.
[I-D.kitamura-ipv6-record-route] [I-D.kitamura-ipv6-record-route]
Kitamura, H., "Record Route for IPv6 (PR6) Hop-by-Hop Kitamura, H., "Record Route for IPv6 (PR6) Hop-by-Hop
Option Extension", draft-kitamura-ipv6-record-route-00 Option Extension", draft-kitamura-ipv6-record-route-00
(work in progress), November 2000. (work in progress), November 2000.
[I-D.lapukhov-dataplane-probe] [I-D.lapukhov-dataplane-probe]
Lapukhov, P. and r. remy@barefootnetworks.com, "Data-plane Lapukhov, P. and r. remy@barefootnetworks.com, "Data-plane
probe for in-band telemetry collection", draft-lapukhov- probe for in-band telemetry collection", draft-lapukhov-
dataplane-probe-01 (work in progress), June 2016. dataplane-probe-01 (work in progress), June 2016.
 End of changes. 20 change blocks. 
43 lines changed or deleted 42 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/