Cisco Systems

evoit@cisco.com

Cisco Systems

ambtripa@cisco.com

Cisco Systems

einarnn@cisco.com

Huawei

ludwig@clemm.org

VMWare

agonzalezpri@vmware.com

YumaWorks

andy@yumaworks.com

Operations & Management NETCONF Draft This document defines Restconf, HTTP2, and HTTP1.1 bindings for the transport of Subscription requests and corresponding push updates. Being subscribed may be either publisher defined event streams or nodes/subtrees of YANG Datastores.

Mechanisms to support Event subscription and push are defined in . Enhancements to which enable YANG Datastore subscription and push are defined in . This document provides a transport specification for these protocols over Restconf and HTTP. Driving these requirements is . The streaming of notifications encapsulating the resulting information push can be done with either HTTP1.1 and HTTP2. When using HTTP2 benefits which can be realized include: Elimination of head-of-line blocking Weighting and proportional dequeuing of Events from different subscriptions Explicit precedence in subscriptions so that events from one subscription must be sent before another dequeues

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. The following terms use the defintions from : configured subscription, dynamic subscription, event notification, publisher, receiver, subscriber, and subscription.

Subscribing to event streams is defined in , YANG Datastore subscription is defined in . This section specifies transport mechanisms applicable to both.

Dynamic Subscriptions for both and its augmentations are configured and managed via signaling messages transported over . These interactions will be accomplished via a Restconf POST into RPCs located on the Publisher. HTTP responses codes will indicate the results of the interaction with the Publisher. An HTTP status code of 200 is the proper response to a successful <establish-subscription> RPC call. The successful <establish-subscription> will result in a HTTP message with returned subscription URI on a logically separate mechanism than was used for the original Restconf POST. This mechanism is via a parallel TCP connection in the case of HTTP 1.x, or in the case of HTTP2 via a separate HTTP stream within the HTTP connection. When a being returned by the Publisher, failure will be indicated by error codes transported in payload. Once established, the resulting stream of notification messages are then delivered via SSE for HTTP1.1 and via HTTP Data for HTTP2.

Requests to [sn] or [yang-push] augmented RPCs are sent on one or more HTTP2 streams indicated by (a) in Figure 2. Notification messages related to a single subscription are pushed on a unique logical channel (b). In the case below, a newly established subscription has its associated messages pushed over HTTP2 stream (7).

| | HTTP 200 OK (URI)| |<---------------------------------------------| | (7)HTTP POST (URI) (7) | |--------------------------------------------->| | | HTTP 200 OK| | |<---------------------------------------------| | | HTTP Data (event-notif)| | |<---------------------------------------------| | Restconf POST (RPC:modify-subscription) | | |--------------------------------------------->| | | | HTTP 200 OK| | |<---------------------------------------------| | | | HTTP Data (subscription-modified)| | |<---------------------------------------------| | | HTTP Data (event-notif)| | |<---------------------------------------------| | Restconf POST (RPC:delete-subscription) | | |--------------------------------------------->| | | | HTTP 200 OK| | |<---------------------------------------------| | | | HTTP Headers (end of stream)| | (/7)<-----------------------------------------(/7) |]]>

Requests to [yang-push] RPCs are sent on the TCP connection indicated by (a). Notification messages are pushed on a separate connection (b). This connection (b) will be used for all notification messages across all subscriptions.

| | HTTP 200 OK (URI)| |<---------------------------------------------| | |HTTP GET (URI) | | |--------------------------------------------->| | | HTTP 200 OK| | |<---------------------------------------------| | | SSE (event-notif)| | |<---------------------------------------------| | Restconf POST (RPC:modify-subscription) | | |--------------------------------------------->| | | | HTTP 200 OK| | |<---------------------------------------------| | | | SSE (subscription-modified)| | |<---------------------------------------------| | | SSE (event-notif)| | |<---------------------------------------------| | Restconf POST (RPC:delete-subscription) | | |--------------------------------------------->| | | | HTTP 200 OK| | |<---------------------------------------------| | | | | | |]]>

