Mark,

This does not require any more trust for say directly connected peers more then today when you publish communities on the web page. 

It is not about opening up your network. It is about expressing your policy in a common way in the exact say amount as you would open up your network today. 

Notice that in addition to common types there is equal amount of space left for operator's define types. It is just that the structure of community can take number of arguments used during execution - that's all. 

Thx,
R.



On Tue, Sep 8, 2020 at 8:10 PM Mark Tinka <mark.tinka@seacom.com> wrote:


On 8/Sep/20 18:41, Robert Raszuk wrote:

> I don't think this is the ask here. 
>
> Today NO_EXPORT takes no parameters. I think it would be of benefit to
> all to be able to signal NO_EXPORT TO ASN_X in a common (std) way
> across all of my peers connected to ASN_X. Moreover policy on all
> vendors could understand it too without you worrying to match
> YOUR_STRING and translate into some local policy. 
>
> That is by no means taking away anything you have at your fingertips
> .. it just adds an option to talk common policy language.

This already happens today, but mostly in a commercial relationship
(customer and provider).

While not technically impossible, I struggle to see operators opening up
their networks to peers they hardly personally (or commercially) know
with such a feature, custom or standardized.

I suppose the bigger question is - can we trust each other, as peers,
with such access to each other's networks?

Mark.