Hi Arash,
Arash Naderpour wrote:
> Yes I know allocations and assignments can be announced from multiple
> countries, but a member has this option to set the country code for
> allocation and assignments based on their needs. If I can set my
> allocation's country code in RIPE DB why I should
some situations. It shouldn't, but
it happens.
Cheers,
Sanjaya
Sent from my mobile
From: db-wg on behalf of Randy Bush via db-wg
Sent: Friday, November 8, 2019 5:32:50 PM
To: Sanjaya Sanjaya via db-wg
Subject: Re: [db-wg] [Ext] Re: NWI-10 Definition
sanjaya:
FWIW, APNIC Whois database has 3 objects with more than one distinct
country attributes, out of the 1,147,623 inetnum/inet6num/autnum
objects.
are these useful to apnic, ops, or even researchers?
randy
walker
Subject: Re: [db-wg] [Ext] Re: NWI-10 Definition of Country
Yes I know allocations and assignments can be announced from multiple
countries, but a member has this option to set the country code for allocation
and assignments based on their needs. If I can set my allocation's country cod
Yes I know allocations and assignments can be announced from multiple
countries, but a member has this option to set the country code for
allocation and assignments based on their needs. If I can set my
allocation's country code in RIPE DB why I should not be able to have the
same value in delegati
Arash,
Arash Naderpour wrote:
> What you name it as "meaningless values" are not meaningless to
> the organizations that they are using it.
How do we know that all, or even most, users of the data infer the same
meanings? Has the RIPE NCC or anyone else ever measured what people understand
th
Sanjaya wrote:
> Just a thought, maybe we could redefine the RIR extended delegated
> file format to incorporate both cc values of inet(6)num|autnum and
> organisation Whois objects like this:
>
> registry|xx|type|start|value|date|status|yy-custodianid
> Where:
> xx = country code of inet(6)num
