Re: [i2rs] draft-mglt-i2rs-security-environment-reqs, REQ 3

<no-hats>

Good catch - this seems to be very aspirational and contradicts
what the architecture says - which is basically that the user may
cause issues.

Regards,
Alia
</no-hats>

On Thu, Aug 27, 2015 at 4:32 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:

> I've been reviewing the environment requirements, thanks for picking up
> this
> work.  Requirement 3 contains the following:
>
>    REQ 3:  The I2RS Agent validates data to ensure injecting the
>            information will not create a deadlock with any other system,
>            nor will it create a routing loop, nor will it cause the
>            control plane to fail to converge.
>
> I2RS has already received feedback from our netconf experts expressing
> concern over how validation even at the schema levels may introduce
> excessive latency.  This contradicts the I2RS "need for speed".
>
> I have a broader concern that the above requirement may simply be an
> intractable problem.  It's a loft goal, but the overhead in validating all
> such things is likely not within the goal of speed.
>
> Thoughts?
>
> -- Jeff
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>