Re: [i2rs] Subscribing to Network Elements @ IETF96 - Thursday 10AM

"Eric Voit (evoit)" <evoit@cisco.com> Thu, 21 July 2016 19:36 UTC

Return-Path: <evoit@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F16A512D8BF for <i2rs@ietfa.amsl.com>; Thu, 21 Jul 2016 12:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level:
X-Spam-Status: No, score=-15.807 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, 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 NhrEzGlBkL2D for <i2rs@ietfa.amsl.com>; Thu, 21 Jul 2016 12:36:08 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7430412D8A5 for <i2rs@ietf.org>; Thu, 21 Jul 2016 12:36:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13056; q=dns/txt; s=iport; t=1469129767; x=1470339367; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=gS3tu8R1oiTGkXevuyUYgNNLEvCPvVg39DR8uGXEudY=; b=jFhEDhX4Grw7RiukQw5oNYIxbD1mV91GZxYPYUzkdi+tRez1ff8PxJyW XlfWbNwO9gk8YLXGwHTIxE+q8VbRLMpIhjLDDReQE/WKQUWOkO2GhLKdL 0gJVCpmMk804FXyfFs+RGqHjjrPxkDM5jrUmJ8du0wKpH1JNkj+9XY7xy g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BRAgB2I5FX/5tdJa1dgnFOVnwGs1GFB?= =?us-ascii?q?IF7JIV2AoEwOBQBAQEBAQEBZRwLhFwBAQUhAQs7IQIBCBEEAQEOAhgCAwIyFAk?= =?us-ascii?q?IAQEEDwQIiCgOknmdGwGNWQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhiqETYR2g?= =?us-ascii?q?kiCXQWTZIVCAYYViE6PQZAgAR42g3NuBoZ4fwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.28,400,1464652800"; d="scan'208,217";a="300812892"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jul 2016 19:36:06 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u6LJa6wv003157 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <i2rs@ietf.org>; Thu, 21 Jul 2016 19:36:06 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 21 Jul 2016 15:36:05 -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.1210.000; Thu, 21 Jul 2016 15:36:05 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: Subscribing to Network Elements @ IETF96 - Thursday 10AM
Thread-Index: AdHdN/cd07bshjPUTCyz8ZfQi3+MlAAApHAgAAA308ABkunT8A==
Date: Thu, 21 Jul 2016 19:36:05 +0000
Message-ID: <d6a57e6f626a4bcf9f08fb9760408a6f@XCH-RTP-013.cisco.com>
References: <09d23b6a25784819b933f433b733c47d@XCH-RTP-013.cisco.com> <ce545224d11248559eb89dfbfec27240@XCH-RTP-013.cisco.com>
In-Reply-To: <ce545224d11248559eb89dfbfec27240@XCH-RTP-013.cisco.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.61.203.80]
Content-Type: multipart/alternative; boundary="_000_d6a57e6f626a4bcf9f08fb9760408a6fXCHRTP013ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/0W0q31nINFWq4RsBsPDmdKOAgpc>
Subject: Re: [i2rs] Subscribing to Network Elements @ IETF96 - Thursday 10AM
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 19:36:10 -0000

Thanks to those of you who came to the Technology Intro session today.   As promised, materials are here:
https://github.com/netconf-wg/yang-push/blob/master/Subscriptions-Intro-IETF96.ppt

Slides include:
Two Views of the Network’s Job
Must have Alternative to Polling
Generalized Publisher Capabilities
Consumption Models
Applicability beyond the Network Element
Event Notifications ≠ Raw Datastore Objects
When to use Event Notifications or YANG Datastore Push
Some Use Cases
Event & YANG Subscription Drafts
Subscription Drafts in Layered Framework
Context with OC-Telemetry.yang
Requirements of RFC 7923
Dampening Eventing vs. Periodic Behavior
Prioritization of Subscriptions
Reviewing the YANG Models
rfc5277bis
yang-push

Thanks,
Eric & Alex


From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Eric Voit (evoit)
Sent: Wednesday, July 13, 2016 3:25 PM
To: i2rs@ietf.org
Subject: [i2rs] Subscribing to Network Elements @ IETF96 - Thursday 10AM

In response to the RFC 7923<https://tools.ietf.org/html/rfc7923> requirements from I2RS, NETCONF is working a set of Subscription technology drafts.   With subscriptions, an Operator can see and react to configuration / operational changes on Network Elements as they occur.

Because the drafts have evolved over the last few IETFs, it is worthwhile to provide a technology overview.  We are having an Intro session for those of you who haven’t followed this daily.

               Subscribing to Network Elements
               IETF-96
Thursday  10:00-11:30AM
               Tegel Conference Room

Material covered:

               Requirements for Subscription to YANG Datastores (from I2RS)
RFC 7923<https://tools.ietf.org/html/rfc7923>

Subscriptions for Event Notifications  (RFC5277bis)
draft-gonzalez-netconf-5277bis<https://datatracker.ietf.org/doc/draft-gonzalez-netconf-5277bis/>


YANG Datastore Push

draft-ietf-netconf-yang-push<https://datatracker.ietf.org/doc/draft-ietf-netconf-yang-push/>

NETCONF Transport for Event Notifications
draft-gonzalez-netconf-event-notifications<https://datatracker.ietf.org/doc/draft-gonzalez-netconf-event-notifications/>

RESTCONF & HTTP Transport for Event Notifications
draft-voit-netconf-restconf-notif<https://datatracker.ietf.org/doc/draft-voit-netconf-restconf-notif/>

Thanks!
Eric (on behalf of the authors and contributors<https://github.com/netconf-wg/yang-push/wiki/Contributors>)