idnits 2.17.1 draft-bakleh-reg-adm-acg-apu-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 21. -- Found old boilerplate from RFC 3978, Section 5.5 on line 412. ** The document claims conformance with section 10 of RFC 2026, but uses some RFC 3978/3979 boilerplate. As RFC 3978/3979 replaces section 10 of RFC 2026, you should not claim conformance with it if you have changed to using RFC 3978/3979 boilerplate. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There is 1 instance of lines with non-ascii characters in the document. == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 10) being 86 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** There are 87 instances of lines with control characters in the document. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Unrecognized Status in '[Target Category: Standards Track] Mohamed A. Elhamalaway, Ph.D.', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC3492' on line 459 looks like a reference -- Missing reference section? 'RFC3491' on line 466 looks like a reference -- Missing reference section? 'RFC3490' on line 473 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internationalized Domain Editors : Mhd. Elfatih Altijani. 2 Names Registration and Khaled Al Ahmad. 3 Administration Guidelines Omar Bakleh. 4 for Arabic Characters Group Reem Dannan. 5 of Languages 6 (Arabic, Persian, Urdu,...) Authors: Rifaah Ekrema 7 Fidaa Aljundi 8 [Target Category: Standards Track] Mohamed A. Elhamalaway, Ph.D. 9 Expires: February, 10, 2005 Rashed Zantout, Ph.D. 10 Ahmad Alkassoum, Ph.D. 11 AbdulRahman Aljadhai Ph.D. 12 Yasir El Ameen 13 Sameh Nouh 14 Sami Taieb Alasmaa 15 September, 8, 2004 17 By submitting this Internet-Draft, each author represents 18 that any applicable patent or other IPR claims of which he 19 or she is aware have been or will be disclosed, and any of 20 which he or she becomes aware will be disclosed, in 21 accordance with Section 6 of BCP 79. 23 Internationalized Domain Names Registration and 24 Administration Guidelines for Arabic Characters Group of 25 Languages (Arabic, Persian, Urdu,...) 27 Status of this Memo: 29 This document is an Internet-Draft and is in full conformance 30 with all provisions of Section 10 of RFC2026 except that the right 31 to produce derivative works is not granted. 33 Internet-Drafts are working documents of the Internet 34 Engineering Task Force (IETF), its areas, and its working groups. 35 Note that other groups may also distribute working documents as 36 Internet-Drafts. 38 Internet-Drafts are draft documents valid for a maximum of 39 six months and may be updated, replaced, or to be made obsolete by 40 other documents at any time. It is inappropriate to use Internet- 41 Drafts as reference material or to cite them other than as "work in 42 progress." 44 The list of current Internet-Drafts can be accessed at 45 http://www.ietf.org/ietf/1id-abstracts.txt 47 The list of Internet-Draft Shadow Directories can be accessed 48 at: http://www.ietf.org/shadow.html. 50 Abstract: 51 This document provides guidelines for zone administrators(including 52 but not limited to registry operators and registrars), and 53 information for all domain names holders, on the administration of 54 those domain names which contain characters drawn from Arabic 55 Characters Group of Languages. Other language groups are encouraged 56 to develop their own guidelines as needed, based on these guidelines 57 if that is helpful. 59 The document gives basic guidelines for IDN registrars (as it 60 is the case for IETF Document that talks about Japanese, Chinese 61 and Korean domain name registration "RFC 3490"). The document 62 provides also information for owners of IDN that contains Arabic 63 characters on name reservation process. The document does not cover 64 Arabic gTLD or ccTLD problems. 66 Comments on this document can be sent to the authors at 67 arabic-idn-admin@aietf.org. 69 Table of content: 71 0. Pre-Note for ASCII-version of this document.................4 73 1. Introduction................................................4 75 2. Specialty of Arabic Characters Group of languages...........4 77 3. Arabic Domain Names Recommendations.........................5 79 4. Basics of searching for Arabic Domain Names.................7 81 5. Ways of saving an Arabic Domain Name........................7 83 6. Administration framework of Arabic Domain names.............8 85 7. Principles underlying these guidelines......................8 87 8. Registration of IDL.........................................8 89 9. Versioning of the language character variant tables.........9 91 10. Technical Recommendations.................................10 93 11. Full Copyright Statement..................................10 95 12. Security Considerations...................................11 97 13. IANA Considerations.......................................11 99 14. References................................................11 101 15. Terms.....................................................11 103 16. Authors...................................................12 105 0. Pre-Note for ASCII-version of this document 107 In order to make meanings clear, especially in examples used 108 to clarify some ideas, such examples will be written using their 109 Unicode representation according to Unicode Standard 3.0. 111 1. Introduction: 113 Introducing domain names as addresses on the internet added a 114 new vision to the Internet, it made internet addresses easy to 115 remember, and meaningful more than using sequences of numbers that 116 does not mean any thing to their user. Nowadays Internet users are 117 looking forward to surf on the net using more meaningful names in 118 their own language. Such names are called Internationalized Domain 119 Names (IDNs). This demand opened a wide field of research and ideas 120 as wide as the diversity of languages used by the people on the 121 earth. Each of these languages has its own writing and reading 122 rules. This fact threatens the integrity and the stability of 123 Internet, unless we invent a good solution that respects and 124 controls this mixture of rules and cultures and represents it with 125 a unique, robust and easy-to-use way. 127 2. Specialty of Arabic Characters Group of Languages: 129 Arabic language is the official language of 22 countries; it is 130 also used by more than 43 Islamic countries that use Arabic 131 characters and scripts. In other words more than one billion 132 potential users could be interested in Arabic Domain Names. The 133 Arabic language as well as all Arabic Characters Group of Languages 134 (Persian, Urdu, Pashto, ..) has many specialties that have to be 135 considered when specifying any solution for Arabic Domain Names. 136 The main specialties of these languages are summed up in the 137 following: 139 1.2. Scripts are written from right to left. 141 2.2. The shapes of the character change in most cases according 142 to its location in the word. 144 2.3. Characters within the word are mostly conjugated with 145 preceding and succeeding characters. 147 2.4. Some characters does not conjugate with following character. 149 2.5. The structure of the sentence starts from the most general to 150 the more specific (the opposite of the English language) 151 (Internet draft) in Arabic is said:( draft {of} Internet). 153 2.6. Special characters called Tashkeel are used in order to give 154 the right pronunciation for the word which affects the meaning. 155 In other words tashkeel can give one word two or More different 156 meanings. Tashkeel is not a seprate character by itself, 157 but it modifies a normal Arabic character to give it the right 158 pronuciation It has to be noted here that word meaning is mostly 159 known from the context of the sentence or even the phrase in which 160 the word is used. For Internet names these special signs have to 161 be included but their application in the Internet Domain Names 162 could be delayed for the time being. 164 2-7. Correct words are written in a unique way, but the character 165 shaddah (U+0651); which falls under the tashkeel signs and 166 means doubling the letter associated with it; sometimes is 167 implicit in the word and sometimes is written. In these two 168 cases the same word; with or without shaddah; has (often) the 169 same meaning; but in some cases shaddah can change the 170 meaning of the word. So to decide considering or ignoring 171 such character an algorithm has to implemented. 173 2.8. Correct orthographical practices about Hamza associated with 174 or without Alef and Yeh have to be followed. The same applies 175 to Yeh, Heh and Teh Marbuta. 177 3. Arabic Domain Names Recommendations: 179 3.1. Arabic domain names must allow the use of (SPACE) 180 character. This condition is vital, as Arabic characters (as cited 181 above) can be conjugated with each other and have different shapes 182 depending on their position in the word. If we do not allow the 183 space, words that form the ADL will be misread and misunderstood by 184 the users. The use of dash character (-) to separate words is NOT 185 acceptable according to IDNA (RFC-3490) which prevents the use of 186 characters that belong to another language when reserving a name 187 for a certain language, besides the fact that this character is not 188 used in Arabic, giving an odd view of the domain name. 190 3.2. Solving the issue that results form shaddah could be done 191 by an algorithm that generates all possible synonyms that results 192 from the implicit existence of shaddah. Grammatical rules that 193 controls the implicit existence of shaddah do exist. Such procedure 194 will prevent registering the same word that contains shaddah more 195 than once according to the existence or the absence of this 196 implicit shaddah by different individuals. Explicit shaddah which 197 does not come from grammatical rules have to be treated as a 198 character, so the registration system have to consider the 199 existence or the absence of this shaddah as a differentiator 200 between different domain names. 202 3.3. Tashkeel Embodiment [Shadda (U+0651), Fatha (U+064E), Damma 203 (U+064F), Kasra (U+0650) and Superscript Aleph (U+0670)] must be 204 taken in the accredited character table, as it will give the 205 possibility to register one name more than once by using these 206 tashkeel characters with some or all alphabetical characters of a 207 certain name (there are 8 possible usage of tashkeel characters 208 that can be used with every other character). In spite of the need 209 to use these characters for correct Arabic Domain Names, we can 210 postpone using these five characters for future use. So tashkeel 211 characters have to be added to the accepted character set of Arabic 212 Domain Names but they have to be ignored currently in the 213 registration system. Meanwhile registration systems have to equate 214 Alef Maksura (U+0649) with Yeh (U+064A) in their processing 215 preventing registering more than one domain name based on these two 216 characters. 218 3.4. Future standards for Arabic Domain Names have to abide to 219 the specificity of the Arabic characters group of languages, which 220 is also valid for all other language groups. A special attention is 221 drawn to (RFC 3490) which does not allow mixing characters from any 222 group of languages with characters belonging to another group. 224 The above recommendations are valid for Persian, Pashto and Urdu 225 and other languages which use Arabic Characters. 227 4. Basics of searching for Arabic Domain Names: 229 Name variants must be considered when searching an ADL, if any 230 name in an ADL package is the subject of a name resolving query, a 231 positive answer is to be given if the package was reserved (except 232 when using one of that common abbreviations). The resolving system 233 on the client side must not ignore tashkeel for future 234 developments, and it should abide to the rules dealing with 235 shaddah. 237 5. Ways of saving an Arabic Domain Name: 239 5.1. Reservation of an ADL: 241 As it is mentioned above, similarity cases (Name variants) must 242 be considered when reserving an Arabic domain name, all names 243 resulting from the similarity cases must be reserved, this will 244 prevent reserving different Arabic names that actually indicates 245 the same content by different persons. We can use the following 246 steps when reserving an Arabic domain name: 248 IN = IDL to be registered 249 if Is Valid(IN) then 250 Begin 251 For each Name in [Names variants of (IN)] do 252 If Is Valid (Name) Then 253 Reserve Name 254 End If 255 End For 256 End If 258 Where �Is Valid� as some algorithm that verifies if that the name 259 is compliant with the ADLs standards? We will call the ADL variants 260 as ADL package. 262 Registering town, city and country names as well as names bearing 263 pure religious meanings could not be registered as Arabic Domain 264 Names. At the same time the system should not allow registering 265 names having meanings that contradict the culture of the people of 266 the Arabic characters group of languages. The system must also 267 abandon registering linguistically non-correct names. 269 5.2. Activation and deactivation of an ADL: 271 If any name of an ADL package is to be activated or deactivated 272 ALL names within the ADL package must be activated and deactivated 273 at the same time, the administration system must provide some 274 mechanism to insure this process. 276 5.3. Deleting an ADL: 277 All names in an ADL package must be deleted when any name in the 278 package is requested to be deleted. 280 6. Administration framework of Arabic Domain Names: 282 The ADL Administration framework is responsible of affording a 283 mechanism that respects all the previous conditions of dealing with 284 an ADL. 286 7. Principles underlying these guidelines: 288 The previous guidelines must be considered with all Arabic 289 characters group of languages. Registration systems for each 290 language could be separated so that every language has its own 291 registration systems. At the same time coordination between these 292 systems is required to prevent reserving some words that have the 293 same writing in more than one language but may have different 294 meaning in another language. 296 This must not affect the integrity of the Internet, as users of 297 a certain national domain name must be able to use domain names of 298 an other nationality. This can be accomplished by giving each 299 nationality of those who use the same characters a special string 300 as a Nationality Identifier (or NID). This NID will help the ADL 301 resolving system to determine the parameters of the " ToAscii " 302 function (RFC 3490). 304 8. Registration of Arabic ADL: 306 ALL the names contained in an ADL package must be reserved 307 automatically by the reservation system. This will prevent 308 registering ADLs that have the same meaning but written differently 309 by more than one person. 311 9. Versioning of the language character variant tables: 313 It is recommended to use the last version of the UNICODE. Only 314 the following Unicode characters are accepted in Arabic domain 315 names (according to Arabic Language standards). 317 U+0020 SPACE 318 U+0621 ARABIC LETTER HAMZA 319 U+0622 ARABIC LETTER ALEF WITH MADDA 320 U+0623 ARABIC LETTER ALEF WITH HAMZA 321 U+0624 ARABIC LETTER WAW WITH HAMZA 322 U+0625 ARABIC LETTER ALEF WITH HAMZA BELOW 323 U+0626 ARABIC LETTER YEH WITH HAMZA ABOVE 324 U+0627 ARABIC LETTER ALEF 325 U+0628 ARABIC LETTER BEH 326 U+0629 ARABIC LETTER THE MARBUTA 327 U+062A ARABIC LETTER TEH 328 U+062B ARABIC LETTER THEH 329 U+062C ARABIC LETTER JEEM 330 U+062D ARABIC LETTER HAH 331 U+062E ARABIC LETTER KHAH 332 U+062F ARABIC LETTER DAL 333 U+0630 ARABIC LETTER THAL 334 U+0631 ARABIC LETTER REH 335 U+0632 ARABIC LETTER ZAIN 336 U+0633 ARABIC LETTER SEEN 337 U+0634 ARABIC LETTER SHEEN 338 U+0635 ARABIC LETTER SAD 339 U+0636 ARABIC LETTER DAD 340 U+0637 ARABIC LETTER TAH 341 U+0638 ARABIC LETTER ZAH 342 U+0639 ARABIC LETTER AIN 343 U+063A ARABIC LETTER GHAIN 344 U+0641 ARABIC LETTER FEH 345 U+0642 ARABIC LETTER QAF 346 U+0643 ARABIC LETTER KAF 347 U+0644 ARABIC LETTER LAM 348 U+0645 ARABIC LETTER MEEM 349 U+0646 ARABIC LETTER NOON 350 U+0647 ARABIC LETTER HEH 351 U+0648 ARABIC LETTER WAW 352 U+0649 ARABIC LETTER ALEF MAKSURA 353 U+064A ARABIC LETTER YEH 354 U+064E ARABIC FATHA 355 U+064F ARABIC DAMMA 356 U+0650 ARABIC KASRA 357 U+0651 ARABIC SHADDA 358 U+0660 ARABIC-INDIC DIGIT ZERO 359 U+0661 ARABIC-INDIC DIGIT ONE 360 U+0662 ARABIC-INDIC DIGIT TWO 361 U+0663 ARABIC-INDIC DIGIT THREE 362 U+0664 ARABIC-INDIC DIGIT FOUR 363 U+0665 ARABIC-INDIC DIGIT FIVE 364 U+0666 ARABIC-INDIC DIGIT SIX 365 U+0667 ARABIC-INDIC DIGIT SEVEN 366 U+0668 ARABIC-INDIC DIGIT EIGHT 367 U+0669 ARABIC-INDIC DIGIT NINE 368 U+0670 ARABIC LETTER SUPERSCRIPT ALEF 370 10. Technical Recommendations: 372 10.1. The ADL solutions is like any other IDN subject of approved 373 RFCs that speaks about the technical details of the realization of 374 IDNs. A solution must be developed using the IDNA (RFC 3490). This 375 in our opinion is the proper way to keep the integrity of the 376 Internet. The solution has also to take the nameprep standard in 377 consideration. We have to notice that the nameprep standard denies 378 the use of the space in a IDNs, and have to note that such denial 379 is not convenient for the Arabic Languages. As mentioned above 380 using the space as a separator between words is not a negotiable 381 matter (from a lingual point of view), so any development of an ADL 382 solution must provide a reasonable answer that enables ADLs to 383 contain spaces otherwise the solution will not be compliant with 384 the Arabic language organizations recommendations in this field. 386 10.2. The solution must handle the problem of variants that 387 results from the existence of space as a separator, this solution 388 can be achieved by ignoring the absence of space between words 389 where a word ends with a non joint letter. The treatment of those 390 variants must be considered when designing the registration system. 392 10.3. Tashkeel must be ignored only by the registration system, 393 and the layer that provides the ToAscii function. This procedure 394 gives the user the ability to use Tashkeel without affecting the 395 functionality of the IDNA. 397 10.4. The variants resulting from the misuse of hamza with or 398 without Alef and Yeh and incorrect use of Yeh, Heh and Teh Marbuta 399 have to be treated as separate cases. 401 11. Full Copyright Statement: 403 Copyright (C) The Internet Society (2005). 405 This document and the information contained herein 406 are provided on an "AS IS" basis and THE CONTRIBUTOR, THE 407 ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE 408 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 409 ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 410 ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 411 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 412 OR FITNESS FOR A PARTICULAR PURPOSE. 414 This document and translations of it may be copied and furnished to 415 others, and derivative works that comment on or otherwise explain it 416 or assist in its implementation may be prepared, copied, published 417 and distributed, in whole or in part, without restriction of any 418 kind, provided that the above copyright notice and this paragraph are 419 included on all such copies and derivative works. However, this 420 document itself may not be modified in any way, such as by removing 421 the copyright notice or references to the Internet Society or other 422 Internet organizations, except as needed for the purpose of 423 developing Internet standards in which case the procedures for 424 copyrights defined in the Internet Standards process must be 425 followed, or as required to translate it into languages other than 426 English. 428 The limited permissions granted above are perpetual and will not be 429 revoked by the Internet Society or its successors or assigns. 431 This document is subject to the rights, licenses and restrictions 432 contained in BCP 78, and except as set forth therein, the authors 433 retain all their rights. 435 12. Security Considerations: 437 This memo relates to IETF process, not any particular technology. 438 There are security considerations when adopting any technology, but 439 there are no known issues of security with IETF Contribution rights 440 policies. 442 13. IANA Considerations 444 IANA is expected to create and maintain a registry of algorithm names 445 to be used as "Algorithm Names" as defined in Section 2.3. The 446 initial value should be "HMAC-MD5.SIG-ALG.REG.INT". Algorithm names 447 are text strings encoded using the syntax of a domain name. There is 448 no structure required other than names for different algorithms must 449 be unique when compared as DNS names, i.e., comparison is case 450 insensitive. Note that the initial value mentioned above is not a 451 domain name, and therefore need not be a registered name within the 452 DNS. New algorithms are assigned using the IETF Consensus policy 453 defined in RFC 2434. The algorithm name HMAC-MD5.SIG-ALG.REG.INT 454 looks like a FQDN for historical reasons; future algorithm names are 455 expected to be simple (i.e., single-component) names. 457 14. References: 459 [RFC3492] 460 Punycode: A Bootstring encoding of Unicode for 461 Internationalized Domain Names in Applications (IDNA) 462 A. Costello 463 Univ. of California, Berkeley 464 Category: Standards Track, March 2003 466 [RFC3491] 467 Nameprep: A Stringprep Profile for Internationalized 468 Domain Names (IDN) 469 P. Hoffman, IMC & VPNC 470 M. Blanchet, Viagenie 471 Category: Standards Track, March 2003 473 [RFC3490] 474 Internationalizing Domain Names in Applications (IDNA) 475 P. Faltstrom, Cisco, Category: Standards Track 476 P. Hoffman, IMC & VPNC, A. Costello, UC Berkeley, March 2003 478 15. Terms: 480 IDN: Internationalized Domain Name. 481 IDNA: Internationalized Domain Name in Application. (RFC 3490) 482 ADL: Arabic Domain Label. 483 Variant: A name that have the same meaning but there exist small 484 differences in the way they are written. 485 ADL package: Group of names resulting from the generation from the 486 variants of an ADL. 487 Nameprep: A Stringprep Profile for Internationalized Domain Names; 488 draft-ietf-idn-nameprep, Feb 2002, Paul Hoffman, Marc Blanchet, 489 work in progress. Punycode: An encoding of Unicode for use with 490 IDNA, draft-ietf-idn-punycode, Feb 2002, Adam M. Costello, 491 work in progress. 493 16. Authors: 495 Rifaah Ekrema: rifaah@aietf.org 496 Founder and Chairman of Arab Information Engineers Task Force. 497 AIETF Organization 498 P.O: 30775 499 Damascus, Syria 500 Phone: +963 93 611087 501 Fax: +963 11 2238490 502 rifaah@aietf.org 504 Mohamed A. Elhamalaway: 505 Computers Engineering Professor in Al-Azhar University, Egypt. 506 Al-Azhar University, Systems & Computers Engineering dept. 507 Cairo, Egypt. 508 Phone: +20 6321465 509 Fax: +20 6377446 510 mhamalwy@yahoo.com 512 Fidaa Jondi: 513 Director of Bunyan Co. For Projects Managements. 514 Nozum Alhausabah Company, 515 Dubai, UAE. 516 Phone: +971 50 6507282 517 fida@hausabah.com 519 Ph.d. Rached Zantout: 520 Coordinator Department of Electrical Engineering, 521 Faculty of Engineering, 522 Hariri Canadian Academy. 523 Beirut, Lebanon 524 Phone: +961 3 842076 525 rached@cyberia.net.lb 527 Ph.d. Ahmed Guessoum: 528 Sharjah University, Sharjah, UAE 529 Phone: +973 50 5190558 530 guessoum@sharjah.ac.ae 532 Ph.D. AbdulRahman Aljadhai: 533 Technical Faculty, Riyadh, KSA 534 phone: +966 1 4529307 535 Mobile: +966 50 4420530 536 asj@linux.org.sa 538 Yasser Hassan Al Ameen: 539 President (Sudan Internet Society). 540 Sudan Internet Society, Khartoum, Sudan 541 Phone: +249 12 391157 542 yassir@isoc.sd 544 Sameh Nouh: 545 Head of Networks department in Damascus University, 546 Networks Department, Damascus University 547 Damascus, Syria 548 Phone: +963 93 469634 549 sameh@damasuniv.shern.net 551 Sami Taieb Alasmaa: 552 Arabic Language Teacher in Africa University. 553 Arabic Department, Khartoum University, 554 Khartoum, Sudan 555 Phone: +249 11 764892 556 Fax: +249 11 764893 557 dartaiebalasma@hotmail.com