Re: [netmod] Query on Announcing Conformance Information in the <hello> Message

Martin Bjorklund <mbj@tail-f.com> Tue, 02 May 2017 08:29 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 363F81314F5 for <netmod@ietfa.amsl.com>; Tue, 2 May 2017 01:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level:
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001, 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 0IBZkCcY7XAg for <netmod@ietfa.amsl.com>; Tue, 2 May 2017 01:29:23 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA7C12EC6E for <netmod@ietf.org>; Tue, 2 May 2017 01:24:58 -0700 (PDT)
Received: from localhost (unknown [173.38.220.40]) by mail.tail-f.com (Postfix) with ESMTPSA id 823341AE028F; Tue, 2 May 2017 10:24:56 +0200 (CEST)
Date: Tue, 02 May 2017 10:25:09 +0200
Message-Id: <20170502.102509.1924138814149890711.mbj@tail-f.com>
To: nite@hq.sk
Cc: andy@yumaworks.com, dhirutrivedi@gmail.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <638dd25c-909e-1d07-78f0-76e1e75549dc@hq.sk>
References: <CAPSfq0bBHjfn7PgcoBqQVRK8Fupfz+UA3kOZWWJS=9WENN5=vw@mail.gmail.com> <CABCOCHR9iiLniaF2Nw6n4q-1xQqRrr_Y6QuMr=f2uAbCM=iPuw@mail.gmail.com> <638dd25c-909e-1d07-78f0-76e1e75549dc@hq.sk>
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/netmod/FcseqgXgdNhOb3k_BgN1aa8By5M>
Subject: Re: [netmod] Query on Announcing Conformance Information in the <hello> Message
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 May 2017 08:29:26 -0000

Robert Varga <nite@hq.sk> wrote:
> On 20/04/17 18:35, Andy Bierman wrote:
> > 
> > Yes -- it looks correct.
> > The structure is defined in RFC 6020:
> > https://tools.ietf.org/html/rfc6020#section-5.6.4
> > 
> 
> Hello Andy,
> 
> One thing that is not quite clear in RFC6020 due to not being clear what
> 'supported module' means.

Right; specifically the difference between "implement" and "support
for import", which is clarified in RFC 7950 and RFC 7895.

> Should deviations be applied in case a module is advertised, but is not
> mentioned in a deviations parameter like this:

No.

>    <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
>        <capability>
>          http://example.com/syslog?module=syslog
>        </capability>
>        <capability>
>          http://example.com/my-deviations?module=my-devs
>        </capability>
>      </hello>
> 
> If not, does this imply that any deviation statement targeting an
> external module, which does not have a matching deviations parameter
> should silently be ignored?

Yes.  Just like a grouping can be defined without ever being used.

For example, a device might put all its deviations in a
single module, but then list it in the deviations parameter for a
subset of all potential modules.


/martin