| < draft-ietf-sfc-ioam-nsh-08.txt | draft-ietf-sfc-ioam-nsh-09.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: 5 October 2022 Thoughtspot | Expires: 29 October 2022 Thoughtspot | |||
| 3 April 2022 | 27 April 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-08 | draft-ietf-sfc-ioam-nsh-09 | |||
| 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 5 October 2022. | This Internet-Draft will expire on 29 October 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 (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| skipping to change at page 2, line 16 ¶ | skipping to change at page 2, line 16 ¶ | |||
| 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 . . . . . . . . . . . . . . . . . 6 | 8.2. Informative References . . . . . . . . . . . . . . . . . 7 | |||
| Appendix A. Discussion of the IOAM encapsulation approach . . . 7 | Appendix A. Discussion of the IOAM encapsulation approach . . . 7 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 | 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 | |||
| Service Header (NSH) [RFC8300] encapsulation for the Service Function | Service Header (NSH) [RFC8300] encapsulation for the Service Function | |||
| skipping to change at page 3, line 44 ¶ | skipping to change at page 3, line 44 ¶ | |||
| | | | | | | | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ | |||
| | | | | | | |||
| | | | | | | |||
| | Payload + Padding (L2/L3/ESP/...) | | | Payload + Padding (L2/L3/ESP/...) | | |||
| | | | | | | |||
| | | | | | | |||
| | | | | | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| The NSH header and fields are defined in [RFC8300]. The "NSH Next | The NSH header and fields are defined in [RFC8300]. The O-bit MUST | |||
| Protocol" value (referred to as "NP" in the diagram above) is | be handled following the rules in [I-D.ietf-sfc-oam-packet]. The | |||
| TBD_IOAM. | "NSH Next Protocol" value (referred to as "NP" in the diagram above) | |||
| is TBD_IOAM. | ||||
| The IOAM related fields in NSH are defined as follows: | The IOAM related fields in NSH are defined as follows: | |||
| IOAM-Type: 8-bit field defining the IOAM-Option-Type, as defined | IOAM-Type: 8-bit field defining the IOAM-Option-Type, as defined | |||
| in the IOAM Option-Type Registry specified in | in the IOAM Option-Type Registry specified in | |||
| [I-D.ietf-ippm-ioam-data]. | [I-D.ietf-ippm-ioam-data]. | |||
| IOAM HDR Len: 8 bit Length field contains the length of the IOAM | IOAM HDR Len: 8 bit Length field contains the length of the IOAM | |||
| header in 4-octet units. | header in 4-octet units. | |||
| skipping to change at page 5, line 13 ¶ | skipping to change at page 5, line 13 ¶ | |||
| +---------------+-------------+---------------+ | +---------------+-------------+---------------+ | |||
| 5. Security Considerations | 5. Security Considerations | |||
| IOAM is considered a "per domain" feature, where one or several | IOAM is considered a "per domain" feature, where one or several | |||
| operators decide on leveraging and configuring IOAM according to | operators decide on leveraging and configuring IOAM according to | |||
| their needs. Still, operators need to properly secure the IOAM | their needs. Still, operators need to properly secure the IOAM | |||
| domain to avoid malicious configuration and use, which could include | domain to avoid malicious configuration and use, which could include | |||
| injecting malicious IOAM packets into a domain. For additional IOAM | injecting malicious IOAM packets into a domain. For additional IOAM | |||
| related security considerations, see Section 10 in | related security considerations, see Section 10 in | |||
| [I-D.ietf-ippm-ioam-data]. | [I-D.ietf-ippm-ioam-data]. For additional OAM and NSH related | |||
| security considerations see Section 5 of [I-D.ietf-sfc-oam-packet]. | ||||
| 6. Acknowledgements | 6. Acknowledgements | |||
| 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, | |||
| Andrew Yourtchenko and Greg Mirsky for the comments and advice. | Andrew Yourtchenko, Greg Mirsky and Mohamed Boucadair for the | |||
| comments and advice. | ||||
| 7. Contributors | 7. Contributors | |||
| In addition to editors listed on the title page, the following people | In addition to editors listed on the title page, the following people | |||
| have contributed to this document: | have contributed to this document: | |||
| Vengada Prasad Govindan | Vengada Prasad Govindan | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| Email: venggovi@cisco.com | Email: venggovi@cisco.com | |||
| skipping to change at page 6, line 36 ¶ | skipping to change at page 6, line 36 ¶ | |||
| 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", Work in Progress, Internet-Draft, draft- | |||
| ietf-ippm-ioam-data-17, 13 December 2021, | ietf-ippm-ioam-data-17, 13 December 2021, | |||
| <https://www.ietf.org/archive/id/draft-ietf-ippm-ioam- | <https://www.ietf.org/archive/id/draft-ietf-ippm-ioam- | |||
| data-17.txt>. | data-17.txt>. | |||
| [I-D.ietf-sfc-oam-packet] | ||||
| Boucadair, M., "OAM Packet and Behavior in the Network | ||||
| Service Header (NSH)", Work in Progress, Internet-Draft, | ||||
| draft-ietf-sfc-oam-packet-01, 25 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>. | |||
| [RFC8300] Quinn, P., Ed., Elzur, U., Ed., and C. Pignataro, Ed., | [RFC8300] Quinn, P., Ed., Elzur, U., Ed., and C. Pignataro, Ed., | |||
| skipping to change at page 7, line 10 ¶ | skipping to change at page 7, line 17 ¶ | |||
| 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", Work in Progress, Internet- | |||
| Draft, draft-ietf-ippm-ioam-deployment-00, 19 October | Draft, draft-ietf-ippm-ioam-deployment-01, 11 April 2022, | |||
| 2021, <https://www.ietf.org/archive/id/draft-ietf-ippm- | <https://www.ietf.org/archive/id/draft-ietf-ippm-ioam- | |||
| ioam-deployment-00.txt>. | 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", Work in Progress, Internet-Draft, | |||
| draft-ietf-ippm-ioam-direct-export-07, 13 October 2021, | draft-ietf-ippm-ioam-direct-export-07, 13 October 2021, | |||
| <https://www.ietf.org/archive/id/draft-ietf-ippm-ioam- | <https://www.ietf.org/archive/id/draft-ietf-ippm-ioam- | |||
| direct-export-07.txt>. | direct-export-07.txt>. | |||
| [I-D.ietf-ippm-ioam-flags] | [I-D.ietf-ippm-ioam-flags] | |||
| End of changes. 10 change blocks. | ||||
| 14 lines changed or deleted | 24 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/ | ||||