rfc-7750

Differentiated Service Code Point and Explicit Congestion Notification Monitoring in the Two-Way Active Measurement Protocol (TWAMP)

J. Hedin, G. Mirsky, S. Baillargeon
date2016-02 streamIETF areaops wgippm statusPROPOSED STANDARD pages11 canonicalhttps://www.rfc-editor.org/rfc/rfc7750 doi10.17487/RFC7750
This document describes an optional extension for Two-Way Active Measurement Protocol (TWAMP) allowing the monitoring of the Differentiated Service Code Point and Explicit Congestion Notification fields with the TWAMP-Test protocol.

updates

Extracted elements (17)

design-rationale §2.2.1

If the provisioned DSCP value is not known (e.g., in TWAMP Light mode), the Session-Reflector MAY copy the DSCP from the received packet or MAY set it to CS0 (zero), leaving the choice implementation-specific because TWAMP Light lacks a TWAMP-Control synchronization mechanism.

measurement, diffserv

design-rationale §2.2.1

The Session-Reflector in DSCP and ECN Monitoring mode does not analyze or act on the ECN value of received test packets, ignoring congestion indications. This is justified because TWAMP deployment experience has shown sending rates are low enough that ignoring ECN will not significantly contribute to network congestion.

measurement, ecn, congestion

interoperability-note §2.2.2

Adding the S-DSCP-ECN field increases the unauthenticated Session-Reflector packet by 4 octets; implementations combining DSCP and ECN Monitoring with Symmetrical Size or Reflects Octets modes (RFC 6038) must account for this size increase in Padding Length calculations.

measurement, diffserv, ecn

interoperability-note §2.2.3

TWAMP Light mode (Appendix I of RFC 5357) does not explicitly state how the Type-P Descriptor is synchronized between Session-Sender and Session-Reflector; this extension assumes that both sides are configured by some means (e.g., CLI) to use the same DSCP value and to support DSCP and ECN Monitoring.

measurement, diffserv, ecn

normative-requirement §2.2.1 SHOULD

If the provisioned ECN value is not known, ECN SHOULD be set to the Not-ECT codepoint value; otherwise the provisioned ECN value for the session SHALL be used.

measurement, ecn

normative-requirement §2.1 MUST

The Control-Client MUST set the DSCP and ECN Monitoring flag in the Modes field of the Setup Response message if it agrees to monitor DSCP and ECN on some or all test sessions invoked with the control connection.

measurement, diffserv, ecn

normative-requirement §2.2.1 MUST

The Session-Reflector MUST extract the DSCP and ECN values from the received packet and MUST use them to populate the S-DSCP-ECN field of the corresponding reflected packet.

measurement, diffserv, ecn

normative-requirement §2.2.1 MUST

The Session-Reflector MUST transmit each reflected test packet with the DSCP set to the provisioned value, not to the received DSCP value.

measurement, diffserv

normative-requirement §2.2.1 MUST

The six least-significant bits of the Differentiated Service field MUST be copied from the received Session-Sender test packet into the Sender DSCP (S-DSCP) field, and the two ECN bits MUST be copied into the Sender ECN (S-ECN) field.

measurement, diffserv, ecn

normative-requirement §2.2.2 SHOULD

When DSCP and ECN Monitoring and Symmetrical Size and/or Reflects Octets modes are negotiated in unauthenticated mode, the Padding Length value SHOULD be greater than or equal to 28 octets to allow for the truncation process recommended in RFC 5357.

measurement, diffserv, ecn

protocol-element §2.1

The DSCP and ECN Monitoring feature uses a new flag (bit position 8) in the TWAMP-Modes field, negotiated during the Server Greeting and Setup Response exchange, to indicate capability and willingness to monitor DSCP and ECN values.

measurement, diffserv, ecn, registry

registry §3

IANA has allocated bit position 8 in the TWAMP-Modes registry (defined in RFC 5618) for the 'DSCP and ECN Monitoring Capability', with semantics defined in Section 2 of RFC 7750.

registry, measurement, diffserv, ecn

security-consideration §4

Monitoring of DSCP and ECN does not introduce additional security threats beyond those already present in TWAMP (RFC 5357) and its existing extensions (RFC 6038). The general security considerations for active measurement of live networks, as discussed in RFC 4656 and RFC 5357, apply.

security, measurement

wire-format §2.2.1

In authenticated and encrypted modes, the Session-Reflector test packet includes the S-DSCP-ECN field (1 octet) placed after the Sender TTL field, followed by 14 octets MBZ and a 16-octet HMAC, as shown in Figure 3.

measurement, diffserv, ecn, crypto

wire-format §2.2.1

In unauthenticated mode, the Session-Reflector test packet includes the S-DSCP-ECN field (1 octet) placed after the Sender TTL field, followed by MBZ padding, as shown in Figure 2.

measurement, diffserv, ecn

wire-format §2.2.1

The Sender DSCP and ECN (S-DSCP-ECN) field is an 8-bit field: bits 0-5 carry the S-DSCP (six least-significant bits of the DS field), and bits 6-7 carry the S-ECN (two ECN bits), as defined in Figure 1.

measurement, diffserv, ecn

wire-format §2.2.2

When DSCP and ECN Monitoring is combined with Symmetrical Size mode in unauthenticated mode, the Session-Sender test packet format uses 28 octets of MBZ (Figure 4) to accommodate the 4-octet increase from the S-DSCP-ECN field in the reflector packet.

measurement, diffserv, ecn