We are in the process of implementing the policy regarding Post Depletion Adjustment of Procedures (2013-03). In this article we will give an overview of the changes we are making to the IP Analyser web interface and API, so you can accommodate your scripts and workflow. We intend to implement these changes on 16 April 2014.
This article is obsolete. The functionality for IP Analyser has been migrated into “My Resources” on my.ripe.net.
Currently, the IP Analyser provides an overview of all invalid assignments , which fall into five categories:
- Overlapping assignments
- Assignments registered without approval
- Sub-allocation warnings
- Objects with an incompatible "status" attribute
- Incomplete RIPE Database objects
The second category, assignments registered without approval, has become completely redundant and will be removed, as will anything regarding assignment windows. This will not affect you in the web interface, but you may have scripting in place around the IP Analyser API , which renders JSON and plain text “asused” style output.
Changes to plain text output
- The section "Invalid Netname(s)" will be removed entirely, including "List of events for netname".
- The section "Summary of assignments in allocations" will be removed entirely.
- "Number of assignments per allocation" (previously in the Summary of assignments in allocations section) will be moved to the Usage of allocations section.
Example of current output
regid: nl.ripencc-ts Usage of allocations ------------------------------------------------------------------------------ Allocation Total Usage % In Use Free ------------------------------------------------------------------------------ 193.0.24.0 - 193.0.31.255 2048 100% 2048 0 ------------------------------------------------------------------------------ 2048 100% 2048 0 Summary of assignments in allocations ------------------------------------------------------------------------------ Allocation Approved AW Infra-AW Invalid Count ------------------------------------------------------------------------------ 193.0.24.0 - 193.0.31.255 0 512 0 1536 2 ------------------------------------------------------------------------------ 0 512 0 1536 2 All assignments ------------------------------------------------------------------------------ Database Assignment size date netname ------------------------------------------------------------------------------ 193.0.24.0 - 193.0.30.255 1792 20131009 RIPENCC-MEETING-PUBLIC 193.0.31.0 - 193.0.31.255 256 20131009 RIPENCC-MEETING-INFRASTRUCTURE Free Address Space ------------------------------------------------------------------------------ Address range size ------------------------------------------------------------------------------ Invalid Netname(s) Netname Inetnum Date Size Not App AW ------------------------------------------------------------------------------ ERROR RIPENCC-MEETING-PUBLIC invalid 193.0.24.0 - 193.0.30.255 20131009 1792 1536 256 List of events for netname RIPENCC-MEETING-PUBLIC Date Event inetnum size App Aw ------------------------------------------------------------------------------ 20050427 aw 0 20050715 aw 128 20130807 aw 256 20131009 inetnum 193.0.24.0 - 193.0.30.255 1792 x 0 256
Example of new output
regid: nl.ripencc-ts Usage of allocations ------------------------------------------------------------------------------ Allocation Total Usage % In Use Free # Asg ------------------------------------------------------------------------------ 193.0.24.0 - 193.0.31.255 2048 100% 2048 0 2 ------------------------------------------------------------------------------ 2048 100% 2048 0 2 All assignments ------------------------------------------------------------------------------ Database Assignment size date netname ------------------------------------------------------------------------------ 193.0.24.0 - 193.0.30.255 1792 20131009 RIPENCC-MEETING-PUBLIC 193.0.31.0 - 193.0.31.255 256 20131009 RIPENCC-MEETING-INFRASTRUCTURE Free Address Space ------------------------------------------------------------------------------ Address range size ------------------------------------------------------------------------------
Changes to JSON output
- The "policyViolations" element (inside "violations") will not be returned anymore. This is not a breaking change since it is an old attribute that will simply not be returned anymore.
Example of current output
{
"allocations" : [
{
"assignments" : [
{
"violations" : {
"policyViolations" : {
"code" : "POLICY_VIOLATION" ,
"message" : "The size of assignment 193.0.24.0 - 193.0.30.255 is 1536 addresses outside the assignment window approval."
}
},
"status" : "ASSIGNED PA" ,
"range" : "193.0.24.0/22,/23,/24" ,
"infra" : false ,
"registrationDate" : "20131009" ,
"netName" : "RIPENCC-MEETING-PUBLIC"
},
Example of new output
{
"allocations" : [
{
"assignments" : [
{
"violations" : {},
"status" : "ASSIGNED PA" ,
"range" : "193.0.24.0/22,/23,/24" ,
"infra" : false ,
"registrationDate" : "20131009" ,
"netName" : "RIPENCC-MEETING-PUBLIC"
},
Comments 0
Comments are disabled on articles published more than a year ago. If you'd like to inform us of any issues, please reach out to us via the contact form here.