Skip to content

Issues: netmod-wg/opstate-reqs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8 Open 1 Closed
8 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

use term "server" throughout draft DONE Editorial
#9 opened Oct 15, 2015 by kwatsen
ability to retrieve both op-state types together DONE
#8 opened Oct 5, 2015 by kwatsen
4
Why limit scope to just IETF-defined modules DONE
#7 opened Sep 14, 2015 by kwatsen
4
clarify impact of synchronous vs asynchronous (esp. wrt intended and applied) DONE
#6 opened Sep 14, 2015 by kwatsen
4
Support for situations when structure of intended configuration is not the same as applied DEAD
#5 opened Sep 14, 2015 by cmoberg
19
Provide a tighter definition of "applied configuration" DONE
#4 opened Sep 14, 2015 by rgwilton
6
Is there a requirement for asynchronous systems to provide a blocking config update? DONE
#3 opened Sep 14, 2015 by rgwilton
10
Define/Clarify "fully synchronized" in "Requirement 1.D" DONE
#1 opened Sep 14, 2015 by rgwilton
3
ProTip! Updated in the last three days: updated:>2025-02-01.