Re: [netconf] Regarding 108 adoption hums

Tianran Zhou <> Mon, 10 August 2020 09:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9272C3A145F for <>; Mon, 10 Aug 2020 02:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oTBRPIWuAf8E for <>; Mon, 10 Aug 2020 02:36:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 663F93A0BC9 for <>; Mon, 10 Aug 2020 02:36:13 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 9317499BE982194B1558; Mon, 10 Aug 2020 10:36:10 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Mon, 10 Aug 2020 10:36:09 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 10 Aug 2020 17:36:00 +0800
Received: from ([]) by ([]) with mapi id 15.01.1913.007; Mon, 10 Aug 2020 17:36:00 +0800
From: Tianran Zhou <>
To: Andy Bierman <>, Juergen Schoenwaelder <>, Adrian Farrel <>, Kent Watsen <>, Netconf <>
Thread-Topic: [netconf] Regarding 108 adoption hums
Thread-Index: AQHWa3W0/zcfmCeL8EOO/Z5e6RwUCakr1QWAgAAFB4CAAOmVAIAEVCng
Date: Mon, 10 Aug 2020 09:36:00 +0000
Message-ID: <>
References: <> <00cf01d66c99$07392530$15ab6f90$> <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_cacf1f0b19ec4b4bac34d42ab9bae254huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netconf] Regarding 108 adoption hums
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 10 Aug 2020 09:36:16 -0000

The working group should not function as a rubber stamp for proprietary solutions and academic work.
We should not ask for the working group adoption, if the solution does not have requirement.
I strongly suggest the Chairs and the ADs to set a high bar to only adopt solutions with at least two implementations.


From: netconf [] On Behalf Of Andy Bierman
Sent: Saturday, August 8, 2020 7:13 AM
To: Juergen Schoenwaelder <>de>; Adrian Farrel <>uk>; Kent Watsen <>et>; Netconf <>
Subject: Re: [netconf] Regarding 108 adoption hums


On Fri, Aug 7, 2020 at 2:17 AM Juergen Schoenwaelder <<>> wrote:

technical discussion of the drafts on the mailing list would help more
than having process meta-discussions. It is good to know who (other
than the authors) is volunteering to substantially review the drafts,
is willing to contribute to the discussions of any issues, and is
planning to implement the technology defined in the drafts as this
will likely help the chairs to make a decision.

IMO it makes more sense to discuss what problems the NETCONF/NETMOD WGs
should be solving, rather than adoption of solutions to problems. The WG should be
finishing up configured notifications. Try to standardize binary telemetry instead
of just leaving placeholders for proprietary vendor solutions.

Your questions are most relevant because we do not have any clear definition
or "support" or "oppose" for adoption of a draft.
Support often means "I am happy for you to work on this draft".
The culture of the IETF creates a strong bias against anybody actually
opposing adoption of anything. Usual attitude: "Let people experiment. Maybe they will
come up with something good in the end."

If only the co-authors support, and nobody opposes, then the work will get stuck.
Often WGs adopt after such a poll outcome and act surprised a year later when
the draft goes nowhere.



On Fri, Aug 07, 2020 at 09:59:15AM +0100, Adrian Farrel wrote:
> Hi chairs,
> I think this is an interesting approach to determining whether there is interest in a number of drafts at the same time, and I agree with you that a hum at a working group meeting means nothing without confirming the opinion on the mailing list.
> But I'm worried that you may be introducing yet another piece of process into how we process documents.
> The adoption poll, itself, is not necessary if it is obvious to the chairs that a draft is within charter and has support [RFC7221]. But in addition to the poll, we also have somehow introduced an IPR poll at adoption time (while I can see the merits of being explicit about IPR, and we have seen one or two people attempt to wriggle out of their responsibilities, it seems unnecessary to serialize the two calls). Now you appear to be introducing an additional step to test "adoption suitability".
> Can I urge you (strongly? :-) to consider the responses to you adoption suitability tests and, if they are solid, to move straight to adoption without making the working group go though a prolonged series of polls. We would, I think, prefer to get on with the work!
> Best,
> Adrian
> -----Original Message-----
> From: netconf <<>> On Behalf Of Kent Watsen
> Sent: 05 August 2020 23:13
> To:<>
> Subject: [netconf] Regarding 108 adoption hums
> The Chairs & AD discussed the results of the various adoption hums conducted during the 108 meeting.  There is a sense that the results didn’t adequately determine if the drafts should be adopted.  In particular, it wasn’t clear if the hums reflected a general desire to solve the problem or support for the particular draft.
> As such, we’ve decided to send subsequent emails for each draft, or set of drafts if appropriate, to solicit input on following questions:
>     1) is the problem important for the NETCONF WG to solve?
>     2) is the draft a suitable basis for the work?
> NETCONF Chairs
> _______________________________________________
> netconf mailing list
> _______________________________________________
> netconf mailing list

Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <>

netconf mailing list<>