Can RIPE staff clarify if there are plans to support PGP authentication
of database updates using ed25519 keys?
This should require not much more that upgrading gnupg to a modern release.
--
ciao,
Marco
Hello.
What's the right how-to convert an existing C class from PI to PA?
According to this:
https://www.ripe.net/manage-ips-and-asns/ipv4/converting-pi-to-pa
"Members can request this update via the LIR Portal." ... but I was not
able to find HOW this may be done (If I try to edit the object, the
field "status" is locked, and I can't edit it anyway... while I can edit
other fields as usual)
Regards
--
Franco Tauceri
DomainRegister
m:
39.3483064202
w:
https://DomainRegister.international e:
franco.tauceri(a)domainregister.it
Dear Working Group,
RIPE Database release 1.96 has been deployed to the Release Candidate environment. We plan to deploy to production on Wednesday 4th December.
This release contains the following main changes since 1.95.1:
* Added "country:" attribute to organisation object type
* Deprecated "mnt-lower:" attribute in autnum object type
* Abuse-c validation comment must refer to the LIR organisation
* Limit number of results in full-text search queries
* Apply query limit to version queries
For a full list of changes, refer to the release notes:
https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rel…
More information on the Release Candidate environment can be found on our website:
https://www.ripe.net/manage-ips-and-asns/db/release-notes/rc-release-candid…
Please let us know if you find any issues with this release in the RC environment.
Regards
Ed Shryane
RIPE NCC
Dear Colleagues,
as presented during the DB-WG session at RIPE 79, we plan to remove the "mnt-lower" attribute from the aut-num object type.
From the RIPE database documentation [0]:
“mnt-lower: This attribute has no meaning in the aut-num object. In the RIPE NCC service region, we do not allocate blocks of
AS numbers for users to assign from. All AS numbers are assigned by the RIPE NCC therefore there is no hierarchy to ‘maintain’
or authorise against. This attribute should be deprecated.”
We plan to implement this change in the next Whois release (we will announce this separately).
We do not expect any operational impact. It is currently an optional attribute. This attribute will be removed (with a warning) from any aut-num updates.
At the same time, we plan to remove this attribute from approximately 948 of 35,144 aut-num objects. We will announce separately to the db-wg and affected maintainers, before and after removal.
Please let me know of any feedback or questions you may have.
Regards
Ed Shryane
RIPE NCC
[0] https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-data…
Dear Colleagues,
As presented during the DB-WG session at RIPE 79, we plan to remove the legacy status "remarks" attribute from inetnum and aut-num objects in the RIPE database.
This remark was added to LEGACY resources in 2015, when implementing the policy 2012-07 "RIPE NCC Services to Legacy Internet Resource Holders” [0].
The remark states: "For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources”
We now consider this remark to be obsolete, and have already performed a similar cleanup on (most) aut-num objects in August 2017.
We plan to shortly remove this remark from approximately 19,059 inetnum and 15 aut-num objects, and will email affected maintainers before and after the change.
Please let me know of any feedback or questions you may have.
Regards
Ed Shryane
RIPE NCC
[0] https://www.ripe.net/participate/policies/proposals/2012-07
