From nobody Tue Jun 21 01:55:36 2022 Return-Path: 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 AB101C15AAC1; Tue, 21 Jun 2022 01:55:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.107 X-Spam-Level: X-Spam-Status: No, score=-2.107 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_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 1aXqn8kCTqGH; Tue, 21 Jun 2022 01:55:31 -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 1DE29C14CF17; Tue, 21 Jun 2022 01:55:30 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id 654C125A12; Tue, 21 Jun 2022 10:55:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1655801728; bh=QGeGzMVs10VisIjOa5Ym03KJpWvUmuOVIWISUK66dww=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=kJpIowpYTLRohogqpJgJBQtHiNPs04EZ73QVNxdAagWFzDgBRePr0i3Mh+Ulxokhh 8r6kjDnisxcVUky7Crw9KS12q00stvh7tyffyBIf0AEqE9ar8KloaTyZ6j6P3KYzZt LcAExaLSnSSF8e2DstxS3lRHcrCoZ4x20SUDVoms= 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 QFCTk47_zNXr; Tue, 21 Jun 2022 10:55:27 +0200 (CEST) Received: from rznt8201.rznt.rzdir.fht-esslingen.de (rznt8201.hs-esslingen.de [134.108.48.164]) (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; Tue, 21 Jun 2022 10:55:27 +0200 (CEST) Received: from rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) by rznt8201.rznt.rzdir.fht-esslingen.de (134.108.48.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.28; Tue, 21 Jun 2022 10:55:26 +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; Tue, 21 Jun 2022 10:55:26 +0200 From: "Scharf, Michael" To: "mohamed.boucadair@orange.com" , "tcpm@ietf.org" CC: "draft-ietf-tcpm-yang-tcp@ietf.org" Thread-Topic: New version for draft-ietf-tcpm-yang-tcp Thread-Index: AdiCLH1yise0HqoiTvCeXoZROecjyQAH2RTwAMAs1uA= Date: Tue, 21 Jun 2022 08:55:26 +0000 Message-ID: <318a409943a043f6b38845f8a1e5e66f@hs-esslingen.de> References: <6ae1d1b1af4043b6a58eae693f1a0e42@hs-esslingen.de> <24504_1655471646_62AC7E1D_24504_349_1_92bed847176447d3a09c1e60de526b28@orange.com> In-Reply-To: <24504_1655471646_62AC7E1D_24504_349_1_92bed847176447d3a09c1e60de526b28@orange.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-06-17T13:12:43Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=b7ff76f0-1255-4e8c-bfb3-dc96bb3ede4b; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0 x-originating-ip: [134.108.140.249] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [tcpm] New version for draft-ietf-tcpm-yang-tcp X-BeenThere: tcpm@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: TCP Maintenance and Minor Extensions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2022 08:55:35 -0000 Hi Med, Thanks. I have noted that comment and suggest to fix it in -08. Michael > -----Original Message----- > From: mohamed.boucadair@orange.com > > Sent: Friday, June 17, 2022 3:14 PM > To: Scharf, Michael ; tcpm@ietf.org > Cc: draft-ietf-tcpm-yang-tcp@ietf.org > Subject: RE: New version for draft-ietf-tcpm-yang-tcp >=20 > Hi Michael, >=20 > I have one minor comment: >=20 > OLD: > The value > should be unknown (0) if connection initiations > to all local IP addresses are accepted."; >=20 > NEW: > The value > should be unspecified (0) if connection initiations > to all local IP addresses are accepted."; >=20 > (there is another occurrence of "unknown (0)" that should be fixed as wel= l) >=20 > Thank you. >=20 > Cheers, > Med >=20 > > -----Message d'origine----- > > De=A0: tcpm De la part de Scharf, Michael > > Envoy=E9=A0: vendredi 17 juin 2022 11:46 > > =C0=A0: tcpm@ietf.org > > Cc=A0: draft-ietf-tcpm-yang-tcp@ietf.org > > Objet=A0: [tcpm] New version for draft-ietf-tcpm-yang-tcp > > > > Hi all, > > > > The authors have published a new version -07 of draft-ietf-tcpm- > > yang-tcp. The long delay was mostly my fault, as my teaching day > > job keeps me busy. > > > > draft-ietf-tcpm-yang-tcp got quite some comments during IETF last > > call. In addition to directorate reviews, there were also further > > comments (see the TCPM list archive). As a result, -07 includes a > > number of changes. The diff can be seen at: > > > > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tcpm-yang-tcp-07 > > > > I'd like to highlight several changes that may be relevant to > > TCPM: > > > > 1/ There was a request to better align with the TCP MIB. We have > > not fully followed that request given TCPM decided against that in > > the past. Nonetheless, we have added the TCP connection state to > > the connection list similar to the TCP MIB. The state description > > follows 793bis. One specific question is whether it actually makes > > sense to have a state "closed". For -07, we have decided to model > > the state "closed". > > > > 2/ The TCP MIB includes a TCP listener table. We have added a > > corresponding list in -07. This again raises some subtle > > questions, most notably, how to model a TCP listener that accepts > > connections on any IPv4 and IPv6 address. The model in -07 allows > > this > > > > 3/ The modeling of TCP-AO authentication parameters has changed. > > The TCP-AO configuration has been moved to the key-chain, i.e., > > the TCP model now augments the YANG model in RFC 8177. This should > > better align with running code. As far as we know, all router > > operating systems configure TCP-AO via the key-chain. The model > > now follows that approach, too. > > > > Please let us know if there are any comments regarding the new > > version -07. It is possible that a follow-up -08 may be needed > > soon-ish. > > > > Thanks > > > > Michael > > > > > > -----Original Message----- > > From: tcpm On Behalf Of internet- > > drafts@ietf.org > > Sent: Thursday, June 16, 2022 6:03 PM > > To: i-d-announce@ietf.org > > Cc: tcpm@ietf.org > > Subject: [tcpm] I-D Action: draft-ietf-tcpm-yang-tcp-07.txt > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > This draft is a work item of the TCP Maintenance and Minor > > Extensions WG of the IETF. > > > > Title : A YANG Model for Transmission Control > > Protocol (TCP) Configuration and State > > Authors : Michael Scharf > > Mahesh Jethanandani > > Vishal Murgai > > Filename : draft-ietf-tcpm-yang-tcp-07.txt > > Pages : 28 > > Date : 2022-06-16 > > > > Abstract: > > This document specifies a minimal YANG model for TCP on devices > > that > > are configured and managed 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 IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-tcpm-yang-tcp/ > > > > There is also an htmlized version available at: > > https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-yang-tcp-07 > > > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tcpm-yang-tcp-07 > > > > > > Internet-Drafts are also available by rsync at > > rsync.ietf.org::internet-drafts > > > > > > _______________________________________________ > > 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 >=20 > __________________________________________________________ > __________________________________________________________ > _____ >=20 > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re= cu ce > message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme o= u > falsifie. Merci. >=20 > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and de= lete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have bee= n > modified, changed or falsified. > Thank you.