NASK: at the NASK: at the cutting edge of cutting edge of technologytechnology

Andrzej BartosiewiczAndrzej BartosiewiczITU-T SG17 meetingITU-T SG17 meetingMoscow, 2005Moscow, 2005

PART 1:TutorialPART 1:Tutorial

DNS resolutionDNS resolution

DNS

(2) question: xn--wwz-hna2g.pl?

(3) answer: IP

(1) please, open page: „www.wąwóz.pl”

(4) download the page.

IDN IDN versusversus ACE string ACE string

www.kozłowski.pl

www.xn--kozowski-8ob.pl

overview of ICANNoverview of ICANN

ICANNICANN The Internet Corporation for Assigned Names The Internet Corporation for Assigned Names

and Numbers (ICANN) is a technical and Numbers (ICANN) is a technical coordination body for the Internetcoordination body for the Internet. Created in . Created in October 1998 by a broad coalition of the October 1998 by a broad coalition of the Internet's business, technical, academic, and Internet's business, technical, academic, and user communities, ICANN is assuming user communities, ICANN is assuming responsibility for a set of technical functions responsibility for a set of technical functions previously performed under U.S. government previously performed under U.S. government contract by IANA and other groups.contract by IANA and other groups.

Specifically, ICANN coordinates the assignment Specifically, ICANN coordinates the assignment of the following identifiers that must be globally of the following identifiers that must be globally unique for the Internet to function:unique for the Internet to function: Internet domain names Internet domain names IP address numbers IP address numbers protocol parameter and port numbers protocol parameter and port numbers

In addition, ICANN coordinates the stable In addition, ICANN coordinates the stable operation of the Internet's root server system.operation of the Internet's root server system.

ICANN cont.ICANN cont. As a non-profit, private-sector corporation, As a non-profit, private-sector corporation,

ICANN is dedicated to preserving the ICANN is dedicated to preserving the operational stability of the Internet; to operational stability of the Internet; to promoting competition; to achieving broad promoting competition; to achieving broad representation of global Internet communities; representation of global Internet communities; and to developing policy through private-and to developing policy through private-sector, bottom-up, consensus-based means. sector, bottom-up, consensus-based means. ICANN welcomes the participation of any ICANN welcomes the participation of any interested Internet user, business, or organizat interested Internet user, business, or organizat

Source: http://www.icann.org/new.htmlSource: http://www.icann.org/new.html

ICANN documentsICANN documents

General infoGeneral infohttp://www.icann.org/topics/idn.htmlhttp://www.icann.org/topics/idn.html

IDN Language Table RegistryIDN Language Table Registry http://www.iana.org/assignments/idn/http://www.iana.org/assignments/idn/

ICANN Statement on IDN Homograph ICANN Statement on IDN Homograph Attacks and Request for Public Attacks and Request for Public CommentComment http://www.icann.org/announcements/annohttp://www.icann.org/announcements/announcement-23feb05.htmuncement-23feb05.htm

overview of IETFoverview of IETF

IETFIETF The Internet Engineering Task Force The Internet Engineering Task Force

(IETF) is a large open international (IETF) is a large open international community of network designers, community of network designers, operators, vendors, and researchers operators, vendors, and researchers concerned with the evolution of the concerned with the evolution of the Internet architecture and the smooth Internet architecture and the smooth operation of the Internet. It is open to operation of the Internet. It is open to any interested individual. any interested individual.

The actual technical work of the IETF is The actual technical work of the IETF is done in its working groups, which are done in its working groups, which are organized by topic into several areas organized by topic into several areas (e.g., routing, transport, security, etc.). (e.g., routing, transport, security, etc.). Much of the work is handled via mailing Much of the work is handled via mailing lists. The IETF holds meetings three lists. The IETF holds meetings three times per year.times per year.

IETF cont.IETF cont. The IETF working groups are grouped into The IETF working groups are grouped into

areas, and managed by Area Directors, or ADs. areas, and managed by Area Directors, or ADs. The ADs are members of the Internet The ADs are members of the Internet Engineering Steering Group (IESG). Providing Engineering Steering Group (IESG). Providing architectural oversight is the Internet architectural oversight is the Internet Architecture Board, (IAB). The IAB also Architecture Board, (IAB). The IAB also adjudicates appeals when someone complains adjudicates appeals when someone complains that the IESG has failed. The IAB and IESG are that the IESG has failed. The IAB and IESG are chartered by the Internet Society (ISOC) for chartered by the Internet Society (ISOC) for these purposes. these purposes.

