From mcrossin at arin.net  Thu Feb  1 14:01:00 2018
From: mcrossin at arin.net (Michael Crossin)
Date: Thu, 1 Feb 2018 19:01:00 +0000
Subject: [arin-tech-discuss] Brief OT&E Outage
Message-ID: <04E9F143-8AAD-46EF-8264-B79578C20534@arin.net>

List,

The Operational Testing and Evaluation environment will have a brief outage today starting at 2:30pm and is expected to last no longer then 30min.

Thanks,

Mike Crossin
Database Systems Administrator
American Registry for Internet Numbers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-tech-discuss/attachments/20180201/b23b7844/attachment.html>

From mcrossin at arin.net  Thu Feb  1 15:17:07 2018
From: mcrossin at arin.net (Michael Crossin)
Date: Thu, 1 Feb 2018 20:17:07 +0000
Subject: [arin-tech-discuss] Brief OT&E Outage - COMPLETE
Message-ID: <3EA56D15-A743-4FFB-B6BB-D0CD4B0E172E@arin.net>

List,

We have completed our work in OT&E and if you experience any issues in using the environment or notice anything erroneous, please reach out to us.

Thanks,

Mike Crossin
Database Systems Administrator
American Registry for Internet Numbers


From: Michael Crossin <mcrossin at arin.net>
Date: Thursday, February 1, 2018 at 2:00 PM
To: "arin-tech-discuss at arin.net" <arin-tech-discuss at arin.net>
Subject: Brief OT&E Outage

List,

The Operational Testing and Evaluation environment will have a brief outage today starting at 2:30pm and is expected to last no longer then 30min.

Thanks,

Mike Crossin
Database Systems Administrator
American Registry for Internet Numbers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-tech-discuss/attachments/20180201/08adf808/attachment.html>

From mcrossin at arin.net  Mon Feb  5 10:19:46 2018
From: mcrossin at arin.net (Michael Crossin)
Date: Mon, 5 Feb 2018 15:19:46 +0000
Subject: [arin-tech-discuss] February OT&E Refresh
Message-ID: <AAD5FA04-FFDF-4446-9C4E-ADC48334631C@arin.net>

List,

This message serves as a notification that the Operational Testing and Evaluation environment will soon begin its monthly maintenance for a code and data refresh today.

Scheduled Work:
The OT&E whois and other application servers will now update to code matching production versions with refreshed database data.
Querying whois.ote.arin.net will not respond until this maintenance has completed.

Expected Duration:
6 hours

Updates:
Following the scheduled maintenance there will be a follow up message indicating completion.

Thanks,

Mike Crossin
Database Systems Administrator
American Registry for Internet Numbers


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-tech-discuss/attachments/20180205/cdbec35c/attachment.html>

From mcrossin at arin.net  Mon Feb  5 19:33:54 2018
From: mcrossin at arin.net (Michael Crossin)
Date: Tue, 6 Feb 2018 00:33:54 +0000
Subject: [arin-tech-discuss] February OT&E Refresh - Complete
Message-ID: <60F87D17-D195-4462-8D4F-51A6C1A181CE@arin.net>

List,

The refresh of the Operational Testing and Evaluation environment was completed within the outlined maintenance window.

All systems within this environment should be accessible to you now if you have requested access to it. If you have requested access previously, there is no need to re-request.

If you experience any issues in using the OT&E environment or notice anything erroneous, please reach out to us.

Thanks,

Mike Crossin
Database Systems Administrator
American Registry for Internet Numbers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-tech-discuss/attachments/20180206/a282a044/attachment.html>

From martin.arlitt at gmail.com  Mon Feb 12 09:40:29 2018
From: martin.arlitt at gmail.com (Martin Arlitt)
Date: Mon, 12 Feb 2018 14:40:29 +0000
Subject: [arin-tech-discuss] How to extract specific information from RDAP
Message-ID: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>

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/20180212/8dafd249/attachment.html>

From andy at arin.net  Mon Feb 12 15:27:18 2018
From: andy at arin.net (Andy Newton)
Date: Mon, 12 Feb 2018 20:27:18 +0000
Subject: [arin-tech-discuss] How to extract specific information from
 RDAP
In-Reply-To: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>
References: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>
Message-ID: <1518467238097.49988@arin.net>

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> on behalf of Martin Arlitt <martin.arlitt at gmail.com>
Sent: Monday, February 12, 2018 9:40 AM
To: 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/20180212/d4dbc5f2/attachment.html>

From martin.arlitt at gmail.com  Mon Feb 12 17:58:25 2018
From: martin.arlitt at gmail.com (Martin Arlitt)
Date: Mon, 12 Feb 2018 22:58:25 +0000
Subject: [arin-tech-discuss] How to extract specific information from
 RDAP
In-Reply-To: <1518467238097.49988@arin.net>
References: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>
 <1518467238097.49988@arin.net>
Message-ID: <CALoNm3nyzi=rkjomor5J80qo4yxu6kEFA+3CkbTkBOmi-YpJ4A@mail.gmail.com>

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> 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> on behalf
> of Martin Arlitt <martin.arlitt at gmail.com>
> *Sent:* Monday, February 12, 2018 9:40 AM
> *To:* 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/20180212/5e1afb15/attachment.html>

From andy at arin.net  Mon Feb 12 21:10:17 2018
From: andy at arin.net (Andy Newton)
Date: Tue, 13 Feb 2018 02:10:17 +0000
Subject: [arin-tech-discuss] How to extract specific information from
 RDAP
In-Reply-To: <CALoNm3nyzi=rkjomor5J80qo4yxu6kEFA+3CkbTkBOmi-YpJ4A@mail.gmail.com>
References: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>
 <1518467238097.49988@arin.net>,
 <CALoNm3nyzi=rkjomor5J80qo4yxu6kEFA+3CkbTkBOmi-YpJ4A@mail.gmail.com>
