Re: [tcpm] Last Call: <draft-ietf-tcpm-yang-tcp-06.txt> (A YANG Model for Transmission Control Protocol (TCP) Configuration) to Proposed Standard

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Fri, 17 June 2022 09:02 UTC

Return-Path: <Michael.Scharf@hs-esslingen.de>
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 55CF0C1527AF; Fri, 17 Jun 2022 02:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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_NONE=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hs-esslingen.de
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 rlVFNPvzXLDy; Fri, 17 Jun 2022 02:02:01 -0700 (PDT)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de [134.108.32.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E48B3C14F726; Fri, 17 Jun 2022 02:02:00 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id 8295725A30; Fri, 17 Jun 2022 11:01:57 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1655456517; bh=MEX4WKhiZXcyhefwmJUmp7ZvjVDOAVjJVtUC+rnzuUU=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=GqG5qtdtYNujcyESx1L/+HNUooO/OX+3XgBcFxwC0ux90iFpciqTP4kD1IuZGsMIH ILIUefbJYNrQM7dtk/1lzlTdX7za+nNQCL4631TXn5ff9GWwG69l1YWmCPfg7u7Acp Drg5imzDCC76W11idZmu8dGddtDdyBPQhyVR7G/Y=
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([127.0.0.1]) by localhost (hs-esslingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WB7UJ0gWJS1m; Fri, 17 Jun 2022 11:01:56 +0200 (CEST)
Received: from rznt8202.rznt.rzdir.fht-esslingen.de (rznt8202.hs-esslingen.de [134.108.48.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Fri, 17 Jun 2022 11:01:56 +0200 (CEST)
Received: from rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) by rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.28; Fri, 17 Jun 2022 11:01:41 +0200
Received: from rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0]) by rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0%3]) with mapi id 15.01.2375.028; Fri, 17 Jun 2022 11:01:41 +0200
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: t petch <ietfa@btconnect.com>, "last-call@ietf.org" <last-call@ietf.org>
CC: "draft-ietf-tcpm-yang-tcp@ietf.org" <draft-ietf-tcpm-yang-tcp@ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>, "tcpm-chairs@ietf.org" <tcpm-chairs@ietf.org>
Thread-Topic: [tcpm] Last Call: <draft-ietf-tcpm-yang-tcp-06.txt> (A YANG Model for Transmission Control Protocol (TCP) Configuration) to Proposed Standard
Thread-Index: AQHYI4aM9TTmAH1uo0S0YW8r6/bX8ayr4N0AgKgnSVA=
Date: Fri, 17 Jun 2022 09:01:41 +0000
Message-ID: <fb2e840b518940e58c381859a13467b2@hs-esslingen.de>
References: <164505133983.5800.270812007978080248@ietfa.amsl.com> <621F403A.3060209@btconnect.com>
In-Reply-To: <621F403A.3060209@btconnect.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.108.140.249]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/Zy5TiUr6NmuokxTv0P8nYd5HLDU>
Subject: Re: [tcpm] Last Call: <draft-ietf-tcpm-yang-tcp-06.txt> (A YANG Model for Transmission Control Protocol (TCP) Configuration) to Proposed Standard
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: Fri, 17 Jun 2022 09:02:05 -0000

Hi Tom,

Many thanks for again reading this draft. These are all good catches.

We have addressed all points noted below in the new version -07, except for one comment:

We have kept in -07 the IP address modeling that includes the zone. My own understand so far is that the models with the zone are the default in many YANG models. As a result, we probably need a reason not to allow a zone in draft-ietf-tcpm-yang-tcp. Allowing it seems a more conservative approach, and therefore we have not changed this in -07. Yet, further feedback on the use of the zone would really be welcome.

Version -07 tries to address also other IETF last call reviews and thus includes several changes. Please have a look at the new version (https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-yang-tcp-07) or the diff (https://www.ietf.org/rfcdiff?url2=draft-ietf-tcpm-yang-tcp-07) and let us know if more is needed.

Best regards

Michael

> -----Original Message-----
> From: t petch <ietfa@btconnect.com>
> Sent: Wednesday, March 2, 2022 11:00 AM
> To: last-call@ietf.org
> Cc: draft-ietf-tcpm-yang-tcp@ietf.org; tcpm@ietf.org; tcpm-chairs@ietf.org
> Subject: Re: [tcpm] Last Call: <draft-ietf-tcpm-yang-tcp-06.txt> (A YANG
> Model for Transmission Control Protocol (TCP) Configuration) to Proposed
> Standard
> 
> On 16/02/2022 22:42, The IESG wrote:
> >
> > The IESG has received a request from the TCP Maintenance and Minor
> Extensions
> > WG (tcpm) to consider the following document: - 'A YANG Model for
> > Transmission Control Protocol (TCP) Configuration'
> 
> Some stray thoughts.
> 
> All the IP address objects use the format that includes the zone; is
> this intended?
> 
> You mention the i2nsf-capability-data-model as an example of modelling
> TCP.  i2nsf-nsf-facing could be another.
> 
> The TLP in the YANG module is out of date (like the Copyright date).
> 
> The example uses port 80 which is traditionally insecure.  A secure port
> might set a better example.
> 
> Tom Petch
> 
> >    <draft-ietf-tcpm-yang-tcp-06.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits final
> > comments on this action. Please send substantive comments to the
> > last-call@ietf.org mailing lists by 2022-03-02. Exceptionally, comments may
> > be sent to iesg@ietf.org instead. In either case, please retain the beginning
> > of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >     This document specifies a minimal YANG model for TCP on devices that
> >     are configured by network management protocols.  The YANG model
> >     defines a container for all TCP connections and groupings of
> >     authentication parameters that can be imported and used in TCP
> >     implementations or by other models that need to configure TCP
> >     parameters.  The model also includes basic TCP statistics.  The model
> >     is compliant with Network Management Datastore Architecture (NMDA)
> >     (RFC 8342).
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-tcpm-yang-tcp/
> >
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
> >
> >
> > _______________________________________________
> > tcpm mailing list
> > tcpm@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcpm
> > .
> >