Re: [tcpm] [Last-Call] Opsdir telechat review of draft-ietf-tcpm-yang-tcp-07

"" <> Mon, 04 July 2022 19:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 539C4C157903; Mon, 4 Jul 2022 12:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.325
X-Spam-Status: No, score=-1.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Qw2OfKFu5U9X; Mon, 4 Jul 2022 12:30:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 50F66C14F735; Mon, 4 Jul 2022 12:30:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4VoeGURyNQPaFlVap255qYCqV+qetq1/47PfRvdx8Uc=; b=PlAn3w/BtyM65qofZtNg2ytHl/ 3Ztz7koLhrBgGrprXqWPNfhzVhDkQWVqJF0znYed/Iojqyv6QOqQAwtG5mGMGQsPtR22yQaj6lelt xS4Lqy/7lWGYOYxoIDri4Rl3DtMY1GsKmawKC+IMbIKWWYH2+4NRuTjLKF3WpKIk1kt9XJfY46Y57 cAUsKjoBynNtTJpGBbdAQcy/Kzyiq1ky0lOtjvmpZkXWKgf0UvprdCFNXC1stzBtEaqdoIiXsmgHM v0FIK3UIWNPgGVURk3kK/ilLLSvM1MX6Wlujck0LxZycxuTmVqrMdYw0k1cOcfF84sSdo0Xbz41k0 6zVmfNOg==;
Received: from ([]:58093 by with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <>) id 1o8Rlf-002Zod-0r; Mon, 04 Jul 2022 15:30:03 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: "" <>
In-Reply-To: <>
Date: Mon, 04 Jul 2022 12:29:57 -0700
Cc: "Scharf, Michael" <>, Gyan Mishra <>, Last Call <>, "" <>, "" <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <>
To: Robert Raszuk <>
X-Mailer: Apple Mail (2.3696.100.31)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-Get-Message-Sender-Via: authenticated_id:
X-From-Rewrite: unmodified, already matched
Archived-At: <>
Subject: Re: [tcpm] [Last-Call] Opsdir telechat review of draft-ietf-tcpm-yang-tcp-07
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Jul 2022 19:30:08 -0000

> On Jul 4, 2022, at 12:15 PM, Robert Raszuk <> wrote:
> Hi,
> > Any application can decide to configure TCP parameters as far as possible in the given operation 
> > system, e.g., via the sockets API. That is orthogonal to the internals of the TCP implementation and the TCP protocol.
> While clients running on top of TCP can configure its parameters I would at least expect to be able to report such values (local and remote) when using the TCP YANG model. For example I can not find the Urgent Flag in the current YANG model.

That’s because URG is not a property of the TCP connection; it’s a property of a segment, not the connection. The same is true for PSH.

> Same for elementary window size of any given connection, same for connection duration, . 

There is no such thing as “elementary window size”. There are a variety of window parameters, i.e., send window, congestion window, receive window. Only the send and receive windows are application / OS set. 

If there’s a list of desired parameters, it would be useful to start by stating them in terms of the TCP specs and explaining why they need to be remotely managed.