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

"Eric Voit (evoit)" <evoit@cisco.com> Mon, 15 July 2019 18:00 UTC

Return-Path: <evoit@cisco.com>
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 403E612011F for <netconf@ietfa.amsl.com>; Mon, 15 Jul 2019 11:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=j4D4Va8A; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.onmicrosoft.com header.b=J9UUn1YI
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 zwOuLQyEtnTL for <netconf@ietfa.amsl.com>; Mon, 15 Jul 2019 11:00:03 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18B1512011E for <netconf@ietf.org>; Mon, 15 Jul 2019 11:00:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21115; q=dns/txt; s=iport; t=1563213602; x=1564423202; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=9HXKf1ILspNdrCwwAjINYIbpe8lUvbqc0rl8LJogUik=; b=j4D4Va8A4cZcFX0PVbhJuLitEfRjAISG4dtKcwM8T471PkqGtedd1Yqt XRhNDoMsvUU3c0WQrmlndJxze8J/MdWyJClg3esuR6SeOfFXazr6XeOxx 4mSCvy8QQ3Ns6kEeemqICoe4C1H5hCZJrXniqqcNuPxHSwVzw3UI1tFtj Y=;
X-Files: smime.p7s : 3975
IronPort-PHdr: =?us-ascii?q?9a23=3AjZpSwheej1sv8FgjqggFLUzXlGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwKZD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFn?= =?us-ascii?q?pnwd4TgxRmBceEDUPhK/u/YjI9HdhqX15+9Hb9Ok9QS47z?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BWAADMvixd/5BdJa1lHAEBAQQBAQc?= =?us-ascii?q?EAQGBUwcBAQsBgRQvKScDalUgBAsoCoQSg0cDhFKJfIJbhzOLR4RVgS6BJAN?= =?us-ascii?q?UAgcBAQEJAwEBJQgCAQGEQAKCZSM0CQ4BAwEBBAEBAgEFbYU8DIVKAQEBAQM?= =?us-ascii?q?SEQoTAQEsCQIBDwIBCBUQHQICAjAlAgQBDQ0GFIMBgR1NAx0BDgOhHQKBOIh?= =?us-ascii?q?gcYEygnkBAQWBMgGDVhiCDAcDBoE0AYFQig4XgUA/gVeCTD6CYQKBSxgVFoJ?= =?us-ascii?q?dMoImi38VgmSFfZVyCQKCGYMrgiCBDY1Pgi2HJY44jTWHSJAIAgQCBAUCDgE?= =?us-ascii?q?BBYFQOIFYcBU7gmyCQQwXFG8BC4I/hRSFP3KBKYwyK4EEAYEgAQE?=
X-IronPort-AV: E=Sophos;i="5.63,493,1557187200"; d="p7s'?scan'208,217";a="595478323"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Jul 2019 18:00:01 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x6FHxxma029325 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 15 Jul 2019 18:00:01 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 15 Jul 2019 13:00:00 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 15 Jul 2019 12:59:57 -0500
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 15 Jul 2019 12:59:56 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jRU2NDVAzbxFAP+G0mAxj8A2CyAq0MAn2JAOEwcSXNAueAk/JFYu8RjCXKJAgZIkEvALB6clCN5uBWi2vsNBitqwrzWf+b9L8qN/22PH75qJKzd7X8Pe5GLEIUVCUsfAKPOfbOfixjEvNNZbCpbSqkhHYMuYi+Crp+meNyf0kmslQqoyCMBQSyoiE0HgPPwcLh2uru3CPy7bmvYSIg/8FGLpzDDpHZs2Rv5msYz+7joC0HN4857X7KtCqTg3NMiyCl/KO/NpywLusqUw61LuFVGLA3Ktc5+KYrNhNsm47ZiJP+VG/ZMpjcQbnzlPyqQfeoWZHVfaTNz1limB24nItQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Y6lF1IKoQ4Qi+WUe7tyX/qyCkL3wlDuC2msaU9Uszg8=; b=NkaR5/MKmaR0g4KiMtBzI4RGqfLNmCYEFOjutm40hv8Id0kdNOTcy/4Ev+C5utfq+u8kyKzF84Dr6GpGru2ddbUbSjfBmHelO2Drh9q09+TloJ+Yv7w0+ARWG4BlboWNhGh5dk0h0omM7L/SSpcv1GSe1yeA5OTTwA0CIukrKa7R0cCBVwLBeVjpAX+DtWeyhnYCuhedCeSe7i67OSVlxoCgW18TF3LmHxuV5g4jCIFlnOrR0bgxADsuICLauiLBctEi80hHpMo2ztojAMiIZ1a6e4/XdxzRYXKjRXy6lTFm2PUEizkIpX+XSoyN2OYINBdsykKlf3ZaqpY8tVMJyw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Y6lF1IKoQ4Qi+WUe7tyX/qyCkL3wlDuC2msaU9Uszg8=; b=J9UUn1YIZRszNglA1cAjH6tQ65WstxNXQZWhYYz/b49SNC696njxXT2rLyvzP3AFBCUwzADOIJNT2Lag34cx1dLnZT3xLKRbIEkYfPj05v5v8f6PbGETzBGStQZJsmxsAM5SX07ic65DF9FcUTIpsVWWC4TAFVShaDS+VZ+oNGw=
Received: from DM5PR1101MB2362.namprd11.prod.outlook.com (10.173.169.16) by DM5PR1101MB2250.namprd11.prod.outlook.com (10.174.246.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2073.10; Mon, 15 Jul 2019 17:59:55 +0000
Received: from DM5PR1101MB2362.namprd11.prod.outlook.com ([fe80::b838:5708:9829:6bc8]) by DM5PR1101MB2362.namprd11.prod.outlook.com ([fe80::b838:5708:9829:6bc8%4]) with mapi id 15.20.2073.012; Mon, 15 Jul 2019 17:59:55 +0000
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Kent Watsen <kent@watsen.net>, Tianran Zhou <zhoutianran@huawei.com>
CC: Qin Wu <bill.wu@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] New Version Notification for draft-zhou-netconf-multi-stream-originators-06.txt
Thread-Index: AQHVOysascekoK9bwkG1OZPXoxZf9qbL4xcw
Date: Mon, 15 Jul 2019 17:59:55 +0000
Message-ID: <DM5PR1101MB23629CE42808FA4501E08EB4A1CF0@DM5PR1101MB2362.namprd11.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAA49CDA59@nkgeml513-mbx.china.huawei.com> <BBA82579FD347748BEADC4C445EA0F21BEE7C407@NKGEML515-MBS.china.huawei.com> <0100016bd9b20da3-e9c9fc64-f9e3-4e19-8b01-88504803093d-000000@email.amazonses.com> <BBA82579FD347748BEADC4C445EA0F21BEE7EA88@NKGEML515-MBS.china.huawei.com> <0100016bf1e894c8-d55d14db-f7ba-4c4a-9ae8-f37aa8ff81a5-000000@email.amazonses.com> <BBA82579FD347748BEADC4C445EA0F21BEE9CA83@NKGEML515-MBS.china.huawei.com> <0100016bf67baa26-3807ff58-9139-4df1-8222-74fd66474b74-000000@email.amazonses.com>
In-Reply-To: <0100016bf67baa26-3807ff58-9139-4df1-8222-74fd66474b74-000000@email.amazonses.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evoit@cisco.com;
x-originating-ip: [173.38.117.74]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f6bd1ea7-1f85-460c-f29d-08d7094e3e61
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(49563074)(7193020); SRVR:DM5PR1101MB2250;
x-ms-traffictypediagnostic: DM5PR1101MB2250:
x-microsoft-antispam-prvs: <DM5PR1101MB2250ECB223EB679DFE0620EBA1CF0@DM5PR1101MB2250.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 00997889E7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(39860400002)(376002)(136003)(396003)(199004)(189003)(55016002)(52536014)(9686003)(6436002)(6306002)(54896002)(66946007)(33656002)(2420400007)(25786009)(74316002)(15650500001)(14444005)(256004)(7696005)(76116006)(81166006)(76176011)(476003)(54906003)(4326008)(446003)(110136005)(11346002)(66066001)(81156014)(5660300002)(316002)(8936002)(229853002)(66446008)(86362001)(99286004)(7110500001)(8676002)(64756008)(966005)(486006)(7736002)(478600001)(102836004)(14454004)(26005)(3846002)(606006)(53936002)(71200400001)(71190400001)(6116002)(186003)(99936001)(790700001)(66476007)(66556008)(2906002)(66616009)(236005)(6246003)(68736007)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR1101MB2250; H:DM5PR1101MB2362.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: PcOmP49YuAlS5fhDQISSpvbRvdQlAq23EAdQWiOG66Gg6QHCtPa4V+bgDDf+T08RObytph615Gl6QSexgbi4hYAwdppT+1+0LeEX+FR1eN8BzgV6f8JnLyJEdHLc+pEACA7nOJspOSezL9rHR3HtdNKmtT3/G+jFYYzgU4koCdc83KnNBEK6ToZZNJgHRElO5E2BuEbkKoO32Ucv73ZGpcDlDVdru2oq0K2u3fDSUV+IFSs6ccsIo9gDek+zKyJEtHqobVIF9KbWD1FGFQsFlqdPaIqwbLqu3RB2JkE6JnSWnQsj26jQuStAL55ZPNNxxigRP19qCEc/USRxplgvXuw04tCdw3hKDJzNvBxumfhcx737lwD+tc9prQVUWmMI3TFWl+xJzIx0K+LmBpMC1WmGlXFIRzLKOrIdkFKV7ak=
Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0157_01D53B14.3B424080"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f6bd1ea7-1f85-460c-f29d-08d7094e3e61
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2019 17:59:55.3048 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: evoit@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR1101MB2250
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.21, xch-rcd-011.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/i6RBThCmCaLWDU_uqMEspyPbyIM>
Subject: Re: [netconf] New Version Notification for draft-zhou-netconf-multi-stream-originators-06.txt
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: Mon, 15 Jul 2019 18:00:06 -0000

