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

Jeffrey Haas <jhaas@pfrc.org> Mon, 05 September 2022 19:08 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 B28F8C1526EC; Mon, 5 Sep 2022 12:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 KUszvTNjWwQb; Mon, 5 Sep 2022 12:08:12 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 95AFFC14CE2E; Mon, 5 Sep 2022 12:08:11 -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 A24001E31E; Mon, 5 Sep 2022 15:08:09 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5177DF97-50D0-4157-8AC6-5993CE888CFC"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <e88b57ef02984116bf96da85b606b3bb@hs-esslingen.de>
Date: Mon, 05 Sep 2022 15:08:08 -0400
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, 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: <C5C5ACD6-DF8F-4E61-93C8-73584721B9C4@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> <E2EC0EAB-3F24-426A-A6C7-85BD0961538D@pfrc.org> <e88b57ef02984116bf96da85b606b3bb@hs-esslingen.de>
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/DND0YSasOEwegGutdoFKn6zSgGc>
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: Mon, 05 Sep 2022 19:08:16 -0000

Michael,


> On Sep 5, 2022, at 4:52 AM, Scharf, Michael <Michael.Scharf@hs-esslingen.de> wrote:
> The authors have published version -08 to address feedback from various reviewers, including your one.
>  
> As you can see at the page https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-yang-tcp-08 <https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-yang-tcp-08>, we added a typedef for MSS and leafs for MSS and PMTUD. Please review this change and let us know if this works for you.

Those changes address my comments.  Thanks!

> We have _not_ added further nodes, as the use case is not clear and there has been no specific suggestion how the draft should be updated. As mentioned before, this document does not try to comprehensively model all potential parameters of a TCP stack. 

It's YANG.  Unlike MIBs, as long as the structure is well-designed, it can be extended later to address deficiencies.

Thanks for the work.

-- Jeff