With a Configured Subscription, all information needed to establish a secure relationship with that Receiver is available on the Publisher. With this information, the Publisher will establish a secure transport connection with the Receiver and then begin pushing notification messages to the Receiver. Since Restconf might not exist on the Receiver, it is not desirable to require that subscribed content be pushed with any dependency on Restconf. Nor is there value which Restconf provides on top of HTTP. Therefore in place of Restconf, a TLS secured HTTP2 Client connection must be established with an HTTP2 Server located on the Receiver. Notification messages will then be sent as part of an extended HTTP POST to the Receiver. POST messages will be addressed to HTTP augmentation code on the Receiver capable of accepting and responding to state change notifications and subscribed content notification messages. The first POST message must be a subscription-started notification. Notifications which include any subscribed content must not be sent until the receipt of an HTTP 200 OK for this initial notification. The 200 OK will indicate that the Receiver is ready for the delivery of subscribed content. At this point a Subscription must be allocated its own HTTP2 stream. Figure 4 depicts this message flow.

| | | HTTP Post Headers, Data (event-notif)| | |<---------------------------------------------| | | HTTP Data (event-notif)| | |<---------------------------------------------| | | HTTP Data (sub-terminate)| | |<---------------------------------------------| | |HTTP 200 OK | | |--------------------------------------------->|]]>

As the HTTP2 transport is available to the Receiver, the Publisher should: take any subscription-priority and copy it into the HTTP2 stream priority, and take a subscription-dependency if it has been provided and map the HTTP2 stream for the parent subscription into the HTTP2 stream dependency.

It is possible that updates across subscriptions might be delivered in a different sequence than the encapsulated records were generated. Reasons for this might include (but are not limited to): generation of event records on different line cards replay of pushed information, and temporary loss of transport connectivity, with update buffering and different dequeuing priorities per Subscription population, marshalling and bundling across independent Subscription Updates, and Therefore each notification message will include a timestamp to provide a Receiver with its best information indicating when a particular record was generated. Use of this timestamp can give an indication of the state of objects at a Publisher. This is especially important when state-entangled information is received across different subscriptions. Note that use of notification message timestamps may not indicate a the exact time of occurrence. So when state-entangled updates have inconsistent object values and temporally close timestamps, a Receiver might consider performing a GET to validate the current state of a Publisher.

Subscribers can dynamically learn whether a RESTCONF server supports various types of Event or Yang datastore subscription capabilities. This is done by issuing an HTTP request OPTIONS, HEAD, or GET on the stream. Some examples building upon the Call flow for HTTP1.1 from Section 3.2.2 are:

If the server supports it, it may respond

yang-push Yang push stream xml https://example.com/streams/yang-push-xml json https://example.com/streams/yang-push-json ]]>

If the server does not support any form of subscription, it may respond

Subscribers can determine the URL to receive updates by sending an HTTP GET as a request for the "location" leaf with the stream list entry. The stream to use for may be selected from the Event Stream list provided in the capabilities exchange. Note that different encodings are supporting using different Event Stream locations. For example, the Subscriber might send the following request:

The Publisher might send the following response:

https://example.com/streams/yang-push-xml ]]>

To subscribe and start receiving updates, the subscriber can then send an HTTP GET request for the URL returned by the Publisher in the request above. The accept header must be "text/event-stream". The Publisher uses the Server Sent Events transport strategy to push filtered events from the event stream. The Publisher MUST support individual parameters within the POST request body for all the parameters of a subscription. The only exception is the encoding, which is embedded in the URI. An example of this is:

Should the publisher not support the requested subscription, it may reply:

application operation-not-supported error Xpath filters not supported with an equivalent JSON encoding representation of: HTTP/1.1 501 Not Implemented Date: Mon, 23 Apr 2012 17:11:00 GMT Server: example-server Content-Type: application/yang.errors+json { "ietf-restconf:errors": { "error": { "error-type": "protocol", "error-tag": "operation-not-supported", "error-message": "Xpath filters not supported." "error-info": { "datastore-push:supported-subscription": { "subtree-filter": [null] } } } } } ]]>

The following is an example of a pushed content for the Subscription above. It contains a subtree with root foo that contains a leaf called bar:

