IETF Logo Mail Archive

Re: [Netconf] Anyone want just Configured Subscriptions?

"Eric Voit (evoit)" <evoit@cisco.com> Mon, 09 July 2018 03: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 388AD130EF7 for <netconf@ietfa.amsl.com>; Sun, 8 Jul 2018 20:05:13 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 jJbjXJxMzIkj for <netconf@ietfa.amsl.com>; Sun, 8 Jul 2018 20:05:11 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D37EA130EF5 for <netconf@ietf.org>; Sun, 8 Jul 2018 20:05:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10944; q=dns/txt; s=iport; t=1531105510; x=1532315110; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=TL6RzWdo5P6HHjTBrNIlBVrCXJqo54KlSIPAMuC9waI=; b=PQYEQwvoilSrjnATEBb4NneilHRlFG27Kpdcej3lLRueB30r2kmb4vbc tvk8gWWnUm/XApnDpCpvCGZtnQPpe+6vwhcM//J6+3VINCF0CeAuJJ6SX Ik1MihNNBqBVLsyZ6ZQo8Ffi4Ji9W0NRG2p4f/zsyBpaMKJLZcmGBxfih 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CoAAB9z0Jb/4kNJK1bGQEBAQEBAQEBAQEBAQcBAQEBAYJTdmJ/KAqDcIgEjDSCB5AkhQ6BeguEbAIXghYhNBgBAgEBAgEBAm0ohTYBAQEBAyMKTBACAQgQBQMNGgMCAgIwFBECBAENBQiDGYEbZKkLghyIRoE6iG6BVj+DcC6FCCiCS4JVApFqh2UJAohqhjCNZZFpAhETAYEkHTiBUnAVgySQUQFvjQgFgSmBGgEB
X-IronPort-AV: E=Sophos;i="5.51,328,1526342400"; d="scan'208,217";a="420781828"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jul 2018 03:05:09 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w69359Cq028139 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Jul 2018 03:05:09 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sun, 8 Jul 2018 23:05:08 -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; Sun, 8 Jul 2018 23:05:08 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Andy Bierman <andy@yumaworks.com>, Martin Bjorklund <mbj@tail-f.com>
CC: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Netconf <netconf@ietf.org>
Thread-Topic: [Netconf] Anyone want just Configured Subscriptions?
Thread-Index: AQHUFdzoQxUMgGR6+EyEsUfGkX4eo6SD/RKAgABHKwCAAA3RgIAA6BaAgAAi8ACAAGVWAIAABZ+AgABuS9A=
Date: Mon, 09 Jul 2018 03:05:08 +0000
Message-ID: <9c3799f19cf84b22a3659c04a548ba67@XCH-RTP-013.cisco.com>
References: <CABCOCHSfzpj3Kca2RRtNFV6wLLt_6r4p3vfS_j4Hzfai-0Y2gA@mail.gmail.com> <20180708.095807.918450792556408986.mbj@tail-f.com> <20180708100310.gn3xaol66f7c7lo5@anna.jacobs.jacobs-university.de> <20180708.180552.1582913595227099806.mbj@tail-f.com> <CABCOCHQfirYPAVJwLELnqw0VJ=js7aFNX9wB7Xcs6Tkw06w1hw@mail.gmail.com>
In-Reply-To: <CABCOCHQfirYPAVJwLELnqw0VJ=js7aFNX9wB7Xcs6Tkw06w1hw@mail.gmail.com>
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.230]
Content-Type: multipart/alternative; boundary="_000_9c3799f19cf84b22a3659c04a548ba67XCHRTP013ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/5sH77j50ydYA4HB3YiRYHmnaYYc>
Subject: Re: [Netconf] Anyone want just Configured Subscriptions?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 09 Jul 2018 03:05:14 -0000

Hi Andy,

From: Andy Bierman, July 8, 2018 12:26 PM

On Sun, Jul 8, 2018 at 9:05 AM, Martin Bjorklund <mbj@tail-f.com<mailto:mbj@tail-f.com>> wrote:
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>> wrote:
> On Sun, Jul 08, 2018 at 09:58:07AM +0200, Martin Bjorklund wrote:
> > Andy Bierman <andy@yumaworks.com<mailto:andy@yumaworks.com>> wrote:
> > >
> > > You mean <start-all-configured-subscriptions> I think.
> >
> > Yes.
> >
>
> If you do this, why does the client, after receiving a call home, not
> simply create dynamic subscriptions? ;-)

Well, the configured subscription is needed anyway in order for the
device to call home, so having the client create all configured
subscriptions as dynamic subscriptions as well doesn't seem quite
right.

It is quite possible that multiple RPC operations are needed to get the session
started, such as reading the YANG library, and that the client
is not ready to receive notifications as soon as the session is started.
So an <activate-configured-sessions> operation may help.


But if the WG agrees that it is ok to send <notification> directly,
this issue goes away.

Sitting idle is definitely OK.
Accepting notifications right away is OK as an implementation feature
outside the standard.

<Eric> If the NETCONF-Notif says that the NETCONF client for a configured subscription must be able to handle accepting notifications right away, do you see any standardization issue with this behavior in this context?

Eric

/martin

Andy

v2.23.0 | Report a Bug | By Email