new filter types and specifics for I2RS protocol?) EN2 Filter, Clarify interplay between filter definitions and different streams. Includes Stream information in subtrees of event payloads. EN3 OAM Mechanisms for diagnostics, e.g. deal with dropped updates, monitoring when they occur, etc. EN4 Encoding, How to allow for seamless integration with non-standard encodings and Transport transports (like GPB/GRPC). Specify requirements encoding and transport must meet, provide examples. EN5 Compatibility Along with Netconf-notif, should this draft obsolete 5277 or be in parallel with it? EN6 Stream Stream discovery. Are adjustments needed for maximal transport independence? EN7 QoS Eric Detecting loss of a sequential update notification, and mechanisms to resend. Implications to transports must be thought through. EN8 Transport Should we have a mandatory transport? EN9 Configured Multiple receivers per Configured Subscription is ok EN10 Stream Replay support will be provided for selected stream types (modify vs. delete) EN11 Security Required layering security requirements/considerations will be added into the YANG model for Configured Subscriptions. It will be up to the transport to meet these requirements. EN12 OAM Test-only option for a subscription is desired. But it still needs to be defined. EN13 Filter RFC6241 Subtree-filter definition in 5277bis cannot apply to elements of an event. Must explicitly define how 6241 doesn't apply filtering within a 5277bis event. EN14 Document Ensure that Configured Subscriptions are fully defined in YANG model. EN15 Document Term for Dynamic and Static Subscriptions (move to "Configured") EN16 Document move Subscription ID in Notification to this document from Yang-push EN17 QoS An ETag is an opaque identifier assigned by a web server to a specific version of a resource found at a URL. If the resource representation at that URL ever changes, a new and different ETag is assigned. Do we want an entity tag MUST be maintained for the root of any subscription? Should this allow correlation across independent subscriptions? Should
new filter types and specifics for I2RS protocol?) EN2 Filter, Stream Clarify interplay between filter definitions and different streams. Includes information in subtrees of event payloads. EN3 OAM Mechanisms for diagnostics, e.g. deal with dropped updates, monitoring when they occur, etc. EN4 Encoding, Transport How to allow for seamless integration with non-standard encodings and transports (like GPB/GRPC). Specify requirements encoding and transport must meet, provide examples. EN5 Compatibility Along with Netconf-notif, should this draft obsolete 5277 or be in parallel with it? EN6 Stream Stream discovery. Are adjustments needed for maximal transport independence? EN7 QoS Eric Detecting loss of a sequential update notification, and mechanisms to resend. Implications to transports must be thought through. EN8 Transport Should we have a mandatory transport? EN9 Configured Multiple receivers per Configured Subscription is ok EN10 Stream Replay support will be provided for selected stream types (modify vs. delete) EN11 Security Required layering security requirements/considerations will be added into the YANG model for Configured Subscriptions. It will be up to the transport to meet these requirements. EN12 OAM Test-only option for a subscription is desired. But it still needs to be defined. EN13 Filter RFC6241 Subtree-filter definition in 5277bis cannot apply to elements of an event. Must explicitly define how 6241 doesn't apply filtering within a 5277bis event. EN14 Document Ensure that Configured Subscriptions are fully defined in YANG model. EN15 Document Term for Dynamic and Static Subscriptions (move to "Configured") EN16 Document move Subscription ID in Notification to this document from Yang-push EN17 QoS An ETag is an opaque identifier assigned by a web server to a specific version of a resource found at a URL. If the resource representation at that URL ever changes, a new and different ETag is assigned. Do we want an entity tag MUST be maintained for the root of any subscription? Should this allow correlation across independent subscriptions? Should
4Drafts-Issues-23June2016.docx