[db-wg] Recognisition of Kosovo and adding of LIR signup options with Kosovo as well as XK in inet(6)num

William,

Job promised to bring it to a RIPE NCC board meeting. This happened here:

https://www.ripe.net/about-us/executive-board/minutes/2022/minutes-159th-executive-board-meeting

"The Board asked to pursue possible solutions for registrations of 
members from Kosovo. Athina Fragkouli noted this situation is being 
analysed and she will report back in the next meeting."

It doesn't seem to have gotten added as an action item, and I don't see 
any further references to it. It is possible the report was made and it 
was not minuted, or that the analysis is taking longer than expected.

Cheers,

--
Shane

On 17/11/2022 00.09, William Weber via db-wg wrote:
> Did anything ever happen with this? I still have to use Albania and with 
> the new country set in ORGs i and other ISPs in Kosovo have even more 
> problems now.
> 
> We are extremely unhappy with this situation, the RIPE NCC and Dutch 
> government can expect an official complaint letter from the Kosovarian 
> government very soon if there is not even any attempt at talking with 
> us/the gov and fixing this issue.
> 
> I simply do not understand how we can be entirely ignored while even our 
> banks usem XK IBANs and Euro as currency, it is absurd.
> 
> --
> William
> BASEHOST SHPK
> Pristina, Kosovo
> 
> On Fri, May 13, 2022 at 10:33 PM William Weber <william at inbox.li 
> <mailto:william at inbox.li>> wrote:
> 
>     In the end i dont care, Kosovo is a country (acknowledged by 50%+ of
>     UN members including NL)
>       and i want to be able to use it as intended.
> 
>     —
>     William
> 
>     Sent from my iPhone
> 
>>     On 13.05.2022, at 21:58, David Conrad <drc at virtualized.org
>>     <mailto:drc at virtualized.org>> wrote:
>>
>>     William,
>>
>>>     On May 13, 2022, at 2:11 AM, William Weber via db-wg
>>>     <db-wg at ripe.net <mailto:db-wg at ripe.net>> wrote:
>>>
>>>     I am aware the the X* series of codes is reserved and not
>>>     permanently assigned, however UN Security Council resolution
>>>     1244/99 (see 6) mandates the use binding to all UN members.
>>>
>>
>>     The “X*” series is not reserved, they are (permanently) designated
>>     for “user-assigned” use. Think 10/8.  Anyone (including RIPE) can
>>     use them for whatever purpose they so choose, just as anyone can
>>     use 10/8. Of course, your use and my use might conflict, but
>>     that’s for us to work out between us (with the obvious scaling
>>     implications that suggests).
>>
>>     FYI, EU is different in that it is “exceptionally reserved”.  It
>>     is one of a number of ISO-3166 codes that have that status
>>     (including UK, AC, DG, SU, and a few others). AP is a bit weird
>>     (IMHO) in that ISO-3166 Maintenance Agency has stated that they
>>     will not use the code “at the present stage.” I gather that’s an
>>     informal agreement between ISO-3166/MA and WIPO. I’ve no clue what
>>     that means for the long-term status of that code.
>>
>>     The real question is what would break if RIPE chooses to use a
>>     user assigned code in their database.  I’ve no idea, but to be
>>     honest, I’m a bit uncomfortable with the precedent it might set
>>     (and political foodfight it might generate given the UN
>>     Statistical Agency hasn’t seen fit to recommend the creation of an
>>     actual ISO-3166 code). However, I doubt my comfort matters.
>>
>>     As far as I can tell, your reference to UN Security Council
>>     resolution 1244/99 is irrelevant, particularly as it
>>     (appropriately, given the status of the ISO-3166 code) doesn’t
>>     mention XK.
>>
>>     FWIW, Jaap Akkerhuis, a person well known to many on this list, is
>>     extremely well-versed in the world of ISO-3166 and could probably
>>     provide any info you might need related to the use of ISO-3166 codes.
>>
>>     Regards,
>>     -drc
>>
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3732979CF967B306.asc
Type: application/pgp-keys
Size: 11519 bytes
Desc: OpenPGP public key
URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20221117/5780b2cb/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20221117/5780b2cb/attachment.sig>