[netconf] teeing up adoption call on draft-zhou-netconf-multi-stream-originators

Kent Watsen <kent+ietf@watsen.net> Thu, 02 May 2019 18:11 UTC

Return-Path: <0100016a79be5df2-196e176a-4ee6-4cd4-8289-e49ee2cb1c5b-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD80F120640; Thu, 2 May 2019 11:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 DTBztOfY1jbL; Thu, 2 May 2019 11:11:25 -0700 (PDT)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com [54.240.8.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5DEE12064D; Thu, 2 May 2019 11:11:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1556820680; h=From:Content-Type:Mime-Version:Subject:Message-Id:Date:Cc:To:Feedback-ID; bh=GyF6aq2W1YV8BalVU0LugU0SL+91FdayIStrNSYB0xo=; b=NxAz+jRI9jc55qpLVYTNMXCDb2b5sv2NuMdgig9Cwtm7IqZ3Duz/rCd2tqCrHCIc etQORB9FPLNzSuUJP3u8DPD3Y5ls8b8atwfotxSURBRUfnHLSRA0iddQs5fBIZ1rfZc iC/KRvZLlph2FitLcTO/flulyC7R60s0VR8pF0rg=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_394C3CE6-E177-463C-AE3A-400DCB289BC3"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-ID: <0100016a79be5df2-196e176a-4ee6-4cd4-8289-e49ee2cb1c5b-000000@email.amazonses.com>
Date: Thu, 2 May 2019 18:11:20 +0000
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: draft-zhou-netconf-multi-stream-originators@ietf.org
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.05.02-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/hBGfqxZ2Jcta3FH7j4WBJsUft2c>
Subject: [netconf] teeing up adoption call on draft-zhou-netconf-multi-stream-originators
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2019 18:11:27 -0000

Authors,

From the minutes, the WG agrees that this is a problem worth solving, but the current documented isn't quite right.  Please update the draft to:

1) focus on introducing a way to configure subscriptions such that any "notif" draft can be used to send notifications out line cards.
1a) do not focus on any particular "notif" transport (at least not in this draft)
1b) assume that the notif transports may be either UDP or TCP (more likely TCP)
1c) assume that the notif transports may be encrypted or not encrypted

2) per Ignas's comment, explicitly state how transport congestion and related aspects are or are not being taken into account.
2a) my opinion is that this draft sets up up the *potential* for a problem (and should say so), but it is likely that the particular "notif" transport used will matter greatly (e.g., unencrypted UDP is less heavy than encrypted TCP).
2b) also my opinion, this draft is comparable to the subscribed-notifications draft in this regard, so lifting text from there should be possible.  Since there is an overlap of authors on both drafts, hopefully what's needed is well understood.

An adoption call will proceed once the update is published addressing the above.

Kent (and Mahesh)  // chairs