draft-ietf-i2rs-pub-sub-requirements-00.txt   draft-ietf-i2rs-pub-sub-requirements-01.txt 
Interface to the Routing System (i2rs) E. Voit Interface to the Routing System (i2rs) E. Voit
Internet-Draft A. Clemm Internet-Draft A. Clemm
Intended status: Informational A. Gonzalez Prieto Intended status: Informational A. Gonzalez Prieto
Expires: September 4, 2015 Cisco Systems Expires: September 10, 2015 Cisco Systems
March 3, 2015 March 9, 2015
Requirements for Subscription to YANG Datastores Requirements for Subscription to YANG Datastores
draft-ietf-i2rs-pub-sub-requirements-00 draft-ietf-i2rs-pub-sub-requirements-01
Abstract Abstract
This document provides requirements for a service that allows client This document provides requirements for a service that allows client
applications to subscribe to updates of a YANG datastore. Based on applications to subscribe to updates of a YANG datastore. Based on
criteria negotiated as part of a subscription, updates will be pushed criteria negotiated as part of a subscription, updates will be pushed
to targeted recipients. Such a capability eliminates the need for to targeted recipients. Such a capability eliminates the need for
periodic polling of YANG datastores by applications and fills a periodic polling of YANG datastores by applications and fills a
functional gap in existing YANG transports (i.e. Netconf and functional gap in existing YANG transports (i.e. Netconf and
Restconf). Such a service can be summarized as a "pub/sub" service Restconf). Such a service can be summarized as a "pub/sub" service
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 4, 2015. This Internet-Draft will expire on September 10, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 30 skipping to change at page 2, line 30
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Assumptions for Subscriber Behavior . . . . . . . . . . . 7 4.1. Assumptions for Subscriber Behavior . . . . . . . . . . . 7
4.2. Subscription Service Requirements . . . . . . . . . . . . 8 4.2. Subscription Service Requirements . . . . . . . . . . . . 8
4.2.1. General . . . . . . . . . . . . . . . . . . . . . . . 8 4.2.1. General . . . . . . . . . . . . . . . . . . . . . . . 8
4.2.2. Negotiation . . . . . . . . . . . . . . . . . . . . . 10 4.2.2. Negotiation . . . . . . . . . . . . . . . . . . . . . 10
4.2.3. Update Distribution . . . . . . . . . . . . . . . . . 10 4.2.3. Update Distribution . . . . . . . . . . . . . . . . . 10
4.2.4. Transport . . . . . . . . . . . . . . . . . . . . . . 11 4.2.4. Transport . . . . . . . . . . . . . . . . . . . . . . 11
4.2.5. Security Requirements . . . . . . . . . . . . . . . . 11 4.2.5. Security Requirements . . . . . . . . . . . . . . . . 11
4.2.6. QoS Requirements . . . . . . . . . . . . . . . . . . 12 4.2.6. QoS Requirements . . . . . . . . . . . . . . . . . . 12
4.2.7. Filtering . . . . . . . . . . . . . . . . . . . . . . 13 4.2.7. Filtering . . . . . . . . . . . . . . . . . . . . . . 13
4.2.8. Assurance and Monitoring . . . . . . . . . . . . . . 14
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.1. Normative References . . . . . . . . . . . . . . . . . . 14 6.1. Normative References . . . . . . . . . . . . . . . . . . 14
6.2. Informative References . . . . . . . . . . . . . . . . . 14 6.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
YANG has gained acceptance as the data definition language of choice YANG has gained acceptance as the data definition language of choice
for control and management related information. Applications that for control and management related information. Applications that
interact with YANG datastores are extending beyond traditional interact with YANG datastores are extending beyond traditional
configuration of network elements. In many cases these applications configuration of network elements. In many cases these applications
are aimed at service-assurance, which involves monitoring of are aimed at service-assurance, which involves monitoring of
operational data and state. The existing YANG technology ecosystem operational data and state. The existing YANG technology ecosystem
is proving insufficient for those applications due to: is proving insufficient for those applications due to:
skipping to change at page 14, line 5 skipping to change at page 14, line 5
apply multiple filters against a single property. apply multiple filters against a single property.
It SHOULD be possible to establish query match criteria on additional It SHOULD be possible to establish query match criteria on additional
objects to be used in conjunction with Property Filtering criteria on objects to be used in conjunction with Property Filtering criteria on
a subscribed object. (For example: if A has changed AND B=1, then a subscribed object. (For example: if A has changed AND B=1, then
Push A.) (Note: Query match capability MAY be done on objects within Push A.) (Note: Query match capability MAY be done on objects within
the datastore even if those objects are not included within the the datastore even if those objects are not included within the
subscription. This of course assumes the subscriber has read access subscription. This of course assumes the subscriber has read access
to those objects.) to those objects.)
4.2.8. Assurance and Monitoring
It MUST be possible to fetch the state of a single subscription from
a Subscription Service.
It MUST be possible to fetch the state of all subscriptions of a
particular Subsciber.
It MUST be possible to fetch a list and status of all Subscription
Requests over a period of time. If there us a failure, some failure
reasons might include:
o Improper security credentials provided to access the target node
o Target node referenced does not exist
o Subscription type requested is not available upon the target node
o Out of resources, or resources not available
o Incomplete negotiations with the Subscriber.
5. Acknowledgements 5. Acknowledgements
We wish to acknowledge the helpful contributions, comments, and We wish to acknowledge the helpful contributions, comments, and
suggestions that were received from Ambika Tripathy and Prabhakara suggestions that were received from Ambika Tripathy and Prabhakara
Yellai as well as the helpfulness of related end-to-end system Yellai as well as the helpfulness of related end-to-end system
context from [i2rs-pubsub-security] from Nancy Cam Winget, Ken Beck, context from [i2rs-pubsub-security] from Nancy Cam Winget, Ken Beck,
and David McGrew. and David McGrew.
6. References 6. References
 End of changes. 6 change blocks. 
6 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/