Search results

use term "server" throughout draft

DONE

Editorial

Status: Open.

#9 In netmod-wg/opstate-reqs;

· kwatsen opened on Oct 15, 2015

ability to retrieve both op-state types together

DONE

Status: Open.

#8 In netmod-wg/opstate-reqs;

· kwatsen opened on Oct 5, 2015

Why limit scope to just IETF-defined modules

DONE

Status: Open.

#7 In netmod-wg/opstate-reqs;

· kwatsen opened on Sep 14, 2015

clarify impact of synchronous vs asynchronous (esp. wrt intended and applied)

DONE

Status: Open.

#6 In netmod-wg/opstate-reqs;

· kwatsen opened on Sep 14, 2015

Support for situations when structure of intended configuration is not the same as applied

DEAD

Status: Open.

#5 In netmod-wg/opstate-reqs;

· cmoberg opened on Sep 14, 2015

Provide a tighter definition of "applied configuration"

DONE

Status: Open.

#4 In netmod-wg/opstate-reqs;

· rgwilton opened on Sep 14, 2015

Is there a requirement for asynchronous systems to provide a blocking config update?

DONE

Status: Open.

#3 In netmod-wg/opstate-reqs;

· rgwilton opened on Sep 14, 2015

Define/Clarify "fully synchronized" in "Requirement 1.D"

DONE

Status: Open.

#1 In netmod-wg/opstate-reqs;

· rgwilton opened on Sep 14, 2015