--- Begin Message ---
Hi Jeroen,
I'm probably the most relevant person to asnwer your question right
now, having been a core developer during the ripe database
reimplementation project in 2013. We did that by running side by side
with the old, C version of the ripe database software. As such, we
w
--- Begin Message ---
Hi all,
Agreed that a yearly email ping-pong is not really a good verification
of abuse contact address. It's trivial to let RIPE NCC mails through
and throw away the rest.
But, one might ask, what's the point of a database if the data is not
reliable? What's the point of al
--- Begin Message ---
On Wed, Oct 11, 2017 at 12:28 PM, Daniel Shaw via db-wg wrote:
> On 11/10/2017, 14:09, Job Snijders via db-wgtyped:
>> You
>> as network operator can easily poll the APNIC or AFRINIC database.
>> There are even a number of "IRR aggregation services" such as NTTCOM
>> and
--- Begin Message ---
The gzip format already contains checksum.
Signing is a different issue. But the first question one might ask is
why this data is still offered through FTP. Using https would also
make most of the signing requirements obsolete.
On Sat, Oct 14, 2017 at 1:02 AM, Aliaksei Sheshk
I think it's about addressing abuse. If there's "bad things coming
in", one usually addresses the source IP address, not the source AS.
Also, one can move a prefix to another AS, but the ownership would
stay the same until returned to RIPE.
On Thu, Oct 19, 2017 at 1:54 AM, Job Snijders via db-wg
Or you could use TCP's built-in keepalive feature:
http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html
On Fri, Dec 8, 2017 at 12:56 PM, Edward Shryane via db-wg
wrote:
> Hi Job, WG,
>
> On 10 Nov 2017, at 15:31, Tim Bruijnzeels via db-wg wrote:
>
> We can look into this next week.
>
> Kind
On Thu, Dec 14, 2017 at 9:55 AM, Tim Bruijnzeels via db-wg
wrote:
> But, as RIPE NCC staff, I believe the working group should discuss this and
> my opinion on this is secondary.
Disagree. RIPE NCC is the focus point of input from all the community
(vs. the dozen ppl who are active on this list)
Hi Nick et al,
The ripe whois database (https://github.com/RIPE-NCC/whois) has an
excellent (=clean, performant and heavily tested) RPSL parser in it for
java. It's minimal work to copy the package, or, since this is BSD licence,
you could release a copy of it for others to use too.
Cheers,
Agost
Correct! I just drawing attention that while implementing the whois server,
we've also checked some rpsl parsers, and most of them failed the sanity
checks, even for parsing.
As for interpreting the mp-export/import lines, those have a grammar that
is also included in the rpsl parser in whois serv
An interesting proposal, but merging an external data set with RIPE
Database arises some questions:
- RIPE Database is set up to contain hierarchical data already. With this
proposal, we would take some of this data outside the database in a manner
that does not guarantee consistency with the data
You are aware you ignored 90% of my points and picked a single one out of
my email?
But let me answer this with an example.
Say, 192.168/16 has 5 children, each a /24.
You put in the geofeed file for a single 192.168/16 a /20, covering four of
these.
The /20 does not exist in the RIPE DB. So a cli
Well, not really. Say, if geofeed: is accepted, that also sets the way how
to store geolocation data in the RIPE Database. I mean, allowing geofeed:
and then adding country:, city: attributes in inetnum would be inconsistent
and confusing.
So it is much more than just an optional attribute. I do t
Would it make sense to wait with implementation until the the ietf draft
comes out of draft status? Seems like jumping into beta waters to me.
Agoston
On Sun, Jan 3, 2021 at 8:22 PM Randy Bush via db-wg wrote:
> hi cynthia
>
> >> Why not use the RPKI to distribute geofeed information?
> >
> > I
As far as I'm aware, since IP addresses _can_ uniquely identify a person
(think of static IPs offered by some ISPs), it is considered personal data
by authorities.
GDPR leaves a huge grey area that is up to interpretation, which in
practice boils down to companies trying to avoid even said grey ar
I, for one, with my regular internet user hat on, am strongly against any
form of geolocation and consider it an invasion of my privacy.
I don't want any random guy on the internet to simply pinpoint the town I'm
living in.
Is there an opt-out from this? Users will demand that there is for sure.
15 matches
Mail list logo
