rfc9551v2.txt | rfc9551.txt | |||
---|---|---|---|---|
skipping to change at line 193 ¶ | skipping to change at line 193 ¶ | |||
On-path telemetry: on-path telemetry can be realized as a hybrid OAM | On-path telemetry: on-path telemetry can be realized as a hybrid OAM | |||
method. The origination of the telemetry information is | method. The origination of the telemetry information is | |||
inherently in band as packets in a DetNet flow are used as | inherently in band as packets in a DetNet flow are used as | |||
triggers. Collection of the on-path telemetry information can be | triggers. Collection of the on-path telemetry information can be | |||
performed using in-band or out-of-band OAM methods. | performed using in-band or out-of-band OAM methods. | |||
1.2. Requirements Language | 1.2. Requirements Language | |||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
"OPTIONAL" in this document are to be interpreted as described in BCP | "OPTIONAL" in this document are to be interpreted as described in | |||
14 [RFC2119] [RFC8174] when, and only when, they appear in all | BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all | |||
capitals, as shown here. The requirements language is used in | capitals, as shown here. The requirements language is used in | |||
Sections 1.1 and 6, and applies to the implementations of DetNet OAM. | Sections 1.1 and 6, and applies to the implementations of DetNet OAM. | |||
2. Role of OAM in DetNet | 2. Role of OAM in DetNet | |||
DetNet networks are expected to provide communications with | DetNet networks are expected to provide communications with | |||
predictable low packet delay, packet loss, and packet misordering. | predictable low packet delay, packet loss, and packet misordering. | |||
Most critical applications will define a set of SLOs to be required | Most critical applications will define a set of SLOs to be required | |||
for the DetNet flows they generate. | for the DetNet flows they generate. | |||
skipping to change at line 558 ¶ | skipping to change at line 558 ¶ | |||
3. the monitoring of levels of resources allocated for a particular | 3. the monitoring of levels of resources allocated for a particular | |||
DetNet flow. Such resources include, but are not limited to, | DetNet flow. Such resources include, but are not limited to, | |||
buffer utilization and scheduler transmission calendar. | buffer utilization and scheduler transmission calendar. | |||
4. the monitoring of any subset of paths traversed through the | 4. the monitoring of any subset of paths traversed through the | |||
DetNet domain by a DetNet flow. | DetNet domain by a DetNet flow. | |||
6.2. For the DetNet Service Sub-layer | 6.2. For the DetNet Service Sub-layer | |||
The OAM functions for the DetNet service sub-layer allow, for | The OAM functions for the DetNet service sub-layer allow, for | |||
example, the recognization/discovery of DetNet relay nodes, the | example, the recognizing/discovery of DetNet relay nodes, the | |||
gathering of information about their configuration, and the checking | gathering of information about their configuration, and the checking | |||
of their operation or status. | of their operation or status. | |||
The requirements on OAM for a DetNet relay node are that DetNet OAM | The requirements on OAM for a DetNet relay node are that DetNet OAM | |||
MUST: | MUST: | |||
1. provide OAM functions for the DetNet service sub-layer. | 1. provide OAM functions for the DetNet service sub-layer. | |||
2. support the discovery of DetNet relay nodes in a DetNet network. | 2. support the discovery of DetNet relay nodes in a DetNet network. | |||
End of changes. 2 change blocks. | ||||
3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |