Re: [tcpm] [GROW] How to reuse the tcp model in the BMP model - asking for suggestions

Jeffrey Haas <jhaas@pfrc.org> Tue, 23 August 2022 19:46 UTC

Return-Path: <jhaas@pfrc.org>
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 CF9C6C14CF15; Tue, 23 Aug 2022 12:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 Q_QQ23F2hLMe; Tue, 23 Aug 2022 12:46:43 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 35E7CC14F73F; Tue, 23 Aug 2022 12:46:42 -0700 (PDT)
Received: from smtpclient.apple (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 314C61E31E; Tue, 23 Aug 2022 15:46:41 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_CA5E2B99-F318-4DCB-8BDA-0F691A1E6809"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <C20B8AFF-9C51-4102-8D55-3FD900DE8938@gmail.com>
Date: Tue, 23 Aug 2022 15:46:40 -0400
Cc: Michael SCHARF <Michael.Scharf@hs-esslingen.de>, Camilo Cardona <camilo@gin.ntt.net>, "draft-ietf-tcpm-yang-tcp.authors@ietf.org" <draft-ietf-tcpm-yang-tcp.authors@ietf.org>, "draft-ietf-tcpm-yang-tcp@ietf.org" <draft-ietf-tcpm-yang-tcp@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Message-Id: <E2EC0EAB-3F24-426A-A6C7-85BD0961538D@pfrc.org>
References: <39BBD72C-808D-45CF-B832-9EF786F45F06@gin.ntt.net> <a8e7d4449ded44cd805f2a20f75b14e8@hs-esslingen.de> <7F96BC15-66B6-4F6B-9B68-AC59FAA0FF39@gin.ntt.net> <3577f12509e949a49ba9494c4f9bb1d7@hs-esslingen.de> <20220725181224.GC14067@pfrc.org> <73CA533F-0911-4A4A-9FF2-21377E3185F4@gin.ntt.net> <47bee885617e4694a6735b80aea9d352@hs-esslingen.de> <20220809145355.GA26219@pfrc.org> <3d87ff887dc74f26b011acc31ac967be@hs-esslingen.de> <20220822160754.GA14484@pfrc.org> <C20B8AFF-9C51-4102-8D55-3FD900DE8938@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/6x64pFpUgxvwa2_Ex7Kc-4rCeik>
Subject: Re: [tcpm] [GROW] How to reuse the tcp model in the BMP model - asking for suggestions
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: Tue, 23 Aug 2022 19:46:44 -0000

Mahesh,

> On Aug 23, 2022, at 3:03 PM, Mahesh Jethanandani <mjethanandani@gmail.com> wrote:
> 
>>> In addition, I have now also checked the OpenConfig YANG models, and they also have ways to set the MSS, for instance:
>>> 
>>>    leaf tcp-mss {
>>>      type uint16;
>>>      description
>>>        "Sets the max segment size for BGP TCP sessions.";
>>>    }
>> 
>> An example above, where a typedef for the uint16 might be helpful.
> 
> Not clear on why you would like to see a typedef rather than a definition for MSS node as suggested by Michael. Or did you mean to put a range for the MSS value?

For individual instances implementing the MSS, you'll want a leaf.

The purpose of a typedef is having each of the places where MSS configuration or operational state is used have a consistent type/constraint and perhaps pointer into the TCP specs.

That way, as a theoretical example, you don't define MSS in one model as uint16 and another as uint32 with a range restriction - which might be how someone's implementation does it.

-- Jeff