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] Prefix length for the "pingable" attribute

Previous message (by thread): [db-wg] Prefix length for the "pingable" attribute
Next message (by thread): [db-wg] Prefix length for the "pingable" attribute

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

Job Snijders job.snijders at hibernianetworks.com
Sat Mar 15 15:44:16 CET 2014

On Sat, Mar 15, 2014 at 02:53:09PM +0100, Tore Anderson wrote:
> Hi WG,
> 
> The documentation unequivocally states the value of the "pingable"
> attribute in route[6] objects must include a prefix length:

<snip>

RFC5943 [1] states that the value of the 'pingable:' attribute is either a
regular IPv4 or IPv6 address (rfc2622 / rfc4012), and makes absolutely no
mention of including a prefix length. 

It probably is a good move to update the RIPE Whois Server documentation
and ensure the value can only be a valid IPv4 or IPv6 address, without
prefix length.

Nice catch Tore!

Kind regards,

Job

[1] - https://tools.ietf.org/html/rfc5943 "RPSL Pingable Attribute"

Previous message (by thread): [db-wg] Prefix length for the "pingable" attribute
Next message (by thread): [db-wg] Prefix length for the "pingable" attribute

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

[ db-wg Archives ]