Re: [irs-discuss] Rough Draft IRS Charter

It may be also worth to document the conflict resolution mechanism
when "fast path" contradicts with "slow path" configurations ...

r.

On Mon, Oct 22, 2012 at 7:50 PM, Russ White <russw@riw.us> wrote:
>
> I think this has already been brought up on the list once before, but
> I'd just like to repeat my concerns on it:
>
> ==
> Thus, the IRS is a "fast path" that can be used to program routing and
> policy state in a router using operational paradigms familiar to
> operators of traditional distributed devices. This differs from the
> programmatic "slow state" that is commonly a device's configuration
> interface because those mechanisms impose many transactional mechanisms
> and requirements, that may slow down the interaction.
> ==
>
> Describing the CLI or other existing interfaces as the "slow path," and
> the proposed as the "fast path," is problematic. First, it implies that
> there is a specific path already available into all control plane
> devices, and that single path is "too slow," for some meaning of "too
> slow." Second, it implies, from the start, that we need new path, rather
> than a possible structure around existing paths that we can use to make
> sense of the routing system as a whole.
>
> I think 2a needs to be better defined so it doesn't overlap with 2c, or
> 2c needs to be made a part of 2a in some way (?).
>
> Thanks!
>
> Russ
>
>
>
> --
> <><
> riwhite@verisign.com
> russw@riw.us
> _______________________________________________
> irs-discuss mailing list
> irs-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/irs-discuss