IETF Logo Mail Archive

Re: [tcpm] IETF 114 TCPM WG - NG TCPM Yang Model

"touch@strayalpha.com" <touch@strayalpha.com> Wed, 27 July 2022 02:19 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AAC2C14F729 for <tcpm@ietfa.amsl.com>; Tue, 26 Jul 2022 19:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.329
X-Spam-Level:
X-Spam-Status: No, score=-1.329 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, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ItO1BcZOBLZq for <tcpm@ietfa.amsl.com>; Tue, 26 Jul 2022 19:19:51 -0700 (PDT)
Received: from server217-2.web-hosting.com (server217-2.web-hosting.com [198.54.115.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1370C13CCFC for <tcpm@ietf.org>; Tue, 26 Jul 2022 19:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; 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=cs5Gg9IdOhgCnV2Cyz3ex91doP0CuOoUE9lACckXKHQ=; b=p2f0awe655hFeFSfNDYj+LYocz sBjMPl6B0rN5m9WUOS8TJDCgaiX6J+kRbKsyUu10tPFyyEOj3WkPgqJ8hu/ra5l4Nj6PVL0h++ljc BM2BhpA61DAuAaGbohiPpelV3w2m1mPr5eLBSGYjm2VOxJBw07FyP9Uq3gZ3R2/cP6mrJ5ej+sASM lztwoROr/GRZ7PuLzkgM26u2o4MByp0pfcCUQVL64XSkY96/5KEj7fMXP/wirVOdQVSACjE29H2Lt eg7OWU7R+yUxe41piJOaF8krhlYzsd/bZ86V+/b7ZuTgpLHCYg1Yi2jMs4iVI19Mbikk63PNNv3Jg 1ruZqqIg==;
Received: from c-73-29-228-215.hsd1.nj.comcast.net ([73.29.228.215]:51090 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <touch@strayalpha.com>) id 1oGWYF-0098am-5O; Tue, 26 Jul 2022 22:13:36 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <A8851A57-748D-4504-97B6-677807EE0DB6@lurchi.franken.de>
Date: Tue, 26 Jul 2022 22:13:27 -0400
Cc: Gyan Mishra <hayabusagsm@gmail.com>, tcpm IETF list <tcpm@ietf.org>, Robert Raszuk <robert@raszuk.net>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>, Jeffrey Haas <jhaas@pfrc.org>, Susan Hares <shares@ndzh.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF72E595-0B1E-4AD9-BDFE-603B9B200F0D@strayalpha.com>
References: <CAJhXr9-zcJg99ML3MSNMTvRFiT_BLzJihQucAdX8MZGDZ84dWw@mail.gmail.com> <CABNhwV1wz2Uhx+DWjabzVz8GAhQD78NFKhq2az=E7dhnxTC-Ww@mail.gmail.com> <A8851A57-748D-4504-97B6-677807EE0DB6@lurchi.franken.de>
To: Michael Tuexen <michael.tuexen@lurchi.franken.de>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/BFmxK56LqzFLi-YT08W9onphBN0>
Subject: Re: [tcpm] IETF 114 TCPM WG - NG TCPM Yang Model
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2022 02:19:55 -0000

Notes below.

> On Jul 26, 2022, at 6:19 PM, Michael Tuexen <michael.tuexen@lurchi.franken.de> wrote:
> 
>> 
>> 
>> Dear TCPM
>> 
>> Attached is the slide deck for the NG TCP Yang model discussion.
>> 
>> Sue, Robert, Jeff, Gunter 
>> 
>> Please review and let me know if I missed any talking points for the NG TCP Yang model.
> A couple of clarifying questions related to slide "What to add to NG TCP Yang Model?",
> especially since I know almost nothing about YANG:
> 
> • All TCP states part of the FSM state machine.
> Understood.

These make sense.

> • All TCP flags and respective states.
> Do you mean the TCP flags SYN, FIN, PSH, ... Does a YANG module all to describe
> packets sent and received?

I can’t see how this can model the TCP flags; all it should be modeling is the states of the connection. The model is for TCP, not TCP packets.

> • All TCP parameters that would be accessible with a local OS kernel hook.
> Doesn't that mean the complete set of state variable the kernel has and isn't that implementation dependent?
> • All windowing parameters including window scaling as well as any windowing related optimizations.
> You mean the receiver window including the window scaling.
> • All TCP options and optimizations set such as Selective ACK.
> I guess you mean the set of TCP extensions which have been negotiated.
> • All TCP slow start congestion control parameters CWIN etc.
> There are a multiple Congestion Controls, even ones not being specified by the IETF.
> So this might get very hard to do. Or do you require a specific CC when using TCP for BGP?

This is where things get confusing to me; it seems that there is either a model for TCP or a model for TCP implementations. The two should not be confused with each other

Joe

> 
> Best regards
> Michael
>> 
>> Thanks 
>> 
>> Gyan
>> 
>> ---------- Forwarded message ---------
>> From: Mishra, Gyan S <gyan.s.mishra@verizon.com>
>> Date: Mon, Jul 25, 2022 at 11:36 PM
>> Subject: IETF 114 TCPM WG - NG TCPM Yang Model
>> To: Hayabusanew <hayabusagsm@gmail.com>
>> 
>> 
>> -- 
>> 
>> 
>> Gyan Mishra
>> Network Solutions Architect 
>> Email gyan.s.mishra@verizon.com
>> M 301 502-1347
>> 
>> 
>> <IETF-114 TCPM TCP Yang Model.pdf>_______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm

v2.23.0 | Report a Bug | By Email