Re: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acceptown-community-01.txt

[Danny McPherson <[e-mail]>]

On Apr 30, 2008, at 2:56 PM, Enke Chen wrote:
>>
>> Sure..  I don't like the idea of changing specs to accommodate
>> implementation optimizations.
>
> welcome to the real world :-)

I do understand the reasoning behind this, although I
don't agree with it.

In the real world, operators are complaining about DFZ
sizes (unique routes), and routing scalability, and churn,
little implementation tweaks that surface as base spec
changes like this have serious implications.

Consider this 'optimization', for example.  Now, most
clusters have at least 2-3 RRs, and many clients.  If you've
got a single client that has 50k external paths that it sees
as best, and that client advertises them to the RRs, and
the RRs reflect them back, just so that the client can discard
them, then unless I'm confused, that little optimization just cost
you 150k (50k routes * 3 RRs, reflected back to client they
were learned from) worth update processing resources on
the clients.  Not to mention implications on churn, or additional
layers of RR hierarchy, or the dynamics this introduces in a
REAL network.

 From a network-level perspective I don't see much of an
optimization at all, quite the contrary, actually.

-danny
_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr