IETF Logo Mail Archive

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

Gyan Mishra <hayabusagsm@gmail.com> Tue, 25 October 2022 02:40 UTC

Return-Path: <hayabusagsm@gmail.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 1532EC14F72A; Mon, 24 Oct 2022 19:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 orxpFJ9q-lfJ; Mon, 24 Oct 2022 19:40:40 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AAD5C14F732; Mon, 24 Oct 2022 19:40:34 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id g16so6807868qtu.2; Mon, 24 Oct 2022 19:40:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hNGp2kbQeLmModdQi+BaDbLtDqN0BsA5nHfbBQICS/0=; b=qXSAqFwcaT4T7HvXrTXLxZecxyFnMyAZHaGoMEzybDl7hhmQZ2g8y/rwQdcLqYIzfx /xZUmAUg3t3uehns6NRBDqHCRx0TMp65pOKeDffLyz+nUTaJx7N9bWDZ0uXA2R5UeyBz VQzieTnSfpyb644Gu5ndiNbRFq8QOTyMisY3eITsCSDKDcCSjL6ed0hA5DY4RofBar6f EMfF5Mhjl6KYcGJcZsRaOMcntXHpuq1x3PR+NqH4ERteqYX8y01gfpUIPY07pQEA9U63 CvH4zhmehSAa4qUGtISD6YFGAFalivU0TEVy5d6+RWu/dB973lyY5k9E2qxW4g8PbNRc KVZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hNGp2kbQeLmModdQi+BaDbLtDqN0BsA5nHfbBQICS/0=; b=rjPMKp1fBkyxTKYqHh3u7mN7UR3mdipQdULlL0st5UETtaU+qY81muED+cKYqHv63v DhTfd90XGozVrXB0wP4ObORo+tfVi10bsUv8Y4fioRVnAx0GOfnIs31RZknHJJZeW0FS nw7D4ea1MvzZVdD8i/UXSFyzPeA607NCHLQzpCS6fs7NikZosi2Qs70KLl0icKRjplh0 WaR+CDUx8WwzJEj+P1NmA8wgVAVw9dPMJE2kZu4qZKsDqneB37IDcDJsZ+c7qJv2D/C5 BoS4MYSGaZYJeFGOwGWsa9b9H1qPq4T3zVgfGxJbRGPEhNOxPVd8JMDwFCHcjhqEs4DJ TrWw==
X-Gm-Message-State: ACrzQf3l2M/p8rpcVq0I0u59WFVDC/0NhlM/mUngAht85yAmB3SJuTrg JZ1FR6ufp7bd2r1uVnbvX4NtAe5wXObKyKhzdS4=
X-Google-Smtp-Source: AMsMyM7U/AyPPAKI/2NRKQNtj/n9t8nE0S10JR4cblsSUmJQ9bVn2fMGXlxvxE3HFB/x6tRXN04It1YqbuQqphvFoAM=
X-Received: by 2002:ac8:5f82:0:b0:39c:dd06:ff45 with SMTP id j2-20020ac85f82000000b0039cdd06ff45mr29982402qta.93.1666665633488; Mon, 24 Oct 2022 19:40:33 -0700 (PDT)
MIME-Version: 1.0
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> <C5C5ACD6-DF8F-4E61-93C8-73584721B9C4@pfrc.org>
In-Reply-To: <C5C5ACD6-DF8F-4E61-93C8-73584721B9C4@pfrc.org>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 24 Oct 2022 22:40:22 -0400
Message-ID: <CABNhwV0Gzbq=Pto8ssnocGg5RfmDzMANpSRcLwFE_ziJBtFVLA@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Camilo Cardona <camilo@gin.ntt.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>, "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>, "grow@ietf.org" <grow@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000b22be05ebd2d5f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/IXwl5zuet38X0HxszMv_RhV9G_E>
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, 25 Oct 2022 02:40:45 -0000

Hi Jeff

It sounds like everything is addressed in the TCP Yang model so we don’t
need new NG TCP model as we had discussed during my IETF 114 presentation.

Just want to close the loop on that topic.

Thank you

Gyan

On Mon, Sep 5, 2022 at 3:08 PM Jeffrey Haas <jhaas@pfrc.org> wrote:

> 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, 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
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*

v2.23.0 | Report a Bug | By Email