Dear Christoffer, End of 2018 sounds reasonable, but I cannot promise.
The main thing here is that we want to ensure that we have achieved alignment with the other RIRs before making ad-hoc changes that would need to be re-addressed. Also, the specification of extension may take some time. We are all committed to doing this, but it’s not entirely clear how long this will take. Once we have the alignment we still need to plan the work in relation to other priorities, but we don’t expect that this will be a huge change to our implementation. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC > On 20 Mar 2018, at 17:55, Christoffer Hansen <netrav...@gmail.com> wrote: > > Dear Tim, > > Do you expect to be able to do unreliable guesswork about when a "future > plan" could be approximately ready ? (Fx. Q3-Q4 2019/Around RIPE78) > > Cheers > Christoffer Hansen > > "You might think that your government is vigilant when it comes to > securing your personal information, or that of your children. You would > be wrong." - Jake Tapper, CNN Chief Washington Correspondent > > On 20-03-2018 17:28, Tim Bruijnzeels wrote: >> Dear all, >> >> There are known differences between the RIR implementations of RDAP. In some >> cases we will need to make extended RDAP specifications, e.g. a resource can >> have multiple countries in the RIPE region. The RIRs are working together to >> make an inventory of these differences, and based on that we will plan >> future work. >> >> Kind regards >> >> Tim Bruijnzeels >> >> Assistant Manager Software Engineering >> RIPE NCC >> >> >>> On 20 Mar 2018, at 16:02, Christoffer Hansen via db-wg <db-wg@ripe.net> >>> wrote: >>> >>> On the github repo[0] they have a small snippet about it. >>> >>> "An org: reference from an inetnum,inet6num,autnum resource is not >>> included in the query response. >>> By contrast, ARIN returns the org reference as a "registrant" entity." >>> >>> As I understand it. RIPE NCC has done an active choice in NOT doing the >>> RDAP implementation similar to ARIN. >>> >>> [0]: >>> https://github.com/RIPE-NCC/whois/blob/master/README.RDAP.md#organisation-entity-is-not-returned-in-ip-or-autnum-query-responses >>> >>> On 20-03-2018 15:48, Brian Rak via db-wg wrote: >>>> I've been attempting to use RDAP to verify our customer's IP >>>> information, however I'm running into some difficulties due to >>>> differences between ARIN's implementation and RIPE's. >>>> >>>> For example, I'm trying to get the organization name for a particular >>>> IP. On ARIN, this is easy. I look through the provided vcards for one >>>> where the kind is 'org', and that gives me the information about the >>>> organization. (ex: https://rdap.arin.net/registry/ip/66.55.158.27 ) >>>> >>>> With RIPE's RDAP implementation, this data does not seem to be readily >>>> available. >>>> >>>> For example, if I look at https://rdap.db.ripe.net/ip/195.66.225.160 I'd >>>> expect to find the string 'London Internet Exchange Ltd.' somewhere >>>> within the response. >>>> >>>> If I look at the web UI: >>>> https://apps.db.ripe.net/db-web-ui/#/query?searchtext=195.66.225.160#resultsSection >>>> , this information is easily available. >>>> >>>> Would it be possible to expand the RDAP results to include organization >>>> information? This seems like it would just be another vcard entry, so >>>> there really shouldn't be any backwards compatibility issues. >>>> >>>> Apologies if this isn't the correct list, I can't really find any >>>> information about RDAP on RIPE's website. >>>> >>>> >>> >> >
