[babel] Martin Duke's Discuss on draft-ietf-babel-source-specific-07: (with DISCUSS)

[Martin Duke via Datatracker <[e-mail]>]

Martin Duke has entered the following ballot position for
draft-ietf-babel-source-specific-07: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-source-specific/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I am concerned about the congestion implications of this architecture. If there
are P prefixes in the network, the number of TLVs exchanged potentially goes
from P to P^2.

Perhaps this is an unrealistic use case. But are there any safeguards in the
protocol against this happening (e.g. limitations on size/freq of updates?) Or
ought there to be some operational guidance to be somewhat selective about
source prefixes?