IETF Logo Mail Archive

Re: [Netconf] NETCONF Notification - Yang support

"Vasudevan.Sridharan@us.fujitsu.com" <Vasudevan.Sridharan@us.fujitsu.com> Thu, 20 April 2017 21:39 UTC

Return-Path: <Vasudevan.Sridharan@us.fujitsu.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 D7F53129C60 for <netconf@ietfa.amsl.com>; Thu, 20 Apr 2017 14:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.89
X-Spam-Level:
X-Spam-Status: No, score=-6.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 OkRO0VG9g-7V for <netconf@ietfa.amsl.com>; Thu, 20 Apr 2017 14:39:00 -0700 (PDT)
Received: from fncnmp03.fnc.fujitsu.com (fncnmp03.fnc.fujitsu.com [168.127.0.56]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F6FB129459 for <netconf@ietf.org>; Thu, 20 Apr 2017 14:39:00 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="5.37,227,1488866400"; d="scan'208,217"; a="90631916"
Received: from unknown (HELO g05usexrtxa03.g05.fujitsu.local) ([168.127.194.63]) by fncnmp01.fnc.fujitsu.com with ESMTP/TLS/AES256-SHA; 20 Apr 2017 16:39:01 -0500
Received: from g05usexrtxa05.g05.fujitsu.local (168.127.194.65) by g05usexrtxa03.g05.fujitsu.local (168.127.194.63) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 20 Apr 2017 16:38:59 -0500
Received: from g05usexrtxa05.g05.fujitsu.local ([168.127.194.65]) by g05usexrtxa05.g05.fujitsu.local ([168.127.194.65]) with mapi id 15.00.1178.000; Thu, 20 Apr 2017 16:38:59 -0500
From: "Vasudevan.Sridharan@us.fujitsu.com" <Vasudevan.Sridharan@us.fujitsu.com>
To: "Eric Voit (evoit)" <evoit@cisco.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/oeu9sXuOAAAWT0QAACWEKA=
Date: Thu, 20 Apr 2017 21:38:59 +0000
Message-ID: <e8028c2167c440dc885570ca6813a7ca@g05usexrtxa05.g05.fujitsu.local>
References: <84987e7634e842f790f1332caee7257c@g05usexrtxa05.g05.fujitsu.local> <8a0f4aa3d7e348c48ca33ed0a5cd41da@XCH-RTP-013.cisco.com>
In-Reply-To: <8a0f4aa3d7e348c48ca33ed0a5cd41da@XCH-RTP-013.cisco.com>
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: [168.127.136.253]
x-tm-as-product-ver: SMEX-11.0.0.1191-8.100.1062-23020.003
x-tm-as-result: No--14.197200-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_e8028c2167c440dc885570ca6813a7cag05usexrtxa05g05fujitsu_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/eQWEXZo4A1_2Jk6awBK0CmbBBxc>
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 21:39:03 -0000

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>
Cc: Gera, Sanjay <Sanjay.Gera@us.fujitsu.com>; Xu, Jing <Jing.Xu@us.fujitsu.com>; Terwilliger, David <david.terwilliger@us.fujitsu.com>; netconf@ietf.org; 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