This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] "AND NOT" in as-expression
- Previous message (by thread): [db-wg] Fwd: RIPE68 DB-WG Draft Agenda (interim) V2
- Next message (by thread): [db-wg] "AND NOT" in as-expression
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aris Lambrianidis
aristidis.lambrianidis at ams-ix.net
Mon May 12 10:01:44 CEST 2014
Good morning all, 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 Kind regards, Aris Lambrianidis AMS-IX -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: </ripe/mail/archives/db-wg/attachments/20140512/a76db806/attachment.sig>
- Previous message (by thread): [db-wg] Fwd: RIPE68 DB-WG Draft Agenda (interim) V2
- Next message (by thread): [db-wg] "AND NOT" in as-expression
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]