Re: [Netconf] schema capabilities in hello

Martin Bjorklund <mbj@tail-f.com> Wed, 09 May 2018 06:50 UTC

Return-Path: <mbj@tail-f.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 ABAA21270A0 for <netconf@ietfa.amsl.com>; Tue, 8 May 2018 23:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 jFKZxQlRjKgG for <netconf@ietfa.amsl.com>; Tue, 8 May 2018 23:50:35 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0B892126CC7 for <netconf@ietf.org>; Tue, 8 May 2018 23:50:35 -0700 (PDT)
Received: from localhost (unknown [173.38.220.61]) by mail.tail-f.com (Postfix) with ESMTPSA id 1999E1AE0442; Wed, 9 May 2018 08:50:34 +0200 (CEST)
Date: Wed, 09 May 2018 08:50:33 +0200
Message-Id: <20180509.085033.1181724067721347729.mbj@tail-f.com>
To: swmike@swm.pp.se
Cc: janl@tail-f.com, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <alpine.DEB.2.20.1805090827570.17103@uplift.swm.pp.se>
References: <alpine.DEB.2.20.1805090811240.17103@uplift.swm.pp.se> <64CFE210-421F-4C2E-9FD5-A3FEFE01929A@tail-f.com> <alpine.DEB.2.20.1805090827570.17103@uplift.swm.pp.se>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/1JU8KjZA6vnYb2KRHyPOuZve_ds>
Subject: Re: [Netconf] schema capabilities in hello
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: Wed, 09 May 2018 06:50:36 -0000

Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Wed, 9 May 2018, Jan Lindblad wrote:
> 
> > NETCONF does not require this, but YANG 1.0 does. See RFC 6020 sec
> > 5.6.4.
> 
> Thanks.
> 
> > Right. This development has been noted by the NETCONF and NETMOD WGs
> > as well, so in YANG 1.1 this is radically changed. Instead of listing
> > all namespaces in hello, they are listed in a YANG data structure
> > called ietf-yang-library. See RFC 7950 sec 5.6.4 and RFC 7895.
> 
> So if an NMS only supporting YANG 1.0 connects to a device that
> supports YANG 1.1, and this NMS relies on the schemas being listed in
> the hello, who's wrong here?

Noone is wrong.  The YANG 1.0-only NMS won't understand the 1.1
modules in the server anyway.  Note that if the server implements a
mix of 1.0 and 1.1 modules, all 1.0 modules MUST be listed in
<hello>.


/martin