draft-ietf-i2rs-pub-sub-requirements-02.txt   draft-ietf-i2rs-pub-sub-requirements-03.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 27, 2015 Cisco Systems Expires: March 31, 2016 Cisco Systems
March 26, 2015 September 28, 2015
Requirements for Subscription to YANG Datastores Requirements for Subscription to YANG Datastores
draft-ietf-i2rs-pub-sub-requirements-02 draft-ietf-i2rs-pub-sub-requirements-03
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 41
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 27, 2015. This Internet-Draft will expire on March 31, 2016.
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 29 skipping to change at page 2, line 29
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Assumptions for Subscriber Behavior . . . . . . . . . . . 8 4.1. Assumptions for Subscriber Behavior . . . . . . . . . . . 8
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. Subscription QoS . . . . . . . . . . . . . . . . . . 12 4.2.6. Subscription QoS . . . . . . . . . . . . . . . . . . 12
4.2.7. Filtering . . . . . . . . . . . . . . . . . . . . . . 14 4.2.7. Filtering . . . . . . . . . . . . . . . . . . . . . . 13
4.2.8. Assurance and Monitoring . . . . . . . . . . . . . . 14 4.2.8. Assurance and Monitoring . . . . . . . . . . . . . . 14
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1. Normative References . . . . . . . . . . . . . . . . . . 15 6.1. Normative References . . . . . . . . . . . . . . . . . . 15
6.2. Informative References . . . . . . . . . . . . . . . . . 15 6.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 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
skipping to change at page 8, line 17 skipping to change at page 8, line 17
Many of the requirements within this section have been morphed from Many of the requirements within this section have been morphed from
OMG's DDS and XMPP.org's requirements specifications. OMG's DDS and XMPP.org's requirements specifications.
4.1. Assumptions for Subscriber Behavior 4.1. Assumptions for Subscriber Behavior
This document provides requirements for the Subscription Service. It This document provides requirements for the Subscription Service. It
does not define all the requirements for the Subscriber/Receiver. does not define all the requirements for the Subscriber/Receiver.
However In order to frame the desired behavior of the Subscription However In order to frame the desired behavior of the Subscription
Service, it is important to specify key input constraints. Service, it is important to specify key input constraints.
4.2. Subscription Service Requirements
This document provides requirements for the Subscription Service. It
does not define all the requirements for the Subscriber/Receiver.
However In order to frame the desired behavior of the Subscription
Service, it is important to specify key input constraints.
A Subscriber should avoid attempting to establish multiple A Subscriber should avoid attempting to establish multiple
Subscriptions pertaining to the same information, i.e. referring to Subscriptions pertaining to the same information, i.e. referring to
the same datastore YANG subtrees. the same datastore YANG subtrees.
A Subscriber may provide Subscription QoS criteria to the A Subscriber may provide Subscription QoS criteria to the
Subscription Service such that if the Subscription Service is unable Subscription Service such that if the Subscription Service is unable
to meet those criteria, the Subscription should not be established. to meet those criteria, the Subscription should not be established.
When a Subscriber needs to restart, it is acceptable for the When a Subscriber needs to restart, it is acceptable for the
Subscriber to have to resubscribe. There is no requirement for the Subscriber to have to resubscribe. There is no requirement for the
skipping to change at page 8, line 46 skipping to change at page 8, line 39
A Subscriber must be able to infer when a Subscription Service is no A Subscriber must be able to infer when a Subscription Service is no
longer active and when no more updates are being sent. longer active and when no more updates are being sent.
A Subscriber may check with a Subscription Service to validate the A Subscriber may check with a Subscription Service to validate the
existence and monitored subtrees of a Subscription. existence and monitored subtrees of a Subscription.
A Subscriber must be able to periodically lease and re-lease a A Subscriber must be able to periodically lease and re-lease a
Subscription from a Subscription Service. Subscription from a Subscription Service.
4.2. Subscription Service Requirements
4.2.1. General 4.2.1. General
A Subscription Service must support the ability to create, renew, A Subscription Service must support the ability to create, renew,
timeout, and terminate a Subscription. timeout, and terminate a Subscription.
A Subscription Service must be able to support and independently A Subscription Service must be able to support and independently
track one or more Subscription Requests by the same Subscriber. track one or more Subscription Requests by the same Subscriber.
A Subscription Service must be able to support an add/change/delete A Subscription Service must be able to support an add/change/delete
of one or more YANG subtrees as part of the same Subscription of one or more YANG subtrees as part of the same Subscription
skipping to change at page 15, line 22 skipping to change at page 15, line 17
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
6.1. Normative References 6.1. Normative References
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/
RFC2328, April 1998,
<http://www.rfc-editor.org/info/rfc2328>.
[RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event [RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event
Notifications", RFC 5277, July 2008. Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008,
<http://www.rfc-editor.org/info/rfc5277>.
[RFC6470] Bierman, A., "Network Configuration Protocol (NETCONF) [RFC6470] Bierman, A., "Network Configuration Protocol (NETCONF)
Base Notifications", RFC 6470, February 2012. Base Notifications", RFC 6470, DOI 10.17487/RFC6470,
February 2012, <http://www.rfc-editor.org/info/rfc6470>.
[RFC6513] Rosen, E. and R. Aggarwal, "Multicast in MPLS/BGP IP [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
VPNs", RFC 6513, February 2012. BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
2012, <http://www.rfc-editor.org/info/rfc6513>.
6.2. Informative References 6.2. Informative References
[AVB-latency] [AVB-latency]
Jeffree, T., "802.1Qav - Forwarding and Queuing Jeffree, T., "802.1Qav - Forwarding and Queuing
Enhancements for Time-Sensitive Streams", December 2009, Enhancements for Time-Sensitive Streams", December 2009,
<http://www.ieee802.org/1/pages/802.1av.html>. <http://www.ieee802.org/1/pages/802.1av.html>.
[OMG-DDS] "Data Distribution Service for Real-time Systems, version
1.2", January 2007, <http://www.omg.org/spec/DDS/1.2/>.
[XEP-0060]
Millard, P., "XEP-0060: Publish-Subscribe", July 2010,
<XEP-0060: Publish-Subscribe>.
[datastore-push] [datastore-push]
Clemm, A., Gonzalez Prieto, A., and E. Voit, "Subscribing Clemm, A., Gonzalez Prieto, A., and E. Voit, "Subscribing
to datastore push updates", October 2014, to datastore push updates", July 2015,
<https://tools.ietf.org/html/draft-netmod-clemm-datastore- <https://tools.ietf.org/html/draft-clemm-netconf-yang-
push-00>. push-01>.
[draft-voit-netmod] [draft-voit-netmod]
Voit, E., "Requirements for Peer Mounting of YANG subtrees Voit, E., "Requirements for Peer Mounting of YANG subtrees
from Remote Datastores", October 2014, from Remote Datastores", September 2015,
<https://tools.ietf.org/html/draft-voit-netmod-peer-mount- <https://tools.ietf.org/html/draft-voit-netmod-peer-mount-
requirements-01>. requirements-03>.
[i2rs-arch] [i2rs-arch]
Atlas, A., "An Architecture for the Interface to the Atlas, A., "An Architecture for the Interface to the
Routing System", December 2014, Routing System", March 2015,
<https://tools.ietf.org/html/draft-ietf-i2rs-architecture- <https://datatracker.ietf.org/doc/draft-ietf-i2rs-
06>. architecture/>.
[i2rs-pubsub-security] [i2rs-pubsub-security]
Beck, K., Cam Winget, N., and D. McGrew, "Using the Beck, K., Cam Winget, N., and D. McGrew, "Using the
Publish-Subscribe Model in the Interface to the Routing Publish-Subscribe Model in the Interface to the Routing
System", July 2013, <https://tools.ietf.org/html/draft- System", July 2013, <https://tools.ietf.org/html/draft-
camwinget-i2rs-pubsub-sec-00>. camwinget-i2rs-pubsub-sec-00>.
[i2rs-traceability] [i2rs-traceability]
Clarke, J., Salgueiro, G., and C. Pignataro, "Interface to Clarke, J., Salgueiro, G., and C. Pignataro, "Interface to
the Routing System (I2RS) Traceability: Framework and the Routing System (I2RS) Traceability: Framework and
Information Model", December 2014, Information Model", May 2015,
<https://datatracker.ietf.org/doc/draft-ietf-i2rs- <https://datatracker.ietf.org/doc/draft-ietf-i2rs-
traceability/>. traceability/>.
[i2rs-usecase] [i2rs-usecase]
Hares, S. and M. Chen, "Summary of I2RS Use Case Hares, S. and M. Chen, "Summary of I2RS Use Case
Requirements", October 2014, Requirements", May 2015,
<https://datatracker.ietf.org/doc/draft-ietf-i2rs-usecase- <https://datatracker.ietf.org/doc/draft-ietf-i2rs-usecase-
reqs-summary/>. reqs-summary/>.
[OMG-DDS] "Data Distribution Service for Real-time Systems, version
1.2", January 2007, <http://www.omg.org/spec/DDS/1.2/>.
[sacm-requirements] [sacm-requirements]
Cam Winget, N., "Secure Automation and Continuous Cam Winget, N., "Secure Automation and Continuous
Monitoring (SACM) Requirements", October 2014, Monitoring (SACM) Requirements", July 2015,
<https://tools.ietf.org/html/draft-ietf-sacm-requirements- <https://tools.ietf.org/html/draft-ietf-sacm-requirements-
02>. 09>.
[XEP-0060]
Millard, P., "XEP-0060: Publish-Subscribe", July 2010,
<XEP-0060: Publish-Subscribe>.
Authors' Addresses Authors' Addresses
Eric Voit Eric Voit
Cisco Systems Cisco Systems
Email: evoit@cisco.com Email: evoit@cisco.com
Alexander Clemm Alexander Clemm
Cisco Systems Cisco Systems
 End of changes. 21 change blocks. 
36 lines changed or deleted 37 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/