Removing the "mnt-lower" attribute from aut-num objects
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-datab...
Dear Colleagues, Tomorrow (Wednesday 4th December), as part of the Whois 1.96 release, we also plan to remove the "mnt-lower" attribute from all "aut-num" objects. Following the Whois release, this attribute will be filtered out from aut-num updates with a warning (i.e. updates won't fail). We will notify the DB-WG again once this is complete. Regards Ed Shryane RIPE NCC
On 21 Oct 2019, at 11:34, Edward Shryane via db-wg <db-wg@ripe.net> wrote:
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-datab...
participants (1)
-
Edward Shryane