Broken RDAP response
We hit issues with: https://rdap.db.ripe.net/ip/37.246.0.0/16 It looks like someone added multiple country: fields in the RIPE database inetnum: 37.246.0.0 - 37.246.255.255 netname: MD-SHATRANS-20120417 country: GB country: US org: ORG-TS151-RIPE How did this even get into the database in the first place? I'm not sure returning an error via RDAP is really the best way of handling this.
On Thu, 9 Aug 2018 at 18:20, Brian Rak via db-wg <db-wg@ripe.net> wrote:
We hit issues with: https://rdap.db.ripe.net/ip/37.246.0.0/16
It looks like someone added multiple country: fields in the RIPE database
inetnum: 37.246.0.0 - 37.246.255.255 netname: MD-SHATRANS-20120417 country: GB country: US org: ORG-TS151-RIPE
How did this even get into the database in the first place? I'm not sure returning an error via RDAP is really the best way of handling this.
Looks like somebody updated the object. The 37.246.0.0/17 is still broken with more than 1 contry code attached. :/ inetnum: 37.246.0.0 - 37.246.127.255 netname: FHN-MPLS-200092990T descr: Fiberhop Communications Ltd. country: GB country: US admin-c: FNS32-RIPE tech-c: FNS32-RIPE status: ASSIGNED PA mnt-by: SHA-MNT created: 2013-03-13T14:13:05Z last-modified: 2018-01-25T22:44:54Z source: RIPE inetnum: 37.246.0.0 - 37.246.255.255 netname: MD-SHATRANS-20120417 country: US org: ORG-TS151-RIPE admin-c: FH5305-RIPE tech-c: FH5305-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-by: SHA-MNT mnt-routes: SHA-MNT notify: noc@fiberhop.com created: 2012-04-17T07:57:05Z last-modified: 2018-08-09T16:30:43Z source: RIPE
On Thu, 9 Aug 2018 at 18:20, Brian Rak via db-wg <db-wg@ripe.net> wrote:
We hit issues with: https://rdap.db.ripe.net/ip/37.246.0.0/16
It looks like someone added multiple country: fields in the RIPE database
inetnum: 37.246.0.0 - 37.246.255.255 netname: MD-SHATRANS-20120417 country: GB country: US org: ORG-TS151-RIPE
How did this even get into the database in the first place? I'm not sure returning an error via RDAP is really the best way of handling this.
Looks like several INETNUM objects have more than 1 country code attached in the RIPE NCC database. :/ ~ > whois -h whois.ripe.net -rB -T as-set,aut-num,domain,filter-set,inetnum,inet6num,person,peering-set,organisation,mntner,key-cert,irt,inet-rtr,poem,poetic-form,role,route,route6,route-set,rtr-set -i mnt-routes,mnt-ref,mnt-nfy,mnt-lower,mnt-irt,mnt-domains,mnt-by SHA-MNT | grep -v '^%' | cat -s inetnum: 37.246.0.0 - 37.246.127.255 netname: FHN-MPLS-200092990T descr: Fiberhop Communications Ltd. country: GB country: US admin-c: FNS32-RIPE tech-c: FNS32-RIPE status: ASSIGNED PA mnt-by: SHA-MNT created: 2013-03-13T14:13:05Z last-modified: 2018-01-25T22:44:54Z source: RIPE inetnum: 37.246.0.0 - 37.246.255.255 netname: MD-SHATRANS-20120417 country: US org: ORG-TS151-RIPE admin-c: FH5305-RIPE tech-c: FH5305-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-by: SHA-MNT mnt-routes: SHA-MNT notify: noc@fiberhop.com created: 2012-04-17T07:57:05Z last-modified: 2018-08-09T16:30:43Z source: RIPE inetnum: 37.246.128.0 - 37.246.191.255 netname: FHN-RPLS-10393K descr: Fiberhop Communications Ltd. country: GB country: US admin-c: FH5305-RIPE tech-c: FH5305-RIPE status: ASSIGNED PA mnt-by: SHA-MNT created: 2013-08-29T17:05:24Z last-modified: 2018-01-25T22:47:10Z source: RIPE inetnum: 37.246.192.0 - 37.246.255.255 netname: FHN-RPLS-54100029K descr: Fiberhop Communications Ltd. country: GB country: US country: TR admin-c: FNS32-RIPE tech-c: FNS32-RIPE status: ASSIGNED PA mnt-by: SHA-MNT created: 2013-03-17T18:34:07Z last-modified: 2018-01-25T22:44:27Z source: RIPE inetnum: 81.162.128.0 - 81.162.191.255 netname: SHA-Trans country: US org: ORG-TS151-RIPE admin-c: FNS32-RIPE tech-c: FNS32-RIPE status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-by: SHA-MNT mnt-routes: SHA-MNT mnt-domains: SHA-MNT created: 2011-12-06T13:51:42Z last-modified: 2018-08-09T16:31:19Z source: RIPE aut-num: AS57598 as-name: SHA-AS org: ORG-TS151-RIPE import: from AS15836 accept ANY export: to AS15836 announce AS57598 admin-c: FH5305-RIPE tech-c: FH5305-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: SHA-MNT mnt-routes: SHA-MNT created: 2011-12-07T11:09:46Z last-modified: 2018-01-26T23:02:37Z source: RIPE route: 37.246.0.0/16 descr: SHA-Trans Route origin: AS57598 mnt-by: SHA-MNT created: 2012-04-19T12:24:58Z last-modified: 2012-04-19T12:24:58Z source: RIPE route: 81.162.128.0/18 descr: "S.H.A. Trans" S.R.L. origin: AS57598 mnt-by: SHA-MNT created: 2011-12-07T11:20:01Z last-modified: 2011-12-07T12:13:43Z source: RIPE mntner: SHA-MNT descr: Fiberhop Communications Ltd. admin-c: FNS32-RIPE upd-to: noc@fiberhop.co.uk auth: SSO # Filtered mnt-by: SHA-MNT created: 2011-12-07T12:11:51Z last-modified: 2018-01-25T22:41:10Z source: RIPE # Filtered irt: IRT-SHATRANS address: FiberHop Communications Ltd. address: 71-75 Shelton Street Covent Garden address: London, WC2H 9JQ address: GB e-mail: noc@fiberhop.co.uk admin-c: FNS32-RIPE tech-c: FNS32-RIPE auth: MD5-PW # Filtered mnt-by: SHA-MNT created: 2012-04-24T18:53:29Z last-modified: 2018-01-27T00:09:45Z source: RIPE # Filtered organisation: ORG-TS151-RIPE org-name: "S.H.A. Trans" S.R.L. org-type: LIR address: 71?75 Shelton Street Covent Garden address: WC2H 9JQ address: London address: UNITED KINGDOM e-mail: noc@fiberhop.com mnt-ref: SHA-MNT mnt-ref: RIPE-NCC-HM-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: SHA-MNT abuse-c: FNS32-RIPE created: 2012-03-19T16:28:42Z last-modified: 2018-08-09T16:02:13Z source: RIPE phone: +13058097217 fax-no: +13058097217 admin-c: FH5305-RIPE role: FiberHop Hostmaster address: 71-75 Shelton Street Covent Garden address: WC2H 9JQ address: London, GB phone: +13058097217 e-mail: noc@fiberhop.com admin-c: MMB144-RIPE admin-c: JC9841-RIPE tech-c: MMB144-RIPE tech-c: JC9841-RIPE nic-hdl: FH5305-RIPE remarks: mnt-by: SHA-MNT created: 2018-01-25T22:34:09Z last-modified: 2018-08-09T15:58:31Z source: RIPE role: FiberHop Network Security nic-hdl: FNS32-RIPE address: 71-75 Shelton Street Covent Garden address: London, GB WC2H 9JQ abuse-mailbox: security@fiberhop.com mnt-by: SHA-MNT e-mail: noc@fiberhop.com created: 2018-01-25T22:33:34Z last-modified: 2018-08-09T16:00:38Z source: RIPE person: Jerry Coleman address: Fiberhop Communications Ltd. address: 71-75 Shelton Street address: Covent Garden, WC2H 9JQ address: London, GB phone: +13058097217 e-mail: jerry.coleman@fiberhop.co.uk nic-hdl: JC9841-RIPE remarks: notify: noc@fiberhop.co.uk mnt-by: SHA-MNT created: 2018-01-25T22:24:04Z last-modified: 2018-01-25T22:34:37Z source: RIPE person: Michael M. Basaran address: Fiberhop Communications Ltd. address: 71-75 Shelton Street address: Covent Garden, WC2H 9JQ address: London, GB phone: +13058097217 e-mail: noc@fiberhop.co.uk nic-hdl: MMB144-RIPE remarks: notify: noc@fiberhop.co.uk mnt-by: SHA-MNT created: 2018-01-25T22:26:34Z last-modified: 2018-01-25T22:34:17Z source: RIPE
On Thu, Aug 09, 2018 at 07:33:40PM +0200, Christoffer Hansen via db-wg wrote:
On Thu, 9 Aug 2018 at 18:20, Brian Rak via db-wg <db-wg@ripe.net> wrote:
We hit issues with: https://rdap.db.ripe.net/ip/37.246.0.0/16
It looks like someone added multiple country: fields in the RIPE database
inetnum: 37.246.0.0 - 37.246.255.255 netname: MD-SHATRANS-20120417 country: GB country: US org: ORG-TS151-RIPE
How did this even get into the database in the first place? I'm not sure returning an error via RDAP is really the best way of handling this.
Looks like several INETNUM objects have more than 1 country code attached in the RIPE NCC database. :/
$ whois -t inetnum |grep country country: [mandatory] [multiple] [ ] That should explain things a bit. Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland
On Thu, 9 Aug 2018 at 20:00, Piotr Strzyzewski <Piotr.Strzyzewski@polsl.pl> wrote:
$ whois -t inetnum |grep country country: [mandatory] [multiple] [ ]
That should explain things a bit.
Indeed it does. Probably less than ideal software design can be the reason for the broken RDAP responses. Brian? /Christoffer
On 8/9/2018 2:05 PM, Christoffer Hansen wrote:
On Thu, 9 Aug 2018 at 20:00, Piotr Strzyzewski <Piotr.Strzyzewski@polsl.pl> wrote:
$ whois -t inetnum |grep country country: [mandatory] [multiple] [ ]
That should explain things a bit. Indeed it does.
Probably less than ideal software design can be the reason for the broken RDAP responses. Brian?
/Christoffer
We're using RDAP to retrieve contacts to verify BGP announcements. I don't really have any idea why this customer had multiple countries setup here. It is interesting that RDAP cannot represent what's apparently a valid database entry though!
* Brian Rak via db-wg
It is interesting that RDAP cannot represent what's apparently a valid database entry though!
Yeah, the standards are unfortunately not in sync. Tim Bruijnzeels said he was going to bring up the issue at an IETF meeting. I don't know if anything came out of it. https://github.com/arineng/nicinfo/issues/21#issuecomment-258860529 Tore
Dear Tore/all, When the RIR Engineering Coordination Group (ECG) met during the last IETF, there was a lot of discussion on the inconsistencies surrounding the RDAP implementations between the RIRs - including this multiple country issue. Our plan is to identify a list of issues and create a shared backlog of work items. We will then prioritise these and start working to address them in Q4 2018. PS. Note that Tim is no longer working at the RIPE NCC - Thiago da Cruz Pereira has taken over many of his duties and was at the ECG meeting. Kind regards, Theodoros Polychniatis, Manager Software Engineering, RIPE NCC On 09/08/2018 20:24, Tore Anderson via db-wg wrote:
* Brian Rak via db-wg
It is interesting that RDAP cannot represent what's apparently a valid database entry though! Yeah, the standards are unfortunately not in sync.
Tim Bruijnzeels said he was going to bring up the issue at an IETF meeting. I don't know if anything came out of it.
https://github.com/arineng/nicinfo/issues/21#issuecomment-258860529
Tore
participants (5)
-
Brian Rak -
Christoffer Hansen -
Piotr Strzyzewski -
Theodoros Polychniatis -
Tore Anderson