Re: [Lsr] [OPSAWG] [GROW] FW: New Version Notification for draft-gu-network-mornitoring-protol-00.txt

Haoyu song <> Mon, 09 July 2018 21:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4578A13107F; Mon, 9 Jul 2018 14:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GOVjAfzqAfjf; Mon, 9 Jul 2018 14:57:28 -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 D8BC113107D; Mon, 9 Jul 2018 14:57:27 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id C2530732E198; Mon, 9 Jul 2018 22:57:23 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 9 Jul 2018 22:57:25 +0100
Received: from ([]) by ([]) with mapi id 14.03.0399.000; Mon, 9 Jul 2018 14:57:17 -0700
From: Haoyu song <>
To: Randy Bush <>, Lizhenbin <>
CC: "" <>, GMO Crops <>, "" <>, "" <>
Thread-Topic: [OPSAWG] [GROW] [Lsr] FW: New Version Notification for draft-gu-network-mornitoring-protol-00.txt
Thread-Index: AQHUFKw5+X6kcVEEo0W4WxYQgude5KSCRYQAgALdE4CAAlGdAA==
Date: Mon, 09 Jul 2018 21:57:17 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Lsr] [OPSAWG] [GROW] FW: New Version Notification for draft-gu-network-mornitoring-protol-00.txt
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Jul 2018 21:57:31 -0000

Hi Randy,

Thank you for comments on draft-song-ntf.
I'm not sure I understand your second point. Could you please clarify it?
Please note we didn't enforce any specific model on the telemetry yet. This doc only concerns the aspect on how to acquire data from networks. It does support the dynamic and interactive configuration for data acquirement. But control is out of scope of this document, although we confirm that telemetry plus control complete the closed control loop. Maybe I misunderstood your point.


-----Original Message-----
From: OPSAWG [] On Behalf Of Randy Bush
Sent: Saturday, July 07, 2018 8:25 PM
To: Lizhenbin <>
Cc:; GMO Crops <>;;
Subject: Re: [OPSAWG] [GROW] [Lsr] FW: New Version Notification for draft-gu-network-mornitoring-protol-00.txt


i am not ignoring you.  i did not want to write unless i had something possibly useful to say; and that requires pretending to think, always difficult.

> I would also like to propose following draft for your reference which 
> trigger us to move forward for better network maintenance with 
> multiple tools in which gRPC/NETCOF and NMP/BMP may play different
> roles:

[ warning: my memory is likely fuzzy, and the glass is dark ]

at an ietf in the late '90s[0], there was a hastily called meeting of the snmp standards bearers and a bunch of operators.  the snmp folk were shocked to learn that no operators used snmp for other than monitoring; no one had snmp write enabled on devices; ops configured with the cli[1].  from this was born netconf and the xml path.  credit where due:
phil eng was already well down this path at the time of that meeting.

but netconf/xml was a mechanism and lacked a model.  snmp had models, whether we thought they were pretty or not.  thus yang was born, and , of course, a new generation wants to use the latest modern toys such as restconf, openconfig, json, ...

draft-song-ntf yearns for an "architectural framework for network telemetry," a lofty and worthwhile goal not, a priori, a bad one.  but a few comments from a jaded old dog.

for a new paradigm to gain traction, it must be *significantly* better than the old one, or the old paradigm must be clearly failing.  in the story above, snmp was clearly failing, aside from using an unfashionable encoding.  and yang clearly provided something needed and missing from netconf.  note that this paradigm shift has taken over 20 years; and we dis the itu et alia.

second, draft-song-ntf is an export-only model.  while telemetry is extremely important, i will be very frustrated if i can only hear and may not speak.  and the more it evolves to a really attractive paradigm and model, the more annoyed i will be that i can not use it for control.

and lastly, to quote don knuth, "premature optimization is the root of all evil."  do not get distracted by squeezing bits out of an encoding.
focus on things such as simple, clear, securable, extensible ...



0 - i would love help pinning down which meeting

1 - i still have the "it's the cli, stupid" tee shirt.  an american
    political slogan of the era was "it's the economy, stupid."

OPSAWG mailing list