Re: [netconf] RFC 8639 configured subscriptions

Michal Vaško <mvasko@cesnet.cz> Tue, 09 March 2021 06:51 UTC

Return-Path: <mvasko@cesnet.cz>
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 917EF3A1493 for <netconf@ietfa.amsl.com>; Mon, 8 Mar 2021 22:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cesnet.cz
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 SDktwdv0uxzy for <netconf@ietfa.amsl.com>; Mon, 8 Mar 2021 22:51:04 -0800 (PST)
Received: from kalendar.cesnet.cz (kalendar.cesnet.cz [IPv6:2001:718:1:1f:50:56ff:feee:34]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 417A23A149B for <netconf@ietf.org>; Mon, 8 Mar 2021 22:51:04 -0800 (PST)
Received: by kalendar.cesnet.cz (Postfix, from userid 110) id 3F8C76007E; Tue, 9 Mar 2021 07:50:57 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=kalendar; t=1615272657; bh=Ynnq6+uV0wUgV1EIN6v7NT704wIoS6hvc/Nb7CNqUwI=; h=From:In-Reply-To:Date:Cc:To:Subject; b=F5iItILE+q0N+eN1XOuyD6IYswhD6oqsWKeejvrvN0/xYlkhE424UP/i934c3olZh iRQn6t/BWl7EAZilu6c7LQ1F8Wvi06aG7VHb24RnKCkW9IvucVHYaNMeWRcoNSkj3/ 4FuETn1ACPHhIxDyvUwXvWyEWsFC7ySd0ObxuRVs=
From: =?utf-8?q?Michal_Va=C5=A1ko?= <mvasko@cesnet.cz>
In-Reply-To: <BL0PR11MB31227C530D0F4303E12D89DBA1939@BL0PR11MB3122.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
X-Forward: 84.42.188.124
Date: Tue, 09 Mar 2021 07:50:57 +0100
Cc: "netconf" <netconf@ietf.org>
To: "Eric Voit (evoit)" <evoit@cisco.com>
MIME-Version: 1.0
Message-ID: <3bf7-60471b00-55-203315c0@163861349>
User-Agent: SOGoMail 5.0.1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/6LgGz5l9aKowBZGy9VrRiE3Wt-I>
Subject: Re: [netconf] =?utf-8?q?RFC_8639_configured_subscriptions?=
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: Tue, 09 Mar 2021 06:51:09 -0000

Hi Eric,

I appreciate the help but what is the official situation then? NETCONF/RESTCONF has RFCs only for dynamic subscriptions so for these protocols configured subscriptions are not supported? Actually, there are no protocols that support it, currently?

Michal

On Monday, March 08, 2021 18:06 CET, "Eric Voit (evoit)" <evoit@cisco.com> wrote: 
 
> Hi Michal,
> 
> Configured subscriptions for NETCONF was originally in RFC-8640.  But the
> draft was rescoped to just dynamic subscriptions by the time it was
> published.  
> 
> So it might be worth looking through:
> https://tools.ietf.org/html/draft-ietf-netconf-netconf-event-notifications-1
> 0
> This version does include the module you request below.  Also included is
> other text which might be of interest.
> 
> Eric
> 
> 
> > -----Original Message-----
> > From: netconf <netconf-bounces@ietf.org> On Behalf Of Michal Vaško
> > Sent: Monday, March 8, 2021 10:17 AM
> > To: netconf <netconf@ietf.org>
> > Subject: [netconf] RFC 8639 configured subscriptions
> > 
> > Hi,
> > 
> > we want to implement both dynamic and configured subscriptions for a
> > NETCONF server. Reading through the RFC, it is pretty clear that the
> configured
> > subscriptions require a YANG module with NETCONF-specific parameters
> > including a "netconf" identity derived from the "transport" identity (juts
> like the
> > "foo" example[1]). We have not managed to find such a module, does it
> exist? If
> > not, could someone provide some more information about how it can be
> > implemented? Thank you.
> > 
> > Regards,
> > Michal
> > 
> > [1] https://tools.ietf.org/html/rfc8639#appendix-A
> > 
> > _______________________________________________
> > netconf mailing list
> > netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf