[db-wg] Proxy proposal large communities

Wouldn't it be better to just change the definition of community in the
RPSL dictionary so that a community of <digit>+ ":" <digit>+ ":"
<digit>+ is valid and then have the tools either barf if they don't
understand or do "the right thing"? That would seem more consistent with
the current scheme where a community can either be an integer or
<digit>+ ":" <digit>+.

I assume a router that can deal with large communities will accept
standard ones in the same clauses if someone wants to do that for local
use only communities.

Mark.

On 12/11/17 17:13, Tim Bruijnzeels via db-wg wrote:
> Dear Working Group,
> 
> As discussed at RIPE 75 I want to forward a request by Job Snijders on GitHub:
> https://github.com/RIPE-NCC/whois/issues/410
> 
> Job is asking to add a “large_community" keyword to RPSL dictionary where applicable.
> 
> And provides the following example:
> 
> Suggestion: name the keyword large_community
> 
> mp-export:      afi ipv6.unicast to AS13105 announce AS-RCNET-V6 AND NOT large_community.contains(21414:0:570)
> export:         to AS6777 action large_community .= { 6777:0:6777 }; announce AS-FORTHNET
> mp-import:      afi ipv6.unicast from AS8631 msk-rs2.ripn.net action large_community={31376:0:2}; pref=100; accept AS-MSKROUTESERVER
> import:         from AS35082 95.128.51.234 at 95.128.51.233 action pref=500; large_community.append(29527:0:35082,29527:0:60000,29527:0:61200,29527:0:61210); accept AS-VIBUS-LONDON
> 
> 
> filter-set:     fltr-as21229-export
> descr:          Filter for AS21229 exported prefixes
> filter:         AS-TVNETWORK AND large_community(21229:0:1)
> 
> 
> From our end I do not see any issues implementing this on the server side, but I can’t speak to how this will be treated by scripts that may parse RPSL today.
> 
> Please discuss.
> 
> Kind regards,
> 
> Tim Bruijnzeels
> Assistant Manager Software Engineering and Senior Technology Officer
> RIPE NCC
> 
> 
>