< draft-brockners-ippm-ioam-vxlan-gpe-01.txt   draft-brockners-ippm-ioam-vxlan-gpe-02.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: December 29, 2018 C. Pignataro Expires: January 6, 2020 C. Pignataro
Cisco Cisco
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
J. Leddy J. Leddy
Comcast
S. Youell S. Youell
JMPC JMPC
T. Mizrahi T. Mizrahi
Marvell Huawei Network.IO Innovation Lab
A. Kfir A. Kfir
B. Gafni B. Gafni
Mellanox Technologies, Inc. Mellanox Technologies, Inc.
P. Lapukhov P. Lapukhov
Facebook Facebook
M. Spiegel M. Spiegel
Barefoot Networks Barefoot Networks
June 27, 2018 July 5, 2019
VXLAN-GPE Encapsulation for In-situ OAM Data VXLAN-GPE Encapsulation for In-situ OAM Data
draft-brockners-ippm-ioam-vxlan-gpe-01 draft-brockners-ippm-ioam-vxlan-gpe-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
outlines how IOAM data fields are encapsulated in VXLAN-GPE. outlines how IOAM data fields are encapsulated in VXLAN-GPE.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 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 December 29, 2018. This Internet-Draft will expire on January 6, 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
(http://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 4, line 46 skipping to change at page 4, line 46
The VXLAN-GPE header and fields are defined in The VXLAN-GPE header and fields are defined in
[I-D.ietf-nvo3-vxlan-gpe]. The VXLAN Next Protocol value for IOAM is [I-D.ietf-nvo3-vxlan-gpe]. The VXLAN Next Protocol value for IOAM is
TBD_IOAM. TBD_IOAM.
The IOAM related fields in VXLAN-GPE are defined as follows: The IOAM related fields in VXLAN-GPE are defined as follows:
IOAM-Type: 8-bit field defining the IOAM Option type, as defined in IOAM-Type: 8-bit field defining the IOAM Option type, as defined in
Section 7.2 of [I-D.ietf-ippm-ioam-data]. Section 7.2 of [I-D.ietf-ippm-ioam-data].
IOAM HDR len: 8-bit unsigned integer. Length of the IOAM HDR in IOAM HDR len: 8-bit unsigned integer. Length of the IOAM HDR in
4-octet units. 4-octet units not including the first 4 octects.
Reserved: 8-bit reserved field MUST be set to zero upon transmission Reserved: 8-bit reserved field MUST be set to zero upon transmission
and ignored upon receipt. and ignored upon receipt.
Next Protocol: 8-bit unsigned integer that determines the type of Next Protocol: 8-bit unsigned integer that determines the type of
header following IOAM protocol. The value is from the IANA header following IOAM protocol. The value is from the IANA
registry setup for VXLAN GPE Next Protocol defined in registry setup for VXLAN GPE Next Protocol defined in
[I-D.ietf-nvo3-vxlan-gpe]. [I-D.ietf-nvo3-vxlan-gpe].
IOAM Option and Data Space: IOAM option header and data is present IOAM Option and Data Space: IOAM option header and data is present
skipping to change at page 7, line 37 skipping to change at page 7, line 37
[ETYPES] "IANA Ethernet Numbers", [ETYPES] "IANA Ethernet Numbers",
<https://www.iana.org/assignments/ethernet-numbers/ <https://www.iana.org/assignments/ethernet-numbers/
ethernet-numbers.xhtml>. ethernet-numbers.xhtml>.
[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-02 (work in progress), March 2018. data-06 (work in progress), July 2019.
[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-06 (work Extension for VXLAN", draft-ietf-nvo3-vxlan-gpe-07 (work
in progress), April 2018. in progress), April 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, <https://www.rfc- DOI 10.17487/RFC2119, March 1997,
editor.org/info/rfc2119>. <https://www.rfc-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,
editor.org/info/rfc2784>. <https://www.rfc-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 [RFC7605] Touch, J., "Recommendations on Using Assigned Transport
Port Numbers", BCP 165, RFC 7605, DOI 10.17487/RFC7605, Port Numbers", BCP 165, RFC 7605, DOI 10.17487/RFC7605,
August 2015, <https://www.rfc-editor.org/info/rfc7605>. August 2015, <https://www.rfc-editor.org/info/rfc7605>.
8.2. Informative References 8.2. Informative References
[FD.io] "Fast Data Project: FD.io", <https://fd.io/>. [FD.io] "Fast Data Project: FD.io", <https://fd.io/>.
[I-D.brockners-proof-of-transit] [I-D.ietf-sfc-proof-of-transit]
Brockners, F., Bhandari, S., Dara, S., Pignataro, C., Brockners, F., Bhandari, S., Dara, S., Pignataro, C.,
Leddy, J., Youell, S., Mozes, D., and T. Mizrahi, "Proof Leddy, J., Youell, S., Mozes, D., Mizrahi, T., Aguado, A.,
of Transit", draft-brockners-proof-of-transit-05 (work in and D. Lopez, "Proof of Transit", draft-ietf-sfc-proof-of-
progress), May 2018. transit-02 (work in progress), March 2019.
[RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function
Chaining (SFC) Architecture", RFC 7665, Chaining (SFC) Architecture", RFC 7665,
DOI 10.17487/RFC7665, October 2015, <https://www.rfc- DOI 10.17487/RFC7665, October 2015,
editor.org/info/rfc7665>. <https://www.rfc-editor.org/info/rfc7665>.
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
skipping to change at page 9, line 18 skipping to change at page 9, line 18
United States United States
Email: cpignata@cisco.com Email: cpignata@cisco.com
Hannes Gredler Hannes Gredler
RtBrick Inc. RtBrick Inc.
Email: hannes@rtbrick.com Email: hannes@rtbrick.com
John Leddy John Leddy
Comcast
Email: John_Leddy@cable.comcast.com Email: john@leddy.net
Stephen Youell Stephen Youell
JP Morgan Chase JP Morgan Chase
25 Bank Street 25 Bank Street
London E14 5JP London E14 5JP
United Kingdom United Kingdom
Email: stephen.youell@jpmorgan.com Email: stephen.youell@jpmorgan.com
Tal Mizrahi Tal Mizrahi
Marvell Huawei Network.IO Innovation Lab
6 Hamada St.
Yokneam 20692
Israel Israel
Email: talmi@marvell.com Email: tal.mizrahi.phd@gmail.com
Aviv Kfir Aviv Kfir
Mellanox Technologies, Inc. Mellanox Technologies, Inc.
350 Oakmead Parkway, Suite 100 350 Oakmead Parkway, Suite 100
Sunnyvale, CA 94085 Sunnyvale, CA 94085
U.S.A. U.S.A.
Email: avivk@mellanox.com Email: avivk@mellanox.com
Barak Gafni Barak Gafni
Mellanox Technologies, Inc. Mellanox Technologies, Inc.
 End of changes. 21 change blocks. 
29 lines changed or deleted 26 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/