From: Kent Watsen, July 15, 2019 12:34 PM



[CC-ing Eric due to urgent SN issue]





Hi Tianran,



Hmmm, my guess is that pretty much all transports supporting configured 
subscriptions will have the server (i.e., line cards) proactively initiate the 
connections to the notifications-receivers (and not have the receivers 
connecting to the servers).   This is more a macro-observation than a 
draft-mahesh-netconf-https-notif specific thing, though that draft follows 
this pattern too.



[Tianran2]: I am sorry I not quite clear. Here we are talking about the 
dynamic subscription. I conclude there are four potential modes.

1. The linecard runs on server mode. The connections are dynamically set up, 
when the receiver know the subscription decomposition result at run time.

2. The linecard runs on server mode. All the potential connections are set up. 
The receiver only get data dynamically.

3. The linecard runs on client mode. The connections are dynamically set up, 
when the linecard know the subscription decomposition result at run time.

4. The linecard runs on client mode. All the potential connections are set up. 
The linecards send data dynamically.



Yes, this section regards dynamic subscriptions, but the macro-observation is 
that it would be good if dynamic-subscriptions behaved like 
configured-subscriptions and, since configured-subscriptions will most likely 
always have the server initiating the connection, it would be consistent if 
that were true for dynamic-subscriptions too (as opposed to having open 
ports).   Makes sense?



