IETF Logo Mail Archive

Re: [Netconf] Subscription Use Cases

"Eric Voit (evoit)" <evoit@cisco.com> Fri, 09 December 2016 12:47 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 1163E129533 for <netconf@ietfa.amsl.com>; Fri, 9 Dec 2016 04:47:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.418
X-Spam-Level:
X-Spam-Status: No, score=-17.418 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, 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 GQrrECVs_NBI for <netconf@ietfa.amsl.com>; Fri, 9 Dec 2016 04:47:18 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5C0C1293F9 for <netconf@ietf.org>; Fri, 9 Dec 2016 04:47:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2307; q=dns/txt; s=iport; t=1481287637; x=1482497237; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=litwo2NE8eHMRkZG57/9D7+LyqgyB9xlTPGF/hwJrQs=; b=byLiAOVPYvIy6+nsEkRHoTfrbfZ2sgPMf206jXGHihuTbswRgBnGsAOX 4/LZftH+qPTt1SvJGNTsVboCS9EvoQO1w4qgC+TS75XYuIPP8xT34PsRJ 98KNSi+zgSbmzw7qV+bsiBiN7MjTkK3VWKOsbahJu3gbeZov1903cn8mg U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BuAQB2pkpY/4ENJK1eGgEBAQECAQEBAQgBAQEBgzcBAQEBAR9agQYHjUKXFJUCggorhXYCggA/FAECAQEBAQEBAWIohGgBAQECAQE6NgkFCwIBCA4HAw0REDIlAgQOBQgTiEgIDqoriy0BAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYY+hFuKKQWaawGGTopJkE6OC4QNAR83gSEkhTVyAYgugQ0BAQE
X-IronPort-AV: E=Sophos;i="5.33,324,1477958400"; d="scan'208";a="358671080"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Dec 2016 12:47:16 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id uB9ClGY9025626 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 9 Dec 2016 12:47:16 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 9 Dec 2016 07:47:16 -0500
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.1210.000; Fri, 9 Dec 2016 07:47:15 -0500
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>
Thread-Topic: [Netconf] Subscription Use Cases
Thread-Index: AQHSUTKNz0LSmZX5b0GYyl1Cgj0Ou6D+G3xggAGB64D///FKsA==
Date: Fri, 09 Dec 2016 12:47:15 +0000
Message-ID: <5e06ffa5d92a4227ae1d64bc8531ac40@XCH-RTP-013.cisco.com>
References: <e9128f79b8bc4923815e40510678c026@XCH-RTP-013.cisco.com> <20161208.100745.1423954834248283961.mbj@tail-f.com> <a2b682ef436c4b67881c26c04ad3d0b5@XCH-RTP-013.cisco.com> <20161209.092651.1622778603139515958.mbj@tail-f.com>
In-Reply-To: <20161209.092651.1622778603139515958.mbj@tail-f.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.226]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/UzRWsdLIY70gdwD8oarjNZS3CNU>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Subject: Re: [Netconf] Subscription Use Cases
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Dec 2016 12:47:20 -0000

> From: Martin Bjorklund, December 9, 2016 3:27 AM
> 
> "Eric Voit (evoit)" <evoit@cisco.com> wrote:
> > Hi Martin,
> >
> > > From: Martin Bjorklund, December 8, 2016 4:08 AM
> > >
> > > I think your requirements below are more like driving forces for
> > > YANG push, right?  Is there any of these that affects the solution
> > > in RFC 5277?
> >
> > The majority of these cases need yang-push.  But yang push is only
> > possible when the information is yang modeled.
> 
> Sure, but that's a completely different thing.
> 
> This discussion is about what needs to be done with RFC 5277.  I'll re-iterate
> what Andy wrote once more:
> 
>   What are the must-have, should-have, and nice-to-have features that are
>   missing from RFC 5277?

At a high level incremental functionality we have been discussing since IETF 94, 95, 96, 97 includes:
- configured subscriptions
- many subscriptions per transport
- modify and delete subscriptions
- control plane notifications
- Restconf & HTTP support
- Data plan notification including subscription-id

At a medium level, existing documentation detailing these requirements can be seen in places like:  
https://www.ietf.org/proceedings/95/slides/slides-95-netconf-7.pdf   Slide 5
https://www.ietf.org/proceedings/96/slides/slides-96-netconf-5.pdf   Slides 5, 28
https://www.ietf.org/proceedings/97/slides/slides-97-netconf-draft-ietf-netconf-yang-push-01.pdf  Slides 20 & 21

At a detailed level, I2RS's RFC-7923 has functional requirements for yang subscriptions. This is what was requested by the WG to be made available for event notifications.  
as well as various WG meeting minutes.

And of course the existing WG minutes, the four draft document appendices, and the Dezign team minutes at:
https://github.com/netconf-wg/yang-push/wiki/Minutes
Attempts to keep a running list of to-be-resolved dialogs.  Of course there is a lag between dialogs and embodiment in the drafts.

If anyone wants to propose a revision to the requirements, I propose they do this as deltas from the existing documentation.

Or course we in the WG can and should discuss and tweak any specific requirement on this mailer based on ongoing learnings over time.   

Eric

> /martin

v2.23.0 | Report a Bug | By Email