ICANN Email Archives: [comments-name-collision-26feb14]

ICANN

[comments-name-collision-26feb14] Chronological Index

Thread Index

1 (backward) ( 1 ) (forward) 1

2014 Jun 10
- Report of Public Comments Chhun Chy
2014 Apr 25
- BC Comment on Namespace Collision Mitigation Report Steve DelBianco
2014 Apr 22
- .Club Domains Comment on "Mitigating the Risk of DNS Namespace Collisions" Jonathan Frost
2014 Apr 21
- Donuts Reply to Collision Issue Mason Cole
- Reply Comments - NTAG Andrew P Merriam
- Verisign additional comments on "Mitigating the Risk of DNS Namespace Collisions" Phase One Report Kaliski, Burt
- Google Registry's Reply to ICANN’s Public Comment on Mitigating the Risk of DNS Namespace Collisions Sarah Falvey
2014 Apr 20
- DNS-OARC Comments on JAS Name Collision Report Keith Mitchell
2014 Apr 15
- esmt.berlin blocklist explanation Andy Gardner
2014 Apr 11
- ICANN Collisions List Hoehne, Claudia
2014 Apr 02
- Verizon - Request for Comments on Mitigating the Risk of DNS Namespace Collisions Flaherty, Patrick Martin (Padraic)
2014 Apr 01
- CNNIC comments on Name Collision Ding Yi
- ISPCP Public Comments to JAS Report Christian Dawson
2014 Mar 31
- ARI Registry Services comments on Name Collision Donna Austin
- Google Registry's Public Comment on Mitigating the Risk of DNS Namespace Collisions Sarah Falvey
- Uniregistry Comment on Names Collision Bret Fausett
- Verisign preliminary comments on "Mitigating the Risk of DNS Namespace Collisions" Phase One Report Kaliski, Burt
- NTAG comments on JAS Namespace Collision Report Rubens Kuhl
- Donuts Comment on JAS Name Collision Report Mason Cole
- United TLD Comment on Mitigating the Risk of DNS Namespace Collisions Statton Hammock
- Public Comment by FairWinds Partners Stephanie Duchesneau
- Valideus comments on Mitigating the Risk of DNS Namespace Collisions Ashley Roberts
- Afnic's comments to name collision report Pierre Bonis
- Verizon - Request for Comments on Mitigating the Risk of DNS Namespace Collisions Flaherty, Patrick Martin (Padraic)
- CONAC's Comments on JAS's Name Collision Mitigating Plan 刘丽梅
2014 Mar 29
- If the IPv4 answer is 127.0.53.53 then what is the IPv6 answer? - While trivial; the lack of IPv6 support is something to consider Martin J. Levy
2014 Mar 28
- Re: Returning 127.0.53.53 is potentially dangerous, and my suggestions for an alternative Jason A Fesler
2014 Mar 12
- comments from .SAARLAND Alexander Siffrin
2014 Feb 28
- Returning 127.0.53.53 is potentially dangerous, and my suggestions for an alternative Aaron Beck

1 (backward) ( 1 ) (forward) 1

Mails in Archive: 29
Mails per page: 60
Archive Last Updated: 2016 Oct 31 18:02:40 (UTC)

Privacy Policy | Terms of Service | Cookies Policy