Re: [Idr] Request for feedback on WG adoption of draft-scharf-tcpm-yang-tcp-04

tom petch <ietfc@btconnect.com> Wed, 25 March 2020 12:52 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A5B3A094D; Wed, 25 Mar 2020 05:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.362
X-Spam-Level:
X-Spam-Status: No, score=-3.362 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-1.463, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMEOeTDa5Dxw; Wed, 25 Mar 2020 05:52:46 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2133.outbound.protection.outlook.com [40.107.20.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E7C33A0913; Wed, 25 Mar 2020 05:52:45 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=grOrotbid0T6DmaUTakhBnvPemIl2o4c3V3PqTYLEs3Ec4ImGTQsA8L1lNoPCahqRSRzJmwrUnYuv6epWCYlX0OhBarns4rrk4JMYnM/9IPsSmAUQz3IpmonhDcHwAyPndxJzv9GHNb9J0V5ON+19/NnD43/+fZc/splM5UyiW4XtKmSoqTkzgfHFB1+DDE/gwu8gMZsdUPf1RD01r98iqkpMO9KERIxdU4ZHoBN691wfq1PLBEeK8uv3A7ltRF7cm1vMgNrEnI0Mr/L6/O9SyupeN/fo48vZwL8iTptisOkAQlvNOfvTOM7ZFHVviKUwwZZn4ldvQiMet2Y+BBz6A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kafksONKk0yhSHBwlvifZjNrYa5UQwtbu9w2XC90PsQ=; b=GfDi/SFPhIN7ZKIm/g3lp8F1/1/6DBd+RhMyGJzSZsO06kfF5KjN3/RnbHskDNr4P6oUMKtakJI+Yg6n+fe3kJfT725sn+V3Mn2WSdNMK7lqkHHqwl9AaMB7NNWSQ1giC/NE/Oal2a6QHYcQpUCV5Dq4o9kxWP3PTAFBijrbRFmILY1KeN5V7XClrpL2f+iBNI2qR9/ciKDF3paaa0mz/LdIj5D7+5AxYh69O1JVZ5cguDW72Ck8wgGIAOaEluO99JCtrcBNUm2RaQD/t+7Nwqu8sn9B8DyC7OP69Bm4BpgQ6JHAintp8FDYKPdj0oYby/IIfErU6HxCxZYDdzXLvg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kafksONKk0yhSHBwlvifZjNrYa5UQwtbu9w2XC90PsQ=; b=WKGmuGyUMaHPq47QgXdzHF5QyZEPQyx8zZih1YWlr7vrzB/wtOa02X13hcWIoZV0VWCYikugo27jPDiHBdOPAufRdN0tUMAWEozcxxFOFZEtqFZfw2w1AzedWFF/Bc7lXWcsFOmuAbQp+tHjZoQkuIN6EtDw27rwC0lWW5fMT0o=
Received: from DB7PR07MB5657.eurprd07.prod.outlook.com (20.178.85.222) by DB7PR07MB4108.eurprd07.prod.outlook.com (52.134.101.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.15; Wed, 25 Mar 2020 12:52:43 +0000
Received: from DB7PR07MB5657.eurprd07.prod.outlook.com ([fe80::a438:bbc9:2ffe:33ee]) by DB7PR07MB5657.eurprd07.prod.outlook.com ([fe80::a438:bbc9:2ffe:33ee%5]) with mapi id 15.20.2856.018; Wed, 25 Mar 2020 12:52:43 +0000
From: tom petch <ietfc@btconnect.com>
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>, "idr@ietf.org" <idr@ietf.org>
CC: tcpm IETF list <tcpm@ietf.org>
Thread-Topic: Request for feedback on WG adoption of draft-scharf-tcpm-yang-tcp-04
Thread-Index: AdX9YZybm8xvduWhO0ywtFiDNCmPqgFQZ2TY
Date: Wed, 25 Mar 2020 12:52:42 +0000
Message-ID: <DB7PR07MB56572390579BC3AC083F152EA0CE0@DB7PR07MB5657.eurprd07.prod.outlook.com>
References: <6EC6417807D9754DA64F3087E2E2E03E2D9F11D2@rznt8114.rznt.rzdir.fht-esslingen.de>
In-Reply-To: <6EC6417807D9754DA64F3087E2E2E03E2D9F11D2@rznt8114.rznt.rzdir.fht-esslingen.de>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-originating-ip: [81.131.229.19]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 51fb6eaa-f37c-435a-4b16-08d7d0bb68b8
x-ms-traffictypediagnostic: DB7PR07MB4108:
x-microsoft-antispam-prvs: <DB7PR07MB4108EECE160D18583B97BB7CA0CE0@DB7PR07MB4108.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0353563E2B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(376002)(346002)(39860400002)(396003)(366004)(66476007)(8676002)(66556008)(81166006)(81156014)(64756008)(110136005)(86362001)(6506007)(7696005)(91956017)(52536014)(76116006)(8936002)(66446008)(9686003)(55016002)(4326008)(316002)(186003)(33656002)(66946007)(26005)(2906002)(71200400001)(66574012)(966005)(5660300002)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB4108; H:DB7PR07MB5657.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +/WAPSdRDxt3AfbnU3BG5HfrbvrxchiT2KcEW/pnrp8lR1I70wR/ui6YJWxTxDi2S2QBkMamR4u1sPJxiDdb3xF/MNzeDamfaYuK8jmpOhJM4UB8WpmLzLPzoRhixHuxLMQ6erwc/hK2Zj22vov8TXoHxolTDQbGcWwRfDFxucaRfnQwNYwy+rAosL88Ebnvz/ExQ6/TxtGOEGtmusfD7eTGztbLRsd5wxsHBfgME67j4AqO3yrN9ZJohIs94mduQ+J9Tlf4EMNrEBAQLv8KUTaXBOYYzzhJHXqBm9Vh+yZ8M5NAkx7tVV44M43ozaSb3jvmv4rjG8x854zN2ze5/ejY7hdnc+rfaIEJfNXckXCj53asA041t13N2rIslWd+0Q5vv2wkTOcvrdIrvwhrFdXRBUHJyS3qy93GbcsPH7gLrvx+CW+ZtwhnSrULLCsz3MkaoZ3DOw1U+EhDa7eNkHa7Gx0g1FWbcLGIF28zNmKcGbf3QqdiwHLl44QKV5iI/m7Z/j8RFrvNIL1TGXO5ew==
x-ms-exchange-antispam-messagedata: D/aD2Vi9gRPCO3+Ca2GFtRK3MzqASFbtYtk0JJDhro+VE1IeloZe1IBsyOojqfVtGGqZi4AtjhWOqijsxannGupCdNosLxz/Yjh0Fiik+LwtiASabY+KPgnnpy+P45toWBDhJPRWHUQulzCODlBKtw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 51fb6eaa-f37c-435a-4b16-08d7d0bb68b8
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2020 12:52:42.8945 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: l68BVk1YWNKVVxbwQF+5i66mVnmwJFn6dCjoXQfHrxk9VegFqnU+VTFjdtgBFR5kDA/kr8fNjtp0QIbKcU40WA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB4108
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3EECplQeVr2GmyJTsCUpQC1JD2c>
Subject: Re: [Idr] Request for feedback on WG adoption of draft-scharf-tcpm-yang-tcp-04
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2020 12:52:49 -0000

From: Idr <idr-bounces@ietf.org> on behalf of Scharf, Michael <Michael.Scharf@hs-esslingen.de>
Sent: 18 March 2020 20:12

Hi all,

This is a heads-up regarding the ongoing adoption call for draft-scharf-tcpm-yang-tcp-04 in TCPM.

<tp>
Michael

I note that you have also sent this to Netconf and that you import groupings from the netconf-tcp draft which makes the netconf draft a Normative Reference except that this I-D does not mention that fact. 

I think this is problematic.  Progress on the netconf I-D has been slow for some years and so your I-D could have to wait a while.  The solution would be to progress the netconf draft but I do not know how this can be expedited.

There are a lot of details in this I-D that I think of as admin which need fixing to conform to YANG Guidelines but would not see that as a bar to adoption whereas dependency on netconf is more debatable IMHO.

Tom Petch


You may want to pay attention. For instance, this document defines groupings for TCP-AO and MD5, which are used by draft-ietf-idr-bgp-model.

If you support work of this document in TCPM, or if you have any comments, please free to provide feedback on the TCPM list (tcpm@ietf.org).

Thanks

Michael (TCPM chair hat off)


Von: Michael Tuexen<mailto:tuexen@fh-muenster.de>
Gesendet: Montag, 16. März 2020 21:44
An: tcpm IETF list<mailto:tcpm@ietf.org>
Cc: draft-scharf-tcpm-yang-tcp@ietf.org<mailto:draft-scharf-tcpm-yang-tcp@ietf.org>
Betreff: Request for feedback on WG adoption of draft-scharf-tcpm-yang-tcp-04

Dear all,

this mail starts a WG adoption call for
https://tools.ietf.org/html/draft-scharf-tcpm-yang-tcp-04

So I would like to solicit feedback regarding support for or objections against the
adoption of the document as a WG document in TCPM.

Please provide feedback before March 31st.

For the context and current state of the document, see the presentation sent yesterday
to the mailing list by Mahesh.

Best regards
Michael