[db-wg] "AND NOT" in as-expression
- Previous message (by thread): [db-wg] "AND NOT" in as-expression
- Next message (by thread): [db-wg] "AND NOT" in as-expression
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Wed May 14 14:20:09 CEST 2014
On Mon, May 12, 2014 at 10:01:44AM +0200, Aris Lambrianidis wrote: > After tinkering around with import-via/export-via attributes, I > realised that "AND NOT" is not supported in the as-expression part of > peering specifications, although it is described in RFC2622 (along > with the semantically equivalent EXCEPT) and included in example (6) > of page 25. > > e.g. currently: > > import: from AS-AMS-IX-PEERS and not AS6777 accept ANY > > is not supported, while > > import: from AS-AMS-IX-PEERS except AS6777 accept ANY > > is. > > I have raised a ticket with RIPE NCC about it. Also, Job Snijders was > kind enough to act quickly and provide patches for both irrtoolset and > whois: https://github.com/RIPE-NCC/whois/pull/237 > http://irrtoolset.isc.org/ticket/48 My question to the community is: does this break your programs or procedures? Kind regards, Job
- Previous message (by thread): [db-wg] "AND NOT" in as-expression
- Next message (by thread): [db-wg] "AND NOT" in as-expression
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]