< draft-ietf-netconf-subscribed-notifications-25.txt   draft-ietf-netconf-subscribed-notifications-26.txt >
NETCONF E. Voit NETCONF E. Voit
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track A. Clemm Intended status: Standards Track A. Clemm
Expires: November 2, 2019 Huawei Expires: November 9, 2019 Huawei
A. Gonzalez Prieto A. Gonzalez Prieto
Microsoft Microsoft
E. Nilsen-Nygaard E. Nilsen-Nygaard
A. Tripathy A. Tripathy
Cisco Systems Cisco Systems
May 01, 2019 May 8, 2019
Subscription to YANG Event Notifications Subscription to YANG Event Notifications
draft-ietf-netconf-subscribed-notifications-25 draft-ietf-netconf-subscribed-notifications-26
Abstract Abstract
This document defines a YANG data model and associated mechanisms This document defines a YANG data model and associated mechanisms
enabling subscriber-specific subscriptions to a publisher's event enabling subscriber-specific subscriptions to a publisher's event
streams. Applying these elements allows a subscriber to request for streams. Applying these elements allows a subscriber to request for
and receive a continuous, custom feed of publisher generated and receive a continuous, custom feed of publisher generated
information. information.
Status of This Memo Status of This Memo
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 November 2, 2019. This Internet-Draft will expire on November 9, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 49 skipping to change at page 2, line 49
2.9. Advertisement . . . . . . . . . . . . . . . . . . . . . . 32 2.9. Advertisement . . . . . . . . . . . . . . . . . . . . . . 32
3. YANG Data Model Trees . . . . . . . . . . . . . . . . . . . . 32 3. YANG Data Model Trees . . . . . . . . . . . . . . . . . . . . 32
3.1. Event Streams Container . . . . . . . . . . . . . . . . . 32 3.1. Event Streams Container . . . . . . . . . . . . . . . . . 32
3.2. Filters Container . . . . . . . . . . . . . . . . . . . . 33 3.2. Filters Container . . . . . . . . . . . . . . . . . . . . 33
3.3. Subscriptions Container . . . . . . . . . . . . . . . . . 33 3.3. Subscriptions Container . . . . . . . . . . . . . . . . . 33
4. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 35 4. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 35
5. Considerations . . . . . . . . . . . . . . . . . . . . . . . 62 5. Considerations . . . . . . . . . . . . . . . . . . . . . . . 62
5.1. IANA Considerations . . . . . . . . . . . . . . . . . . . 62 5.1. IANA Considerations . . . . . . . . . . . . . . . . . . . 62
5.2. Implementation Considerations . . . . . . . . . . . . . . 63 5.2. Implementation Considerations . . . . . . . . . . . . . . 63
5.3. Transport Requirements . . . . . . . . . . . . . . . . . 64 5.3. Transport Requirements . . . . . . . . . . . . . . . . . 64
5.4. Security Considerations . . . . . . . . . . . . . . . . . 64 5.4. Security Considerations . . . . . . . . . . . . . . . . . 65
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 68 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 68
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 68 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.1. Normative References . . . . . . . . . . . . . . . . . . 68 7.1. Normative References . . . . . . . . . . . . . . . . . . 69
7.2. Informative References . . . . . . . . . . . . . . . . . 70 7.2. Informative References . . . . . . . . . . . . . . . . . 70
Appendix A. Example Configured Transport Augmentation . . . . . 71 Appendix A. Example Configured Transport Augmentation . . . . . 71
Appendix B. Changes between revisions . . . . . . . . . . . . . 73 Appendix B. Changes between revisions . . . . . . . . . . . . . 73
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 79
1. Introduction 1. Introduction
This document defines a YANG data model and associated mechanisms This document defines a YANG data model and associated mechanisms
enabling subscriber-specific subscriptions to a publisher's event enabling subscriber-specific subscriptions to a publisher's event
streams. Effectively this enables a 'subscribe then publish' streams. Effectively this enables a 'subscribe then publish'
skipping to change at page 6, line 25 skipping to change at page 6, line 25
Note that there is no mixing-and-matching of dynamic and configured Note that there is no mixing-and-matching of dynamic and configured
operations on a single subscription. Specifically, a configured operations on a single subscription. Specifically, a configured
subscription cannot be modified or deleted using RPCs defined in this subscription cannot be modified or deleted using RPCs defined in this
document. Similarly, a dynamic subscription cannot be directly document. Similarly, a dynamic subscription cannot be directly
modified or deleted by configuration operations. It is however modified or deleted by configuration operations. It is however
possible to perform a configuration operation which indirectly possible to perform a configuration operation which indirectly
impacts a dynamic subscription. By changing value of a pre- impacts a dynamic subscription. By changing value of a pre-
configured filter referenced by an existing dynamic subscription, the configured filter referenced by an existing dynamic subscription, the
selected event records passed to a receiver might change. selected event records passed to a receiver might change.
Also note that transport specific transport specifications based on Also note that transport-specific specifications based on this
this specification MUST detail the lifecycle of dynamic specification MUST detail the lifecycle of dynamic subscriptions, as
subscriptions, as well as the lifecycle of configured subscriptions well as the lifecycle of configured subscriptions (if supported).
(if supported).
A publisher MAY terminate a dynamic subscription at any time. A publisher MAY terminate a dynamic subscription at any time.
Similarly, it MAY decide to temporarily suspend the sending of Similarly, it MAY decide to temporarily suspend the sending of
notification messages for any dynamic subscription, or for one or notification messages for any dynamic subscription, or for one or
more receivers of a configured subscription. Such termination or more receivers of a configured subscription. Such termination or
suspension is driven by internal considerations of the publisher. suspension is driven by internal considerations of the publisher.
1.4. Relationship to RFC 5277 1.4. Relationship to RFC 5277
This document is intended to provide a superset of the subscription This document is intended to provide a superset of the subscription
skipping to change at page 8, line 52 skipping to change at page 8, line 52
messages during network transit. messages during network transit.
o A "weighting" so that bandwidth proportional to this weighting can o A "weighting" so that bandwidth proportional to this weighting can
be allocated to this subscription relative to other subscriptions. be allocated to this subscription relative to other subscriptions.
o a "dependency" upon another subscription. o a "dependency" upon another subscription.
If the publisher supports the "dscp" feature, then a subscription If the publisher supports the "dscp" feature, then a subscription
with a "dscp" leaf MUST result in a corresponding [RFC2474] DSCP with a "dscp" leaf MUST result in a corresponding [RFC2474] DSCP
marking being placed within the IP header of any resulting marking being placed within the IP header of any resulting
notification messages and subscription state change notifications. notification messages and subscription state change notifications. A
publisher MUST respect the DSCP markings for subscription traffic
egressing that publisher.
Where TCP is used, a publisher which supports the "dscp" feature Different DSCP code points require different transport connections.
SHOULD ensure that a subscription's notification messages are As a result where TCP is used, a publisher which supports the "dscp"
feature must ensure that a subscription's notification messages are
returned within a single TCP transport session where all traffic returned within a single TCP transport session where all traffic
shares the subscription's "dscp" leaf value. Where this cannot be shares the subscription's "dscp" leaf value. Where this cannot be
guaranteed, any "establish subscription" RPC request SHOULD be guaranteed, any "establish subscription" RPC request SHOULD be
rejected with a "dscp-unavailable" error. rejected with a "dscp-unavailable" error.
For the "weighting" parameter, when concurrently dequeuing For the "weighting" parameter, when concurrently dequeuing
notification messages from multiple subscriptions to a receiver, the notification messages from multiple subscriptions to a receiver, the
publisher MUST allocate bandwidth to each subscription proportionally publisher MUST allocate bandwidth to each subscription proportionally
to the weights assigned to those subscriptions. "Weighting" is an to the weights assigned to those subscriptions. "Weighting" is an
optional capability of the publisher; support for it is identified optional capability of the publisher; support for it is identified
skipping to change at page 9, line 30 skipping to change at page 9, line 33
buffered notification messages containing event records selected by buffered notification messages containing event records selected by
the parent subscription MUST be dequeued prior to the notification the parent subscription MUST be dequeued prior to the notification
messages of the dependent subscription. If notification messages messages of the dependent subscription. If notification messages
have dependencies on each other, the notification message queued the have dependencies on each other, the notification message queued the
longest MUST go first. If a "dependency" included within an RPC longest MUST go first. If a "dependency" included within an RPC
references a subscription which does not exist or is no longer references a subscription which does not exist or is no longer
accessible to that subscriber, that "dependency" MUST be silently accessible to that subscriber, that "dependency" MUST be silently
removed. "Dependency" is an optional capability of the publisher; removed. "Dependency" is an optional capability of the publisher;
support for it is identified via the "qos" feature. support for it is identified via the "qos" feature.
"Dependency" and "weight" parameters will only be respected and
enforced between subscriptions that share the same "dscp" leaf value.
There are additional types over publisher capacity overload which
this specification does not address within its scope. For example,
the prioritization of which subscriptions have precedence when the
publisher CPU is overloaded is not discussed. As a result,
implementation choices will need to be made to address such
considerations.
2.4. Dynamic Subscriptions 2.4. Dynamic Subscriptions
Dynamic subscriptions are managed via protocol operations (in the Dynamic subscriptions are managed via protocol operations (in the
form of [RFC7950], Section 7.14 RPCs) made against targets located form of [RFC7950], Section 7.14 RPCs) made against targets located
within the publisher. These RPCs have been designed extensibly so within the publisher. These RPCs have been designed extensibly so
that they may be augmented for subscription targets beyond event that they may be augmented for subscription targets beyond event
streams. For examples of such augmentations, see the RPC streams. For examples of such augmentations, see the RPC
augmentations within [I-D.ietf-netconf-yang-push]'s YANG model. augmentations within [I-D.ietf-netconf-yang-push]'s YANG model.
2.4.1. Dynamic Subscription State Model 2.4.1. Dynamic Subscription State Model
skipping to change at page 18, line 45 skipping to change at page 18, line 45
o Optional parameters to identify where traffic should egress a o Optional parameters to identify where traffic should egress a
publisher: publisher:
* A "source-interface" which identifies the egress interface to * A "source-interface" which identifies the egress interface to
use from the publisher. Publisher support for this is optional use from the publisher. Publisher support for this is optional
and advertised using the "interface-designation" feature. and advertised using the "interface-designation" feature.
* A "source-address" address, which identifies the IP address to * A "source-address" address, which identifies the IP address to
stamp on notification messages destined for the receiver. stamp on notification messages destined for the receiver.
* A "source-vrf" which identifies the VRF on which to reach * A "source-vrf" which identifies the Virtual Routing and
receivers. This VRF is a network instance as defined within Forwarding (VRF) instance on which to reach receivers. This
[I-D.draft-ietf-rtgwg-ni-model]. Publisher support for VRFs is VRF is a network instance as defined within [RFC8529].
optional and advertised using the "supports-vrf" feature. Publisher support for VRFs is optional and advertised using the
"supports-vrf" feature.
If none of the above parameters are set, notification messages If none of the above parameters are set, notification messages
MUST egress the publisher's default interface. MUST egress the publisher's default interface.
A tree diagram describing these parameters is shown in Figure 20 A tree diagram describing these parameters is shown in Figure 20
within Section 3.3. All parameters are described within the YANG within Section 3.3. All parameters are described within the YANG
model in Section 4. model in Section 4.
2.5.1. Configured Subscription State Model 2.5.1. Configured Subscription State Model
skipping to change at page 20, line 6 skipping to change at page 20, line 6
(*): resulting subscription state change notification (*): resulting subscription state change notification
Figure 8: Publisher state model for a configured subscription Figure 8: Publisher state model for a configured subscription
A subscription in the valid state may move to the invalid state in A subscription in the valid state may move to the invalid state in
one of two ways. First, it may be modified in a way which fails a one of two ways. First, it may be modified in a way which fails a
re-evaluation. See (2) in the diagram. Second, the publisher might re-evaluation. See (2) in the diagram. Second, the publisher might
determine that the subscription is no longer supportable. This could determine that the subscription is no longer supportable. This could
be for reasons of an unexpected but sustained increase in an event be for reasons of an unexpected but sustained increase in an event
stream's event records, degraded CPU capacity, a more complex stream's event records, degraded CPU capacity, a more complex
referenced filter, or other higher priority subscriptions which have referenced filter, or other subscriptions which have usurped
usurped resources. See (3) in the diagram. No matter the case, a resources. See (3) in the diagram. No matter the case, a
"subscription-terminated" notification is sent to any receivers in an "subscription-terminated" notification is sent to any receivers in an
active or suspended state. A subscription in the valid state may active or suspended state. A subscription in the valid state may
also transition to the concluded state via (5) if a configured stop also transition to the concluded state via (5) if a configured stop
time has been reached. In this case, a "subscription-concluded" time has been reached. In this case, a "subscription-concluded"
notification is sent to any receivers in active or suspended states. notification is sent to any receivers in active or suspended states.
Finally, a subscription may be deleted by configuration (4). Finally, a subscription may be deleted by configuration (4).
When a subscription is in the valid state, a publisher will attempt When a subscription is in the valid state, a publisher will attempt
to connect with all receivers of a configured subscription and to connect with all receivers of a configured subscription and
deliver notification messages. Below is the state machine for each deliver notification messages. Below is the state machine for each
skipping to change at page 25, line 45 skipping to change at page 25, line 45
<eventTime>2007-09-01T10:00:00Z</eventTime> <eventTime>2007-09-01T10:00:00Z</eventTime>
<link-failure xmlns="http://acme.example.com/system"> <link-failure xmlns="http://acme.example.com/system">
<if-name>so-1/2/3.0</if-name> <if-name>so-1/2/3.0</if-name>
<if-admin-status>up</if-admin-status> <if-admin-status>up</if-admin-status>
<if-oper-status>down</if-oper-status> <if-oper-status>down</if-oper-status>
</link-failure> </link-failure>
</notification> </notification>
Figure 10: subscribed notification message Figure 10: subscribed notification message
[RFC5277] Section 2.2.1 states that a notification message is to be
sent to a subscriber which initiated a "create-subscription". With
this specification, this [RFC5277] statement should be more broadly
interpreted to mean that notification messages can also be sent to a
subscriber which initiated an "establish-subscription", or a
configured receiver which has been sent a "subscription-started".
When a dynamic subscription has been started or modified, with When a dynamic subscription has been started or modified, with
"establish-subscription" or "modify-subscription" respectively, event "establish-subscription" or "modify-subscription" respectively, event
records matching the newly applied filter criteria MUST NOT be sent records matching the newly applied filter criteria MUST NOT be sent
until after the RPC reply has been sent. until after the RPC reply has been sent.
When a configured subscription has been started or modified, event When a configured subscription has been started or modified, event
records matching the newly applied filter criteria MUST NOT be sent records matching the newly applied filter criteria MUST NOT be sent
until after the "subscription-started" or "subscription-modified" until after the "subscription-started" or "subscription-modified"
notifications has been sent, respectively. notifications has been sent, respectively.
skipping to change at page 35, line 23 skipping to change at page 35, line 23
Figure 20: Subscriptions tree diagram Figure 20: Subscriptions tree diagram
Above is a tree diagram for the subscriptions container. All objects Above is a tree diagram for the subscriptions container. All objects
contained in this tree are described within the included YANG model contained in this tree are described within the included YANG model
within Section 4. within Section 4.
4. Data Model 4. Data Model
This module imports typedefs from [RFC6991], [RFC8343], and This module imports typedefs from [RFC6991], [RFC8343], and
[RFC8040], and it references [I-D.draft-ietf-rtgwg-ni-model], [RFC8040], and it references [RFC8529], [XPATH], [RFC6241],
[XPATH], [RFC6241], [RFC7049], [RFC7540], [RFC7951] , [RFC7950] and [RFC7049], [RFC7540], [RFC7951] , [RFC7950] and [RFC8259].
[RFC8259].
[ note to the RFC Editor - please replace XXXX within this YANG model [ note to the RFC Editor - please replace XXXX within this YANG model
with the number of this document, and XXXY with the number of with the number of this document ]
[I-D.draft-ietf-rtgwg-ni-model] ]
[ note to the RFC Editor - please replace the two dates within the [ note to the RFC Editor - please replace the two dates within the
YANG module with the date of publication ] YANG module with the date of publication ]
<CODE BEGINS> file "ietf-subscribed-notifications@2019-05-01.yang" <CODE BEGINS> file "ietf-subscribed-notifications@2019-05-06.yang"
module ietf-subscribed-notifications { module ietf-subscribed-notifications {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"; "urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications";
prefix sn; prefix sn;
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
skipping to change at page 36, line 4 skipping to change at page 35, line 49
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"RFC 8343: A YANG Data Model for Interface Management"; "RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-netconf-acm { import ietf-netconf-acm {
prefix nacm; prefix nacm;
reference reference
"RFC 8341: Network Configuration Access Control Model"; "RFC 8341: Network Configuration Access Control Model";
} }
import ietf-network-instance { import ietf-network-instance {
prefix ni; prefix ni;
reference reference
"draft-ietf-rtgwg-ni-model-12: YANG Model for Network Instances"; "RFC 8529: YANG Model for Network Instances";
} }
import ietf-restconf { import ietf-restconf {
prefix rc; prefix rc;
reference reference
"RFC 8040: RESTCONF Protocol"; "RFC 8040: RESTCONF Protocol";
} }
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
skipping to change at page 37, line 14 skipping to change at page 37, line 12
Redistribution and use in source and binary forms, with or without Redistribution and use in source and binary forms, with or without
modification, is permitted pursuant to, and subject to the license modification, is permitted pursuant to, and subject to the license
terms contained in, the Simplified BSD License set forth in Section terms contained in, the Simplified BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating to IETF Documents 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the RFC This version of this YANG module is part of RFC XXXX; see the RFC
itself for full legal notices."; itself for full legal notices.";
revision 2019-05-01 { revision 2019-05-06 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX:Subscription to YANG Event Notifications"; "RFC XXXX:Subscription to YANG Event Notifications";
} }
/* /*
* FEATURES * FEATURES
*/ */
skipping to change at page 51, line 10 skipping to change at page 51, line 10
description description
"Information in a 'modify-subscription' RPC error response "Information in a 'modify-subscription' RPC error response
which indicates the reason why the subscription to an event which indicates the reason why the subscription to an event
stream has failed to be modified."; stream has failed to be modified.";
} }
leaf filter-failure-hint { leaf filter-failure-hint {
type string; type string;
description description
"Information describing where and/or why a provided filter "Information describing where and/or why a provided filter
was unsupportable for a subscription."; was unsupportable for a subscription. The syntax and
semantics of this hint are implementation-specific.";
} }
} }
} }
rpc delete-subscription { rpc delete-subscription {
description description
"This RPC allows a subscriber to delete a subscription that "This RPC allows a subscriber to delete a subscription that
was previously created from by that same subscriber using the was previously created from by that same subscriber using the
'establish-subscription' RPC. 'establish-subscription' RPC.
skipping to change at page 64, line 39 skipping to change at page 64, line 39
may not choose to require the use of the same logical channel for the may not choose to require the use of the same logical channel for the
RPCs and the event records. However the event records and the RPCs and the event records. However the event records and the
subscription state change notifications MUST be sent on the same subscription state change notifications MUST be sent on the same
transport session to ensure the properly ordered delivery. transport session to ensure the properly ordered delivery.
A specific transport specification MUST identity any encoding A specific transport specification MUST identity any encoding
supported. Where a configured subscription's transport allows supported. Where a configured subscription's transport allows
different encodings, the specification MUST identify the default different encodings, the specification MUST identify the default
encoding. encoding.
A subscriber which includes a "dscp" leaf within an "establish-
subscription" request will need to understand and consider what the
corresponding DSCP value represents within the domain of the
publisher.
Additional transport requirements will be dictated by the choice of Additional transport requirements will be dictated by the choice of
transport used with a subscription. For an example of such transport used with a subscription. For an example of such
requirements with NETCONF transport, see requirements with NETCONF transport, see
[I-D.draft-ietf-netconf-netconf-event-notifications]. [I-D.draft-ietf-netconf-netconf-event-notifications].
5.4. Security Considerations 5.4. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management transports that is designed to be accessed via network management transports
such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF
skipping to change at page 65, line 37 skipping to change at page 65, line 45
For dynamic subscriptions, implementations need to protect against For dynamic subscriptions, implementations need to protect against
malicious or buggy subscribers which may send a large number malicious or buggy subscribers which may send a large number
"establish-subscription" requests, thereby using up system resources. "establish-subscription" requests, thereby using up system resources.
To cover this possibility operators SHOULD monitor for such cases To cover this possibility operators SHOULD monitor for such cases
and, if discovered, take remedial action to limit the resources used, and, if discovered, take remedial action to limit the resources used,
such as suspending or terminating a subset of the subscriptions or, such as suspending or terminating a subset of the subscriptions or,
if the underlying transport is session based, terminate the if the underlying transport is session based, terminate the
underlying transport session. underlying transport session.
The replay mechanisms described in Sections Section 2.4.2.1 and The replay mechanisms described in Section 2.4.2.1 and Section 2.5.6
Section 2.5.6 provides access to historical event records. By provides access to historical event records. By design, the access
design, the access control model that protects these records could control model that protects these records could enable subscribers to
enable subscribers to view data to which they were not authorized at view data to which they were not authorized at the time of
the time of collection. collection.
Using DNS names for configured subscription receiver "name" lookup Using DNS names for configured subscription receiver "name" lookup
can cause situations where the name resolves unexpectedly differently can cause situations where the name resolves unexpectedly differently
on the publisher, so the recipient would be different than expected. on the publisher, so the recipient would be different than expected.
An attacker that can cause the publisher to use an incorrect time can An attacker that can cause the publisher to use an incorrect time can
induce message replay by setting the time in the past, and introduce induce message replay by setting the time in the past, and introduce
a risk of message loss by setting the time in the future. a risk of message loss by setting the time in the future.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that are
skipping to change at page 69, line 5 skipping to change at page 69, line 11
For their valuable comments, discussions, and feedback, we wish to For their valuable comments, discussions, and feedback, we wish to
acknowledge Andy Bierman, Tim Jenkins, Martin Bjorklund, Kent Watsen, acknowledge Andy Bierman, Tim Jenkins, Martin Bjorklund, Kent Watsen,
Balazs Lengyel, Robert Wilton, Sharon Chisholm, Hector Trevino, Susan Balazs Lengyel, Robert Wilton, Sharon Chisholm, Hector Trevino, Susan
Hares, Michael Scharf, and Guangying Zheng. Hares, Michael Scharf, and Guangying Zheng.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.draft-ietf-rtgwg-ni-model]
Berger, L., Hopps, C., and A. Lindem, "YANG Network
Instances", draft-ietf-rtgwg-ni-model-12 (work in
progress), March 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
DOI 10.17487/RFC2474, December 1998, DOI 10.17487/RFC2474, December 1998,
<https://www.rfc-editor.org/info/rfc2474>. <https://www.rfc-editor.org/info/rfc2474>.
skipping to change at page 70, line 35 skipping to change at page 70, line 35
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8529] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X.
Liu, "YANG Data Model for Network Instances", RFC 8529,
DOI 10.17487/RFC8529, March 2019,
<https://www.rfc-editor.org/info/rfc8529>.
[XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath) [XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath)
Version 1.0", November 1999, Version 1.0", November 1999,
<http://www.w3.org/TR/1999/REC-xpath-19991116>. <http://www.w3.org/TR/1999/REC-xpath-19991116>.
7.2. Informative References 7.2. Informative References
[I-D.draft-ietf-netconf-netconf-event-notifications] [I-D.draft-ietf-netconf-netconf-event-notifications]
Clemm, Alexander., Voit, Eric., Gonzalez Prieto, Alberto., Clemm, Alexander., Voit, Eric., Gonzalez Prieto, Alberto.,
Nilsen-Nygaard, E., and A. Tripathy, "NETCONF support for Nilsen-Nygaard, E., and A. Tripathy, "NETCONF support for
event notifications", May 2018, event notifications", May 2019,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-netconf-netconf-event-notifications/>. draft-ietf-netconf-netconf-event-notifications/>.
[I-D.draft-ietf-netconf-restconf-notif] [I-D.draft-ietf-netconf-restconf-notif]
Voit, Eric., Clemm, Alexander., Tripathy, A., Nilsen- Voit, Eric., Clemm, Alexander., Tripathy, A., Nilsen-
Nygaard, E., and Alberto. Gonzalez Prieto, "Restconf and Nygaard, E., and Alberto. Gonzalez Prieto, "Restconf and
HTTP transport for event notifications", May 2018, HTTP transport for event notifications", May 2019,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-netconf-restconf-notif/>. draft-ietf-netconf-restconf-notif/>.
[I-D.ietf-netconf-yang-push] [I-D.ietf-netconf-yang-push]
Clemm, Alexander., Voit, Eric., Gonzalez Prieto, Alberto., Clemm, Alexander., Voit, Eric., Gonzalez Prieto, Alberto.,
Tripathy, A., Nilsen-Nygaard, E., Bierman, A., and B. Tripathy, A., Nilsen-Nygaard, E., Bierman, A., and B.
Lengyel, "YANG Datastore Subscription", May 2018, Lengyel, "YANG Datastore Subscription", May 2019,
<https://datatracker.ietf.org/doc/ <https://datatracker.ietf.org/doc/
draft-ietf-netconf-yang-push/>. draft-ietf-netconf-yang-push/>.
[RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object
Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049, Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049,
October 2013, <https://www.rfc-editor.org/info/rfc7049>. October 2013, <https://www.rfc-editor.org/info/rfc7049>.
[RFC7540] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext [RFC7540] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext
Transfer Protocol Version 2 (HTTP/2)", RFC 7540, Transfer Protocol Version 2 (HTTP/2)", RFC 7540,
DOI 10.17487/RFC7540, May 2015, DOI 10.17487/RFC7540, May 2015,
skipping to change at page 73, line 27 skipping to change at page 73, line 27
foo foo
This example YANG model for transport "foo" will not be seen in a This example YANG model for transport "foo" will not be seen in a
real world deployment. For a real world deployment supporting an real world deployment. For a real world deployment supporting an
actual transport technology, a similar YANG model must be defined. actual transport technology, a similar YANG model must be defined.
Appendix B. Changes between revisions Appendix B. Changes between revisions
(To be removed by RFC editor prior to publication) (To be removed by RFC editor prior to publication)
v25 - v26
o Tweaks from Alissa Cooper's review, and Benjamin Kaduk's discuss.
o Magnus' review help refine the words on several 'overload'
considerations. And a couple of QoS requirements were clarified.
o Note on interpreting RFC-5277 so that notification messages can
follow establish-subscription RPCs.
o draft-ietf-rtgwg-ni-model updated to RFC-8529
v24 - v25 v24 - v25
o Replay security consideration added based on Roman Danyliw's o Replay security consideration added based on Roman Danyliw's
discuss discuss
o Spelling fixes, acronyms expanded o Spelling fixes, acronyms expanded
o Tweaks and updates based Benjamin Kaduk's comments. This includes o Tweaks and updates based Benjamin Kaduk's comments. This includes
the adding of clarifying security considerations, a couple of the adding of clarifying security considerations, a couple of
claifications in the YANG definitions, and ensuring a fuller set claifications in the YANG definitions, and ensuring a fuller set
 End of changes. 28 change blocks. 
43 lines changed or deleted 78 lines changed or added

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