The General Area Director also serves as the The General Area Director also serves as the chair of the IESG and of the IETF, and is an ex-chair of the IESG and of the IETF, and is an ex-officio member of the IAB. officio member of the IAB.

http://www.ietf.org/overview.htmlhttp://www.ietf.org/overview.html

IETF documensIETF documens

Internationalizing Domain Names in Internationalizing Domain Names in Applications (IDNA)Applications (IDNA)http://www.ietf.org/rfc/rfc3490.txthttp://www.ietf.org/rfc/rfc3490.txt

Nameprep: A Stringprep Profile for Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)Internationalized Domain Names (IDN)

http://www.ietf.org/rfc/rfc3491.txthttp://www.ietf.org/rfc/rfc3491.txt Punycode: A Bootstring Encoding of Punycode: A Bootstring Encoding of

Unicode for Internationalized Domain Unicode for Internationalized Domain Names in Applications (IDNA) Names in Applications (IDNA) http://www.ietf.org/rfc/rfc3492.txthttp://www.ietf.org/rfc/rfc3492.txt

IDNs charterIDNs charterhttp://www.ietf.org/html.charters/idn-http://www.ietf.org/html.charters/idn-charter.htmlcharter.html

role of ITUrole of ITU

role of ITUrole of ITU Plenipotentiary Conference (Marrakesh Plenipotentiary Conference (Marrakesh

2002) 2002) Resolution 102: Resolution 102: “Management of Internet Domain “Management of Internet Domain

Names and Addresses”Names and Addresses” Resolution 133: “Role of administrations of Resolution 133: “Role of administrations of

Member States in the management of Member States in the management of internationalized domain names” internationalized domain names”

““Resolution 48 – Internationalized domain Resolution 48 – Internationalized domain names” of The World Telecommunication names” of The World Telecommunication Standardization Assembly (Florianópolis, Standardization Assembly (Florianópolis, 2004)2004), , Study Group 17 Study Group 17 of ITU-T is of ITU-T is instructed instructed to study to study Internationalized Internationalized Domain NamesDomain Names, and to continue to liaise , and to continue to liaise and cooperate with appropriate entities in and cooperate with appropriate entities in this areathis area

ITU documentsITU documents

RSS channelRSS channelhttp://www.itu.int/osg/spu/newslog/categories/ihttp://www.itu.int/osg/spu/newslog/categories/internationalizedDomainNames/nternationalizedDomainNames/

Introcution to IDNs by R.ShawIntrocution to IDNs by R.Shawhttp://www.itu.int/osg/spu/presentations/2003/Ihttp://www.itu.int/osg/spu/presentations/2003/ITU-moscow-presentation-idn.pdfTU-moscow-presentation-idn.pdf

Resolution 102 of Plenipotentiary Resolution 102 of Plenipotentiary ConferenceConference http://www.itu.int/osg/spu/resolutions/2002/reshttp://www.itu.int/osg/spu/resolutions/2002/res102.html102.html

Resolution 133 of Plenipotentiary Resolution 133 of Plenipotentiary ConferenceConference http://www.itu.int/osg/spu/resolutions/2002/reshttp://www.itu.int/osg/spu/resolutions/2002/resplen5.htmlplen5.html

Resolution 48Resolution 48 of WTSAof WTSAhttp://www.itu.int/ITU-T/wtsa/resolutions04/Reshttp://www.itu.int/ITU-T/wtsa/resolutions04/Res48E.pdf48E.pdf

technical backgroundtechnical background

technical foundationtechnical foundation

The Internet Engineering Task Force (IETF) The Internet Engineering Task Force (IETF) has approved documents whichhas approved documents which provide provide thethe technical foundation for handling domain technical foundation for handling domain names with Unicode characters (domain names with Unicode characters (domain names which contain non-ASCII names which contain non-ASCII characters)characters)::

RFC 3490RFC 3490 Internationalizing Domain Names Internationalizing Domain Names in Applicationsin Applications

RFC 3491RFC 3491 Nameprep: A Stringprep Profile Nameprep: A Stringprep Profile for Internationalized Domain Namesfor Internationalized Domain Names

