< draft-spiegel-ippm-ioam-rawexport-01.txt   draft-spiegel-ippm-ioam-rawexport-02.txt >
ippm M. Spiegel ippm M. Spiegel
Internet-Draft Barefoot Networks Internet-Draft Barefoot Networks
Intended status: Informational F. Brockners Intended status: Informational F. Brockners
Expires: April 25, 2019 S. Bhandari Expires: January 9, 2020 S. Bhandari
R. Sivakolundu R. Sivakolundu
Cisco Cisco
October 22, 2018 July 8, 2019
In-situ OAM raw data export with IPFIX In-situ OAM raw data export with IPFIX
draft-spiegel-ippm-ioam-rawexport-01 draft-spiegel-ippm-ioam-rawexport-02
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 how In-situ Operations, Administration, and Maintenance discusses how In-situ Operations, Administration, and Maintenance
(IOAM) information can be exported in raw, i.e. uninterpreted, format (IOAM) information can be exported in raw, i.e. uninterpreted, format
from network devices to systems, such as monitoring or analytics from network devices to systems, such as monitoring or analytics
systems using IPFIX. systems using IPFIX.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 April 25, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 6, line 20 skipping to change at page 6, line 20
MTU: Maximum Transmit Unit MTU: Maximum Transmit Unit
OAM: Operations, Administration, and Maintenance OAM: Operations, Administration, and Maintenance
POT: Proof of Transit POT: Proof of Transit
3. IPFIX for IOAM raw data export 3. IPFIX for IOAM raw data export
IPFIX, being a generic export protocol, can export any Information IPFIX, being a generic export protocol, can export any Information
Elements as long as they are described in the information model. Elements as long as they are described in the information model. The
IPFIX protocol is well suited for and is defined as the protocol for IPFIX protocol is well suited for and is defined as the protocol for
exporting packet samples in [RFC5476]. exporting packet samples in [RFC5476].
IPFIX/PSAMP [RFC7011], [RFC5476] already define many of the IPFIX/PSAMP [RFC7011], [RFC5476] already define many of the
information elements needed for exporting sections of packets needed information elements needed for exporting sections of packets needed
for deriving context and raw IOAM data export. This document for deriving context and raw IOAM data export. This document
specifies required extensions of the IPFIX information model for specifies extensions of the IPFIX information model for meeting the
meeting the requirements in Section 1.1. requirements in Section 1.1.
3.1. Key IPFIX information elements leveraged for IOAM raw data export 3.1. Key IPFIX information elements leveraged for IOAM raw data export
The existing IPFIX Information Elements that are required for IOAM The existing IPFIX Information Elements that are required for IOAM
raw data export are listed here. Their details are available in raw data export are listed here. Their details are available in
IANA's IPFIX registry [IANA-IPFIX]. IANA's IPFIX registry [IANA-IPFIX].
The existing IPFIX Information Elements used to carry the sections of The existing IPFIX Information Elements used to carry the sections of
the packets including IOAM data within it are as follows: the packets including IOAM data within it are as follows:
skipping to change at page 19, line 38 skipping to change at page 19, line 38
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-ippm-ioam-data] [I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S., Pignataro, C., Gredler, H., Brockners, F., Bhandari, S., Pignataro, C., Gredler, H.,
Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov, Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov,
P., Chang, R., daniel.bernier@bell.ca, d., and J. Lemon, P., Chang, R., daniel.bernier@bell.ca, d., and J. Lemon,
"Data Fields for In-situ OAM", draft-ietf-ippm-ioam- "Data Fields for In-situ OAM", draft-ietf-ippm-ioam-
data-04 (work in progress), October 2018. data-06 (work in progress), July 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet [RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet
Sampling (PSAMP) Protocol Specifications", RFC 5476, Sampling (PSAMP) Protocol Specifications", RFC 5476,
DOI 10.17487/RFC5476, March 2009, DOI 10.17487/RFC5476, March 2009,
<https://www.rfc-editor.org/info/rfc5476>. <https://www.rfc-editor.org/info/rfc5476>.
skipping to change at page 20, line 15 skipping to change at page 20, line 15
[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,
"Specification of the IP Flow Information Export (IPFIX) "Specification of the IP Flow Information Export (IPFIX)
Protocol for the Exchange of Flow Information", STD 77, Protocol for the Exchange of Flow Information", STD 77,
RFC 7011, DOI 10.17487/RFC7011, September 2013, RFC 7011, DOI 10.17487/RFC7011, September 2013,
<https://www.rfc-editor.org/info/rfc7011>. <https://www.rfc-editor.org/info/rfc7011>.
9.2. Informative References 9.2. Informative References
[I-D.brockners-ippm-ioam-geneve] [I-D.brockners-ippm-ioam-geneve]
Brockners, F., Bhandari, S., Govindan, V., Pignataro, C., Brockners, F., Bhandari, S., Govindan, V., Pignataro, C.,
Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Mozes, Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Lapukhov,
D., Lapukhov, P., and R. Chang, "Geneve encapsulation for P., Gafni, B., Kfir, A., and M. Spiegel, "Geneve
In-situ OAM Data", draft-brockners-ippm-ioam-geneve-01 encapsulation for In-situ OAM Data", draft-brockners-ippm-
(work in progress), June 2018. ioam-geneve-02 (work in progress), March 2019.
[I-D.brockners-ippm-ioam-vxlan-gpe] [I-D.brockners-ippm-ioam-vxlan-gpe]
Brockners, F., Bhandari, S., Govindan, V., Pignataro, C., Brockners, F., Bhandari, S., Govindan, V., Pignataro, C.,
Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Kfir, A., Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Kfir, A.,
Gafni, B., Lapukhov, P., and M. Spiegel, "VXLAN-GPE Gafni, B., Lapukhov, P., and M. Spiegel, "VXLAN-GPE
Encapsulation for In-situ OAM Data", draft-brockners-ippm- Encapsulation for In-situ OAM Data", draft-brockners-ippm-
ioam-vxlan-gpe-01 (work in progress), June 2018. ioam-vxlan-gpe-02 (work in progress), July 2019.
[I-D.ietf-sfc-ioam-nsh] [I-D.ietf-sfc-ioam-nsh]
Brockners, F., Bhandari, S., Govindan, V., Pignataro, C., Brockners, F., Bhandari, S., Govindan, V., Pignataro, C.,
Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Mozes, Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Mozes,
D., Lapukhov, P., and R. Chang, "NSH Encapsulation for In- D., Lapukhov, P., and R. Chang, "Network Service Header
situ OAM Data", draft-ietf-sfc-ioam-nsh-00 (work in (NSH) Encapsulation for In-situ OAM (IOAM) Data", draft-
progress), May 2018. ietf-sfc-ioam-nsh-01 (work in progress), March 2019.
[I-D.ioametal-ippm-6man-ioam-ipv6-options] [I-D.ioametal-ippm-6man-ioam-ipv6-options]
Bhandari, S., Brockners, F., Pignataro, C., Gredler, H., Bhandari, S., Brockners, F., Pignataro, C., Gredler, H.,
Leddy, J., Youell, S., Mizrahi, T., Kfir, A., Gafni, B., Leddy, J., Youell, S., Mizrahi, T., Kfir, A., Gafni, B.,
Lapukhov, P., Spiegel, M., and S. Krishnan, "In-situ OAM Lapukhov, P., Spiegel, M., Krishnan, S., and R. Asati,
IPv6 Options", draft-ioametal-ippm-6man-ioam- "In-situ OAM IPv6 Options", draft-ioametal-ippm-6man-ioam-
ipv6-options-01 (work in progress), October 2018. ipv6-options-02 (work in progress), March 2019.
[I-D.weis-ippm-ioam-eth] [I-D.weis-ippm-ioam-eth]
Weis, B., Brockners, F., Hill, C., Bhandari, S., Govindan, Weis, B., Brockners, F., Hill, C., Bhandari, S., Govindan,
V., Pignataro, C., Gredler, H., Leddy, J., Youell, S., V., Pignataro, C., Gredler, H., Leddy, J., Youell, S.,
Mizrahi, T., Kfir, A., Gafni, B., Lapukhov, P., and M. Mizrahi, T., Kfir, A., Gafni, B., Lapukhov, P., and M.
Spiegel, "Ethernet Encapsulation for In-situ OAM Data", Spiegel, "EtherType Protocol Identification of In-situ OAM
draft-weis-ippm-ioam-eth-00 (work in progress), October Data", draft-weis-ippm-ioam-eth-01 (work in progress),
2018. March 2019.
[IANA-IPFIX] [IANA-IPFIX]
"IP Flow Information Export (IPFIX) Entities", "IP Flow Information Export (IPFIX) Entities",
<https://www.iana.org/assignments/ipfix/ipfix.xhtml>. <https://www.iana.org/assignments/ipfix/ipfix.xhtml>.
[RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804, [RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804,
DOI 10.17487/RFC2804, May 2000, DOI 10.17487/RFC2804, May 2000,
<https://www.rfc-editor.org/info/rfc2804>. <https://www.rfc-editor.org/info/rfc2804>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
 End of changes. 13 change blocks. 
23 lines changed or deleted 23 lines changed or added

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