I'd really like to urge us to stick to 'what is the problem we are
trying to solve?'
Specifically:
 "Can you define a 'route-leak' please"

and I'm OK with there being more than one TYPE of 'route-leak', job 1
for GROW should be to do this, then move along to: "And operations
folk really don't like these types of things, could there be a remedy
please?"


-chris

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to