RFC 3492RFC 3492 Punycode: Punycode: A Bootstring encoding of Unicode for A Bootstring encoding of Unicode for Internationalized Domain Names in Internationalized Domain Names in ApplicationsApplications

IDNA (RFC 3490): example IDNA (RFC 3490): example

NAMEPREP (RFC 3491):NAMEPREP (RFC 3491):KOZŁOWSKI.pl KOZŁOWSKI.pl

kozłowski.plkozłowski.pl PUNYCODE (RFC 3492):PUNYCODE (RFC 3492):

kozłowski.pl kozłowski.pl

kozowski-8ob.plkozowski-8ob.pl Prefix: xn--Prefix: xn--

kozowski-8ob.pl kozowski-8ob.pl

xn--kozowski-xn--kozowski-8ob.pl8ob.pl

types of IDNstypes of IDNs

Basic types of IDNs:Basic types of IDNs: ML.ASCIIML.ASCII

Multilingual.ASCII Domain Multilingual.ASCII Domain NamesNames (ccTLD or gTLD) (ccTLD or gTLD)

ML.MLML.MLMultilingual.MultilingualMultilingual.Multilingual (ccTLD (ccTLD or gTLD)or gTLD)

ICANN guidelinesICANN guidelines

ICANN gICANN guidelinesuidelines 1. Top-level domain registries that 1. Top-level domain registries that

implement internationalized domain name implement internationalized domain name capabilities will do so in strict compliance capabilities will do so in strict compliance with the with the technical requirements described technical requirements described in RFCs 3490, 3491, and 3492in RFCs 3490, 3491, and 3492 (collectively, (collectively, the "IDN standards").the "IDN standards").

2. In implementing the IDN standards, top-2. In implementing the IDN standards, top-level domain registries will employ an level domain registries will employ an "inclusion-based" approach (meaning that "inclusion-based" approach (meaning that code points that are not explicitly code points that are not explicitly permitted by the registry are prohibitedpermitted by the registry are prohibited) ) for identifying permissible code points from for identifying permissible code points from among the full Unicode repertoire.among the full Unicode repertoire.

ICANN gICANN guidelinesuidelines 3. In implementing the IDN standards, top-3. In implementing the IDN standards, top-

level domain registries will (a) level domain registries will (a) associate associate each registered internationalized domain each registered internationalized domain name with one language or set of name with one language or set of languageslanguages, (b) employ language-specific , (b) employ language-specific registration and administration rules that registration and administration rules that are documented and publicly available, are documented and publicly available, such as the reservation of all domain such as the reservation of all domain names with equivalent character variants names with equivalent character variants in the languages associated with the in the languages associated with the registered domain name, and, (c) where registered domain name, and, (c) where the registry finds that the registration and the registry finds that the registration and administration rules for a given language administration rules for a given language would benefit from a character variants would benefit from a character variants table, allow registrations in that language table, allow registrations in that language only when an appropriate table is available.only when an appropriate table is available.

ICANN gICANN guidelinesuidelines 4. Registries will work collaboratively with 4. Registries will work collaboratively with

relevant and interested stakeholders to relevant and interested stakeholders to develop language-specific registration develop language-specific registration policies (including, where the registry policies (including, where the registry determines appropriate, character variant determines appropriate, character variant tables), with the objective of achieving tables), with the objective of achieving consistent approaches to IDN consistent approaches to IDN implementation for the benefit of DNS implementation for the benefit of DNS users worldwide. Registries will work users worldwide. Registries will work collaboratively with each other to address collaboratively with each other to address common issues, through, for example, ad common issues, through, for example, ad hoc groups, regional groups, and global hoc groups, regional groups, and global fora, such as the ICANN IDN Registry fora, such as the ICANN IDN Registry Implementation Committee.Implementation Committee.

ICANN gICANN guidelinesuidelines 5. In implementing the IDN 5. In implementing the IDN

standards, top-level domain standards, top-level domain registries should, at least initially, registries should, at least initially, limit any given domain label (such as limit any given domain label (such as a second-level domain name) to the a second-level domain name) to the characters associated with one characters associated with one language or set of languages only.language or set of languages only.

6. Top-level domain registries (and 6. Top-level domain registries (and registrars) should provide registrars) should provide informational resources and services informational resources and services in all languages for which they offer in all languages for which they offer internationalized domain name internationalized domain name registrations.registrations.

