Re: [Netconf] request for comments on draft-ietf-netconf-udp-pub-channel

Martin Bjorklund <> Mon, 11 June 2018 07:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ACD80130E13 for <>; Mon, 11 Jun 2018 00:48:29 -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 yLaTvjvRmBfF for <>; Mon, 11 Jun 2018 00:48:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E2C16130E11 for <>; Mon, 11 Jun 2018 00:48:27 -0700 (PDT)
Received: from localhost (unknown []) by (Postfix) with ESMTPSA id 3AB781AE01AA; Mon, 11 Jun 2018 09:48:25 +0200 (CEST)
Date: Mon, 11 Jun 2018 09:48:24 +0200
Message-Id: <>
From: Martin Bjorklund <>
In-Reply-To: <>
References: <>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Netconf] request for comments on draft-ietf-netconf-udp-pub-channel
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 11 Jun 2018 07:48:30 -0000


I have read draft-ietf-netconf-udp-pub-channel-02, but struggle with
some basics.

I don't understand how this new transport is supposed to fit into the
design of draft-ietf-netconf-subscribed-notifications.  For example,
the udp-pub-channel draft seems to expect a request to
"establish-subscription" over NETCONF to send the notifications over
UDP.  But AFAICT this is not possible with the current design of

Is the transport in this draft supposed to work for notifications in
general, or only YANG push notifications?

Also, it seems many of the references to yang-push really should be to

It would also be useful to align terminology with the other
documents.  It seems a "Master" is really the management protocol
server?  And "Agent" is what subscribed-notifications calls a
"publisher"?  Or maybe the "Master" is the "publisher"?

You also use the term "data originator", but I am not quite sure if
that is the same as "Agent"?


Tianran Zhou <> wrote:
> Hi WG,
> We've got some comments on the UDP based Publication Channel for
> Streaming Telemetry. And we are going to update it, specifically on
> the security aspect.
> Could you please help to review?
> Any comment is appreciated.
> Thanks,
> Tianran
> _______________________________________________
> Netconf mailing list