All,
I think the common description is a good thing and not so hard to build.
What I think would be a bit more challenging is to create a protocol
extension where each AS (adjucent or not) would be able to signal set of
communities it honors and supports in an automated way.
Today it is all
Having gone through a flavor of this issue as part of the wide communities
work, I think you’ll find it a bit more constrained than you might think.
For purposes of a yang model, the main short term question is whether you wish
to collapse some of the actions to common ones that might be
Please remember to send the "what do your implementations do" questions to
the grow mailing list. This will let us aggregate the answers.
-- Jeff (an implementation owner)
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
