Browse Prior Art Database

USING IN-BAND OPERATIONS, ADMINISTRATION, AND MAINTENANCE SUPERFRAME STRUCTURE FOR FLEXIBLE MESSAGE SIZE AND ENHANCED CAPABILITY

IP.com Disclosure Number: IPCOM000253482D
Publication Date: 2018-Apr-03
Document File: 6 page(s) / 183K

Publishing Venue

The IP.com Prior Art Database

Related People

Randy Zhang: AUTHOR [+4]

Abstract

In-band (or In-situ) Operations, Administration, and Maintenance (IOAM) provides a mechanism to communicate OAM messages over user packets as they travel through a network configured to support that feature. The mechanisms described herein enhance IOAM functionality by defining a superframe structure that consists of one or more follow-on packets that share the same customer packet headers. The superframe structure provides several benefits, including: (1) supporting more flexible and larger messages across one or more IOAM packets; (2) creating lightweight IOAM packets to avoid potential issues due to packet size; and (3) allowing more IOAM message types (through a capability field) to be supported.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 25% of the total text.

Copyright 2018 Cisco Systems, Inc. 1

USING IN-BAND OPERATIONS, ADMINISTRATION, AND MAINTENANCE SUPERFRAME STRUCTURE FOR FLEXIBLE MESSAGE SIZE AND ENHANCED

CAPABILITY

AUTHORS: Randy Zhang Rajiv Asati

Frank Brockners Carlos M. Pignataro Shwetha Bhandari

CISCO SYSTEMS, INC.

ABSTRACT

In-band (or In-situ) Operations, Administration, and Maintenance (IOAM)

provides a mechanism to communicate OAM messages over user packets as they travel

through a network configured to support that feature. The mechanisms described herein

enhance IOAM functionality by defining a superframe structure that consists of one or

more follow-on packets that share the same customer packet headers. The superframe

structure provides several benefits, including: (1) supporting more flexible and larger

messages across one or more IOAM packets; (2) creating lightweight IOAM packets to

avoid potential issues due to packet size; and (3) allowing more IOAM message types

(through a capability field) to be supported.

DETAILED DESCRIPTION

In-band (or In-situ) Operations, Administration, and Maintenance (IOAM)

provides a mechanism to communicate OAM messages over user packets as they travel

through a network configured to support that feature. IOAM protocol details are defined in

several IETF drafts, including those available at https://tools.ietf.org/html/draft-ietf-ippm-

ioam-data-01, https://tools.ietf.org/html/draft-brockners-proof-of-transit-04, and

https://tools.ietf.org/html/draft-brockners-inband-oam-transport-05.

The actual data of the IOAM messages are carried in each packet, which may vary

in size. All of the data is contained within a single packet. If large IOAM messages are

inserted into a user packet, this can cause potential issues due to packet size, such as

Maximum Transmission Unit (MTU) limitations, legacy chip processing limitations, Layer

Copyright 2018 Cisco Systems, Inc. 2

4 (L4) header processing difficulties for Equal-Cost Multi-Path (ECMP), or limited

capabilities in some Internet of Things (IoT) devices. As a result, IOAM message sizes are

very limited, even though some applications may require larger message sizes.

IOAM drafts define the message type using a 16-bit Trace Type field. Bits 0-11 are

already defined, which only leaves four available bits (i.e., undefined bits 12-15). The

mechanisms described herein involve creating a superframe structure that (1) supports

more flexible and larger messages across one or more IOAM packets; (2) creates

lightweight IOAM packets to avoid potential issues due to packet size; and (3) allows more

IOAM message types (through a capability field) to be supported.

In one example, a superframe structure is defined on top of the IOAM packets,

which consists of one or more follow-on IOAM packets that share the same headers as the

original customer packet. The follow-on packets are generated by an IOAM ingress node

(i.e., the entry node into the IOAM domain). At egress, IOAM packets are processed as

before. Additionally, the s...