rfc9359v3.txt | rfc9359.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) X. Min | Internet Engineering Task Force (IETF) X. Min | |||
Request for Comments: 9359 ZTE Corp. | Request for Comments: 9359 ZTE Corp. | |||
Category: Standards Track G. Mirsky | Category: Standards Track G. Mirsky | |||
ISSN: 2070-1721 Ericsson | ISSN: 2070-1721 Ericsson | |||
L. Bo | L. Bo | |||
China Telecom | China Telecom | |||
March 2023 | April 2023 | |||
Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities | Echo Request/Reply for Enabled In Situ OAM (IOAM) Capabilities | |||
Abstract | Abstract | |||
This document describes a generic format for use in echo request/ | This document describes a generic format for use in echo request/ | |||
reply mechanisms, which can be used within an IOAM-Domain, allowing | reply mechanisms, which can be used within an IOAM-Domain, allowing | |||
the IOAM encapsulating node to discover the enabled IOAM capabilities | the IOAM encapsulating node to discover the enabled IOAM capabilities | |||
of each IOAM transit and IOAM decapsulating node. The generic format | of each IOAM transit and IOAM decapsulating node. The generic format | |||
is intended to be used with a variety of data planes such as IPv6, | is intended to be used with a variety of data planes such as IPv6, | |||
skipping to change at line 684 ¶ | skipping to change at line 684 ¶ | |||
| 0b00 | 64-bit "PktID" and 64-bit "Cumulative" data | | | 0b00 | 64-bit "PktID" and 64-bit "Cumulative" data | | |||
+------+---------------------------------------------+ | +------+---------------------------------------------+ | |||
Table 1: SoP and Description | Table 1: SoP and Description | |||
0b01 - 0b11 are available for assignment via the IETF Review process | 0b01 - 0b11 are available for assignment via the IETF Review process | |||
as per [RFC8126]. | as per [RFC8126]. | |||
5.2. IOAM TSF Capability Registry | 5.2. IOAM TSF Capability Registry | |||
This registry defines four code points for the IOAM TSF Capability | This registry defines four codepoints for the IOAM TSF Capability | |||
field for identifying the timestamp format as explained in Section 5 | field for identifying the timestamp format as explained in Section 5 | |||
of [RFC9197]. | of [RFC9197]. | |||
A new entry in this registry requires the following fields: | A new entry in this registry requires the following fields: | |||
* TSF (TimeStamp Format): a 2-bit binary field as defined in | * TSF (TimeStamp Format): a 2-bit binary field as defined in | |||
Section 3.2.4. | Section 3.2.4. | |||
* Description: a terse description of the meaning of this TSF value. | * Description: a terse description of the meaning of this TSF value. | |||
skipping to change at line 806 ¶ | skipping to change at line 806 ¶ | |||
Nainar, N. K., Pignataro, C., Akiya, N., Zheng, L., Chen, | Nainar, N. K., Pignataro, C., Akiya, N., Zheng, L., Chen, | |||
M., and G. Mirsky, "BIER Ping and Trace", Work in | M., and G. Mirsky, "BIER Ping and Trace", Work in | |||
Progress, Internet-Draft, draft-ietf-bier-ping-08, 6 March | Progress, Internet-Draft, draft-ietf-bier-ping-08, 6 March | |||
2023, <https://datatracker.ietf.org/doc/html/draft-ietf- | 2023, <https://datatracker.ietf.org/doc/html/draft-ietf- | |||
bier-ping-08>. | bier-ping-08>. | |||
[OAM-for-SFC] | [OAM-for-SFC] | |||
Mirsky, G., Meng, W., Ao, T., Khasnabish, B., Leung, K., | Mirsky, G., Meng, W., Ao, T., Khasnabish, B., Leung, K., | |||
and G. Mishra, "Active OAM for Service Function Chaining | and G. Mishra, "Active OAM for Service Function Chaining | |||
(SFC)", Work in Progress, Internet-Draft, draft-ietf-sfc- | (SFC)", Work in Progress, Internet-Draft, draft-ietf-sfc- | |||
multi-layer-oam-22, 25 July 2022, | multi-layer-oam-23, 23 March 2023, | |||
<https://datatracker.ietf.org/doc/html/draft-ietf-sfc- | <https://datatracker.ietf.org/doc/html/draft-ietf-sfc- | |||
multi-layer-oam-22>. | multi-layer-oam-23>. | |||
[RFC4302] Kent, S., "IP Authentication Header", RFC 4302, | [RFC4302] Kent, S., "IP Authentication Header", RFC 4302, | |||
DOI 10.17487/RFC4302, December 2005, | DOI 10.17487/RFC4302, December 2005, | |||
<https://www.rfc-editor.org/info/rfc4302>. | <https://www.rfc-editor.org/info/rfc4302>. | |||
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", | [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", | |||
RFC 4303, DOI 10.17487/RFC4303, December 2005, | RFC 4303, DOI 10.17487/RFC4303, December 2005, | |||
<https://www.rfc-editor.org/info/rfc4303>. | <https://www.rfc-editor.org/info/rfc4303>. | |||
[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet | [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet | |||
End of changes. 4 change blocks. | ||||
4 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |