Re: [Netconf] schema capabilities in hello

Jan Lindblad <> Wed, 09 May 2018 06:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7241112D879 for <>; Tue, 8 May 2018 23:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fL64BKIVXxGb for <>; Tue, 8 May 2018 23:22:47 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CD42C126DED for <>; Tue, 8 May 2018 23:22:46 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTPSA id 0425E1AE034F; Wed, 9 May 2018 08:22:44 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Jan Lindblad <>
In-Reply-To: <>
Date: Wed, 09 May 2018 08:22:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Mikael Abrahamsson <>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <>
Subject: Re: [Netconf] schema capabilities in hello
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 May 2018 06:22:48 -0000


> I received a question I couldn't answer. It was regarding capabilities exchange in hellos:
> It seems common way of doing this is to list all schemas as "capabilties". The person asking the question said one vendor did not list all schemas in capabilities, and one NMS they were trying out relied on the schemas being listed in the hello, for discovery.
> Looking at above URL from the NETCONF RFC, one might imply that it only talks about netconf capabilities, not what schemas it supports. Yet, most implementations seem to list all schemas in their hellos.

NETCONF does not require this, but YANG 1.0 does. See RFC 6020 sec 5.6.4.

> So which one is correct here? My immediate reaction is that it's kind of "bloated" to list 1000 schemas (or more) in the hello, and that the schemas supported is something that shouldn't need to be exchanged every time one connects to the device.

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.