<eric> I think the dynamic subscription case is what several WG members have 
indicated has the most market demand.  With these dynamic subscriptions, there 
has certainly been a desire to match these to the existing transport paradigms 
of NETCONF / RESTCONF.   So I wouldn't suggest changing the overall 
connectivity paradigm of single-stream dynamic subscriptions based on the 
needs multi-line-cards.





 Ah, a "channel" container was added, I didn't see that before.  The draft 
should've defined YANG module to add a "channel" container.  That said, I 
don't think what you're hoping to achieve here is legal/valid YANG (please 
ensure that all examples are validated using e.g., `yanglint`).



[Tianran2]: I did not define a YANG module for this, because this may make the 
this draft depend on draft-mahesh-netconf-https-notif. But I sent the comment 
to the mailing list to suggest draft-mahesh-netconf-https-notif to apply this 
modification.

 <https://mailarchive.ietf.org/arch/msg/netconf/YmIh2l1xGJUq5gYwvrzcwnRphPg> 
https://mailarchive.ietf.org/arch/msg/netconf/YmIh2l1xGJUq5gYwvrzcwnRphPg



Or do you think this draft can define a configuration framework, not include 
the details? So that transport like draft-mahesh-netconf-https-notif can 
augment.



Ah, I recall seeing that message fly by before.  Seems like no one replied, 
too bad.   Really, this is not a something any transport draft (e.g., 
draft-mahesh-netconf-https-notif) should have to specify.  It would have to be 
the SN draft (currently in AUTH48) and likely published before Montreal.  This 
creates quite a problem.  I strongly advise raising this to the SN draft 
authors (specifically Eric Voit, CC-ed) ASAP!



<eric> There have been discussions on whether to add multi-line type card 
augmentations for the basic YANG model.  But to-date, these have been seen as 
future augmentations to be worked through the WG.  (Which we are exploring 
now.)



Based on leaving the AUTH48 work as-is, it seems like Tianran's suggestion 
seems a reasonable approach...  Anything specific to multi-line card 
augmentation should be in draft-zhou-netconf-multi-stream-originator.   And 
then any transports which want to support these multi-line card models can 
refer to the appropriate augmentations.


Eric







Kent // contributor