Hi Denis,
While I kinda support this, I also like how the whitepages feature
allows you to easily see if an object was protected from deletion or
not.
Would it be possible to add some kind of extra data in the whois
response for protected objects? (like the data about abuse email when
you query f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
UNSUBSCRIBE
--- Original Message ---
On Tuesday, February 22nd, 2022 at 1:50, Cynthia Revström via db-wg
wrote:
> Hi,
>
> My opinions on this can probably be summed up with me pretty much
>
> entirely agreeing with Job, Randy, and mostly
Hi,
My opinions on this can probably be summed up with me pretty much
entirely agreeing with Job, Randy, and mostly with Gert.
With regards to Gert's reply I would just like to say that I think
trying to decide who is and isn't a legal entity is something really
complicated and last I checked the
hi ed:
one step forward, one back.
in a previous life, i was a programming language hacker snd compiler
writer. we used to make very strong negative review of any proposals
to muck about with semantics in comment fields. just don't.
randy
--
To unsubscribe from this mailing list, get a pass
Dear Ed, WG,
Thank you for the update!
On Mon, Feb 21, 2022 at 03:56:00PM +0100, Edward Shryane via db-wg wrote:
> Accordingly, we will allow "geofeed:" on ALLOCATED PA or top-level
> ASSIGNED PI (for IPv4) and ALLOCATED-BY-RIR on top-level ASSIGNED PI
> (for IPv6).
Perhaps a typo slipped in: I
Hi,
On Mon, Feb 21, 2022 at 03:56:00PM +0100, Edward Shryane via db-wg wrote:
> Please let us know what you think.
I think the NCC's legal team is still off a weird tangent...
Prefixes assigned to legal entities (non-persons) are never PII.
Gert Doering
-- NetMaster
--
have you enable
Hi Ed
Can you clarify this comment...
>
> Our Legal team have considered the concerns from a part of the community
> regarding the eligible size for “geofeed:” validation and concluded the
> following:
> Since resources with prefix size equal to the size distributed/registered by
> the RIPE NC
Hi Ed,
Thanks for the work done.
On 21/02/2022 15:56, Edward Shryane via db-wg wrote:
We will also start enforcing the same validation on "remarks: geofeed" as on
"geofeed:" for consistency.
I think you should not enforce anything on remarks. For what I know,
remarks have been a free text
Hi Job, Colleagues,
Firstly, apologies for the delay in finding a solution to the /48 restriction
on the geofeed implementation.
Our Legal team have considered the concerns from a part of the community
regarding the eligible size for “geofeed:” validation and concluded the
following:
Since re
Colleagues
The co-chairs recently had a zoom meeting with the RIPE NCC. One of
the things we discussed was clearing up a number of old issues. We
need to clear the deck and move on with new and perhaps more relevant
issues. We will address a number of issues for the last time. In some
cases the ch
10 matches
Mail list logo