< draft-brockners-ippm-ioam-geneve-00.txt   draft-brockners-ippm-ioam-geneve-01.txt >
ippm F. Brockners ippm F. Brockners
Internet-Draft S. Bhandari Internet-Draft S. Bhandari
Intended status: Standards Track V. Govindan Intended status: Standards Track V. Govindan
Expires: September 4, 2018 C. Pignataro Expires: December 29, 2018 C. Pignataro
Cisco Cisco
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
J. Leddy J. Leddy
Comcast Comcast
S. Youell S. Youell
JMPC JMPC
T. Mizrahi T. Mizrahi
Marvell Marvell
P. Lapukhov P. Lapukhov
Facebook Facebook
B. Gafni B. Gafni
A. Kfir A. Kfir
Mellanox Technologies, Inc. Mellanox Technologies, Inc.
M. Spiegel M. Spiegel
Barefoot Networks Barefoot Networks
March 3, 2018 June 27, 2018
Geneve encapsulation for In-situ OAM Data Geneve encapsulation for In-situ OAM Data
draft-brockners-ippm-ioam-geneve-00 draft-brockners-ippm-ioam-geneve-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
outlines how IOAM data fields are encapsulated in Geneve. outlines how IOAM data fields are encapsulated in Geneve.
Status of This Memo Status of This Memo
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 September 4, 2018. This Internet-Draft will expire on December 29, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 31 skipping to change at page 2, line 31
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirement Language . . . . . . . . . . . . . . . . . . 3 2.1. Requirement Language . . . . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
3. IOAM Data Field Encapsulation in Geneve . . . . . . . . . . . 3 3. IOAM Data Field Encapsulation in Geneve . . . . . . . . . . . 3
4. Considerations . . . . . . . . . . . . . . . . . . . . . . . 5 4. Considerations . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Discussion of the encapsulation approach . . . . . . . . 5 4.1. Discussion of the encapsulation approach . . . . . . . . 5
4.2. IOAM and the use of the Geneve O-bit . . . . . . . . . . 6 4.2. IOAM and the use of the Geneve O-bit . . . . . . . . . . 6
4.3. Transit devices . . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
8. Normative References . . . . . . . . . . . . . . . . . . . . 7 8. Normative References . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
In-situ OAM (IOAM) records OAM information within the packet while In-situ OAM (IOAM) records OAM information within the packet while
the packet traverses a particular network domain. The term "in-situ" 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 refers to the fact that the IOAM data fields are added to the data
packets rather than is being sent within packets specifically packets rather than is being sent within packets specifically
dedicated to OAM. This document defines how IOAM data fields are dedicated to OAM. This document defines how IOAM data fields are
transported as part of the Geneve [I-D.ietf-nvo3-geneve] transported as part of the Geneve [I-D.ietf-nvo3-geneve]
encapsulation. The IOAM data fields are defined in encapsulation. The IOAM data fields are defined in
skipping to change at page 6, line 32 skipping to change at page 6, line 32
4.2. IOAM and the use of the Geneve O-bit 4.2. IOAM and the use of the Geneve O-bit
[I-D.ietf-nvo3-geneve] defines an "O bit" for OAM packets. Per [I-D.ietf-nvo3-geneve] defines an "O bit" for OAM packets. Per
[I-D.ietf-nvo3-geneve] the O bit indicates that the packet contains a [I-D.ietf-nvo3-geneve] the O bit indicates that the packet contains a
control message instead of data payload. Packets that carry IOAM control message instead of data payload. Packets that carry IOAM
data fields in addition to regular data payload / customer traffic data fields in addition to regular data payload / customer traffic
must not set the O bit. Packets that carry only IOAM data fields must not set the O bit. Packets that carry only IOAM data fields
without any payload must set the O bit. without any payload must set the O bit.
4.3. Transit devices
If IOAM is deployed in domains where UDP port numbers are not
controlled and do not have a domain-wide meaning, such as on the
global Internet, transit devices MUST NOT attempt to modify the IOAM
data contained in the IOAM option class. In case UDP port numbers
are not controlled there might be UDP packets, which leverage the UDP
port number that Geneve utilizes, i.e. 6081, but the payload of these
packets isn't Geneve. The scenario and associated reasoning is
discussed in [RFC7605] which states that "it is important to
recognize that any interpretation of port numbers -- except at the
endpoints -- may be incorrect, because port numbers are meaningful
only at the endpoints."
5. IANA Considerations 5. IANA Considerations
IANA is requested to allocate a Geneve "option class" numbers for IANA is requested to allocate a Geneve "option class" numbers for
IOAM: IOAM:
+---------------+-------------+---------------+ +---------------+-------------+---------------+
| Option Class | Description | Reference | | Option Class | Description | Reference |
+---------------+-------------+---------------+ +---------------+-------------+---------------+
| x | TBD_IOAM | This document | | x | TBD_IOAM | This document |
+---------------+-------------+---------------+ +---------------+-------------+---------------+
skipping to change at page 7, line 19 skipping to change at page 7, line 35
The authors would like to thank Eric Vyncke, Nalini Elkins, Srihari The authors would like to thank Eric Vyncke, Nalini Elkins, Srihari
Raghavan, Ranganathan T S, Karthik Babu Harichandra Babu, Akshaya Raghavan, Ranganathan T S, Karthik Babu Harichandra Babu, Akshaya
Nadahalli, Stefano Previdi, Hemant Singh, Erik Nordmark, LJ Wobker, Nadahalli, Stefano Previdi, Hemant Singh, Erik Nordmark, LJ Wobker,
and Andrew Yourtchenko for the comments and advice. and Andrew Yourtchenko for the comments and advice.
8. Normative References 8. 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., and d. daniel.bernier@bell.ca, "Data Fields P., Chang, R., daniel.bernier@bell.ca, d., and J. Lemon,
for In-situ OAM", draft-ietf-ippm-ioam-data-01 (work in "Data Fields for In-situ OAM", draft-ietf-ippm-ioam-
progress), October 2017. data-02 (work in progress), March 2018.
[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-05 (work in progress), September 2017. nvo3-geneve-06 (work in progress), March 2018.
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
rfc2119>. editor.org/info/rfc2119>.
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, Traina, "Generic Routing Encapsulation (GRE)", RFC 2784,
DOI 10.17487/RFC2784, March 2000, <https://www.rfc- DOI 10.17487/RFC2784, March 2000, <https://www.rfc-
editor.org/info/rfc2784>. editor.org/info/rfc2784>.
[RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced [RFC3232] Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced
by an On-line Database", RFC 3232, DOI 10.17487/RFC3232, by an On-line Database", RFC 3232, DOI 10.17487/RFC3232,
January 2002, <https://www.rfc-editor.org/info/rfc3232>. January 2002, <https://www.rfc-editor.org/info/rfc3232>.
[RFC7605] Touch, J., "Recommendations on Using Assigned Transport
Port Numbers", BCP 165, RFC 7605, DOI 10.17487/RFC7605,
August 2015, <https://www.rfc-editor.org/info/rfc7605>.
Authors' Addresses Authors' Addresses
Frank Brockners Frank Brockners
Cisco Systems, Inc. Cisco Systems, Inc.
Hansaallee 249, 3rd Floor Hansaallee 249, 3rd Floor
DUESSELDORF, NORDRHEIN-WESTFALEN 40549 DUESSELDORF, NORDRHEIN-WESTFALEN 40549
Germany Germany
Email: fbrockne@cisco.com Email: fbrockne@cisco.com
Shwetha Bhandari Shwetha Bhandari
Cisco Systems, Inc. Cisco Systems, Inc.
Cessna Business Park, Sarjapura Marathalli Outer Ring Road Cessna Business Park, Sarjapura Marathalli Outer Ring Road
Bangalore, KARNATAKA 560 087 Bangalore, KARNATAKA 560 087
India India
Email: shwethab@cisco.com Email: shwethab@cisco.com
Vengada Prasad Govindan Vengada Prasad Govindan
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 13 change blocks. 
13 lines changed or deleted 33 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/