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] Suggestion further validity-checking

Previous message (by thread): [db-wg] Suggestion further validity-checking

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

Edward Shryane eshryane at ripe.net
Tue May 28 13:36:54 CEST 2019

Hi Jens,

> On 28 May 2019, at 13:21, Jens Ott - Opteamax GmbH via db-wg <db-wg at ripe.net> wrote:
> 
> Hi Job,
> 
> sure I can ;)
> 
> 
> route:          176.67.224.0/21
> descr:          VITSOL ASN route
> origin:         AS56973
> holes:          176.67.226.0/21
> mnt-by:         JKRATOS
> mnt-by:         OHUBALEK-MNT
> mnt-by:         PS32766-MNT
> created:        2011-06-29T13:16:32Z
> last-modified:  2017-01-30T12:27:51Z
> source:         RIPE
> 
> The holes network could have a maximum netmask of /23
> 

Whois returns a different error in this case: "prefix length 21 is invalid on 176.67.226.0/21".

This is the only holes attribute where the prefix length doesn't match the prefix (as you mentioned, /23 is ok).


> Kind regards
> Jens
> 


Regards
Ed Shryane
RIPE NCC

Previous message (by thread): [db-wg] Suggestion further validity-checking

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

[ db-wg Archives ]