name-collision-02aug13-en

More documents

Recommendations

Info

Rank TLD Existing TLD Proposed TLD Potential TLD 40 cc 86,001 41 ua 82,335 42 es 80,213 43 tr 69,257 44 invalid 66,675 45 co 65,951 46 se 64,724 47 id 62,117 48 novalocal 60,370 49 cz 58,249 50 ro 54,482 51 vn 53,066 52 homestation 52,258 53 null 50,080 54 gr 48,422 55 kg 48,403 56 loc 48,205 57 private 47,384 58 arris 46,763 59 ch 45,822 60 mx 45,453 61 ar 45,360 62 hk 43,821 63 notinuse 43,121 64 intra 42,085 65 za 41,839 66 bind 41,699 67 be 38,607 68 gprs 38,113 69 nz 35,987 70 dk 35,620 71 dom 35,102 72 il 34,826 73 sg 32,674 74 pt 29,863 75 no 29,444 76 hu 28,975 77 cl 28,900 78 mil 28,766 Name Collision Study Report Page 26 Version 1.5 2013.08.02
Rank TLD Existing TLD Proposed TLD Potential TLD 79 html 28,478 80 sys 27,724 81 my 25,482 82 sk 25,063 83 th 24,497 84 fi 24,366 85 tendaap 24,171 86 gateway 23,917 87 none 23,213 88 ws 22,178 89 ph 21,451 90 actdsltmp 21,152 91 server 20,674 92 pri 20,624 93 su 19,963 94 intranet 19,907 95 ice 19,825 96 pvt 19,633 97 lt 19,482 98 la 19,226 99 minihub 19,187 100 asus 18,873 Table 3—Number of existing, proposed, and potential TLD strings in TLD position (2013) This list includes 3 proposed TLDs. Name Collision Study Report Page 27 Version 1.5 2013.08.02
Page 1 and 2: Name Collision in the DNS A study o
Page 3 and 4: necessary to definitively establish
Page 5 and 6: Contents Executive Summary ........
Page 7 and 8: 9.4.3 Residual risk................
Page 9 and 10: 1 Introduction A name that is prope
Page 11 and 12: How widespread is the use of intern
Page 13 and 14: The root zone contains pointers dow
Page 15 and 16: indistinguishable, and few user int
Page 17 and 18: On 28 May 2013 ICANN announced 12 t
Page 19 and 20: Processing of the DITL data was car
Page 21 and 22: 4 Name collision potential The key
Page 23 and 24: Rank String Count (thousands) 24 re
Page 25: Rank TLD Existing TLD Proposed TLD
Page 29 and 30: Rank 2012 2013 Change Proposed TLD
Page 31 and 32: Rank 2012 2013 Change Proposed TLD
Page 33 and 34: Rank String Count (thousands) Prefi
Page 35 and 36: For most of the proposed TLDs for w
Page 37 and 38: Total a c e f h i j k l m star 12 1
Page 39 and 40: Resolver rank DITL2103 rank TLD Exi
Page 41 and 42: Resolver rank DITL2103 rank TLD Exi
Page 43 and 44: 4.3.3 Weighting of resolver traffic
Page 45 and 46: 5 Name collision etiology The scope
Page 47 and 48: Proposed TLD usage all a-root c-roo
Page 49 and 50: Apparently the Google Chrome browse
Page 51 and 52: _sipinternaltls._tcp. _sipfederatio
Page 53 and 54: 6.1.1 Name lookup ambiguity Suppose
Page 55 and 56: 6.1.3 Non-query DNS traffic Althoug
Page 57 and 58: when local policy was to validate a
Page 59 and 60: signed, the relying party can confi
Page 61 and 62: significantly extend the range or s
Page 63 and 64: that the CA’s cert is distributed
Page 65 and 66: implications when certs are utilize
Page 67 and 68: credentials, perhaps as a prelude t
Page 69 and 70: Assuming that a comprehensive risk/
Page 71 and 72: Proposed TLD A AAAA MX PTR SRV TXT
Page 73 and 74: Proposed TLD A AAAA MX PTR SRV TXT
Page 75 and 76: Mozilla organization, and a survey
Page 77 and 78:
8 Name collision risk assessment Ri
Page 79 and 80:
8.3 Risk assessment framework The r
Page 81 and 82:
For example, this report (and other
Page 83 and 84:
The gradient plotted in Figure 4 is
Page 85 and 86:
9.1.1 Advantages A permanently rese
Page 87 and 88:
9.4 Look before you leap Verisign [
Page 89 and 90:
10 References [1] Invalid Top Level
Page 91 and 92:
Appendix A—Complete 2012 Counts T
Page 93 and 94:
Rank Proposed TLD As TLD As SLD At
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
25 169 sap 1,735 18,189 556 20,480
Page 137 and 138:
95 124 bom 251 64 348 663 96 50 ibm
Page 139 and 140:
165 115 moe 110 179 391 680 166 145
Page 141 and 142:
235 182 space 62 571 108 742 236 17
Page 143 and 144:
305 320 cool 44 21 55 120 306 436 i
Page 145 and 146:
375 404 lat 31 37 116 183 376 329 g
Page 147 and 148:
445 416 ping 22 46 704 772 446 377
Page 149 and 150:
515 619 ira 16 21 74 110 516 449 ri
Page 151 and 152:
585 594 financial 11 61 9 81 586 59
Page 153 and 154:
655 514 agency 8 58 154 220 656 450
Page 155 and 156:
725 714 chloe 6 3 5 14 726 894 reis
Page 157 and 158:
795 745 realty 4 21 90 115 796 803
Page 159 and 160:
865 923 banque 3 2 9 14 866 1015 fe
Page 161 and 162:
935 870 jmp 2 30 7 40 936 987 montb
Page 163 and 164:
1005 1025 tatar 1 10 5 16 1006 973
Page 165 and 166:
1075 1161 mutuelle 1 4 1 6 1076 976
Page 167 and 168:
1145 1169 lancome 0 2 5 7 1146 1186
Page 169 and 170:
1215 1256 xn--ngbc5azd 0 0 0 0 1216
Page 171 and 172:
1285 1267 kyknet 0 0 0 0 1286 1325
Page 173 and 174:
1355 n/a allfinanzberatung 0 0 0 0
Page 175 and 176:
Appendix C—Internal Name Certific
Page 177 and 178:
Proposed TLD 2013 2014 2015 2016 20
Page 179 and 180:
Proposed TLD 2013 2014 2015 2016 20
Page 181 and 182:
Appendix E—Top 25 by Root Server
Page 183 and 184:
Appendix G—SLD is an Existing TLD
Page 185 and 186:
Appendix I—TLD and SLD are both a
Page 187 and 188:
Appendix K—QNAME is www.ProposedT
Page 189 and 190:
Appendix M—LDAP and Kerberos name
Page 191 and 192:
Appendix O—_dns-sd DNS names (201
Page 193 and 194:
ice link google red mail smart worl
Page 195 and 196:
star mail ltd google sap app world
Page 197:
Appendix S—10-character SLD with
show all

name-collision-02aug13-en

Create successful ePaper yourself

Delete template?

Save as template?