URI and IRIURI and IRI

Uniform Resource IdentifierUniform Resource Identifier

A Uniform Resource Identifier (URI) is A Uniform Resource Identifier (URI) is a compact sequence of characters a compact sequence of characters that identifies an abstract or physical that identifies an abstract or physical resource.resource. This specification defines This specification defines the generic URI syntax and a process the generic URI syntax and a process for resolving URI references that for resolving URI references that might be in relative form, along with might be in relative form, along with guidelines and security guidelines and security considerations for the use of URIs on considerations for the use of URIs on the Internet. the Internet.

RFC 3986RFC 3986

examples of URIexamples of URI

ftp://ftp.is.co.za/rfc/rfc1808.txtftp://ftp.is.co.za/rfc/rfc1808.txt http://www.ietf.org/rfc/rfc2396.txthttp://www.ietf.org/rfc/rfc2396.txt ldap://[2001:db8::7]/c=GB?ldap://[2001:db8::7]/c=GB?

objectClass?oneobjectClass?one mailto:John.Doe@example.commailto:John.Doe@example.com news:comp.infosystems.www.servernews:comp.infosystems.www.server tel:+1-816-555-1212tel:+1-816-555-1212 telnet://192.0.2.16:80/telnet://192.0.2.16:80/ urn:oasis:names:specification:docbourn:oasis:names:specification:docbo

ok:dtd:xml:4.1. ok:dtd:xml:4.1.

Internationalized Resource Internationalized Resource IdentifiersIdentifiers

Internationalized ResourceInternationalized Resource Identifiers Identifiers (IRIs) are a new protocol element, a (IRIs) are a new protocol element, a complement to URIs. complement to URIs.

An IRI is a sequence of characters An IRI is a sequence of characters from the Universal Character Set from the Universal Character Set (Unicode/ISO10646). There is a (Unicode/ISO10646). There is a mapping from IRIs to URIs, which mapping from IRIs to URIs, which means that IRIs can be used instead means that IRIs can be used instead of URIs where appropriate to identify of URIs where appropriate to identify resources.resources.

RFC 3987RFC 3987

IDN aware applicationsIDN aware applications

web browsersweb browsers CaminoCamino

URL: http://www.mozilla.org/products/camino/ URL: http://www.mozilla.org/products/camino/  EpiphanyEpiphany

URL: http://www.gnome.org/projects/epiphany/ URL: http://www.gnome.org/projects/epiphany/  FirefoxFirefox

URL: http://www.mozilla.org/products/firefox/ URL: http://www.mozilla.org/products/firefox/  GaleonGaleon

URL: http://galeon.sourceforge.net URL: http://galeon.sourceforge.net  KonquerorKonqueror

URL: http://www.konqueror.org/ URL: http://www.konqueror.org/  MozillaMozilla

URL: http://www.mozilla.org/products/mozilla1.x/ URL: http://www.mozilla.org/products/mozilla1.x/  Netscape Netscape

URL: http://www.netscape.com URL: http://www.netscape.com  OperaOpera

URL: http://www.opera.com URL: http://www.opera.com  SafariSafari

URL: http://www.apple.com/safari/  URL: http://www.apple.com/safari/  

e-mail / ftpe-mail / ftp FoxmailFoxmail

URL: http://fox.foxmail.com.cn URL: http://fox.foxmail.com.cn  FTP Core FTP Core

URL: http://www.coreftp.com URL: http://www.coreftp.com  Voyager FTP Voyager FTP

URL: http://www.ftpvoyager.com URL: http://www.ftpvoyager.com  Secure FTPSecure FTP

URL: http://www.securenetterm.com URL: http://www.securenetterm.com  Smart FTPSmart FTP

URL: http://www.smartftp.com URL: http://www.smartftp.com 

otherother

i-Nav™ and Componentsi-Nav™ and ComponentsURL: http://www.idnnow.com  URL: http://www.idnnow.com  

Applications Supported: Internet Applications Supported: Internet Explorer 5.0 and higher; Microsoft Explorer 5.0 and higher; Microsoft Outlook 2000, 2002 (XP), 2003; Outlook 2000, 2002 (XP), 2003; Outlook Express 5.0 and higher Web-Outlook Express 5.0 and higher Web-based E-mail Support: Hotmail, based E-mail Support: Hotmail, Yahoo(.com,.jp,.cn.,.kr) , Daum, Yahoo(.com,.jp,.cn.,.kr) , Daum, Netease(163.com) Netease(163.com) 

