[Re: [sed] inetnums, country origin issues]

Mark Tohill wrote:

> Hi,
>
> I’m new to list so please be patient.
>
> I saw a thread dating back to 2003 titled “Change of country enties in
> the database” and have an issue with country codes.
>
> We are in an ISP which serves users in both Northern Ireland and the
> Republic of Ireland. Our main inetnum /16 has a country code of GB.
>
> It seems some of our RoI customers suffer from this regarding
> redirection of search engines etc.
>
> We do have a some degree of address consolidation for PoP’s in both
> countries.
>
> Should we have separate inetnum’s for these PoP’s and get rid of the /16?
>
> What is the best way to handle this?
>
> Any help appreciated.
>
> Mark
>

Hello Mark,

Well, you could put several Country codes in a separate <country: >
attribute.
As you can see, it is 'multiple':

whois -t inetnum

inetnum: [mandatory] [single] [primary/look-up key]
netname: [mandatory] [single] [lookup key]
descr: [mandatory] [multiple] [ ]
country: [mandatory] [multiple] [ ]
org: [optional] [single] [inverse key]
admin-c: [mandatory] [multiple] [inverse key]
tech-c: [mandatory] [multiple] [inverse key]
rev-srv: [optional] [multiple] [inverse key]
status: [mandatory] [single] [ ]
remarks: [optional] [multiple] [ ]
notify: [optional] [multiple] [inverse key]
mnt-by: [mandatory] [multiple] [inverse key]
mnt-lower: [optional] [multiple] [inverse key]
mnt-domains: [optional] [multiple] [inverse key]
mnt-routes: [optional] [multiple] [inverse key]
mnt-irt: [optional] [multiple] [inverse key]
changed: [mandatory] [multiple] [ ]
source: [mandatory] [single] [ ]

You can also make several 'Assignments' under your /16 Allocation, to
different organisations,
with different Country codes.

Does this answer your question somewhat?

Regards,

Trudy Prins
RIPE NCC