[i2rs] New "-00": draft-voit-i2rs-pub-sub-requirements

"Eric Voit (evoit)" <evoit@cisco.com> Thu, 11 December 2014 15:21 UTC

Return-Path: <evoit@cisco.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9A781A1B6C for <i2rs@ietfa.amsl.com>; Thu, 11 Dec 2014 07:21:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 t-fxtnHKJ0Sr for <i2rs@ietfa.amsl.com>; Thu, 11 Dec 2014 07:21:57 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7548A1A1AA8 for <i2rs@ietf.org>; Thu, 11 Dec 2014 07:21:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3520; q=dns/txt; s=iport; t=1418311318; x=1419520918; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=R6D/hOxL6ff8fodjnoPxCMkhb5pCFGZV7ORKS6VlI0c=; b=GT+CaEZQQRyzdmnGcm8CFqVnCknSSF1Gq9J1VvzUs+Qv+3TJKPxeAW84 iWFlljcZI06dn9u+9fxDZnsA6DC2zjHMwT+JasdD518j0Vxg7o/UYTr1E 0QzBaFhvsFscwTcHQb7r+Lh19dwAO3FulR5YbgTI602Xpo+wbfw9Awqg8 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkkHAHa1iVStJA2N/2dsb2JhbABZgwZSWASDAcJ1hWwCHIEAFgEBAQEBfYQMAQEBBCMRRQwGARkEAQEDAgYCARoDAgQwFAEICQEEDgUIAYgjDcFQll4BAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSGOIBYbDYJiLoETBY1/gz6GPTCCLY1KIoNsbgGBRH4BAQE
X-IronPort-AV: E=Sophos;i="5.07,558,1413244800"; d="scan'208";a="379473085"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-3.cisco.com with ESMTP; 11 Dec 2014 15:21:57 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id sBBFLu7h003537 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <i2rs@ietf.org>; Thu, 11 Dec 2014 15:21:56 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.205]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Thu, 11 Dec 2014 09:21:56 -0600
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: New "-00": draft-voit-i2rs-pub-sub-requirements
Thread-Index: AdAVViieql0DVYwjTDSQ2bF1EzwXyQ==
Date: Thu, 11 Dec 2014 15:21:55 +0000
Message-ID: <EF64FF31F4C4384DBCE5D513A791C2B120AC501F@xmb-aln-x11.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.134.131]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/NsFhpFHPIj44WsOwAnd3c6btnKM
Cc: "Alexander Clemm (alex)" <alex@cisco.com>, "Alberto Gonzalez Prieto (albertgo)" <albertgo@cisco.com>
Subject: [i2rs] New "-00": draft-voit-i2rs-pub-sub-requirements
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 11 Dec 2014 15:22:00 -0000

A number of I2RS WG documents ask for Pub/Sub capabilities.  Other WG have addressed or are looking for similar mechanisms.  The document 
http://tools.ietf.org/html/draft-voit-i2rs-pub-sub-requirements-00 
assembles a view of requirements for a YANG Datastore from an I2RS perspective, and makes comparisons with capabilities in standards in and beyond the IETF. 

This document is a good companion document for
https://tools.ietf.org/html/draft-netmod-clemm-datastore-push-00 

Thanks,
Eric , Alex, & Alberto

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, December 11, 2014 10:03 AM
To: Alberto Gonzalez Prieto (albertgo); Alberto Gonzalez Prieto (albertgo); Alexander Clemm (alex); Eric Voit (evoit); Alexander Clemm (alex); Eric Voit (evoit)
Subject: New Version Notification for draft-voit-i2rs-pub-sub-requirements-00.txt


A new version of I-D, draft-voit-i2rs-pub-sub-requirements-00.txt
has been successfully submitted by Eric Voit and posted to the IETF repository.

Name:		draft-voit-i2rs-pub-sub-requirements
Revision:	00
Title:		Requirements for Subscription to YANG Datastores
Document date:	2014-12-10
Group:		Individual Submission
Pages:		13
URL:            http://www.ietf.org/internet-drafts/draft-voit-i2rs-pub-sub-requirements-00.txt
Status:         https://datatracker.ietf.org/doc/draft-voit-i2rs-pub-sub-requirements/
Htmlized:       http://tools.ietf.org/html/draft-voit-i2rs-pub-sub-requirements-00


Abstract:
   This document provides requirements for a service that allows client
   applications to subscribe to updates of a YANG datastore.  Based on
   criteria negotiated as part of a subscription, updates will be pushed
   to targeted recipients.  Such a capability eliminates the need for
   periodic polling of YANG datastores by applications and fills a
   functional gap in existing YANG transports (i.e.  Netconf and
   Restconf).  Such a service can be summarized as a "pub/sub" service
   for YANG datastore updates.  Beyond a set of basic requirements for
   the service, various refinements are addressed.  These refinements
   include: periodicity of object updates, filtering out of objects
   underneath a requested a subtree, and delivery QoS guarantees.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat