IETF Logo Mail Archive

Re: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00

"Eric Voit (evoit)" <evoit@cisco.com> Tue, 03 September 2019 15: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 8CCD01208DC for <netconf@ietfa.amsl.com>; Tue, 3 Sep 2019 08:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-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, URIBL_BLOCKED=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=ZjBurSeD; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.onmicrosoft.com header.b=I3FCRIgY
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 KRa81CTJLgMJ for <netconf@ietfa.amsl.com>; Tue, 3 Sep 2019 08:00:45 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 439F7120948 for <netconf@ietf.org>; Tue, 3 Sep 2019 08:00:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15253; q=dns/txt; s=iport; t=1567522845; x=1568732445; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ffCX/F0mF+7hy5LeRKRIThXZQ0nLnIE6vjbXL0D3O1M=; b=ZjBurSeD1fsLrRbbXsjpjrkwJTmgtg4vCP/nyO3XMFO5l/rr95yZHVX/ 7dKudwybJN3gkXRoyPq92qEf9OsTz8BW/xARXs6ib2rVfUvJ61l+rtDR3 3XD6+QNwT77lWjgv9OsyY2+iwFvdHLWRtsomzjROWPdiB3Xv9+X5o49IY U=;
X-Files: smime.p7s : 3975
IronPort-PHdr: 9a23:yJU2HxTL+E0LjgFpk/6ikpDHVdpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESUDdfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOiEkG8VefFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAADzfm5d/5tdJa1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwQBAQEBAQsBgRUvKScDbVYgBAsqCodeA4RShieCXIc/i1GEXIEuFIEQA1QCBwEBAQkDAQEjCgIBAYQ/AoJ2IzQJDgIDCAEBBAEBAQIBBgRthS4MhUoBAQEEEgsQEwEBNwEPAgEIEQQBAQ4hAjAdCAIEAQ0FCAYNB4I1TIEdTQMdAQIMnywCgTiIYYIlgnwBAQWBNgKDVhiCDwcDBoE0AYFQiicYgUA/gRFGgkw+gmEBAQOBKwESASErgxCCJoxMiQCIDY1XbQqCH4M4gimBEo4DgjOHNo59jXaHdZBUAgQCBAUCDgEBBYFQOGdxcBU7gmyCQoNyhRSFP3OBKYxYgSIBgSIBAQ
X-IronPort-AV: E=Sophos;i="5.64,463,1559520000"; d="p7s'?scan'208,217";a="625174123"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Sep 2019 15:00:42 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x83F0g4P006341 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 3 Sep 2019 15:00:42 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 3 Sep 2019 10:00:42 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 3 Sep 2019 10:00:41 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 3 Sep 2019 10:00:41 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=B8jz8gYV/BKja4GXswzb41VL4t/uVfa1eFFWD7fHkNRZTFo3NhQK/3i/fT1HoxwPAlQlA7z4UcUXWyqJrSKqLjyIeGqBV2pxJgCmCXDpRPlYSrQpeYdhM7WLoeWvSpwgns07OBDpVK1klqnxcsnAEAevJvKk9e0uvM8VgQSACoEUnzqHaXe9U2C5xGE8S1cpAdWkj4bTl+yxd2DNK5n5UNihS1/tAWQqIE/hGmS64LonsKpFmNFsI0xuS4As/Eq7Do7sL8Cl8iwOd6YaqZq/7Cc/YWyN6dgssa/054srJCSkf6OkpkgXe4Bpxs9IYlc2oGliceBfCID+SJa6VEDu7g==
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=xYA4JALX9ZhMO/hnA1h5rsdDqpFifVi39FjJTBe+5H8=; b=FH7Vx3VBgcCijgG7ylYD+NMuIe46NYCieZAsnKJoyHJnaZ3WsMUZAktpSXPEt0ZUATLJYSG62svQLT3lWm9M+eyVQ4gVW+Xe1ZFa6BqWu8dksl0JQR1GzFU2ZVTPfmdZrYm7VffVvruVszrYzXlTjBYmB/t8r+3DVJ/XYkULfVTMOZ6TPjkA6yQEPdFOTN7pOVGOiST8e4bN9SKc6UqHW2AaSDAKcmnK3vz53mFD+g/EVPzDBDaNUj9O438UxXfM4AxyUl55bWmYDQeH5/oGrRiHguVRSWQTul9z3skQBwAL4evhpWZzaMxU+53iWHi3RDtcp/ZoI5XzQtAUUVyasA==
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=xYA4JALX9ZhMO/hnA1h5rsdDqpFifVi39FjJTBe+5H8=; b=I3FCRIgYKa3DFrTdKUdmrq/j/9QSDDIAo7cmaAh+OsaSNsM522ycKkJoe5oYJO4ZyUhA9Hge3RmHe7bW9i6ck9+TUhxOYYDLtdDRykzQy9S1HMHL2ggxYRvi5/HL3TGQPG4z8wRO7kdjj9wyrAUFqKojCTSBqEmVb61sfEWGBGE=
Received: from SN6PR11MB2638.namprd11.prod.outlook.com (52.135.91.149) by SN6PR11MB2894.namprd11.prod.outlook.com (20.176.241.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.18; Tue, 3 Sep 2019 15:00:40 +0000
Received: from SN6PR11MB2638.namprd11.prod.outlook.com ([fe80::a545:a4eb:27b:bac7]) by SN6PR11MB2638.namprd11.prod.outlook.com ([fe80::a545:a4eb:27b:bac7%7]) with mapi id 15.20.2220.013; Tue, 3 Sep 2019 15:00:40 +0000
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Kent Watsen <kent+ietf@watsen.net>, Mahesh Jethanandani <mjethanandani@gmail.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00
Thread-Index: AQHVXFoPNB92Y7jVYEStg347+aEuhKcaAhVg
Date: Tue, 03 Sep 2019 15:00:39 +0000
Message-ID: <SN6PR11MB2638BF4053A1308CAA4849A8A1B90@SN6PR11MB2638.namprd11.prod.outlook.com>
References: <0100016ccff35064-9da3c8b6-263c-47f6-a4f2-4db9495bc8b7-000000@email.amazonses.com>
In-Reply-To: <0100016ccff35064-9da3c8b6-263c-47f6-a4f2-4db9495bc8b7-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.88]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: be411211-f4e1-48d6-292c-08d7307f7c65
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(49563074)(7193020); SRVR:SN6PR11MB2894;
x-ms-traffictypediagnostic: SN6PR11MB2894:
x-microsoft-antispam-prvs: <SN6PR11MB2894B2DEE789CA6A75396510A1B90@SN6PR11MB2894.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01494FA7F7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(39860400002)(376002)(136003)(346002)(366004)(199004)(189003)(4326008)(7736002)(74316002)(81156014)(81166006)(8676002)(76176011)(26005)(186003)(6506007)(53546011)(8936002)(14444005)(256004)(446003)(11346002)(486006)(476003)(229853002)(99936001)(102836004)(52536014)(66066001)(6436002)(55016002)(6306002)(54896002)(9686003)(5660300002)(236005)(478600001)(53936002)(86362001)(14454004)(606006)(33656002)(966005)(316002)(71200400001)(110136005)(71190400001)(2906002)(3846002)(6116002)(790700001)(6246003)(7696005)(99286004)(76116006)(25786009)(66446008)(66946007)(66616009)(66556008)(64756008)(66476007); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2894; H:SN6PR11MB2638.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: sZqpomUFjL343MHUUCJH7XZ4uCmLLyGTWqjuSEg840PBEpKPs9slR0pnkn1DSKZd+qTgVC09vVLkDSa0MMvO/BqyfYR8aMeyU8WQ8USFUkImmbgnpKagjtyYqOPTdDazLw0FVaMQQdCzOlUaHoVFOsMCTpHkbFNFYlulBJErA8KcajPCzCc7pCIg1Q3xYmFTP6/cg1R3PQzIGpW/L+FAtAfmx3VVNp69wbiHOUc1W0oNy9ZOW422tSGy7TGgJGtQF3CTFyzLC3qQzNW/qYIRS1kho0ibbNUdAcNq0WdFneLU3DFSrC+b+9+OEY/FN82po2K3dT4mc+lhXabVfaia8RiRAwFMysPRI9hwYbJ9cqUghEKCOFv+t3xzDKzb4LqS8GD9qgoEifcLWF6Ygy5LuOau32Zu5rmnxM9sgKS4Ln4=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_025A_01D56246.BD7CC080"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: be411211-f4e1-48d6-292c-08d7307f7c65
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Sep 2019 15:00:40.0849 (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: MFb+D929qaF8fZ9j2pqgOswOmLw8CvJokQOVDS5hKBZ4HtGMYWsPnvqZt7c8R06O
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB2894
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.18, xch-aln-008.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/R-8ukrzxi9rVczF3idtiW91kR8I>
Subject: Re: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00
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: Tue, 03 Sep 2019 15:00:54 -0000

I support the adoption.

 

Building upon that, there are a few elements which would be good to consider
in future iterations.

 

(1)  Understanding the capabilities of the configured receiver is important.
One or more publishers of configured subscriptions could be used to
overwhelm a receiver which doesn't even support subscriptions.    This
document should include ways to ensure a configured stream won't be
established with an endpoint unequipped to deal with the inbound
notifications.  As a starting point for these discussions, there are
mechanisms in draft-ietf-netconf-restconf-notif v5 to address this.   E.g.,
the  HTTP transport augmentation on the receiver must send an "HTTP OK" to a
"subscription-started" notification before the publisher starts streaming
any subscribed content.

 

(2)  Multiple versions of draft-ietf-netconf-restconf-notif include
topics/text which might be useful, even as an appendix.   For example
Section B.2 of v5 includes example config operations and interaction models.

 

Side comment:  there are advantages in subscriptions over HTTP2 transports,
which I don't believe it will be covered in this draft.  GRPC has the
ability to optimize based its leverage of HTTP2.    To examples from
draft-ietf-netconf-restconf-notif v5 which are good to think about are:

(a) optimizing multiple configured subscription streams to a single receiver
(such as a controller). 

(b) it can be easier overwhelm a receiver which is unable to control or
handle the volume of Event Notifications received  

It would be good to somehow capture the implications of using different
underlying HTTP capabilities as part of these discussions.

 

Thanks,

Eric

 

From: netconf <netconf-bounces@ietf.org> On Behalf Of Kent Watsen
Sent: Monday, August 26, 2019 6:02 PM
To: netconf@ietf.org
Subject: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00

 

This email begins a 2-week adoption poll for:

 

    https://tools.ietf.org/html/draft-mahesh-netconf-https-notif-00

In-room support for this draft was noted but, as always, it is necessary to
confirm WG consensus on the list.  If interested in the WG defining an
HTTPS-based solution for *configured subscriptions* (for which there are
none to date), please voice your support for this draft's adoption.  If
objecting, please state your reasons.  

 

PS: Authors, please additionally respond to as if there is any IPR to
disclose.


Kent and Mahesh // as chairs

v2.23.0 | Report a Bug | By Email