Re: [netconf] FW: New Version Notification for draft-ietf-netconf-notification-capabilities-03.txt

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Tue, 13 August 2019 17:34 UTC

Return-Path: <rrahman@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 0F29E120232 for <netconf@ietfa.amsl.com>; Tue, 13 Aug 2019 10:34: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=Dffru26m; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.onmicrosoft.com header.b=g4yoJMdW
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 KW7t3Jp6zBEz for <netconf@ietfa.amsl.com>; Tue, 13 Aug 2019 10:34:03 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A5CD12011B for <netconf@ietf.org>; Tue, 13 Aug 2019 10:34:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=38971; q=dns/txt; s=iport; t=1565717643; x=1566927243; h=from:to:subject:date:message-id:mime-version; bh=jLn2TMSGjQuhHTshr/eacNkMW3v5PRA5RsQgduiiq44=; b=Dffru26m2OpwN6lHYHdyEF/ur9l8f39542JTWB3b3ieE3nrqXymMqiy3 nueNTpK0qxdeFe8FmfysAbpqgjfFQbPtjjxETpAAeEsbMQnBzX9EEaOYm qt4sZMAxrTmoUPaWvijYTy/8H9cB1SBZ1UeRZ1rMWz3AvRzVOf+VZuXRT g=;
X-Files: smime.p7s : 407
IronPort-PHdr: =?us-ascii?q?9a23=3AFAJkkh0L0fmBSq0FsmDT+zVfbzU7u7jyIg8e44?= =?us-ascii?q?YmjLQLaKm44pD+JxKHt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSw?= =?us-ascii?q?dDjMwXmwI6B8vQE1fyLPvjaQQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ALAABQ9FJd/5pdJa1mGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUwQBAQEBAQsBgRUvUANtVSAECyqEHoNHA4RShj1Mgg+?= =?us-ascii?q?TCIRagS4UgRADVAIHAQEBCQMBASUIAgEBhD8CF4JkIzQJDgEEAQEEAQEEAQp?= =?us-ascii?q?thScMhUoBAQIDEhEKEwEBNQMLBgEIEQQBAQ4dAgQwHQoEARIOFIMAAYFqAx0?= =?us-ascii?q?BAgyiCwKBOIhgc4EygnoBAQWBNgIOQYJ6GIINBwmBNAGBUIoYF4FAP4ERJx+?= =?us-ascii?q?CTD6CYQEBAgEBFoEUARIBCS2CdDKCJo8ShQ4jaod0ji0JAoIdgzCCJIEPjU8?= =?us-ascii?q?bgjBthkKNCoFUjVWHX5AkAgQCBAUCDgEBBYFQOGdxcBUaISoBgkEJgjk4gzq?= =?us-ascii?q?FFIU/cgGBKIt4gkMBAQ?=
X-IronPort-AV: E=Sophos;i="5.64,382,1559520000"; d="p7s'?scan'208,217";a="306411524"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Aug 2019 17:33:46 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x7DHXkOY013195 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 13 Aug 2019 17:33:46 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 13 Aug 2019 12:33:45 -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; Tue, 13 Aug 2019 12:33:44 -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; Tue, 13 Aug 2019 12:33:44 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cAlMWCl2Nf+LViQPYuEuvZtrvFGZznaJy82TNiZArGRU+DTc2NRtq2uHn7bFO86YaKFKpH1OHvVGP6bcQfsZT54iMvkx7LICmrGyWY0BPwEl/4LK1i0aERi42FHruVKsyQ/cmd5hiWc/HNxdcRKO9FhtDOWUAQEM6cFGyEze+Wh8fUXh3DFXqMk2BTaImKgfE6uFOMW8WzhEM0cGFjbzL9rBO8zi4VkTvA94UDhpzjtb+9NbRnMRwHzCIhqSY3qI8oKdqU+wykS7ZHCDPlQqPdwH+ycgkbDDt6vnCNTKxg67Q92OZnfwCMqt+buftRbpQX9qUTo3FjvZWhVUOFumaQ==
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=dtJbrIo/TxwnmPsUK5TFuwWkaM2qQJ8vjtrc/XheUVE=; b=iaqxu5BRj5GDr3xTYnwV946bWswzHjv1t1rAgkJCPwIBNnQJ1Sc/u3jnVA9z1cbuAWr2TouoLqp45c36qgclR+vfxxQ3gJM3Nnye17jVKIXnIozrI6XqlDM+tWpXpteB31ymKYH0faulI3Ovw/pr+ZSeSeKmEIU/fxj14PWF/yGOwCC3Aw77HUaLI+S8N3lVelbqhST2FILGp6R/qMbb2izD/usH7v1lQYeDgkeUUk3QTtPrwEVRAMhUmodpjxaLhDu98GxzyiblDb3GMzSMz1+Bt9ZnKmn0rRnNBIRCFhXsx5vaphjToIhOmOXqn0NAWVheNFQhLcyNfSG6qmefGg==
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=dtJbrIo/TxwnmPsUK5TFuwWkaM2qQJ8vjtrc/XheUVE=; b=g4yoJMdWguvjGrTt+K/druCp04+dIzP3ZxccW+7ODUxBmsZF2H740gv/v1BJb58oqCo7CTdtpZArF3J27GowEAF9aDPa19Xs/6TFTCGMHciWzWnydEBwHE1TCaLWO3vteLr+0ITGGabtwHSzE0Ox1ZMPEpIKxP9DQbxVFxYOL0Q=
Received: from MN2PR11MB4157.namprd11.prod.outlook.com (20.179.150.223) by MN2PR11MB4413.namprd11.prod.outlook.com (52.135.39.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.23; Tue, 13 Aug 2019 17:33:43 +0000
Received: from MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::80bb:d4b:bc47:7daf]) by MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::80bb:d4b:bc47:7daf%3]) with mapi id 15.20.2157.022; Tue, 13 Aug 2019 17:33:43 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: =?utf-8?B?QmFsw6F6cyBMZW5neWVs?= <balazs.lengyel@ericsson.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] FW: New Version Notification for draft-ietf-netconf-notification-capabilities-03.txt
Thread-Index: AQHVUf1AExMeuBVv1k69JXrika1c0A==
Date: Tue, 13 Aug 2019 17:33:42 +0000
Message-ID: <A6899D18-E94A-472E-AFDE-0960344A0B28@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rrahman@cisco.com;
x-originating-ip: [2001:420:2840:1250:6900:eb73:e481:aee6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 76b6d53f-6a74-4e9f-6283-08d72014631d
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:MN2PR11MB4413;
x-ms-traffictypediagnostic: MN2PR11MB4413:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <MN2PR11MB4413622736C002B065617F8CABD20@MN2PR11MB4413.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01283822F8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(39860400002)(366004)(396003)(376002)(136003)(13464003)(189003)(199004)(7736002)(14454004)(966005)(486006)(256004)(476003)(5024004)(66574012)(8936002)(71190400001)(53546011)(99286004)(186003)(81166006)(71200400001)(81156014)(8676002)(102836004)(46003)(36756003)(14444005)(6506007)(2501003)(2616005)(305945005)(6116002)(15650500001)(33656002)(478600001)(5660300002)(66556008)(66616009)(6512007)(6436002)(6306002)(6486002)(229853002)(66476007)(66946007)(25786009)(64756008)(66446008)(53936002)(58126008)(110136005)(6246003)(99936001)(86362001)(2906002)(316002)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4413; H:MN2PR11MB4157.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: Y4N6qn9tGurkYs95+QzYu8AD+UKS5UuKmTtAeVhljfkBl6jHQWNDpAtntcZFGhKyPNmhBRIEK41CpdNpxwDGuH4qhLFxXVlqTgHc3DsUndq1RUU4bCoMiUwWduZOFAJgZan+9ODimAnojYxrjLHqqyKak+a19Kj9FAkYb8lhM2Gkb4WdRz1juxAr3dcPrzI9umSX61Q0Po30V4zzm8gNzVMf7uvtm2WZMOMs+3n4JtHQuMtooL17IU23CjhN78NwTCR3KQbM6ypWQFoiz7RfzyOKkstGG8kdQCz7D79KvyP6DS54zEFA3I0EHMOaWgFSZx+I9zbNElJcipuKXrPOIzg/HTSwF8GPyRtOsISUKc6KGj8xNzaeJ3F1+Ka/71cJ+OxuPQW7O3SrH2Mnt/FjaHEfV6EcYKQ6Igo3+RJ7PFQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/mixed; boundary="_002_A6899D18E94A472EAFDE0960344A0B28ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 76b6d53f-6a74-4e9f-6283-08d72014631d
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Aug 2019 17:33:42.8640 (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: bYARkv9bXM6jYxsgZCXvhoeT7EySq055SJcSRJcD0tcuPPPmeS5XUVPhkzKvCrsJy09ljR34PHl1ZJCFd2a8fA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4413
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/wnBSI8V9NVxNJuBTJISJ4t9Ss5U>
Subject: Re: [netconf] FW: New Version Notification for draft-ietf-netconf-notification-capabilities-03.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: Tue, 13 Aug 2019 17:34:06 -0000

Balazs, I don't think the comment in the attached email has been addressed?

Regards,
Reshad.

On 2019-08-13, 11:12 AM, "netconf on behalf of Balázs Lengyel" <netconf-bounces@ietf.org on behalf of balazs.lengyel@ericsson.com> wrote:

    I updated the draft with all comments from and after the meeting. Please review.
    Changes v02 - v03
    
       o  Allow throughput related capabilities to be defined on top,
          datastore or data node level.  Described that specific capability
          values always override generic ones.
    
       o  Indicate that non-NMDA servers can also use this model.
    
       o  Updated according to draft-ietf-netmod-yang-instance-file-
          format-04
    
    Regards Balazs
    
    -----Original Message-----
    From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
    Sent: 2019. augusztus 13., kedd 17:02
    To: Benoit Claise <bclaise@cisco.com>om>; Alexander Clemm <ludwig@clemm.org>rg>; Balázs Lengyel <balazs.lengyel@ericsson.com>
    Subject: New Version Notification for draft-ietf-netconf-notification-capabilities-03.txt
    
    
    A new version of I-D, draft-ietf-netconf-notification-capabilities-03.txt
    has been successfully submitted by Balazs Lengyel and posted to the IETF repository.
    
    Name:		draft-ietf-netconf-notification-capabilities
    Revision:	03
    Title:		Yang-Push Notification Capabilities
    Document date:	2019-08-13
    Group:		netconf
    Pages:		18
    URL:            https://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-capabilities-03.txt
    Status:         https://datatracker.ietf.org/doc/draft-ietf-netconf-notification-capabilities/
    Htmlized:       https://tools.ietf.org/html/draft-ietf-netconf-notification-capabilities-03
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-netconf-notification-capabilities
    Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-notification-capabilities-03
    
    Abstract:
       This document proposes a YANG module that allows a server to specify
       server capabilities related to "Subscription to YANG Datastores"
       (Yang-Push).  It proposes to use YANG Instance Data to document this
       information and make it already available at implementation time, but
       also allow it to be reported at runtime.
    
                                                                                      
    
    
    Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
    
    The IETF Secretariat
    
    

--- Begin Message ---
OK, will add it.  Balazs

 

From: Reshad Rahman (rrahman) <rrahman@cisco.com> 
Sent: 2019. július 23., kedd 16:34
To: Balázs Lengyel <balazs.lengyel@ericsson.com>om>; netconf@ietf.org
Subject: Comment on draft-ietf-notification-capabilities

 

Hi Balazs,

 

Section 2 mentions that the capabilities could change at run-time. For those implementations which support this, there would be value if the datastore-subscription-capabilities container is on-change capable?

This should be indicated with an entry for that node in the on-change-notification-capability list (for the operational datastore)? Could we have some text in the draft for this?

 

Regards,

Reshad.

--- End Message ---