Source: VerisignSource: Verisign

technical problemstechnical problems

variants variants

The The variant(s)variant(s) are the character(s) are the character(s) and/or string(s) that are equivalent and/or string(s) that are equivalent to the base character. to the base character.

Note that these might not be true Note that these might not be true equivalent characters: a base equivalent characters: a base character might have a mapping to a character might have a mapping to a particular variant character, but that particular variant character, but that variant character does not have to variant character does not have to have a mapping to the base have a mapping to the base character. character.

Source: „A Method for Registering Internationalized Domain Names” Source: „A Method for Registering Internationalized Domain Names” P.HoffmanP.Hoffman

bundlesbundles A "registration bundle" is the set of all A "registration bundle" is the set of all

labels that comes from expanding the base labels that comes from expanding the base characters for a single name into their characters for a single name into their variants. variants.

A registry has three options for how to A registry has three options for how to handle the case where the registration handle the case where the registration bundle has more than one label. The policy bundle has more than one label. The policy options are:options are: Resolve all labels in the zone, making the zone Resolve all labels in the zone, making the zone

information identical to that of the registered information identical to that of the registered label.label.

Block all labels other than the registered label so Block all labels other than the registered label so they cannot be registered in the future.they cannot be registered in the future.

Resolve some labels and block some other Resolve some labels and block some other labels. labels.

Source: „A Method for Registering Internationalized Domain Names” Source: „A Method for Registering Internationalized Domain Names” P.HoffmanP.Hoffman

registration policyregistration policy

Registration policy can be divided Registration policy can be divided in three main categories:in three main categories:

Restrictions based on „Code Restrictions based on „Code Pages”,Pages”,

Restrictions based on „Code Restrictions based on „Code Points” requred by languages Points” requred by languages (one or more languages),(one or more languages),

No restrictions.No restrictions.

to do listto do list

already done…already done…

IDN Standards (RFCs) IDN Standards (RFCs) - ready- ready ICANN IDN Guidelines ICANN IDN Guidelines - ready- ready web browsers – ready, web browsers – ready, except IEexcept IE supported by many ccTLDs and gTLDsupported by many ccTLDs and gTLD

to do…to do…

Internationalized Resource Internationalized Resource IdentifiersIdentifiers

e-e-mailmail applications applications web browsers – Interner Explorerweb browsers – Interner Explorer IDN in Digital CertificatesIDN in Digital Certificates IDN over EPPIDN over EPP (if applicable) (if applicable) Interner ExplorerInterner Explorer and… general acceptance and… general acceptance

worldwide!worldwide!

general infogeneral info

PART 2: Polish PART 2: Polish experienceexperience

NASK: backgroundNASK: background

established in 1993established in 1993 R&D entity R&D entity ITU-T Sector Member: since October ITU-T Sector Member: since October

20042004 registry for .PLregistry for .PL registry for +48 ENUMregistry for +48 ENUM ISP/TSP (hosting, Internet Acces, IP ISP/TSP (hosting, Internet Acces, IP

Transit, corporate networks, Transit, corporate networks, videoconference, VoIP services)videoconference, VoIP services)

280 employees (total)280 employees (total)

technological success storytechnological success story

March 2003: EPP (the first registry in March 2003: EPP (the first registry in Europe)Europe)

September 2003: IDNs (the first September 2003: IDNs (the first registy in Europe)registy in Europe)

March 2004: ISO 9001:2000 (the first March 2004: ISO 9001:2000 (the first ccTLD registry all over the world with ccTLD registry all over the world with ISO 9001 in the field of domain ISO 9001 in the field of domain names)names)

May 2004: EPP for ENUM (the first May 2004: EPP for ENUM (the first national ENUM registry all over the national ENUM registry all over the world with EPP registry system)world with EPP registry system)

April 2004: Wait List Service April 2004: Wait List Service („options”)(„options”)

implementation implementation

history of IDNshistory of IDNs February 2002 – February 2003:February 2002 – February 2003:

Consultations with LICConsultations with LIC Press conferences, press releasesPress conferences, press releases Consultations and discussions with Consultations and discussions with