Message-ID: <1518487816544.70008@arin.net>

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>
Sent: Monday, February 12, 2018 5:58 PM
To: Andy Newton
Cc: 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/c960499b/attachment.html>

From martin.arlitt at gmail.com  Tue Feb 13 09:24:15 2018
From: martin.arlitt at gmail.com (Martin Arlitt)
Date: Tue, 13 Feb 2018 14:24:15 +0000
Subject: [arin-tech-discuss] How to extract specific information from
 RDAP
In-Reply-To: <1518487816544.70008@arin.net>
References: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>
 <1518467238097.49988@arin.net>
 <CALoNm3nyzi=rkjomor5J80qo4yxu6kEFA+3CkbTkBOmi-YpJ4A@mail.gmail.com>
 <1518487816544.70008@arin.net>
Message-ID: <CALoNm3mTBHQKGATZB9R2S6okyAKFG+Ui6SEpykE+-R=9tKsioQ@mail.gmail.com>

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> 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>
> *Sent:* Monday, February 12, 2018 5:58 PM
> *To:* Andy Newton
> *Cc:* 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> 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> on behalf
>> of Martin Arlitt <martin.arlitt at gmail.com>
>> *Sent:* Monday, February 12, 2018 9:40 AM
>> *To:* 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/f5f47ea4/attachment.html>

From andy at arin.net  Tue Feb 13 15:38:37 2018
From: andy at arin.net (Andy Newton)
Date: Tue, 13 Feb 2018 20:38:37 +0000
Subject: [arin-tech-discuss] How to extract specific information from
 RDAP
In-Reply-To: <CALoNm3mTBHQKGATZB9R2S6okyAKFG+Ui6SEpykE+-R=9tKsioQ@mail.gmail.com>
References: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>
 <1518467238097.49988@arin.net>
 <CALoNm3nyzi=rkjomor5J80qo4yxu6kEFA+3CkbTkBOmi-YpJ4A@mail.gmail.com>
 <1518487816544.70008@arin.net>,
 <CALoNm3mTBHQKGATZB9R2S6okyAKFG+Ui6SEpykE+-R=9tKsioQ@mail.gmail.com>
Message-ID: <1518554316869.23122@arin.net>

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>

From martin.arlitt at gmail.com  Tue Feb 13 15:47:19 2018
From: martin.arlitt at gmail.com (Martin Arlitt)
Date: Tue, 13 Feb 2018 20:47:19 +0000
Subject: [arin-tech-discuss] How to extract specific information from
 RDAP
In-Reply-To: <1518554316869.23122@arin.net>
References: <CALoNm3muX3X4-ECSXBTMxZuOqg8b6wAyHSBdWq3A9ccfrsoDVg@mail.gmail.com>
 <1518467238097.49988@arin.net>
 <CALoNm3nyzi=rkjomor5J80qo4yxu6kEFA+3CkbTkBOmi-YpJ4A@mail.gmail.com>
 <1518487816544.70008@arin.net>
 <CALoNm3mTBHQKGATZB9R2S6okyAKFG+Ui6SEpykE+-R=9tKsioQ@mail.gmail.com>
 <1518554316869.23122@arin.net>
Message-ID: <CALoNm3mSBn_hLqkFsU0NdwdKrPeeqtr16J6yNAzWTk-fPrUGwg@mail.gmail.com>

Thanks Andy. I look forward to trying your new features when they become
available.

Thanks
Martin

On Tue, Feb 13, 2018 at 1:38 PM Andy Newton <andy at arin.net> wrote:

> 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> 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>
>> *Sent:* Monday, February 12, 2018 5:58 PM
>> *To:* Andy Newton
>> *Cc:* 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> 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> on
>>> behalf of Martin Arlitt <martin.arlitt at gmail.com>
>>> *Sent:* Monday, February 12, 2018 9:40 AM
>>> *To:* 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/a233c33e/attachment.html>

From astranzky at velia.net  Wed Feb 14 03:18:04 2018
From: astranzky at velia.net (Alexander Stranzky)
Date: Wed, 14 Feb 2018 09:18:04 +0100
Subject: [arin-tech-discuss] RegRWS questions
Message-ID: <11c0ea3c-780c-5c49-f320-ca0a0e55ebff@velia.net>

Hello,

some questions that the RegRWS docs don't fully answer:

(1) Which timezone are the timestamps served with (I assume EST)? Are
there any exceptions?

(2) On
https://www.arin.net/resources/restfulmethods.html#ticketgetmessage it
says in the text a Message payload is returned, in the Definition box it
says it's a Ticket payload ...

Cheers, Alex

PS. in case you wonder what it's for: https://github.com/Dormilich/arin

-- 
velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau
Gesch?ftsf?hrer: Franz G. K?hler, Arek Akilli * AG Hanau * HRB 7588
Tel: +49 6181 1898119 * http://www.velia.net
Follow us on twitter: https://twitter.com/velia_net


From astranzky at velia.net  Mon Feb 19 11:47:07 2018
From: astranzky at velia.net (Alexander Stranzky)
Date: Mon, 19 Feb 2018 17:47:07 +0100
Subject: [arin-tech-discuss] RegRWS questions
Message-ID: <65369e09-ae2e-a48e-6ed1-5fd5ba0f15d9@velia.net>

Hello,

in the Error payload, how many <message> element are allowed inside the
<additionalInfo> element? (there is no RNC to look that up)

Cheers, Alex

-- 
velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau
Gesch?ftsf?hrer: Franz G. K?hler, Arek Akilli * AG Hanau * HRB 7588
Tel: +49 6181 1898119 * http://www.velia.net
Follow us on twitter: https://twitter.com/velia_net