IETF Logo Mail Archive

[netconf] NACM and draft-ietf-netconf-notification-capabilities-07

Benoit Claise <bclaise@cisco.com> Mon, 18 November 2019 09:34 UTC

Return-Path: <bclaise@cisco.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 0CE9F1208A9 for <netconf@ietfa.amsl.com>; Mon, 18 Nov 2019 01:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 UuGyAXVYjYLl for <netconf@ietfa.amsl.com>; Mon, 18 Nov 2019 01:34:50 -0800 (PST)
Received: from bgl-iport-3.cisco.com (bgl-iport-3.cisco.com [72.163.197.27]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E50FD1201DB for <netconf@ietf.org>; Mon, 18 Nov 2019 01:34:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2287; q=dns/txt; s=iport; t=1574069690; x=1575279290; h=to:cc:from:subject:message-id:date:mime-version; bh=QT3zytfXjHeTrq1qGfd6K8yBMA5noEknr0UYtT7fGLc=; b=TET0NsV1mYN1h/UQ0aUwyGind9ILUKL197xkRM+jB078xqa4+FYwYDAW R6WpBIUvu11SsaobKl2XU3Oqg+A7linixMBpgvJpeqzAgIofgiNxri9sL IPM8gMZ/K4ALa3ksZjnWfSIE2ILxysv2xXbQTO/eQZSGzAZrODqHelWtH w=;
X-IronPort-AV: E=Sophos; i="5.68,319,1569283200"; d="scan'208,217"; a="98465561"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 18 Nov 2019 09:34:47 +0000
Received: from [10.68.221.200] ([10.68.221.200]) (authenticated bits=0) by bgl-core-4.cisco.com (8.15.2/8.15.2) with ESMTPSA id xAI9YhkX019628 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Mon, 18 Nov 2019 09:34:47 GMT
To: Balazs Lengyel <balazs.lengyel@ericsson.com>
Cc: "Robert Wilton -X (rwilton - Ensoft Ltd at Cisco)" <rwilton@cisco.com>, NETCONF <netconf@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <71259b42-2e44-7584-36af-6eaa860c41cf@cisco.com>
Date: Mon, 18 Nov 2019 17:34:43 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------0998BC4B6C528AFB0307CB91"
Content-Language: en-US
X-Authenticated-User: bclaise
X-Outbound-SMTP-Client: 10.68.221.200, [10.68.221.200]
X-Outbound-Node: bgl-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/S-EJ27JdAEmw8prvABSBwu8xh8w>
Subject: [netconf] NACM and draft-ietf-netconf-notification-capabilities-07
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG 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: Mon, 18 Nov 2019 09:34:52 -0000

Dear all,

Coming back to Rob Wilton's message at the mike about NACM reference to 
draft-ietf-netmod-rfc6991-bis-02 
<https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc6991-bis/>
 From draft-ietf-netconf-notification-capabilities-07

    import ietf-netconf-acm  { prefix nacm; }
    import ietf-yang-push    {
      prefix yp;
      description
        "This module requires ietf-yang-push to be implemented.";
    }

Along the same lines, I believe it makes sense to add "This module does 
not require NACM to be implemented."

Thinking some more about it... Actually, I don't like "This module 
requires ietf-yang-push to be implemented."
What if I want to implement this draft for gRPC and not YANG-push?
This capability should be independent of the streaming protocol IMO

Regards, Benoit

v2.23.0 | Report a Bug | By Email