IETF Logo Mail Archive

Re: [Netconf] Anyone want just Configured Subscriptions?

"Eric Voit (evoit)" <evoit@cisco.com> Tue, 10 July 2018 22:27 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 6BF6B131196 for <netconf@ietfa.amsl.com>; Tue, 10 Jul 2018 15:27:29 -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 PtTJ2Qxwx-Dr for <netconf@ietfa.amsl.com>; Tue, 10 Jul 2018 15:27:27 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D966130E86 for <netconf@ietf.org>; Tue, 10 Jul 2018 15:27:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2636; q=dns/txt; s=iport; t=1531261645; x=1532471245; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=O4vHKW7vUVCbDTNKdppK6o/DL6RY1Cjf54G8130k4NE=; b=bbguLZj/lARoUVPHk9pvve0fAX20+ZQuZCeDVaLFbYfSye/lpeGwi1uV x1tId48kJfb5QpFFVUIn9xNFVLa2d09+dBa/IwL3BvrJ/zgaHXsVDDyMq 3NwgHy7KB1RIvWlomSQQjKftbD+Mr1d1Wr6RJ82Gb0Qz8g2RUOV6sMUEt M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CMAgAVMkVb/4MNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYNJY38oCoNwiASMOIIKgziReoF6CxgLhANGAheCEyE0GAECAQECAQECbRwMhTYBAQEDAQEBIRETJwsFCwIBCA4HAwICCR0CAgIlCxUQAgQBDQUIgxmBdwgPqwaBLoMlhSqBMwWBC4dugVc/g3MugxkBAYFKLYJqglUCmVIJAo8cjWiRawIREwGBJB04gVJwFTuCaYsVhT5vjDWBGgEB
X-IronPort-AV: E=Sophos;i="5.51,335,1526342400"; d="scan'208";a="140698477"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jul 2018 22:27:24 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w6AMROPa023685 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 10 Jul 2018 22:27:24 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 10 Jul 2018 18:27:24 -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; Tue, 10 Jul 2018 18:27:24 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Lou Berger <lberger@labn.net>, Kent Watsen <kwatsen@juniper.net>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Netconf <netconf@ietf.org>
Thread-Topic: [Netconf] Anyone want just Configured Subscriptions?
Thread-Index: AQHUFdzoQxUMgGR6+EyEsUfGkX4eo6SD/RKAgABHKwCAAA3RgIAA6BaAgAAi8ACAAGVWAIAABZ+AgABuS9CAAdcZAIAAkeGwgACDggCAABApAIAAAZAA///ZGeA=
Date: Tue, 10 Jul 2018 22:27:23 +0000
Message-ID: <8ec9acc459be4f51a653086989b1d387@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> <9c3799f19cf84b22a3659c04a548ba67@XCH-RTP-013.cisco.com> <CABCOCHT=7-dPzTPYLvVN1J12uwGWh9GoA7r5nu=zYYD1nnFwTQ@mail.gmail.com> <273f987e3a224411a01a599afb42f25f@XCH-RTP-013.cisco.com> <20180710193940.jsslo3657wwee6ku@anna.jacobs.jacobs-university.de> <051A20E4-26D0-41C9-B93D-2A094E46EFBA@juniper.net> <c0ab2e56-4c09-6b21-f32e-b0475ef51e37@labn.net>
In-Reply-To: <c0ab2e56-4c09-6b21-f32e-b0475ef51e37@labn.net>
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.41.32.86]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/xn-5aSVraqctYlh0jU7PDUZiE-Y>
Subject: Re: [Netconf] Anyone want just Configured Subscriptions?
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: Tue, 10 Jul 2018 22:27:30 -0000

> From: Lou Berger, July 10, 2018 4:43 PM
> 
> On 7/10/2018 4:37 PM, Kent Watsen wrote:
> >
> >> So in short, after RFC 8071 call home, you get NC/RC client and
> >> server starting with a <hello> exchange. Ideally, the client would
> >> indicate its readiness to receive unsolicited notifications before
> >> you push notifications to the client (and the notification sender may
> >> even be interested to know that it is sending notifications to a
> >> remote system that does not just drop them). So either the clients
> >> invokes an RPC to start the notification flow or, if you want to
> >> optimize one round trip, the client includes a special
> >>
> >>   :willing-to-receive-unsolicited-notifications
> >>
> >> capability in the <hello> exchange.
> > I agree that a client-advertised capability would be goodness here,
> > but it only works for NC-clients, there is no corollary for RC-clients.
> >
> > Maybe clients should send a "willing-to-receive-unsolicited-notifications"
> > RPC instead?
> or an an error when an unsolicited notification is received by a client that
> doesn't support it.
> (optimizing for what I think suspect will be the common case in the long
> term...)

Effectively this is what draft-ietf-netconf-restconf-notif, section 4.2 defines now.  A successful POST of a "subscription-started" notification must occur before events are sent.  Failure to receiver an OK for the POST means an error to the publisher.

Some form of RESTCONF Call Home with capability advertisement could also occur before the "subscription-started" POST.  However this advertisement of client capabilities might not be needed for all implementations.

Eric

> Lou
> 
> >
> > Kent // contributor
> >
> >
> >
> >
> >
> > _______________________________________________
> > Netconf mailing list
> > Netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> >

v2.23.0 | Report a Bug | By Email