On Wed, Jan 10, 2018 at 5:15 AM, Juergen Schoenwaelder < [email protected]> wrote:
> On Mon, Jan 08, 2018 at 05:05:09AM -0800, Eric Rescorla wrote: > > > > ---------------------------------------------------------------------- > > COMMENT: > > ---------------------------------------------------------------------- > > > > > > protocol interactions with other systems and that is neither > > conventional nor dynamic configuration. > > Could you provide an example of this? > > Many DHCP implementations do not go through a dynamic datastore and > deliver configuration state straight into the operational state. An IP > address learned via DHCP on such a system will be tagged with > or:learned. > I don't think it's imperative, but it would be nice to have this example in the text. > datastore that holds the complete current configuration on the > > device. It MAY include configuration that requires further > > transformation before it can be applied, e.g., inactive > > > > If I am reading the text, this doesn't seem to be true because "system > > configuration" is not included. > > Yes, it might make sense to remove 'complete' here to align the > sentence in 5.1.3 with the definition of 'running configuration > datastore'. > Thanks, -Ekr > > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
