Hi Maria
On Thu, 16 May 2024 at 10:04, Maria Stafyla wrote:
>
> Hi Denis,
>
>
> I would like to acknowledge that all our legal framework documents, including
> the RIPE Database Terms and Conditions, are written by legal professionals.
I really don't know why everyone thinks I am some nasty
Hi Ed
This sounds like a good move. I have 2 questions about the rules.
If I query 1000 personal data sets on an IP address, then I log in to
my access account, can I query 1000 more? I know this to some extent
bypasses the strict rules. But in that office situation you referred
to, suppose
Hi Maria
Oh dear!!! I wasn't going to respond to this. No one is interested in
getting things right, so why should I bother? But I read it again and
it is so wrong, I couldn't just walk away. Let's go back to 2010.
The RIPE Database Terms and Conditions is one of the most important
corporate
Colleagues
The proposers of 2023-04 assured the community that their motivation
was purely to provide aggregation, an optional, minor, inconsequential
feature that did not change anything else. So if their minds were
focused purely on aggregation, as they have told us and we must accept
that
Hi Athina, Maria
It would be nice if one of you can give an update to the community on
this issue of the Terms & Conditions being out of step your with
current legal opinion.
cheers
denis
co-chair DB-WG
On Wed, 17 Apr 2024 at 07:36, denis walker wrote:
>
> Colleagues
>
> In the Impact Analysis
Hi
On Sat, 27 Apr 2024 at 20:56, Semisol via db-wg wrote:
>
> Hetzner apparently creates an `inet6num` object per dedicated server
> allocation (enough to get my IP blocked for 1 day trying to query them all),
> and it took several seconds to execute the query.
>
> > whois -r -- "-i mnt-by
Colleagues
In the Impact Analysis (IA) for 2023-04, the RIPE NCC legal team
expressed rules for entering personal data into the RIPE Database that
are quite different to our previous understanding. This legal IA was
relied on heavily by the proposers of 2023-04 and constantly referred
to by them
Hi Aleksi
Here we discuss the semantics of how the database applies the logic for
route object creation. If you want to discuss the logic, I suggest you move
over to the routing-wg and talk with other routing experts :)
cheers
denis
co-chair DB-WG
On Mon, 15 Apr 2024 at 14:52, Aleksi Suhonen
Hi guys
It is not unintended behaviour or a bug. It is by design. See
https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space/#authorisation-rules-for-creating-route-objects
There used to be a flow chart showing this but I can't find it now.
cheers
denis
co-chair DB-WG
On
Colleagues
Interesting comments. Maybe I am the problem with the DB-WG? I
announce that I am stepping down as co-chair after the next RIPE
Meeting, Ed makes a proposal and within 4 hours on a Friday afternoon
8 people have supported the proposal. We haven't had that much support
for anything on
Hi Peter
There are two seats available as I am stepping down as a co-chair
after this next RIPE Meeting. I am slowly moving myself towards full
retirement :)
cheers
denis
co-chair DB-WG
On Fri, 29 Mar 2024 at 08:18, Peter Hessler via db-wg wrote:
>
> Hi David,
>
> You mention two seats to fill
Hi Sander and others
On Wed, 20 Mar 2024 at 23:06, Sander Steffann wrote:
>
> Hi Denis,
>
> > So we just stay where we are, yet again, with the NCC sending out tens
> > of thousands of emails every day to some of the almost a million email
> > addresses in the database and you all continue to
On Wed, 20 Mar 2024 at 07:51, Lutz Donnerhacke via db-wg wrote:
>
> * Denis Walker wrote:
> > But looking through lots of email notifications about changes that you
> > already know about, because you did them, and maybe in the middle is a
> > notification of an attempted security breach that
On Tue, 19 Mar 2024 at 17:03, denis walker via db-wg wrote:
> Hi Gert
>
> On Tue, 19 Mar 2024 at 16:05, Gert Doering wrote:
> >
> > Hi,
> >
> > On Tue, Mar 19, 2024 at 03:55:26PM +0100, denis walker via db-wg wrote:
> > > This new anti-spam measure i
Hi Gert
On Tue, 19 Mar 2024 at 16:05, Gert Doering wrote:
>
> Hi,
>
> On Tue, Mar 19, 2024 at 03:55:26PM +0100, denis walker via db-wg wrote:
> > This new anti-spam measure is a convenient point to reflect on how one
> > part of the RIPE Database is used. Notific
Colleagues
I know none of you want to talk about any redevelopment of the RIPE
Database. Not even doing it bit by bit. I keep reminding you that it
is a 30 year old design and barely fit for purpose in the modern
world. But still you all want to keep this dinosaur even though it is
now on life
Colleagues
As Maria said, we now have a new defined purpose explicitly related to
geofeed. Ed has confirmed that the prefix size restrictions have been
removed. Does anyone think there is still anything outstanding
regarding the implementation, deployment and use of geofeed? In
particular
situations.
Cheers
Denis
Co-chair DB-WG
On Tue, 9 Jan 2024, 00:21 Leo Vegoda, wrote:
> Hi Denis,
>
> On Mon, 8 Jan 2024 at 15:16, denis walker via db-wg
> wrote:
> >
> > Hi
> >
> > Maybe Leo or Dmitry could give an intro into what they mean by
> 'alte
Hi
Maybe Leo or Dmitry could give an intro into what they mean by 'alternative
modes of contact' so people can think about it before the discussion.
Cheers
Denis
Co-chair DB-WG
On Mon, 8 Jan 2024, 22:59 David Tatlisu via db-wg, wrote:
> Hi,
> Picking up from RIPE87, the first interim working
Colleagues
The discussion and agreement of the text for a new purpose for the
RIPE Database covering geolocation was done by the RIPE NCC and it's
executive board. They refused to publish the text in advance, didn't
announce that the board had agreed to it or that the T document has
been updated.
Hi Sergey
The RIPE Database is a public registry. It allows anyone to query it
anonymously from a unix terminal window, for example, from any IP
address. As long as such access is permitted there is physically and
technically no means to limit access by any individual person.
The T DO contain
Maria, Colleagues
I think there is still some confusion here. I am not questioning the
process of updating a legal document. You said "'THE' proposed
amendments have to be first presented to the Executive Board". But no
one knows what 'the' proposed update is. Let me summarise the last 9
months
Hi Maria
Thanks for this. Just to remind everyone, can you publish the final
proposed amendments that you are going to put to the board.
cheers
denis
co-chair DB-WG
On Wed, 26 Jul 2023 at 11:54, Maria Stafyla wrote:
>
> Hi Denis,
>
> This is still in progress.
>
> Our intention is to submit
Hi Nick
I am not interested in google searches for rules of parliamentary
committees. I am interested in RIPE specific documented rules. The
parliamentary committee situations you referred to are generally
formal, in person meetings where a single person has been appointed as
the president or
thoughts.
cheers
denis
co-chair DB-WG
On Fri, 21 Jul 2023 at 00:19, Sylvain Baya wrote:
>
> {change the topic. focus: basic tasks}
> Dear RIPE DB-WG,
> Hope this email finds you in good health.
> Please see my comments below inline...
> Thanks.
>
> Le mercredi 19 juillet 2023
Hi Niall
On Thu, 20 Jul 2023 at 16:19, Niall O'Reilly wrote:
>
> Hi, Denis.
>
> On 19 Jul 2023, at 18:41, denis walker via db-wg wrote:
>
> > One or two vocal members of this community frequently express their
> > opinion that all WG chairs should sit silen
Hi Nick
On Thu, 20 Jul 2023 at 16:41, Nick Hilliard via db-wg wrote:
>
>
> the job of a chair is to ensure that the business of the forum is done,
> in an orderly and efficient way.
Where is this stated?
> From this point of view, an "active"
> chair is good, and to be welcomed. What isn't
Colleagues
On Wed, 24 May 2023 at 08:52, Wessel Sandkuijl via db-wg wrote:
>
> Hi,
>
> I've reviewed Ed's impact analysis for NWI-4 and his proposal to add a new
> status value "ALLOCATED-ASSIGNED PA". This will not cover all use cases and
> it's use will most likely be limited as most people
Hi Maria
"> On the implementation side, we will discuss internally how we can
make it explicit when adding a geofeed attribute that the privacy of
the users of the related resources is respected."
How are these internal discussions progressing? Do you have any suggestions yet?
">We will work on
Colleagues
One or two vocal members of this community frequently express their
opinion that all WG chairs should sit silently in the background, post
an occasional review and wait to declare consensus or not. I am always
willing to try out ideas from the community. So for the last couple of
Hi Ed
On Mon, 19 Jun 2023, 14:40 Edward Shryane via db-wg, wrote:
> Dear colleagues,
>
> NWI-14 was implemented in Whois 1.107 which was deployed to production
> today.
>
> Accordingly I've marked NWI-14 as finished on the Numbered Work Items page:
>
Hi Randy
On Fri, 9 Jun 2023 at 20:42, Randy Bush wrote:
>
> > That would be fine if we had a very active and engaging community. Like we
> > had 20 years ago. But the vast vast vast majority of this community is
> > silent on almost all database matters. The vocal people are a handful of
> >
Hi Randy
That would be fine if we had a very active and engaging community. Like we
had 20 years ago. But the vast vast vast majority of this community is
silent on almost all database matters. The vocal people are a handful of
well known members of the community, whose views on many matters are
Colleagues
In the past we have done an NWI update as a presentation during the
RIPE Meeting. However, as there is usually very little movement on
most NWIs, the presentations are not very informative. This time we
will present the update as an email and ask for any questions in the
AOB at the end
Hi Warren
I totally agree with you. We are waiting for a response from the RIPE NCC
legal team otherwise we are all making guesses in the dark. I'm sure a
response will come soon
Cheers
Denis
Co-chair DB-WG
On Mon, 24 Apr 2023, 21:50 Warren Kumari, wrote:
>
>
>
>
> On Thu, Apr 13, 2023 at
Colleagues
Just a quick reminder if anyone is interested in becoming a chair of the
DB-WG please contact the current chairs.
Cheers
William and Denis
Co-chairs DB-WG
On Thu, 13 Apr 2023, 12:21 denis walker, wrote:
> Colleagues
>
> The process for selecting chairs and terms of office is
Hi Randy, Sylvain
IANAL either but I understood the main legal issue was that there is
no defined purpose to use the RIPE Database for geolocation services.
So whatever is in that referenced file is not covered by a valid
purpose. We have had the "geoloc:" attribute for a long time. The
value of
Colleagues
A question for the legal team at the RIPE NCC. Would a simple purpose,
as suggested below, address all the concerns you had about the use of
the "geofeed:" attribute and allow you to remove any restrictions you
felt were necessary when it was introduced?
cheers
denis
co-chair DB-WG
Colleagues
The process for selecting chairs and terms of office is documented here
https://www.ripe.net/participate/ripe/wg/active-wg/db/database-wg-chair-selection-process
Accordingly, Denis's term of office expires at RIPE 86. If anyone is
interested in joining the team please contact
Hi Randy
Try
-rB -Tdomain -i mb MAINT-RGNET
-r means no referenced person/role objects
-B means the unfiltered objects
-Tdomain means only domain primary objects queried
-i mb MAINT-RGNET means objects that are maintained by MAINT-RGNET
cheers
denis
co-chair DB-WG
On Wed, 12 Apr 2023 at
Colleagues
The conversation on deploying geofeed died shortly after RIPE 85. The
last comment was from myself asking if anyone was willing to propose
some wording for a new purpose covering the use of the RIPE Database
for geolocation information. No one proposed any wording. So below I
have made
he goal of a single, officially supported
attribute for geolocation purposes, later deprecating all the
others...please, please, please let us know. Then we can wrap this
issue up with a ToDo list and some time lines.
cheers
denis
co-chair DB-WG
>
> Kind regards,
> Laurent Pellegrino
>
>
meantime the "country:"
> attribute in INET(6)NUM object is helpful.
>
> Best regards
> Éric
>
> -Original Message-
> From: db-wg On Behalf Of denis walker via db-wg
> Sent: Wednesday, March 8, 2023 3:52 AM
> To: Leo Vegoda
> Cc: RIPE Database WG ; Havar
Colleagues
I would like to clarify a couple of points here in case anyone has
doubts. I often get heavily involved in some discussions on the
mailing list. I sometimes have strong views and probably come across
as quite pushy. But I always present arguments to support my
viewpoint. I am not one
Hi Randy
On Wed, 8 Mar 2023 at 03:11, Randy Bush wrote:
>
> > I suggest that this is not just a localized decision of the db-wg, but
> > has global implications.
>
> +1, and this aside from the idea having other fatal flaws, as discussed
> here before.
Can you please be a little more specific?
Hi Leo
>From my perspective as an analyst it's getting interesting now... Yes
we can consider it as a complex problem needing a complex
solution...but are either really complex? Maybe it is the environment
that is complex and not this specific problem or solution.
On Wed, 8 Mar 2023 at 01:29,
Hi Leo
On Tue, 7 Mar 2023 at 23:51, Leo Vegoda wrote:
>
> Hi,
>
> I strongly support what George has written.
>
> On Tue, 7 Mar 2023 at 14:29, George Michaelson via db-wg
> wrote:
>
> [...]
>
> > I don't necessarily disagree with you about the risks here, but I
> > suggest that the decision to
Hi George
Thanks for your comments. Of course global context is important in
these situations and I appreciate you raising this issue.
It says in the file:
https://ftp.ripe.net/pub/stats/ripencc/RIR-Statistics-Exchange-Format.txt
3.3 Record format:
...
cc= ISO 3166 2-letter
HI Cynthia
On Thu, 2 Mar 2023 at 17:43, Cynthia Revström via db-wg wrote:
>
> Hi db-wg,
>
> I just want to start out by saying that I support efforts to try to better
> understand and document this.
> What I don't (currently) support is changing DB policy (policy in the form of
> RIPE
Hi Leo
On Mon, 20 Feb 2023 at 16:37, Leo Vegoda wrote:
>
> On Mon, 20 Feb 2023 at 07:25, denis walker wrote:
> > On Mon, 20 Feb 2023 at 15:58, Leo Vegoda wrote:
>
> [...]
>
> > > Setting semantics aside... I don't know whether changing definitions —
> > > and adding a missing definition is a
Hi Leo
On Mon, 20 Feb 2023 at 15:58, Leo Vegoda wrote:
>
> On Thu, 26 Jan 2023 at 07:18, denis walker wrote:
>
> [...]
>
> > This is exactly what I said. In the quoted para above I said "the
> > country codes have a well defined meaning", which you agree with. Then
> > I said "but when entered
Colleagues
We still have many outstanding issues, some of which have been on and
off the table for years. We cannot make any progress on them as we do
not have the attention of enough people in the community. It will be
good if we can clear up some of these issues before the next RIPE
meeting.
On Wed, 8 Feb 2023 at 12:09, Ángel González Berdasco via db-wg
wrote:
>
> 07-02-2023 19:22 +0200, Hank Nussbacher wrote:
> > As a LIR we want to extract all records for which we are registered
> > as mnt-by. We tried:
> >
> >
>
Hi Leo
On Thu, 26 Jan 2023 at 13:48, Leo Vegoda wrote:
>
> On Thu, 26 Jan 2023 at 03:55, denis walker via db-wg wrote:
> >
> > Hi Ed
> >
> > Thanks for the explanation. But as I explained to Cynthia, "org-name:"
> > and "country:" are ve
cannot reliably use (a subset of) this data
for purpose A or B...
cheers
denis
co-chair DB-WG
On Thu, 26 Jan 2023 at 11:54, Edward Shryane wrote:
>
> Hi Denis,
>
> > On 24 Jan 2023, at 17:19, denis walker via db-wg wrote:
> >
> > Colleagues
> >
> > Following on f
Colleagues
Following on from Havard's comments below I would like to expand the
discussion to consider the general use of country codes in the RIPE
Database. As I tend to write long emails that many people don't read,
I'll summarise my main points first then expand on the details for
those who
Hi Angel
This is all explained in a RIPE Labs article
https://labs.ripe.net/author/stefania_fokaeos/our-plan-to-update-country-codes/
and was discussed extensively in Oct/Nov 2019 and early 2020 on this
mailing list.
cheers
denis
co-chair DB-WG
On Thu, 12 Jan 2023 at 22:09, Ángel González
doesn't really matter in
this instance. It is the fact that this user edited data has no
meaning and is of no value or use to anyone besides the person who
entered it.
cheers
denis
co-chair DB-WG
>
> -Cynthia
>
> On Tue, Jan 10, 2023 at 2:03 PM denis walker via db-wg wrote:
>>
>&g
Colleagues
We have a number of outstanding issues from RIPE 85 so let's start
with NWI-10. Ed said in his update,
"Country code is now editable in organisations without co-maintained resources"
I think this is a really bad idea.
The country codes entered into ORGANISATION objects by the RIPE NCC
Colleagues
The chairs agree that we have a consensus on making this change and
regarding it as a bug fix on the implementation of NWI-5. We therefore
ask the RIPE NCC to implement this bug fix when it is convenient to
fit it into their development plans.
It can be done in two stages:
1/ Creating
Colleagues
Just a quick reminder in case you missed the previous email. Looks
like no one has any objections...
cheers
denis
co-chair DB-WG
On Thu, 8 Dec 2022 at 16:43, denis walker wrote:
>
> Colleagues
>
> There is some support for the idea that if AUT-NUM objects in
> RIPE-NONAUTH authorise
Colleagues
There is some support for the idea that if AUT-NUM objects in
RIPE-NONAUTH authorise the creation of AS-SET objects, these set
objects will also be in RIPE-NONAUTH. There is also support for this
to be considered as a bug from the implementation of 'NWI-5 Out of
region ROUTE(6)/AUT-NUM
On Thu, 24 Nov 2022 at 16:13, Nick Hilliard via db-wg wrote:
>
> Niall O'Reilly via db-wg wrote on 23/11/2022 18:17:
> > What I have in mind is AS-NIALLSPECIAL, which I populate with a list of
> > AS numbers which I want to advertise to let others know that these
> > are to be handled in some
On Tue, 29 Nov 2022 at 20:44, Nick Hilliard wrote:
>
> Cynthia Revström wrote on 29/11/2022 18:56:
> > I agree with Nick.
> > However there are currently as-set objects in RIPE based on aut-num
> > objects in RIPE-NONAUTH.
> > I think it might be worth considering if these should be cleaned up.
>
On Tue, 29 Nov 2022, 19:56 Cynthia Revström, wrote:
> I agree with Nick.
> However there are currently as-set objects in RIPE based on aut-num
> objects in RIPE-NONAUTH.
> I think it might be worth considering if these should be cleaned up.
>
As an intermediate step we could set the source to
Colleagues
Any thoughts on these 'RIPE-NONAUTH' objects?
On Tue, 22 Nov 2022 at 21:17, denis walker wrote:
>
> Hi Nick
>
> On Tue, 22 Nov 2022 at 20:11, Nick Hilliard wrote:
> >
> > denis walker via db-wg wrote on 22/11/2022 19:00:
> > > Any thoughts on thi
Hi Niall
On Wed, 23 Nov 2022 at 00:30, Niall O'Reilly via db-wg wrote:
>
> On 22 Nov 2022, at 19:11, Nick Hilliard via db-wg wrote:
>
> > Careful with this, e.g. AS-NULL. There are some situations where
> > referencing an empty set can be useful in RPSL.
>
> I'm not sure whether Nick meant this
Hi Nick
On Tue, 22 Nov 2022 at 20:11, Nick Hilliard wrote:
>
> denis walker via db-wg wrote on 22/11/2022 19:00:
> > Any thoughts on this? There are 2128 AUT-NUM objects with source
> > RIPE-NONAUTH. Do we want these to be able to authorise the creation of
> > hierarchica
Colleagues
On Mon, 21 Nov 2022 at 13:54, denis walker wrote:
>
> One question to the community...do we want to disallow authorisation
> of new AS-SET objects from ASNs in RIPE-NONAUTH?
>
Any thoughts on this? There are 2128 AUT-NUM objects with source
RIPE-NONAUTH. Do we want these to be able to
Colleagues
The chairs discussed this issue over the weekend and agreed that we
see a consensus to change the syntax rules for AS-SET object names in
the RIPE Database. We also agreed that we believe this feature request
can be managed through the Numbered Work Item process. We therefore
ask the
Colleagues
I know it is a weekend but there does seem to be some urgency on this
matter. The chairs have been following this discussion and have a
couple of questions before we move on.
The chairs believe we can consider this to be a feature request for
the RIPE Database and handle it through
policies (as far as I know).
>
> Also ran into this issue and would like to see policy support to
> handle this kind of abuse.
>
> On Mon, Nov 14, 2022 at 3:08 PM denis walker via db-wg wrote:
> > Interesting timing. I was about to make the same suggestion but for a
> > d
Hi Job
Interesting timing. I was about to make the same suggestion but for a
different reason...accountability. Currently ANYONE can create a set
object in the RIPE Database. You can be completely anonymous, not a
member or LIR, hold no resources. All you need to do is create a ROLE,
MNTNER and
Colleagues
I would like to apologise for missing the DB-WG session at RIPE 85. I
was taken ill the night before with severe gastric problems, which I
have only recently recovered from. Now I am still recovering from
covid also.
I would like to thank my co-chair William for stepping in at the
Hi Frank
Thank you for some very useful information here. This is the type of
input we need in these discussions. I have had many discussions with
the RIPE NCC legal team about this proposal. They did point out to me
there is a difference between processing personal data for the
'legitimate
Hi Frank
First of all I would like to thank you for joining this discussion.
With any policy discussion it is important to get as wide a range of
views as possible. We also like to hear from people who use the RIPE
Database to get a better understanding of who uses it and for what
purpose.
There
Colleagues
For now I want to focus on the privacy part of the proposal. I will
come back to verification later. So below is my response to all the
issues raised in the impact analysis (with references to verification
removed for now).
cheers
denis
proposal author
> Impact Analysis
>
> Note: to
Hi Sander
Thanks for the comments and kicking off the new discussion. I have to
admit I was a bit confused by some of the comments in the impact
analysis, including these.
On Sun, 9 Oct 2022 at 13:33, Sander Steffann via db-wg wrote:
>
> Hi,
>
> > The RIPE NCC has prepared an impact analysis on
Colleagues
Since we sent out the form below, not one person has responded :(
Vacation time is over, you are no longer sitting on the beach with
that glass of wine (not that that should stop you thinking about the
RIPE Database)...so can we please have some form filling time to help
out the RIPE
e Kerr via db-wg wrote:
>
> Denis,
>
> On 12/09/2022 16.12, denis walker via db-wg wrote:
> >
> > Do you use the RIPE Database as your IPAM solution? If so, read on
>
> Thanks for bringing this up!
>
> This was an area that the RIPE Database Requirements Tas
Colleagues
Do you use the RIPE Database as your IPAM solution? If so, read on
The RIPE NCC has done a brief review of the recommendations made by
the DB Task Force (DBTF). You can find it here:
t;> Agoston
>>
>> On Thu, Aug 4, 2022 at 7:24 PM Carlos Friaças via db-wg
>> wrote:
>>>
>>>
>>>
>>> Hi,
>>>
>>> A small comment inline:
>>>
>>>
>>> On Thu, 4 Aug 2022, denis walker via db-wg wrote:
>
Colleagues
I have spent some time thinking about the wording of the current
purpose of the RIPE Database in relation to geolocation services. In
some ways the purposes are very loosely written. That means they are
open to interpretation. I think they can be interpreted to cover the
"geofeed:"
On Fri, 29 Jul 2022, 17:29 Randy Bush, wrote:
> > A lot of this discussion is about interpreting one defined purpose
> > trying to make everything fit in order to 'get around' a legal review.
>
> another interpretation is that this discussion is trying to bridge a
> rather shocking gap between
Hi Maria
There has been quite a discussion in the last 24 hours from various angles
about interpretation of terminology and purposes and context. Perhaps this
is a good moment to pause and allow the legal team to review the discussion
and see if anything that has been said affects your analysis.
On Fri, 29 Jul 2022, 16:04 Massimo Candela, wrote:
>
>
> I'm not against making the purpose of the database more explicit towards
> geolocation data. I was just commenting that I don't see why the current
> generic purposes are not good enough (especially since we have a bunch
> of other
On Fri, 29 Jul 2022, 16:41 Randy Bush, wrote:
> > I was probably being a bit loose with my definitions but are you
> > saying that ALL content providers are network operators?
>
> i eagerly await your counter-example
>
It was a question not a statement.
Cheers
denis
Co- chair DB-WG
>
> randy
Hi Ángel
On Fri, 29 Jul 2022, 16:36 Ángel González Berdasco via db-wg, <
db-wg@ripe.net> wrote:
> On 29-07-2022 02:32 +0200, denis walker wrote:
> > This purpose would cover:
> > -"geofeed:"
> > -"geoloc:"
> > -"language:"
> > -"abuse-c:"
> > -IRT object
> > -use of ROLE objects for contacts for
On Fri, 29 Jul 2022, 16:00 Randy Bush, wrote:
> >> the purpose has been for operational use since dirt was invented. the
> > The term 'operational use' has never actually been defined. But if we
> > were to define it then I suspect it will be more about network
> > operators solving technical
On Fri, 29 Jul 2022, 16:08 Randy Bush, wrote:
> > Content providers 'not=' network operators.
>
> given the state of the actual operational internet, this is a rather
> shocking statement from a ripe wg co-chair.
>
I was probably being a bit loose with my definitions but are you saying
that ALL
Hi Niall
On Fri, 29 Jul 2022, 14:42 Niall O'Reilly via db-wg, wrote:
> On 29 Jul 2022, at 1:55, Randy Bush via db-wg wrote:
>
> > the purpose has been for operational use since dirt was invented. the
> > geofeed: attribute points to data which operators, namely content
> > providers, need.
>
>
Hi Randy
On Fri, 29 Jul 2022 at 02:55, Randy Bush via db-wg wrote:
>
> the purpose has been for operational use since dirt was invented. the
The term 'operational use' has never actually been defined. But if we
were to define it then I suspect it will be more about network
operators solving
Hi Massimo
On Fri, 29 Jul 2022 at 04:11, Massimo Candela via db-wg wrote:
>
>
> Hi,
>
>
> On 28/07/2022 15:52, Randy Bush via db-wg wrote:
> > and, being a researcher, i have no clue about
> > this research spin at all.
>
>
> I also don't understand where the research context is coming from.
>
Colleagues
My vacation is almost over and I have a lot of emails to reply to so I
will start with the topic of the day, geofeed. We have to think out of
the box here. You are all approaching this issue from the same wrong
angle. There is no point criticizing the legal team for doing their
job.
Hi William
On Fri, 22 Jul 2022, 12:50 William Weber via db-wg, wrote:
> As cybercriminal i wholeheartedly support the idea of removing all
> personal data from the RIPE DB.
>
Sound bites may sound good but add little to a discussion.
A large part of the business data in the RIPE Database is
Ronald
(For those who don't read long emails...) The bottom line is that this
proposal recommends to remove postal addresses of contacts, not
publish the 'full' postal address of natural persons holding
resources, replace personal data with business data and generally
bring the contents of the
Colleagues
During the conversion we had some time ago about contacts we concluded that
no one is going to visit a contact or post them a letter.
The IRT object also had a mandatory address attribute that is defined in
the documentation as:
"This is a full postal address for the business contact
Colleagues
[Apologies to Job for copying your email from the Routing WG but you
explained it well :) ]
The RIPE NCC has asked the Database WG Chairs to facilitate a working
group conversation on framing the RIPE Database service subcomponents
in terms of criticality.
At the bottom of this email
e just my initial thoughts on the topic and there are probably many
> other things that I haven't considered.
>
> -Cynthia
>
> On Mon, Jul 4, 2022, 13:47 denis walker via db-wg wrote:
>>
>> Colleagues
>>
>> I know this has been a long discussion with severa
Colleagues
I know this has been a long discussion with several elements to
consider. But with just over a week of this discussion period
remaining, are there any comments or thoughts on the "descr:"
attribute containing personal data?
cheers
denis
Proposal author
-- Forwarded message
1 - 100 of 301 matches
Mail list logo
