< draft-ietf-sfc-ioam-nsh-09.txt   draft-ietf-sfc-ioam-nsh-10.txt >
SFC F. Brockners, Ed. SFC F. Brockners, Ed.
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track S. Bhandari, Ed. Intended status: Standards Track S. Bhandari, Ed.
Expires: 29 October 2022 Thoughtspot Expires: November 19, 2022 Thoughtspot
27 April 2022 May 18, 2022
Network Service Header (NSH) Encapsulation for In-situ OAM (IOAM) Data Network Service Header (NSH) Encapsulation for In-situ OAM (IOAM) Data
draft-ietf-sfc-ioam-nsh-09 draft-ietf-sfc-ioam-nsh-10
Abstract Abstract
In-situ Operations, Administration, and Maintenance (IOAM) is used In-situ Operations, Administration, and Maintenance (IOAM) is used
for recording and collecting operational and telemetry information for recording and collecting operational and telemetry information
while the packet traverses a path between two points in the network. while the packet traverses a path between two points in the network.
This document outlines how IOAM data fields are encapsulated with the This document outlines how IOAM data fields are encapsulated with the
Network Service Header (NSH). Network Service Header (NSH).
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 29 October 2022. This Internet-Draft will expire on November 19, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Simplified BSD License text as described in Section 4.e of
provided without warranty as described in the Revised BSD License. the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. IOAM encapsulation with NSH . . . . . . . . . . . . . . . . . 3 3. IOAM encapsulation with NSH . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Discussion of the IOAM encapsulation approach . . . 7 Appendix A. Discussion of the IOAM encapsulation approach . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
In-situ OAM (IOAM), as defined in [I-D.ietf-ippm-ioam-data], is used In-situ OAM (IOAM), as defined in [I-D.ietf-ippm-ioam-data], is used
to record and collect OAM information while the packet traverses a to record and collect OAM information while the packet traverses a
particular network domain. The term "in-situ" refers to the fact particular network domain. The term "in-situ" refers to the fact
that the OAM data is added to the data packets rather than is being that the OAM data is added to the data packets rather than is being
sent within packets specifically dedicated to OAM. This document sent within packets specifically dedicated to OAM. This document
defines how IOAM data fields are transported as part of the Network defines how IOAM data fields are transported as part of the Network
skipping to change at page 3, line 16 skipping to change at page 3, line 19
The NSH is defined in [RFC8300]. IOAM-Data-Fields are carried as NSH The NSH is defined in [RFC8300]. IOAM-Data-Fields are carried as NSH
payload using a next protocol header which follows the NSH headers. payload using a next protocol header which follows the NSH headers.
An IOAM header is added containing the different IOAM-Data-Fields. An IOAM header is added containing the different IOAM-Data-Fields.
The IOAM-Data-Fields MUST follow the definitions corresponding to The IOAM-Data-Fields MUST follow the definitions corresponding to
IOAM-Option-Types (e.g. see Section 5 of [I-D.ietf-ippm-ioam-data] IOAM-Option-Types (e.g. see Section 5 of [I-D.ietf-ippm-ioam-data]
and Section 3.2 of [I-D.ietf-ippm-ioam-direct-export]). In an and Section 3.2 of [I-D.ietf-ippm-ioam-direct-export]). In an
administrative domain where IOAM is used, insertion of the IOAM administrative domain where IOAM is used, insertion of the IOAM
header in NSH is enabled at the NSH tunnel endpoints, which also header in NSH is enabled at the NSH tunnel endpoints, which also
serve as IOAM encapsulating/decapsulating nodes by means of serve as IOAM encapsulating/decapsulating nodes by means of
configuration. There can be multiple IOAM headers added by
encapsulating nodes as configured. The IOAM transit nodes (e.g. an
SFF) MUST process all the IOAM headers that are relevant based on its
configuration. See [I-D.ietf-ippm-ioam-deployment] for a discussion configuration. See [I-D.ietf-ippm-ioam-deployment] for a discussion
of deployment related aspects of IOAM-Data-fields. of deployment related aspects of IOAM-Data-fields.
0 1 2 3 0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+
|Ver|O|U| TTL | Length |U|U|U|U|MD Type| NP = TBD_IOAM | | |Ver|O|U| TTL | Length |U|U|U|U|MD Type| NP = TBD_IOAM | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ N +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ N
| Service Path Identifier | Service Index | S | Service Path Identifier | Service Index | S
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ H +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ H
skipping to change at page 6, line 31 skipping to change at page 6, line 41
2185 Park Boulevard 2185 Park Boulevard
Palo Alto, CA 94306 Palo Alto, CA 94306
US US
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-ippm-ioam-data] [I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields
for In-situ OAM", Work in Progress, Internet-Draft, draft- for In-situ OAM", draft-ietf-ippm-ioam-data-17 (work in
ietf-ippm-ioam-data-17, 13 December 2021, progress), December 2021.
<https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-
data-17.txt>.
[I-D.ietf-sfc-oam-packet] [I-D.ietf-sfc-oam-packet]
Boucadair, M., "OAM Packet and Behavior in the Network Boucadair, M., "OAM Packet and Behavior in the Network
Service Header (NSH)", Work in Progress, Internet-Draft, Service Header (NSH)", draft-ietf-sfc-oam-packet-01 (work
draft-ietf-sfc-oam-packet-01, 25 April 2022, in progress), April 2022.
<https://www.ietf.org/archive/id/draft-ietf-sfc-oam-
packet-01.txt>.
[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>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
skipping to change at page 7, line 16 skipping to change at page 7, line 30
"Network Service Header (NSH)", RFC 8300, "Network Service Header (NSH)", RFC 8300,
DOI 10.17487/RFC8300, January 2018, DOI 10.17487/RFC8300, January 2018,
<https://www.rfc-editor.org/info/rfc8300>. <https://www.rfc-editor.org/info/rfc8300>.
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.ietf-ippm-ioam-deployment] [I-D.ietf-ippm-ioam-deployment]
Brockners, F., Bhandari, S., Bernier, D., and T. Mizrahi, Brockners, F., Bhandari, S., Bernier, D., and T. Mizrahi,
"In-situ OAM Deployment", Work in Progress, Internet- "In-situ OAM Deployment", draft-ietf-ippm-ioam-
Draft, draft-ietf-ippm-ioam-deployment-01, 11 April 2022, deployment-01 (work in progress), April 2022.
<https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-
deployment-01.txt>.
[I-D.ietf-ippm-ioam-direct-export] [I-D.ietf-ippm-ioam-direct-export]
Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F., Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F.,
Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ
OAM Direct Exporting", Work in Progress, Internet-Draft, OAM Direct Exporting", draft-ietf-ippm-ioam-direct-
draft-ietf-ippm-ioam-direct-export-07, 13 October 2021, export-07 (work in progress), October 2021.
<https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-
direct-export-07.txt>.
[I-D.ietf-ippm-ioam-flags] [I-D.ietf-ippm-ioam-flags]
Mizrahi, T., Brockners, F., Bhandari, S., Sivakolundu, R., Mizrahi, T., Brockners, F., Bhandari, S., Sivakolundu, R.,
Pignataro, C., Kfir, A., Gafni, B., Spiegel, M., and J. Pignataro, C., Kfir, A., Gafni, B., Spiegel, M., and J.
Lemon, "In-situ OAM Loopback and Active Flags", Work in Lemon, "In-situ OAM Loopback and Active Flags", draft-
Progress, Internet-Draft, draft-ietf-ippm-ioam-flags-07, ietf-ippm-ioam-flags-07 (work in progress), October 2021.
13 October 2021, <https://www.ietf.org/archive/id/draft-
ietf-ippm-ioam-flags-07.txt>.
[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, DOI 10.17487/RFC7665, October 2015,
<https://www.rfc-editor.org/info/rfc7665>. <https://www.rfc-editor.org/info/rfc7665>.
Appendix A. Discussion of the IOAM encapsulation approach Appendix A. Discussion of the IOAM encapsulation approach
This section lists several approaches considered for encapsulating This section lists several approaches considered for encapsulating
IOAM with NSH and presents the rationale for the approach chosen in IOAM with NSH and presents the rationale for the approach chosen in
skipping to change at page 9, line 16 skipping to change at page 9, line 25
additional layer of TLV nesting that the use of NSH MD Type 2 would additional layer of TLV nesting that the use of NSH MD Type 2 would
result in. In addition, this option does not constrain IOAM data to result in. In addition, this option does not constrain IOAM data to
a maximum of 256 octets, thus allowing support for very large a maximum of 256 octets, thus allowing support for very large
deployments. deployments.
Authors' Addresses Authors' Addresses
Frank Brockners (editor) Frank Brockners (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Hansaallee 249, 3rd Floor Hansaallee 249, 3rd Floor
40549 DUESSELDORF DUESSELDORF, NORDRHEIN-WESTFALEN 40549
Germany Germany
Email: fbrockne@cisco.com Email: fbrockne@cisco.com
Shwetha Bhandari (editor) Shwetha Bhandari (editor)
Thoughtspot Thoughtspot
3rd Floor, Indiqube Orion, 24th Main Rd, Garden Layout, HSR Layout 3rd Floor, Indiqube Orion, 24th Main Rd, Garden Layout, HSR Layout
Bangalore, KARNATAKA 560 102 Bangalore, KARNATAKA 560 102
India India
Email: shwetha.bhandari@thoughtspot.com Email: shwetha.bhandari@thoughtspot.com
 End of changes. 14 change blocks. 
33 lines changed or deleted 29 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/