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] bug? accepting larger than 32 bit BGP Communities in RPSL
- Previous message (by thread): [db-wg] bug? accepting larger than 32 bit BGP Communities in RPSL
- Next message (by thread): [db-wg] bug? accepting larger than 32 bit BGP Communities in RPSL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kaveh Ranjbar
kranjbar at ripe.net
Mon Jan 7 19:05:36 CET 2013
Hello, The bug is fixed and the fix will be included in our next release. We will send an announcement when the release is deployed to the production. There are currently 8 objects in the RIPE Database containing invalid data regarding this new syntax check. We will contact their maintainers to fix those issues after the deployment. Kind Regards, Kaveh. --- Kaveh Ranjbar, RIPE NCC Database Group Manager On Jan 5, 2013, at 6:45 PM, Nigel Titley <nigel at titley.com> wrote: > > On 03/01/2013 20:23, Nick Hilliard wrote: >> On 02/01/2013 14:59, Job Snijders wrote: >>> Accepting 64 bit values where only 32bit values can exist is absolute >>> garbage and should not be accepted by the RIPE DB. >> Good grief, Job, it's only zeros and ones. Do chill out - bugs happen! >> > Looks like this is just a bug. Can we just get it fixed please? Shouldn't be too difficult I'm sure. > > Nigel >
- Previous message (by thread): [db-wg] bug? accepting larger than 32 bit BGP Communities in RPSL
- Next message (by thread): [db-wg] bug? accepting larger than 32 bit BGP Communities in RPSL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]