Re: inetnums, country origin issues

[Trudy Prins trudy@localhost]

Hi Mark,

Well, I'm glad this is sorted out now :)
Let me know if you have any more questions,

Cheers,

--
Trudy Prins
RIPE NCC


Mark Tohill wrote:

>Trudy,
>
>Thanks for your reply!
>
>IT turns out our problem is we have been allocated our space, but it has
>not been assigned, as yet, hence the RIPE Maintainer. I assumed it had
>been assigned :(
>
>I'll have to put in PA Assignment requests first, then hopefully I'll be
>able to create separate inetnums, with appropriate differing country
>codes.
>
>It's all beginning to make sense now....
>
>Thanks again,
>Mark.
>
>inetnum:         194.46.0.0 - 194.46.255.255
>org:             ORG-UTVI1-RIPE
>netname:         UK-GENESIS-940228
>descr:           UTV Internet
>country:         GB
>admin-c:         CS667-RIPE
>tech-c:          CS667-RIPE
>status:          ***ALLOCATED*** PA 
>mnt-by:          RIPE-NCC-HM-MNT
>mnt-lower:       AS2873-MNT
>mnt-routes:      AS2873-MNT
>mnt-domains:     AS2873-MNT
>source:          RIPE # Filtered
>
>
>
>
>-----Original Message-----
>From: Trudy Prins [
	    
	    
] 
>Sent: 13 March 2006 10:58
>To: Mark Tohill
>Subject: 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
>
>
>  
>


-- 
Trudy