Re: [dnsext] draft-diao-aip-dns
Phillip Hallam-Baker <hallam@gmail.com> Fri, 29 June 2012 14:31 UTC
Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A3521F8738; Fri, 29 Jun 2012 07:31:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1340980290; bh=tx5pWd8m+03f21yVf3vZqxYSHrweeNOm5wnJEGwhV/E=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:From:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=GxYcC3wwSIuRgTbxavYyt7deJ/TuCjPYTkbEtq7fOa0H9Ib6Yx4rXd0koCBwZm5WS mQtlDkBQcKNulkDcdzZT8Hw2m3pY4vTDRLeDz1pX0shv0Yp+tQ8h8WK55nEOUYrjtq R2K8D4rpiSVP0DEC28Ow3Wec2Qoz4reNwvn0nvMA=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C71A321F8741 for <dnsext@ietfa.amsl.com>; Fri, 29 Jun 2012 07:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.208
X-Spam-Level:
X-Spam-Status: No, score=-2.208 tagged_above=-999 required=5 tests=[AWL=-1.391, BAYES_05=-1.11, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cYdVCWf-7-ZW for <dnsext@ietfa.amsl.com>; Fri, 29 Jun 2012 07:31:26 -0700 (PDT)
Received: from mail-yw0-f42.google.com (mail-yw0-f42.google.com [209.85.213.42]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6C421F8757 for <dnsext@ietf.org>; Fri, 29 Jun 2012 07:31:22 -0700 (PDT)
Received: by yhfq11 with SMTP id q11so3361478yhf.15 for <dnsext@ietf.org>; Fri, 29 Jun 2012 07:31:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=dvBoknl8/bNDep7jsOuDJ14rGGDl7HE/OgQ6TphJC4Q=; b=ExHMq4Y1ASsDl1kG7rtYXXwjWwjEavVy6IT4pyaJjuTdhyudhB94czAGHTGmps4tFN Dvzk7iyKkperU9IiHujZ7NIKSM2h/+pk4sAH9vNyi8cvygBg7IUWKac5DOSZymanZjjL HB0TCe2UESLeLZJTQjGBx0h8cPDyNckmm+JIbq8yb16mQ2ij6jNNBcmRO9xaAlCJOdfy 8V/n+4k//KxrVA4iUmreYGATjiXiUP4XPTSHPIPWPWZGLFdIeYXPvLfe8XuiF9aZMtl4 SzPJrmcJThoTvpXL0MbVpUcTUYNFsaMNW09M+F2jBwvw9JKrSpjflUjoKsH4kdaKvUPp n8uQ==
MIME-Version: 1.0
Received: by 10.236.76.9 with SMTP id a9mr2931206yhe.96.1340980281990; Fri, 29 Jun 2012 07:31:21 -0700 (PDT)
Received: by 10.147.33.19 with HTTP; Fri, 29 Jun 2012 07:31:21 -0700 (PDT)
In-Reply-To: <B726DEA1-2E57-4E67-B481-5788CB26869E@vpnc.org>
References: <1340433313.43178.YahooMailClassic@web161701.mail.bf1.yahoo.com> <B726DEA1-2E57-4E67-B481-5788CB26869E@vpnc.org>
Date: Fri, 29 Jun 2012 10:31:21 -0400
Message-ID: <CAMm+Lwh1J8+LB44X0XmUm+Fob1bSrdJLY76Vr8qsUx0yeDat+A@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
Cc: DNSEXT Working Group <dnsext@ietf.org>
Subject: Re: [dnsext] draft-diao-aip-dns
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org
Those of us who have been watching the moves by Russia and China for some time, in particular their proposals into the Dubai ITU meeting have been expecting something of the sort for some time. The draft in question is simply describing a capability that the Chinese have had deployed for at least five years, albeit maybe in a different technical form. People have been proposing splitting from ICANN since before there was an ICANN. And when the CEO is being paid close to a million dollars a year and the whole operation is being driven by rent seeking, I think many of the people behind those proposals might be seen as prescient, if not for the fact that many of them were looking to achieve a bit of rent seeking of their own. CABForum is currently looking at the bad things that could happen if .corp is allowed. It turns out that a large number of corporations already use this internally. Now leaving aside the technical considerations, I do not think that CABForum should have to pay $17,000 to make a formal objection on security grounds. Of course Russia and China are going to find plenty of other countries to support their position when the status quo is indefensible. Their other tactic for attracting support is to promise countries that the ITU is going to do something about reclaiming the international telephone calling fees that have been lost as the public telephone system has been effectively disintermediated. At this point a split in the DNS root is more than inevitable, it has already taken place. I would prefer to know how the split is implemented from a technical point of view rather than have to try to work it out. People can fuss over whether this is a good or a bad thing, but the countries that are looking to censor their net to avoid criticism of their regimes are going to be doing that with or without approval here. The IETF can approve the draft and have the state control faction claim that they have IETF endorsement of their scheme or if it is rejected they will use the rejection as 'proof' of the 'need' to develop standards in ITU instead. This is not an unprecedented fight either. There were/are similar fights over MAC address assignments and over barcodes and currently there are similar fights over RFID. The barcode system we use today was created by the Europeans super-setting the US scheme after they found the US organization's terms ridiculous and unacceptable. I think that eventually we will have a flat DNS where everyone is able to register in the root zone at the same cost as present .com domains or at the most the cost of an EV cert and with the same level of reliability, service etc. The whole concept of hierarchical partitioning of the namespace was bogus from the start. RealNames had the right concept but the wrong business model. For any scheme like that to be viable, there has to be an open registration model. Open up the root zone completely and many of the problems created by domain name squatting either go away or are drastically reduced in scope. Eventually the public delegation points outside the root would wither away. companies will not need to get worked up about crooks registering their name in every random TLD that is given a taxi badge by ICANN. -- Website: http://hallambaker.com/ _______________________________________________ dnsext mailing list dnsext@ietf.org https://www.ietf.org/mailman/listinfo/dnsext
- [dnsext] draft-diao-aip-dns Tony Finch
- Re: [dnsext] draft-diao-aip-dns Ondřej Surý
- Re: [dnsext] draft-diao-aip-dns Stephane Bortzmeyer
- Re: [dnsext] draft-diao-aip-dns Eric Brunner-Williams
- Re: [dnsext] draft-diao-aip-dns Ondřej Surý
- [dnsext] draft-diao-aip-dns Fred Baker
- Re: [dnsext] draft-diao-aip-dns Donald Eastlake
- Re: [dnsext] draft-diao-aip-dns Ralph Droms
- Re: [dnsext] draft-diao-aip-dns Mark Andrews
- Re: [dnsext] draft-diao-aip-dns Warren Kumari
- Re: [dnsext] draft-diao-aip-dns Andrew Sullivan
- Re: [dnsext] draft-diao-aip-dns Stephane Bortzmeyer
- Re: [dnsext] draft-diao-aip-dns Ralph Droms
- Re: [dnsext] draft-diao-aip-dns Mark Andrews
- Re: [dnsext] draft-diao-aip-dns SM
- Re: [dnsext] draft-diao-aip-dns Nicholas Weaver
- Re: [dnsext] draft-diao-aip-dns Doug Barton
- Re: [dnsext] draft-diao-aip-dns Ralph Droms
- Re: [dnsext] draft-diao-aip-dns Eric Brunner-Williams
- Re: [dnsext] draft-diao-aip-dns Jiankang YAO
- Re: [dnsext] draft-diao-aip-dns Jiankang YAO
- Re: [dnsext] draft-diao-aip-dns YP Diao
- Re: [dnsext] draft-diao-aip-dns Paul Hoffman
- Re: [dnsext] draft-diao-aip-dns Phil Regnauld
- Re: [dnsext] draft-diao-aip-dns Paul Hoffman
- Re: [dnsext] draft-diao-aip-dns Phillip Hallam-Baker
- Re: [dnsext] draft-diao-aip-dns Dmitry Burkov
- Re: [dnsext] draft-diao-aip-dns Jim Reid
- Re: [dnsext] draft-diao-aip-dns Ralph Droms
- Re: [dnsext] draft-diao-aip-dns Nicholas Weaver
- Re: [dnsext] draft-diao-aip-dns Jim Reid
- Re: [dnsext] draft-diao-aip-dns YP Diao
- [dnsext] "knowing A root key" was Re: draft-diao-… Edward Lewis