Hello,
recently I stumbled upon some less-used status of the INETNUM object,
namely LIR-PARTITIONED PA & LIR-PARTITIONED PI. Since there is no
difference in the docs
(https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/rpsl-object-types/4-2-descriptions-of
Am 20.09.18 um 15:40 schrieb denis walker:
> Hi Alexander
>
> You may well be right but duplicated personal data in a public database
> for 'convenience' is probably not acceptable.
Hi Dennis,
I totally agree with you. But unfortunately it's difficult to force ISPs
to clean up their data.
Regar
On 20/09/2018 15:04, denis walker via db-wg wrote:
> Colleagues,
>
> I will start with a blunt question, then give some arguments for my
> concern. In May the RIPE NCC told me there are?more than 2 million
> PERSON objects in the RIPE Database. That is almost 25% of the objects
> in the database. W
> What is the current best practice for handling Auth on HTTP API updates to
> the RIPE database, and is there a roadmap for change that I can consider as I
> write my tools to publish and maintain objects?
Same situation here on my end. Anyways, I'd love to have an
authentication method that u
Am 12.11.17 um 12:00 schrieb db-wg-requ...@ripe.net:
> Out of 114181 ORGANISATION objects, 112 objects use multiple consecutive
> whitespace in the ?org-name:? attribute and only 1 uses a multi-line value.
> While this is a tiny fraction these objects are a bit problematic to us when
> we ver
--- Begin Message ---
personal opinion: I don't care as a programmer.
company's opinion: A - all our network resources are routed solely
through our RIPE-AutNum.
--
velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau
Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau *
