[netmod] 答复: NBC changes and warnings

"Fengchong (frank)" <frank.fengchong@huawei.com> Thu, 21 April 2022 02:51 UTC

Return-Path: <frank.fengchong@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 035CF3A0A8C for <netmod@ietfa.amsl.com>; Wed, 20 Apr 2022 19:51:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2DoQlVx1fZhM for <netmod@ietfa.amsl.com>; Wed, 20 Apr 2022 19:51:18 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B448E3A0A8A for <netmod@ietf.org>; Wed, 20 Apr 2022 19:51:17 -0700 (PDT)
Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KkMQW2nRkz6F97k for <netmod@ietf.org>; Thu, 21 Apr 2022 10:47:31 +0800 (CST)
Received: from dggpemm500004.china.huawei.com (7.185.36.219) by fraeml707-chm.china.huawei.com (10.206.15.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 21 Apr 2022 04:51:13 +0200
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by dggpemm500004.china.huawei.com (7.185.36.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 21 Apr 2022 10:51:12 +0800
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2375.024; Thu, 21 Apr 2022 10:51:12 +0800
From: "Fengchong (frank)" <frank.fengchong@huawei.com>
To: Andy Bierman <andy@yumaworks.com>, NetMod WG <netmod@ietf.org>
Thread-Topic: [netmod] NBC changes and warnings
Thread-Index: AQHYVNP0caONEw+vRk+CroSiRSZ9rKz5q1Zg
Date: Thu, 21 Apr 2022 02:51:12 +0000
Message-ID: <2996841cbc3a4f0cab0869b1fd221a20@huawei.com>
References: <CABCOCHT=9VYrCRuOcTnX+EbVG-LCWuMUGoHimPQm8NpWYLR=7Q@mail.gmail.com>
In-Reply-To: <CABCOCHT=9VYrCRuOcTnX+EbVG-LCWuMUGoHimPQm8NpWYLR=7Q@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.113.80]
Content-Type: multipart/alternative; boundary="_000_2996841cbc3a4f0cab0869b1fd221a20huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/EQ3TMdq8n4vOkb9Kmj48fcoMQxI>
Subject: [netmod] 答复: NBC changes and warnings
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2022 02:51:20 -0000

Andy,
       Server don’t know how the client’s yang modules is, so server can not judge whether the NBC changes exist.

发件人: netmod [mailto:netmod-bounces@ietf.org] 代表 Andy Bierman
发送时间: 2022年4月21日 0:30
收件人: NetMod WG <netmod@ietf.org>
主题: [netmod] NBC changes and warnings

Hi,

Before any significant NBC change can be introduced, a process needs
to be in place to minimize the disruption that the NBC change will cause.

Consider the recent change by GitHub to remove support for SSH passwords
and require keys instead.  They warned people for about 2 years this change
was coming.  Not just on the WEB site, but in the tools. Every time
a user logged in over SSH with a password, a warning was printed.

For those willing to read the warning and act upon it, there was no
service disruption at all when SSH passwords were finally turned off.

When NETCONF was introduced in 2006, everything was new.
The NETCONF error-severity=warning did not even work, and nobody cared.
It still doesn't work.

There are other possibilities besides
"We can never make an NBC change because nobody will read the warning
in the description-stmt anyway."  That's true. So let's fix it in the protocols
and in the YANG language, so they do get the warning.


Andy