my-sub 2015-03-09T19:14:56.233Z some_string ]]>

Or with the equivalent YANG over JSON encoding representation as defined in :

To modify a Subscription, the subscriber issues another POST request on the provided URI using the same subscription-id as in the original request. For example, to modify the update period to 10 seconds, the subscriber may send:

To delete a Subscription, the Subscriber issues a DELETE request on the provided URI using the same subscription-id as in the original request

The basic encoding will look as below. It will consists of a JSON representation wrapped in an HTTP2 header.

Subscriptions could be used to intentionally or accidentally overload the resources of a Publisher. For this reason, it is important that the Publisher has the ability to prioritize the establishment and push of notification messages where there is the potential for resource exhaust. In addition, a server needs to be able to suspend existing Subscriptions when needed. When this occurs, the subscription status must be updated accordingly and the Receivers notified. A Subscription could be used to attempt retrieve information for which a Receiver has no authorized access. Therefore it is important that data pushed via a Subscription is authorized equivalently with regular data retrieval operations. Data being pushed to a Receiver needs therefore to be filtered accordingly, just like if the data were being retrieved on-demand. The Netconf Authorization Control Model applies even though the transport is not NETCONF. One or more Publishers of Configured Subscriptions could be used to overwhelm a Receiver which doesn't even support Subscriptions. There are two protections here. First, notification messages for Configured Subscriptions MUST only be transmittable over encrypted transports. Clients which do not want pushed content need only terminate or refuse any transport sessions from the Publisher. Second, the HTTP transport augmentation on the Receiver must send an HTTP 200 OK to a subscription started notification before the Publisher starts streaming any subscribed content. One or more Publishers could overwhelm a Receiver which is unable to control or handle the volume of Event Notifications received. In deployments where this might be a concern, HTTP2 transport such as HTTP2) should be selected.

We wish to acknowledge the helpful contributions, comments, and suggestions that were received from: Susan Hares, Tim Jenkins, Balazs Lengyel, Kent Watsen, Michael Scharf, and Guangying Zheng.

Cisco Huawei Cisco Cisco Cisco Huawei Cisco VMWare Cisco Cisco YumaWorks Ericsson

Several technologies are expected to be seen within a deployment to achieve security and ease-of-use requirements. These are not necessary for an implementation of this specification, but will be useful to consider when considering the operational context.

Implementations should include the ability to transparently incorporate 'call home' so that secure TLS connections can originate from the desired device.

HTTP sessions might not quickly allow a Subscriber to recognize when the communication path has been lost from the Publisher. To recognize this, it is possible for a Receiver to establish a TLS heartbeat . In the case where a TLS heartbeat is included, it should be sent just from Receiver to Publisher. Loss of the heartbeat should result in any Subscription related TCP sessions between those endpoints being torn down. The subscription can then attempt to re-establish.

An initial goal for this document was to support transport seamlessly without any mapping or extra layering. However there is an incompatibility of RESTCONF and GRPC. RESTCONF uses HTTP GET, and GRPC uses HTTP2's POST rather than GET. As GET is used across RESTCONF for things like capabilities exchange, a seamless mapping depends on specification changes outside the scope of this document. If/when GRPC supports GET, or RESTCONF is updated to support POST, this should be revisited. It is hoped that the resulting fix will be transparent to this document.

(To be removed by RFC editor prior to publication) v01 - v03 Terminoology aligned with draft-voit-netconf-notification-messages. Tweaks to wording/capitalization/format. v01 - v02 Removed sections now redundant with [sn] and [yang-push] such as: mechanisms for subscription maintenance, terminology definitions, stream discovery. 3rd party subscriptions are out-of-scope. SSE only used with Restconf and HTTP1.1 Dynamic Subscriptions Timeframes for event tagging are self-defined. Clean-up of wording, references to terminology, section numbers. v00 - v01 Removed the ability for more than one subscription to go to a single HTTP2 stream. Updated call flows. Extensively. SSE only used with Restconf and HTTP1.1 Dynamic Subscriptions HTTP is not used to determine that a Receiver has gone silent and is not Receiving Event Notifications Many clean-ups of wording and terminology