[PDB-tech] proposed new attribute: max_allowed_peering_next_hop_latency

[Job Snijders]

Hi PDB,

I propose a new attribute for network records called
"max_allowed_peering_next_hop_latency".

The purpose of this attribute is to signal to other interested parties
(human peering coordinators looking for new interconnection, or computer
scripts generating route server configs) what the maximum unidirectional
latency can be between the two (potentially) peering routers.

Some networks have as part of their peering policy that there will be no
more then a certain number of miliseconds latency between the direct BGP
peers - it would be good to be able to express that consideration in
PeeringDB.

This value is ONLY intended to express something about eBGP inter-domain
peering links, not backbone links.

The default value can be "" (undefined), other allowed values would be
positive non-zero integers. The value's datatype is miliseconds.

I expect some IP carriers to use the value as part of signalling their
peering requirements, and some (distributed/remotely peered) IXPs to use
the value to assist in their route server configuration generation
process.

Thoughts?

Kind regards,

Job