This read-write enable/disable object controls whether this device requests the tunnel peer to flow control its transmissions on a per-session basis, noting this feature was part of draft L2TP specifications rather than the final RFC and should only be enabled if all peers use draft-compliant implementations, and regardless of setting, a peer's own flow-control request is always honored. An admin enables this only in a controlled environment where every L2TP peer is known to be running compatible draft-era software. For example, mixing this enabled with a fully RFC-compliant peer that doesn't understand the draft flow-control mechanism could cause interoperability problems, so an admin would leave it disabled in a standard mixed-vendor deployment.