网络配置通知
[英]Netconf Notifications
问题描述
RFC 5277 defines notification replay support. 
RFC 5277 定义了通知重放支持。 Just wondering what customer problems this notification replay can solve?只是想知道此通知重播可以解决哪些客户问题？ What could be the need to scan through list of past notifications?扫描过去的通知列表可能需要什么？ At any point of time, controllers can always fire "get" RPC and determine current state.在任何时候，控制器总是可以触发“get”RPC 并确定当前状态。
Any inputs on this are appreciated.对此的任何投入表示赞赏。
1 个解决方案
解决方案1
0 2019-10-10 13:41:25
Notification replay is mostly required to sync NETCONF clients with servers without the need to do a full RPC.通知重播主要用于将 NETCONF 客户端与服务器同步，而无需执行完整的 RPC。 In some systems, the configuration + operational data becomes quite large, so the notification replay allows for a delta sync.在某些系统中，配置 + 操作数据变得非常大，因此通知重放允许增量同步。
The main problem with this is that the server will only keep a limited time window of notifications;这样做的主要问题是服务器只会保留有限的通知时间窗口； so if a client asks for a replay of the last week, the server may be only able to provide a subset of that.所以如果客户端要求重播上周，服务器可能只能提供其中的一个子集。
RESTCONF has a different solution for this same issue, the last-modified header field( https://www.rfc-editor.org/rfc/rfc8040#section-3.4.1.1 ), which allows for doing a get of 'data that has changed since timestamp x'. RESTCONF 对同一问题有不同的解决方案，即最后修改的标头字段（ https://www.rfc-editor.org/rfc/rfc8040#section-3.4.1.1 ），它允许获取“数据”自时间戳 x' 以来发生了变化。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.