Re: [netconf] Éric Vyncke's No Objection on draft-ietf-netconf-yang-push-22: (with COMMENT)

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Tue, 30 April 2019 17:06 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 BE70B1202ED; Tue, 30 Apr 2019 10:06:06 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=dr9JhDqC; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=MGYC54CU
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 QtBdDWza_Aa6; Tue, 30 Apr 2019 10:06:04 -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 4E79F12008D; Tue, 30 Apr 2019 10:06:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4386; q=dns/txt; s=iport; t=1556643964; x=1557853564; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=oyG4U8u3ZHgpHZUHSMbtOSr7Tl1RNYrBij9ben/Faq4=; b=dr9JhDqC3mkCAlzZlqWnMYXQtEQ+M9uW+lSEpxFEXu2EecM2pIDvlJdW /wKFZoR5sw2DDjIWXq9J/ZtWGYR+lPOBQXAM5hweZKrvzEByC77Rvowj2 iJpn8ccT6XZDR9QwXZBZTpHufptMWewItX47fZVJ7RpLYVbp/kUDXqas3 U=;
IronPort-PHdr: =?us-ascii?q?9a23=3ADHhEYh2DAJFlzF6qsmDT+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?A0AIAACjf8hc/51dJa1mGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGBPVADaVUgBAsohBCDRwOEUoo9gleXIoEuFIE?= =?us-ascii?q?QA1QOAQElCIRAAheGGiM0CQ4BAwEBBAEBAgECbRwMhUoBAQEDARIREQwBATc?= =?us-ascii?q?BCwYBCBEEAQEBAgImAgQwFQUDCgQBDQUigwABgWoDDg8BDqQCAoE1iF9xgS+?= =?us-ascii?q?CeQEBBYEyARNBgn8Ygg4DBoELJwGEYYZoF4FAP4ERJx+CTD6CYQIBAgGBKgE?= =?us-ascii?q?SAQ8XECECglAygiaLDII3mGZfCQKCCYYViFqDSxuCDYY3jGuDCYkFhSOBII4?= =?us-ascii?q?OAgQCBAUCDgEBBYFPOGVYEQhwFWUBgg0BM4IPDBcUgziFFIU/cgGBKJA+DRc?= =?us-ascii?q?HgiUBAQ?=
X-IronPort-AV: E=Sophos;i="5.60,414,1549929600"; d="scan'208";a="265578303"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Apr 2019 17:06:03 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x3UH62A9025051 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 30 Apr 2019 17:06:03 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 30 Apr 2019 12:06:02 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 30 Apr 2019 12:06:02 -0500
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 30 Apr 2019 12:06:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oyG4U8u3ZHgpHZUHSMbtOSr7Tl1RNYrBij9ben/Faq4=; b=MGYC54CU5RI9P/6se0heh/CMH17eOEjr87byLAxB5wUILkN1kWFwEyvPPVcSzblTfMDadXZh0O8CJ6UntLQlAxxVj5xw4TiVuNjCv+uPBU+xlVab8OjRvLPtzJBkuAnTM1PmbWZurDGoiwneRmkY+R8I6N/GXGU25nfUascRGoE=
Received: from DM5PR1101MB2105.namprd11.prod.outlook.com (10.174.104.15) by DM5PR1101MB2121.namprd11.prod.outlook.com (10.174.104.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.10; Tue, 30 Apr 2019 17:06:00 +0000
Received: from DM5PR1101MB2105.namprd11.prod.outlook.com ([fe80::a113:a1ba:aae0:4a12]) by DM5PR1101MB2105.namprd11.prod.outlook.com ([fe80::a113:a1ba:aae0:4a12%6]) with mapi id 15.20.1835.010; Tue, 30 Apr 2019 17:06:00 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "Eric Voit (evoit)" <evoit@cisco.com>, Alexander Clemm <ludwig@clemm.org>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "'The IESG'" <iesg@ietf.org>
CC: "draft-ietf-netconf-yang-push@ietf.org" <draft-ietf-netconf-yang-push@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>
Thread-Topic: =?utf-8?B?W25ldGNvbmZdICDDiXJpYyBWeW5ja2UncyBObyBPYmplY3Rpb24gb24gZHJh?= =?utf-8?Q?ft-ietf-netconf-yang-push-22:_(with_COMMENT)?=
Thread-Index: AQHU/3b8vQfuk8IrZECnJQ9aK8WPBw==
Date: Tue, 30 Apr 2019 17:06:00 +0000
Message-ID: <244A8033-612B-4A31-BA37-CDD4AF93502B@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.6.190114
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rrahman@cisco.com;
x-originating-ip: [2001:420:2840:1250:2421:2f0a:1dbc:638e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: df5477e8-0362-4fa2-23d2-08d6cd8e1ee3
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:DM5PR1101MB2121;
x-ms-traffictypediagnostic: DM5PR1101MB2121:
x-ms-exchange-purlcount: 4
x-ld-processed: 5ae1af62-9505-4097-a69a-c1553ef7840e,ExtAddr
x-microsoft-antispam-prvs: <DM5PR1101MB21217E02DAC59154308CDB52AB3A0@DM5PR1101MB2121.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 00235A1EEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(376002)(366004)(346002)(396003)(39860400002)(13464003)(189003)(199004)(316002)(99286004)(25786009)(305945005)(6306002)(54906003)(110136005)(6512007)(53936002)(7736002)(966005)(14454004)(97736004)(33656002)(14444005)(256004)(6436002)(86362001)(76116006)(229853002)(66946007)(66446008)(66476007)(66556008)(64756008)(6246003)(478600001)(4326008)(6486002)(91956017)(58126008)(6116002)(82746002)(2906002)(66574012)(36756003)(81166006)(68736007)(73956011)(8936002)(71200400001)(81156014)(71190400001)(224303003)(83716004)(186003)(46003)(5660300002)(6506007)(53546011)(476003)(2616005)(486006)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR1101MB2121; H:DM5PR1101MB2105.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: ha0aLgKlXAv9757qdy3RJbhn/QAQLUGoHgrV0OiUTXNsLYVNY578Hrvt2xtyyfUFFpb3Wd6HVgxZ9xfODt7IExUOwrZOUF5LmUj5p/f/Fe3V3/AwXyWT7stgkCPV07+ZYnWIAfkoeDjNMhgWImRqp4Vg4hYth0LEdenzOJK8sh2Bo0B7L4s129cWcQ6BeTRbAPt8wo9ZAuJPcqnEjRgioKoTco9htWU5j/zLkB6jYEVSS9F8vaKqQRusvPDDGzFmbUXkvJ7GWts99dSdnkbsNNELhLqtKVzifx4FtlPHfw7jszdJRFcKM+l53SdKlv6GWEnbw65EUoJC1R/xBt0MiVq/2smzMLlPgt8KMBBUi30a6CLklW/Y9VE662q4t3tZm4NgtEMxk3QbOU0g/hRfGyQmuH+Vrb9N0FD7IlVPhbw=
Content-Type: text/plain; charset="utf-8"
Content-ID: <10928D96A291924C8A0FB48F8FF710E0@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: df5477e8-0362-4fa2-23d2-08d6cd8e1ee3
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Apr 2019 17:06:00.6035 (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-Transport-CrossTenantHeadersStamped: DM5PR1101MB2121
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/gIbiyvbaKb-E6i1prcfOQoiilzY>
Subject: Re: [netconf] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-netconf-yang-push-22=3A_=28with_COMMENT=29?=
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, 30 Apr 2019 17:06:07 -0000

On 2019-04-30, 12:50 PM, "netconf on behalf of Eric Voit (evoit)" <netconf-bounces@ietf.org on behalf of evoit@cisco.com> wrote:

    > From: Alexander Clemm, April 30, 2019 12:33 PM
    > 
    > Hello Eric,
    > 
    > Thank you for your review!  Replies inline, <ALEX>
    > 
    > --- Alex
    > 
    > -----Original Message-----
    > From: Eric Vyncke (evyncke) <evyncke@cisco.com>
    > Sent: Monday, April 29, 2019 6:21 AM
    > To: The IESG <iesg@ietf.org>
    > Cc: netconf@ietf.org; draft-ietf-netconf-yang-push@ietf.org;
    > kent+ietf@watsen.net; netconf-chairs@ietf.org
    > Subject: Re: Éric Vyncke's No Objection on draft-ietf-netconf-yang-push-22:
    > (with COMMENT)
    > 
    > Please ignore my comment C3, my bad...
    > 
    > -éric
    > 
    > On 29/04/2019, 15:12, "iesg on behalf of Éric Vyncke via Datatracker" <iesg-
    > bounces@ietf.org on behalf of noreply@ietf.org> wrote:
    > 
    >     Éric Vyncke has entered the following ballot position for
    >     draft-ietf-netconf-yang-push-22: No Objection
    > 
    >     When responding, please keep the subject line intact and reply to all
    >     email addresses included in the To and CC lines. (Feel free to cut this
    >     introductory paragraph, however.)
    > 
    > 
    >     Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
    >     for more information about IESG DISCUSS and COMMENT positions.
    > 
    > 
    >     The document, along with other ballot positions, can be found here:
    >     https://datatracker.ietf.org/doc/draft-ietf-netconf-yang-push/
    > 
    > 
    > 
    >     ----------------------------------------------------------------------
    >     COMMENT:
    >     ----------------------------------------------------------------------
    > 
    >     Getting a streaming telemetry for changes in datastore appears quite useful.
    > 
    >     Please note that I did not review in depth after the section 4.
    > 
    >     Comments
    >     --------
    > 
    >     C1) Out of curiosity, it is surprising for a netconf wg document to have 7
    >     errors indicated by the YANG validator. Are they real errors or is the `pyang`
    >     validator incorrect or missing references?
    > 
    > <ALEX> There is a bug in the validator, which has been encountered for a while
    > and which Eric can explain.
    > </ALEX>
    
    The YANG validator errors are due to a solved bug in yanglint.   
    
    As Kent discusses in his "draft-ietf-netconf-subscribed-notifications" shepherd writeup, the errors clear with new versions of yanglint.
    https://datatracker.ietf.org/doc/draft-ietf-netconf-subscribed-notifications/shepherdwriteup/ 
    
       [SHEPHERD] `pyang` and `yanglint` were used to validate the YANG module 
       defined in this document.  Note that Datatracker shows YANG validation 
       errors, but the module validates fine on my machine (I'm using yanglint
       0.16.110, whereas DataTracker is using yanglint 0.14.80).
    
    Eric

It was fixed in 0.16.59
https://tools.ietf.org/tools/ietfdb/ticket/2667

Regards,
Reshad.