Re: [netconf] New Version Notification for draft-zhou-netconf-multi-stream-originators-06.txt

Kent Watsen <> Wed, 10 July 2019 02:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3A857120048 for <>; Tue, 9 Jul 2019 19:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Lh0hDscdMjcx for <>; Tue, 9 Jul 2019 19:24:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0470F1200C5 for <>; Tue, 9 Jul 2019 19:24:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw;; t=1562725453; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=S4NIJGZduaAgjrqOZWUky5oysuS+jHh8tkVj2v+hqkQ=; b=GBnJSEA9MZ9fVyoichw3upHxXm0qlbkSUdOVH0NxnDftyuaatzXxak3eTTCL5q3t vfjuhvstaXygROV6djKO2cXan6bKjcKucgOdJfa2cAwNgCW8QCKZkJhrqgwI9HJ8e8z 2Pq9dYMf0EodGM3INklRvZKxi0GDzt9v3n2BIxBs=
From: Kent Watsen <>
Message-ID: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_95434BEC-F264-446F-9F05-15F963A39C19"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 10 Jul 2019 02:24:13 +0000
In-Reply-To: <>
Cc: Qin Wu <>, "" <>
To: Tianran Zhou <>
References: <> <>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.07.10-
Archived-At: <>
Subject: Re: [netconf] New Version Notification for draft-zhou-netconf-multi-stream-originators-06.txt
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: Wed, 10 Jul 2019 02:24:17 -0000

Hi Tianran,

>> 1. In dynamic subscription case, how does Publisher agent behind Publisher
>> master know where a particular receiver is when pushing subscribed data to
>> the receiver in a separate channel?
> I think Appendix A.1 gives one example to show how this works in RESTCONF case.
> Firstly, the reply to the dynamic subscription will return the resource access URIs.
> Then, the receiver can use the URIs to GET the data.
> This is similar to draft-ietf-netconf-restconf-notif-15.

I was also unsure (the draft needs to be more clear with regards to expected behavior).  That said, I have a fews concerns:

1) will the client (a.k.a. the receiver) establish a full RESTCONF protocol connection to each line-card?  What YANG-library response might the line-cards return?
2) are we sure the client connections will always be routable to the line cards?
3) are there any security issues with line-cards having open ports?

Given the above, and the potential symmetry to the configured case, did you consider letting the server establish the connection to the client?  From an operator's perspective, perhaps both options need to be supported?   

>> 2. How multi-stream originator works for configured subscription case? 
> In appendix A.2, I use the similar example as in draft-mahesh-netconf-https-notif-00 to illustrate.
> In brief, the originators run on client mode, and connect to the receiver actively.

This example appears to be an exact copy/paste from draft-mahesh-netconf-https-notif, at least.  I didn't notice any differences and, that being the case, am unsure (again) what the expected behavior was intended to be.  Could you add a sequence diagram illustrating internal interactions?

Kent // contributor