netmod-wg opstate-reqs issues - Githubissues

netmod-wg / opstate-reqs

draft-chairs-netmod-opstate-reqs

1 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

use term "server" throughout draft

#9 kwatsen opened 9 years ago
0
ability to retrieve both op-state types together

#8 kwatsen opened 9 years ago
4
Why limit scope to just IETF-defined modules

#7 kwatsen opened 9 years ago
4
clarify impact of synchronous vs asynchronous (esp. wrt intended and applied)

#6 kwatsen opened 9 years ago
4
Support for situations when structure of intended configuration is not the same as applied

#5 cmoberg opened 9 years ago
19
Provide a tighter definition of "applied configuration"

#4 rgwilton opened 9 years ago
6
Is there a requirement for asynchronous systems to provide a blocking config update?

#3 rgwilton opened 9 years ago
10
Is there a requirement to indicate why intended config != applied cfg?

#2 rgwilton closed 9 years ago
2
Define/Clarify "fully synchronized" in "Requirement 1.D"

#1 rgwilton opened 9 years ago
3