European ccTLD RegistriesEuropean ccTLD Registries Preliminary presentations during CENTR Preliminary presentations during CENTR

Administrative Workshop, CENTR Administrative Workshop, CENTR Technical Workshop.Technical Workshop.

March 2003: IETF RFC 3490, 3491 March 2003: IETF RFC 3490, 3491 and 3492and 3492

August the 11th, 2003: NASK’s IETF August the 11th, 2003: NASK’s IETF draftdraft

llaunch date:aunch date: September the September the 11th, 200311th, 2003

history of IDNs history of IDNs

September the 11th, 2003: Polish September the 11th, 2003: Polish script (under .pl)script (under .pl)

September the 18th, 2003: +Polish September the 18th, 2003: +Polish script under 2nd levelscript under 2nd level

October the 6th, 2003: +Germans October the 6th, 2003: +Germans characterscharacters

October the 20th, 2003: +Latin 1 October the 20th, 2003: +Latin 1 Supplement and Latin Extended-A Supplement and Latin Extended-A

November the 3rd, 2003: +GreekNovember the 3rd, 2003: +Greek February the 26th, 2004: February the 26th, 2004: ++CyrillicCyrillic

IDN rulesIDN rules

First Come, First Served method,First Come, First Served method, nno pre-registrations,o pre-registrations, nno „sunrise” period,o „sunrise” period, ACE version only for input, output, ACE version only for input, output,

processing,processing, NASK accepts only valid ACE strings NASK accepts only valid ACE strings

according to RFC 3490, 3491, 3492,according to RFC 3490, 3491, 3492, ““xn--” is the only accepted prefix for xn--” is the only accepted prefix for

ACE domain names,ACE domain names,

IDN rulesIDN rules nno special rules for ACE domain o special rules for ACE domain

namesnames combination of characters from combination of characters from

different character sets is not different character sets is not allowedallowed

nno variantso variants nno bundlingo bundling nno association with languageso association with languages – –

- - no “language tags”no “language tags” no changes to internal databases, no changes to internal databases,

protocols (EPP), invoicing, protocols (EPP), invoicing, procedures, customer care etc.procedures, customer care etc.

statisticsstatistics

registrations (weekly)registrations (weekly)

0

200

400

600

800

1000

1200

1400

1600

1800

2003

-09-

11

2003

-10-

02

2003

-10-

23

2003

-11-

13

2003

-12-

04

2003

-12-

25

2004

-01-

15

2004

-02-

05

2004

-02-

26

2004

-03-

18

2004

-04-

08

2004

-04-

29

2004

-05-

20

2004

-06-

10

2004

-07-

01

2004

-07-

22

2004

-08-

12

2004

-09-

02

2004

-09-

23

2004

-10-

14

2004

-11-

04

2004

-11-

25

2004

-12-

16

2005

-01-

06

2005

-01-

27

2005

-02-

17

2005

-03-

10

registrations (cumulative)registrations (cumulative)

0

1000

2000

3000

4000

5000

6000

2003

-09-

11

2003

-10-

02

2003

-10-

23

2003

-11-

13

2003

-12-

04

2003

-12-

25

2004

-01-

15

2004

-02-

05

2004

-02-

26

2004

-03-

18

2004

-04-

08

2004

-04-

29

2004

-05-

20

2004

-06-

10

2004

-07-

01

2004

-07-

22

2004

-08-

12

2004

-09-

02

2004

-09-

23

2004

-10-

14

2004

-11-

04

2004

-11-

25

2004

-12-

16

2005

-01-

06

2005

-01-

27

2005

-02-

17

2005

-03-

10

IDN statsIDN stats

< 2% IDNs< 2% IDNs > 98% ASCII> 98% ASCII

2%

98%

securitysecurity

homograph attackshomograph attacks

NASK prevents existing NASK prevents existing registrants from homograph registrants from homograph attacks:attacks: different script mixing (for different script mixing (for

example characters from Cyrillic example characters from Cyrillic and Latin script) is not allowed and Latin script) is not allowed under .plunder .pl

registration of domain names in registration of domain names in Cyrillics similar to existing Latin Cyrillics similar to existing Latin domain names is not alloweddomain names is not allowed

andrzej.bartosiewicz @ nask.plandrzej.bartosiewicz @ nask.plwww.bartosiewicz.plwww.bartosiewicz.pl