IETF Logo Mail Archive

Re: [Netconf] configured subscriptions over netconf and restconf

"Eric Voit (evoit)" <evoit@cisco.com> Fri, 20 July 2018 19:05 UTC

Return-Path: <evoit@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 4E677131149 for <netconf@ietfa.amsl.com>; Fri, 20 Jul 2018 12:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 5NaGTJHYnYem for <netconf@ietfa.amsl.com>; Fri, 20 Jul 2018 12:05:52 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1547C13110E for <netconf@ietf.org>; Fri, 20 Jul 2018 12:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2300; q=dns/txt; s=iport; t=1532113552; x=1533323152; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=arWnJ+3Bd+b+3uhT8wWPvZMtpXebzotrulJp7nZwk00=; b=g0zTGUX1r6dtBd1Go6ibYQx9Yq5bJjIDX4RsjZ1Pi4zR4UYgxZidNlaW mVWuklaXn27i00JeyKw1vOxY0l4eD/fGfPRR3o2vZyGsvr4Rwno4MQAap 4uci2uTc0dmdyzWgdF5NHaiXDk7I95yRrgp3p1JI7AcLlRPNZM3SiM3gY 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CmAACNMVJb/4MNJK1ZAxkBAQEBAQEBAQEBAQEHAQEBAQGDTWN/KAqLeIwyggyVPIF6CxgLhANGAoMMITQYAQIBAQIBAQJtHAyFNgEBAQEDAQE4NBcCAgIBCA4CAQQBAQ0SEBsMCx0IAgQBEgiDGYF/D60WilAFBYh9gVc/g3QugxkBAYIBJoUPAplsCQKPJo16kXoCERSBJB04gVJwFTuCaYY0hGGFPm+MCIEbAQE
X-IronPort-AV: E=Sophos;i="5.51,380,1526342400"; d="scan'208";a="426792091"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jul 2018 19:05:51 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id w6KJ5ojW021920 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 20 Jul 2018 19:05:51 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 20 Jul 2018 15:05:50 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1320.000; Fri, 20 Jul 2018 15:05:50 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] configured subscriptions over netconf and restconf
Thread-Index: AQHUIBDRFxKMAIeyfUGDXpoj+uZquaSYdTvQ
Date: Fri, 20 Jul 2018 19:05:50 +0000
Message-ID: <ba396886645f4495a34aba663ec89dad@XCH-RTP-013.cisco.com>
References: <20180720100229.7ndhp74ylb53tmgh@anna.jacobs.jacobs-university.de>
In-Reply-To: <20180720100229.7ndhp74ylb53tmgh@anna.jacobs.jacobs-university.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.152, xch-rtp-012.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/LGGipaNZy5CjU1W3N5zznrEbgP0>
Subject: Re: [Netconf] configured subscriptions over netconf and restconf
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 20 Jul 2018 19:06:00 -0000

Some thoughts on the business need:

- Configured subscriptions over RESTCONF is not something of interest to me.

- I have not seen many requests for configured subscriptions over NETCONF.   Like Kent, we are prepared to implement these if given a business case.

- What we do have in production is multiple variants of configured subscriptions over proprietary transport. 

- On past threads, Henk has stated he needs configured subscriptions standardized now for non-NC/RC transports.  (So progressing configured in SN makes sense.)

So I completely agree with your premise below.  In fact, this was option A2 during Monday's WG meeting.  To support this, we have already scoped out the document changes which would be needed to correspondingly reduce the scope of NETCONF-Notif to just dynamic subscriptions.

Eric

> -----Original Message-----
> From: Netconf <netconf-bounces@ietf.org> On Behalf Of Juergen
> Schoenwaelder
> Sent: Friday, July 20, 2018 6:02 AM
> To: netconf@ietf.org
> Subject: [Netconf] configured subscriptions over netconf and restconf
> 
> Hi,
> 
> thinking more about this, I wonder who is interested (in the sense I am
> implementing this) in configured subscriptions over NETCONF and
> RESTCONF (SSE - not some new HTTP/2 transport, which is not RESTCONF).
> 
> It could be that NC and RC clients are just fine with doing dynamic
> subscriptions (since they can) and configured subscriptions essentially exist
> to use notification streaming protocols that themself have no way to
> dynamically subscribe. If this would be true, then defining a transport for
> configured subscriptions over plain NC and RC seems like a waste of effort.
> Then I would rather be specific that configured subscriptions are for non
> NC/RC transports and remove the text how to make configured
> subscriptions work with NC/RC.
> 
> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email