On Wed, Jan 10, 2018 at 07:00:18AM -0800, Eric Rescorla wrote:
> 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.
There is more explanatory text in section 5.3.4 and I believe this
should be sufficient:
o learned: represents configuration that has been learned via
protocol interactions with other systems, including protocols such
as link-layer negotiations, routing protocols, DHCP, etc.
/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
