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/db-wg@ripe.net/

[db-wg] RIPE DB syntax check for mp-import

Previous message (by thread): [db-wg] RIPE DB syntax check for mp-import
Next message (by thread): [db-wg] RIPE DB syntax check for mp-import

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Job Snijders job at ntt.net
Thu Aug 6 10:23:14 CEST 2015

On Thu, Aug 06, 2015 at 01:51:10AM +0200, Tomas Hlavacek wrote:
> I just noticed that aut-num object for AS2852 in RIPE DB contains line
> 
> mp-import:      afi ipv6.unicastfrom AS39790
> 
> with 'afi ipv6.unicast' and 'from' keywords merged, which causs some
> confusion of my parsing scripts.
> 
> Maybe I am missing something but I think this is not syntactically valid, is
> it? And if it is not, how could that get into RIPE DB?

Smells like a bug!

https://tools.ietf.org/html/rfc4012 states:

   The possible values for <afi> are as follows:

      ipv4.unicast
      ipv4.multicast
      ipv4 (equivalent to ipv4.unicast, ipv4.multicast)
      ipv6.unicast
      ipv6.multicast
      ipv6 (equivalent to ipv6.unicast, ipv6.multicast)
      any (equivalent to ipv4, ipv6)
      any.unicast (equivalent to ipv4.unicast, ipv6.unicast)
      any.multicast (equivalent to ipv4.multicast, ipv6.multicast)

Kind regards,

Job

Previous message (by thread): [db-wg] RIPE DB syntax check for mp-import
Next message (by thread): [db-wg] RIPE DB syntax check for mp-import

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]