[Netconf] schema capabilities in hello

Mikael Abrahamsson <swmike@swm.pp.se> Wed, 09 May 2018 06:14 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E0E34126DFB for <netconf@ietfa.amsl.com>; Tue, 8 May 2018 23:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 8aEloFl90e-Y for <netconf@ietfa.amsl.com>; Tue, 8 May 2018 23:14:47 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EE84126DED for <netconf@ietf.org>; Tue, 8 May 2018 23:14:47 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id DF57CB1; Wed, 9 May 2018 08:14:44 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1525846484; bh=81x66sZARc8WZzAFgd9JLA1zwm+JYMxa4IODzbDIyIY=; h=Date:From:To:Subject:From; b=J1qtnB/VK3JmQxJHHBRfQZnQrff/QoB9K3be3XLKxK1dlRIZuZKT5+8nA6nXlytJ2 MHsOKnA0FM8z0KEkFJQOV5MFrleHUK27okZrSztJD51cpRMiY9RjXP1m78OsL0RNRo W5NZ5cfCOUQHmFj9lnmVloRGlxHO4JNoQCcHvGfQ=
Received: from localhost (localhost []) by uplift.swm.pp.se (Postfix) with ESMTP id DD7B9B0 for <netconf@ietf.org>; Wed, 9 May 2018 08:14:44 +0200 (CEST)
Date: Wed, 09 May 2018 08:14:44 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: netconf@ietf.org
Message-ID: <alpine.DEB.2.20.1805090811240.17103@uplift.swm.pp.se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/acGonnFyThZwyJ23siQqZiRAzag>
Subject: [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:14:50 -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.

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.


Mikael Abrahamsson    email: swmike@swm.pp.se