IETF Logo Mail Archive

Re: [Netconf] NETCONF Notification - Yang support

"Eric Voit (evoit)" <evoit@cisco.com> Thu, 20 April 2017 22:18 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 9147E1316EA for <netconf@ietfa.amsl.com>; Thu, 20 Apr 2017 15:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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
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 S_6WEc9gcSvT for <netconf@ietfa.amsl.com>; Thu, 20 Apr 2017 15:18:54 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADD8128799 for <netconf@ietf.org>; Thu, 20 Apr 2017 15:18:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14821; q=dns/txt; s=iport; t=1492726734; x=1493936334; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xJrQVCnszGtOJ+72ja21/w/Z08sL9QSMmWBWzAxaj34=; b=lA2Tjr5Jl0Rv/KS7LpgVMG7gkhTotjyyhVcePxebfESpQLIUU1h18OUC 01aZqAGiosUXM43nuvoZDHpWcLA68nATA3neOCyj9VSsCvH5cd76YT+WM WosPeJYamByC5iyMjTU9txkpbvtTyDWcHK/AbiGjHqyJYcyu6Tk8gkPIV k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DjAAD9MvlY/4oNJK1dGQEBAQEBAQEBAQEBBwEBAQEBgm5mYYEMB411kWiQLoU1gg8uhXYCg30/GAECAQEBAQEBAWsdC4UVAQEBAQMtSgIQAgEIEQQBASgHMhQJCAEBBA4FCAGKEw6sOYsiAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZThHaEQSQohS8FlkCGdAGHFItlggmFM4oilBMBHziBBWMVhyl1AYgggQ0BAQE
X-IronPort-AV: E=Sophos;i="5.37,227,1488844800"; d="scan'208,217";a="415349133"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Apr 2017 22:18:52 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v3KMIqIt004712 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Apr 2017 22:18:52 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Apr 2017 18:18:51 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1210.000; Thu, 20 Apr 2017 18:18:51 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "Vasudevan.Sridharan@us.fujitsu.com" <Vasudevan.Sridharan@us.fujitsu.com>
CC: "Sanjay.Gera@us.fujitsu.com" <Sanjay.Gera@us.fujitsu.com>, "Jing.Xu@us.fujitsu.com" <Jing.Xu@us.fujitsu.com>, "david.terwilliger@us.fujitsu.com" <david.terwilliger@us.fujitsu.com>, "netconf@ietf.org" <netconf@ietf.org>, "netconf@ops.ietf.org" <netconf@ops.ietf.org>
Thread-Topic: NETCONF Notification - Yang support
Thread-Index: AdK6GDAirR2YMDiwQTO3/oeu9sXuOAAAWT0QAACWEKAAAb7TwA==
Date: Thu, 20 Apr 2017 22:18:51 +0000
Message-ID: <c611dbbe42534524b63aa5cadd79f1ef@XCH-RTP-013.cisco.com>
References: <84987e7634e842f790f1332caee7257c@g05usexrtxa05.g05.fujitsu.local> <8a0f4aa3d7e348c48ca33ed0a5cd41da@XCH-RTP-013.cisco.com> <e8028c2167c440dc885570ca6813a7ca@g05usexrtxa05.g05.fujitsu.local>
In-Reply-To: <e8028c2167c440dc885570ca6813a7ca@g05usexrtxa05.g05.fujitsu.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.226]
Content-Type: multipart/alternative; boundary="_000_c611dbbe42534524b63aa5cadd79f1efXCHRTP013ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/pZ6hxaMEd9af8nDfuS4xH2rEIYU>
Subject: Re: [Netconf] NETCONF Notification - Yang support
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing 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, 20 Apr 2017 22:18:58 -0000

If I am reading your thread right, you are looking at models like:
http://www.netconfcentral.org/modules/nc-notifications/2008-07-14
and seeing if they have been standardized.   They have not.

As RFC 5277 predated yang, there is no yang-model.  But
"urn:ietf:params:netconf:capability:notification:1.0"
Is still advertised.  This is not an issue.

https://datatracker.ietf.org/doc/draft-ietf-netconf-subscribed-notifications/
will eventually advertise:
"urn:ietf:params:netconf:capability:notification:2.0"
with a yang model behind it.

Eric

From: Vasudevan.Sridharan@us.fujitsu.com [mailto:Vasudevan.Sridharan@us.fujitsu.com]
Sent: Thursday, April 20, 2017 5:39 PM
To: Eric Voit (evoit) <evoit@cisco.com>
Cc: Sanjay.Gera@us.fujitsu.com; Jing.Xu@us.fujitsu.com; david.terwilliger@us.fujitsu.com; netconf@ietf.org; netconf@ops.ietf.org
Subject: RE: NETCONF Notification - Yang support

Eric,

Thanks for the quick response. My question is more of a basic one - If a NETCONF server advertises a capability in hello exchange, is it necessary to have a yang implementation to support the advertised capability?

I don't see this in RFC5277 (may be because it was standardized before yang RFC came into picture).

I see this as a requirement in https://tools.ietf.org/html/rfc6243#section-4.1

Thanks,
Vasu.

From: Eric Voit (evoit) [mailto:evoit@cisco.com]
Sent: Thursday, April 20, 2017 4:08 PM
To: Sridharan, Vasudevan <Vasudevan.Sridharan@us.fujitsu.com<mailto:Vasudevan.Sridharan@us.fujitsu.com>>
Cc: Gera, Sanjay <Sanjay.Gera@us.fujitsu.com<mailto:Sanjay.Gera@us.fujitsu.com>>; Xu, Jing <Jing.Xu@us.fujitsu.com<mailto:Jing.Xu@us.fujitsu.com>>; Terwilliger, David <david.terwilliger@us.fujitsu.com<mailto:david.terwilliger@us.fujitsu.com>>; netconf@ietf.org<mailto:netconf@ietf.org>; netconf@ops.ietf.org<mailto:netconf@ops.ietf.org>
Subject: RE: NETCONF Notification - Yang support

Hi Vasudevan,

Have you looked yet at:
https://datatracker.ietf.org/doc/draft-ietf-netconf-subscribed-notifications/
This is on a path to obsolete RFC-5277.

Also there is work discussed at the last IETF:
https://tools.ietf.org/html/draft-voit-netmod-yang-notifications2-00
is this hitting the areas in which you are asking?

Eric

From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Vasudevan.Sridharan@us.fujitsu.com<mailto:Vasudevan.Sridharan@us.fujitsu.com>
Sent: Thursday, April 20, 2017 4:59 PM
To: netconf@ietf.org<mailto:netconf@ietf.org>; netconf@ops.ietf.org<mailto:netconf@ops.ietf.org>
Cc: Sanjay.Gera@us.fujitsu.com<mailto:Sanjay.Gera@us.fujitsu.com>; Jing.Xu@us.fujitsu.com<mailto:Jing.Xu@us.fujitsu.com>; david.terwilliger@us.fujitsu.com<mailto:david.terwilliger@us.fujitsu.com>
Subject: [Netconf] NETCONF Notification - Yang support

Hi Authors,

I 'm looking at the notifications.yang and nc-notifications.yang. Is this standardized?

RFC5277 (which predates Yang RFC6020) doesn't mention of the any yang for notifications. So can you please guide me on the status of this yang. Is a NETCONF server/client compliant with RFC5277 expected to support this yang for schema discovery or is it an inherent capability as part of "urn:ietf:params:netconf:capability:notification:1.0" capability?

Thanks a lot in advance for the response.

Thanks,
Vasudevan Sridharan.

v2.23.0 | Report a Bug | By Email