[arin-tech-discuss] How to extract specific information from RDAP

[Andy Newton]

Matt,


I'm glad that 1.4.1 helps.


To answer your larger question, I don't think you are overlooking anything. Perhaps the largest issue will come from jCard, which is the JSON equivalent of vCard. The IETF specified its use in RDAP to solve some internationalization problems, but with that flexibility comes some complications.


I am looking at new features for NicInfo that I hope will help with the problem you have described. I'll keep you informed as to that progress.


-andy?


________________________________
From: Martin Arlitt <martin.arlitt at gmail.com>
Sent: Tuesday, February 13, 2018 9:24 AM
To: Andy Newton
Cc: arin-tech-discuss at arin.net
Subject: Re: [arin-tech-discuss] How to extract specific information from RDAP

Hi Andy

version 1.4.1 resolves the issues I was having with --json and --jv. Thanks for fixing this so quickly.

The issue for me now is identifying a common set of fields across registry records that contain the information I want. The start and end IP addresses seem common and easy to extract. However, registration dates and organization information appear to me to be a bit more scattered in the records, so I'm not sure how to consistently extract the same information across records. Is this  in fact the situation or am I overlooking something?

Thanks
Martin

On Mon, Feb 12, 2018 at 7:10 PM Andy Newton <andy at arin.net<mailto:andy at arin.net>> wrote:

Hi Martin,


I have pushed 1.4.1 of the NicInfo gem which I believes fixes the --json and --jv features.

Please let me know if you have any further issues or questions.

Thanks for your input.

-andy




?

________________________________
From: Martin Arlitt <martin.arlitt at gmail.com<mailto:martin.arlitt at gmail.com>>
Sent: Monday, February 12, 2018 5:58 PM
To: Andy Newton
Cc: arin-tech-discuss at arin.net<mailto:arin-tech-discuss at arin.net>
Subject: Re: [arin-tech-discuss] How to extract specific information from RDAP

Hi Andy

Thanks for the detailed reply. I look forward to hearing from you when you have an update on either topic.

Thanks
Martin

On Mon, Feb 12, 2018 at 1:27 PM Andy Newton <andy at arin.net<mailto:andy at arin.net>> wrote:

Hi Martin,


It would appear that the --json and --jv options have a bug where they output in Ruby form and not JSON.

I put a bug in the issue tracker to note this: https://github.com/arineng/nicinfo/issues/32

The fix is probably simple, and I'll dig into it as soon as I am able.

With regard to a delimited file with a set of fields, I am currently in the process of adding new features that might accomplish what you are after. However, it has required refactoring of a great deal of the code and the progress is a bit slow. I'll keep you apprised of the progress.

Thanks
Andy Newton,
Chief Engineer, ARIN






________________________________
From: arin-tech-discuss <arin-tech-discuss-bounces at arin.net<mailto:arin-tech-discuss-bounces at arin.net>> on behalf of Martin Arlitt <martin.arlitt at gmail.com<mailto:martin.arlitt at gmail.com>>
Sent: Monday, February 12, 2018 9:40 AM
To: arin-tech-discuss at arin.net<mailto:arin-tech-discuss at arin.net>
Subject: [arin-tech-discuss] How to extract specific information from RDAP

Hi

I would like to extract some specific information about IP address allocations (e.g., startAddress, endAddress, handle, organization name, organization contact, last update date) in a systematic way. If I use nicinfo manually, I usually see the information I want. When I try to retrieve the same information ifrom nicinfo's JSON format or via nicinfo's  --jv options, I'm running into a variety of problems. I expect I'm doing something wrong. If anyone could offer any tips on how to a) determine the most common fields in RDAP records for IP address range allocations (including the corresponding organization information)  and b) how to most efficiently produce a delimited file of selected fields from a set of RDAP queries I would really appreciate it.

Thanks
Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-tech-discuss/attachments/20180213/180cb938/attachment.html>