1 (backward)
( 1 ) (forward) 1
- Returning 127.0.53.53 is potentially dangerous, and my suggestions for an alternative,
Aaron Beck
(Fri Feb 28 05:46:29 2014)
- comments from .SAARLAND,
Alexander Siffrin
(Wed Mar 12 14:17:39 2014)
- 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
(Sat Mar 29 06:34:24 2014)
- CONAC's Comments on JAS's Name Collision Mitigating Plan,
刘丽梅
(Mon Mar 31 04:27:32 2014)
- Verizon - Request for Comments on Mitigating the Risk of DNS Namespace Collisions,
Flaherty, Patrick Martin (Padraic)
(Mon Mar 31 16:51:27 2014)
- Afnic's comments to name collision report,
Pierre Bonis
(Mon Mar 31 17:00:32 2014)
- Valideus comments on Mitigating the Risk of DNS Namespace Collisions,
Ashley Roberts
(Mon Mar 31 17:37:05 2014)
- Public Comment by FairWinds Partners,
Stephanie Duchesneau
(Mon Mar 31 19:12:22 2014)
- United TLD Comment on Mitigating the Risk of DNS Namespace Collisions,
Statton Hammock
(Mon Mar 31 19:14:37 2014)
- Donuts Comment on JAS Name Collision Report,
Mason Cole
(Mon Mar 31 21:01:19 2014)
- NTAG comments on JAS Namespace Collision Report,
Rubens Kuhl
(Mon Mar 31 21:03:21 2014)
- Verisign preliminary comments on "Mitigating the Risk of DNS Namespace Collisions" Phase One Report,
Kaliski, Burt
(Mon Mar 31 21:28:59 2014)
- Uniregistry Comment on Names Collision,
Bret Fausett
(Mon Mar 31 21:30:23 2014)
- Google Registry's Public Comment on Mitigating the Risk of DNS Namespace Collisions,
Sarah Falvey
(Mon Mar 31 22:01:14 2014)
- ARI Registry Services comments on Name Collision,
Donna Austin
(Mon Mar 31 23:51:31 2014)
- ISPCP Public Comments to JAS Report,
Christian Dawson
(Tue Apr 01 04:14:53 2014)
- CNNIC comments on Name Collision,
Ding Yi
(Tue Apr 01 07:09:23 2014)
- ICANN Collisions List,
Hoehne, Claudia
(Fri Apr 11 08:17:37 2014)
- esmt.berlin blocklist explanation,
Andy Gardner
(Tue Apr 15 00:30:32 2014)
- DNS-OARC Comments on JAS Name Collision Report,
Keith Mitchell
(Sun Apr 20 16:47:49 2014)
- Google Registry's Reply to ICANN’s Public Comment on Mitigating the Risk of DNS Namespace Collisions,
Sarah Falvey
(Mon Apr 21 16:45:17 2014)
- Verisign additional comments on "Mitigating the Risk of DNS Namespace Collisions" Phase One Report,
Kaliski, Burt
(Mon Apr 21 21:18:27 2014)
- Reply Comments - NTAG,
Andrew P Merriam
(Mon Apr 21 22:07:06 2014)
- Donuts Reply to Collision Issue,
Mason Cole
(Mon Apr 21 23:54:15 2014)
- .Club Domains Comment on "Mitigating the Risk of DNS Namespace Collisions",
Jonathan Frost
(Tue Apr 22 00:52:13 2014)
- BC Comment on Namespace Collision Mitigation Report,
Steve DelBianco
(Fri Apr 25 16:17:44 2014)
- Report of Public Comments,
Chhun Chy
(Tue Jun 10 21:08:43 2014)
1 (backward)
( 1 ) (forward) 1
Mails in Archive: 29
Mails per page: 60
Archive Updated: 2016 Oct 31 18:02:40 (local time zone is Central European)
|