| rfc8924v2.txt | rfc8924.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) S. Aldrin | Internet Engineering Task Force (IETF) S. Aldrin | |||
| Request for Comments: 8924 Google | Request for Comments: 8924 Google | |||
| Category: Informational C. Pignataro, Ed. | Category: Informational C. Pignataro, Ed. | |||
| ISSN: 2070-1721 N. Kumar, Ed. | ISSN: 2070-1721 N. Kumar, Ed. | |||
| Cisco | Cisco | |||
| R. Krishnan | R. Krishnan | |||
| VMware | VMware | |||
| A. Ghanwani | A. Ghanwani | |||
| Dell | Dell | |||
| September 2020 | October 2020 | |||
| Service Function Chaining (SFC) Operations, Administration, and | Service Function Chaining (SFC) Operations, Administration, and | |||
| Maintenance (OAM) Framework | Maintenance (OAM) Framework | |||
| Abstract | Abstract | |||
| This document provides a reference framework for Operations, | This document provides a reference framework for Operations, | |||
| Administration, and Maintenance (OAM) for Service Function Chaining | Administration, and Maintenance (OAM) for Service Function Chaining | |||
| (SFC). | (SFC). | |||
| skipping to change at line 288 ¶ | skipping to change at line 288 ¶ | |||
| OAM functions applicable at this component include (but are not | OAM functions applicable at this component include (but are not | |||
| limited to) testing the SFCs and the SFPs, validation of the | limited to) testing the SFCs and the SFPs, validation of the | |||
| correlation between an SFC and the actual forwarding path followed | correlation between an SFC and the actual forwarding path followed | |||
| by a packet matching that SFC, i.e., the Rendered Service Path | by a packet matching that SFC, i.e., the Rendered Service Path | |||
| (RSP). Some of the hops of an SFC may not be visible when | (RSP). Some of the hops of an SFC may not be visible when | |||
| Hierarchical Service Function Chaining (hSFC) [RFC8459] is in use. | Hierarchical Service Function Chaining (hSFC) [RFC8459] is in use. | |||
| In such schemes, it is the responsibility of the Internal Boundary | In such schemes, it is the responsibility of the Internal Boundary | |||
| Node (IBN) to glue the connectivity between different levels for | Node (IBN) to glue the connectivity between different levels for | |||
| end-to-end OAM functionality. | end-to-end OAM functionality. | |||
| classifier component: | Classifier component: | |||
| OAM functions applicable at this component include testing the | OAM functions applicable at this component include testing the | |||
| validity of the classification rules and detecting any incoherence | validity of the classification rules and detecting any incoherence | |||
| among the rules installed when more than one classifier is used, | among the rules installed when more than one classifier is used, | |||
| as explained in Section 2.2 of [RFC7665]. | as explained in Section 2.2 of [RFC7665]. | |||
| Figure 2 illustrates an example where OAM for the three defined | Figure 2 illustrates an example where OAM for the three defined | |||
| components are used within the SFC environment. | components are used within the SFC environment. | |||
| +-Classifier +-Service Function Chain OAM | +-Classifier +-Service Function Chain OAM | |||
| | OAM | | | OAM | | |||
| skipping to change at line 540 ¶ | skipping to change at line 540 ¶ | |||
| SFF, SF, and SFC Proxy) on the tested layer. This function is | SFF, SF, and SFC Proxy) on the tested layer. This function is | |||
| typically useful for gathering information from every transit device | typically useful for gathering information from every transit device | |||
| or for isolating the failure point to a specific SF within an SFC or | or for isolating the failure point to a specific SF within an SFC or | |||
| for an entire SFC. Some of the OAM functions supported by trace | for an entire SFC. Some of the OAM functions supported by trace | |||
| functions are: | functions are: | |||
| * the ability to trigger an action from every transit device at the | * the ability to trigger an action from every transit device at the | |||
| SFC layer, using TTL or other means, | SFC layer, using TTL or other means, | |||
| * the ability to trigger every transit device at the SFC layer to | * the ability to trigger every transit device at the SFC layer to | |||
| generate a response with OAM code(s), using TTL or other means, | generate a response with OAM code(s) using TTL or other means, | |||
| * the ability to discover and traverse ECMP paths within an SFC, and | * the ability to discover and traverse ECMP paths within an SFC, and | |||
| * the ability to skip SFs that do not support OAM while tracing SFs | * the ability to skip SFs that do not support OAM while tracing SFs | |||
| in an SFC. | in an SFC. | |||
| 4.4. Performance Measurement Functions | 4.4. Performance Measurement Functions | |||
| Performance measurement functions involve measuring of packet loss, | Performance measurement functions involve measuring of packet loss, | |||
| delay, delay variance, etc. These performance metrics may be | delay, delay variance, etc. These performance metrics may be | |||
| End of changes. 3 change blocks. | ||||
| 3 lines changed or deleted | 3 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/ | ||||