Return-Path: 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 D706612D0B2 for ; Wed, 13 Jul 2016 12:24:46 -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_H3=-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 XC4NECiw9xLj for ; Wed, 13 Jul 2016 12:24:45 -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 CAE9A12B05C for ; Wed, 13 Jul 2016 12:24:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7798; q=dns/txt; s=iport; t=1468437884; x=1469647484; h=from:to:subject:date:message-id:references:mime-version; bh=HVuUBNnH9yDkCr6cVcNcXCrFrBrjkmAq9kOc77C99BA=; b=g8ztThjhSRtlt+jMxsZXKceVyBznKAt9vn30gbj56/TAVvRVEaYWKcgO Kt54AXZ0wcaus09817uyVibFfEISid8uJnud6HqzjfzOmpGVUdsGjU8fg N5XCpMC+ZirkvUPNnJhyL0NDchjrRf5GPGwXd3mSSONAmxBvcviYCrjaK 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BaAgAllYZX/4QNJK1bgnBOVoECs16FB?= =?us-ascii?q?IF7JIcpOBQBAQEBAQEBZRwLhF0GLTshAgEtITIlAQEEG4goDsEAAQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBARkFhiqOaQWTXoU+AYEzhF2IP482kBYBHjaDcYkmfwEBAQ?= X-IronPort-AV: E=Sophos;i="5.28,358,1464652800"; d="scan'208,217";a="297471309" Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Jul 2016 19:24:39 +0000 Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u6DJOcZQ032537 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Wed, 13 Jul 2016 19:24:39 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.1210.3; Wed, 13 Jul 2016 15:24:38 -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; Wed, 13 Jul 2016 15:24:37 -0400 From: "Eric Voit (evoit)" To: "i2rs@ietf.org" Thread-Topic: Subscribing to Network Elements @ IETF96 - Thursday 10AM Thread-Index: AdHdN/cd07bshjPUTCyz8ZfQi3+MlAAApHAgAAA308A= Date: Wed, 13 Jul 2016 19:24:37 +0000 Message-ID: References: <09d23b6a25784819b933f433b733c47d@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.118.56.232] Content-Type: multipart/alternative; boundary="_000_ce545224d11248559eb89dfbfec27240XCHRTP013ciscocom_" MIME-Version: 1.0 Archived-At: Subject: [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\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 19:24:47 -0000 --_000_ce545224d11248559eb89dfbfec27240XCHRTP013ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In response to the RFC 7923 requiremen= ts from I2RS, NETCONF is working a set of Subscription technology drafts. = With subscriptions, an Operator can see and react to configuration / opera= tional changes on Network Elements as they occur. Because the drafts have evolved over the last few IETFs, it is worthwhile t= o 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 Subscriptions for Event Notifications (RFC5277bis) draft-gonzalez-netconf-5277bis YANG Datastore Push draft-ietf-netconf-yang-push NETCONF Transport for Event Notifications draft-gonzalez-netconf-event-notifications RESTCONF & HTTP Transport for Event Notifications draft-voit-netconf-restconf-notif Thanks! Eric (on behalf of the authors and contributors) --_000_ce545224d11248559eb89dfbfec27240XCHRTP013ciscocom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

In response to the RFC 7923 requi= rements from I2RS, NETCONF is working a set of Subscription technology draf= ts.   With subscriptions, an Operator can see and react to configuration / operational changes on Network Elements as th= ey occur. 

 

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

 

   &nbs= p;           Subsc= ribing to Network Elements<= /p>

        &nbs= p;      IETF-96=

Thursday  10:00-11:3= 0AM

        &nbs= p;      Tegel Conference Room

 

Material covered:

 

        &nbs= p;      Requirements for Subscription to YANG Data= stores (from I2RS)

RFC 7923 

 

Subscriptions for Event N= otifications  (RFC5277bis)

draft-gonzalez-netconf-= 5277bis

 

YANG Datastore Push

draft-ietf-netconf-yan= g-push

 

NETCONF Transport for Eve= nt Notifications

draft-gonza= lez-netconf-event-notifications 

 

RESTCONF & HTTP Trans= port for Event Notifications

draft-voit-netconf-r= estconf-notif

 

Thanks!

Eric (on behalf of the authors and contributors)

--_000_ce545224d11248559eb89dfbfec27240XCHRTP013ciscocom_--