Re: [dnsext] afasterinternet.com trial and draft-vandergaast-edns-client-subnet-00
Phillip Hallam-Baker <hallam@gmail.com> Sun, 04 September 2011 03:01 UTC
Return-Path: <hallam@gmail.com>
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 0CBC021F84F6 for <dnsext@ietfa.amsl.com>; Sat, 3 Sep 2011 20:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.453
X-Spam-Level:
X-Spam-Status: No, score=-3.453 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 s3yFrt3nU4mM for <dnsext@ietfa.amsl.com>; Sat, 3 Sep 2011 20:01:39 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id B2C6721F84F5 for <dnsext@ietf.org>; Sat, 3 Sep 2011 20:01:39 -0700 (PDT)
Received: by gyf3 with SMTP id 3so3237456gyf.31 for <dnsext@ietf.org>; Sat, 03 Sep 2011 20:03:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qRtt1hSLx68rnPR0xuViVF7rIm/bY3YCAY2hc9lqmD0=; b=nfjFpeWF0a61k6r8JxDCWE6EJYkHMnfpp+E96V8L5rWa5V8YK6LK1+R/WEveAZ1Sc3 Jxk11e39ilzLg59Kd13Q81lXykRs5536RF4Ug4r9KvgwFE92vQPMA4W9PEfRg1tBiRpU FbuWjFwe5k86rRr9jt6HTyZJyhPVoyjGZAoHg=
MIME-Version: 1.0
Received: by 10.101.131.4 with SMTP id i4mr1855774ann.61.1315105397677; Sat, 03 Sep 2011 20:03:17 -0700 (PDT)
Received: by 10.100.47.4 with HTTP; Sat, 3 Sep 2011 20:03:17 -0700 (PDT)
In-Reply-To: <20110831114728.GA99123@shinkuro.com>
References: <20110830162134.GB84494@shinkuro.com> <CAMbvoa+nh5k8eOA-XRwBD5oxm17+=Q4gCagq0OBS5OEQX=g1sw@mail.gmail.com> <20110831031256.GA98758@shinkuro.com> <CAAF6GDfA3+A+fJz2TY+Jg5WcVWkpAdR8n-4tXMC+zQYe9aGYpw@mail.gmail.com> <20110831114728.GA99123@shinkuro.com>
Date: Sat, 03 Sep 2011 23:03:17 -0400
Message-ID: <CAMm+LwiEvwqA4=aCNacGe32Dm3OVSFBH92g_mT+pjWwX3vAtfg@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary="001636c92a3f12204104ac14d6d6"
Cc: dnsext@ietf.org
Subject: Re: [dnsext] afasterinternet.com trial and draft-vandergaast-edns-client-subnet-00
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>
X-List-Received-Date: Sun, 04 Sep 2011 03:01:41 -0000
It occurs to me that this thread demonstrates that a Standard is NOT required. Nor has it ever been. Anyone who wants to can choose any code point and use it. If they have enough market presence they can make sure that nobody else wants that same code point. I do not agree with the need for a private use space. Private use just means that each experiment will burn a minimum of one code point and if successful will burn a second plue require a transition. We have been there with X-headers. They didn't really work. One of the problems with the DNS area is that there are far too many people who think that they have a veto point on the Internet and that is just not true (thank the deity). I am not trying to pick on the DNS area, just point out that it is not only governments who regard it as a chokepoint and thus the subject matter inevitably attracts people who think that it is their mission in life to protect the Internet from making the mistakes that they in their wisdom are uniquely capable of recognizing. I am willing to follow a process if an assignment process gives me a reasonable chance of getting an assignment on a reasonable schedule. By which I mean a small number of months as for RR code points. But do not be mistaken: I am not recognizing a right of veto by doing so. If the barrier is Standard required then I am simply going to tell people the number I have picked. I didn't get to vote for anyone involved so they should not exactly be surprised if I don't recognize their right to a veto. Some of you know the political sympathies that got me involved in the Internet in the first place: I believe in democracy. Do not be at all surprised if my lack of tolerance for unaccountable decisions is not limited to those of dictators and autocrats. A consensus based approach can be appropriate if the remit of an organization is limited to finding out what we can agree to do together. It is not acceptable if the organization is going to presume to claim veto power over what they do when agreement is not reached. We have a similar situation with SRV prefixes which for various reasons have not been properly tracked for the past ten years. Each time there are proposals to rationalize the prefix registry people pull out absurd technical and logistical issues until the enthusiasm for the proposal is beaten into submission and lies bleeding and battered but not quite dead for the next few years. In the meantime every protocol designer who believes inthe SRV approach just does what I have done in W3C and OASIS standards and writes the stupid code points into the spec. There, done. On Wed, Aug 31, 2011 at 7:47 AM, Andrew Sullivan <ajs@anvilwalrusden.com>wrote: > On Tue, Aug 30, 2011 at 08:23:51PM -0700, Colm MacCárthaigh wrote: > > On Tue, Aug 30, 2011 at 8:12 PM, Andrew Sullivan <ajs@anvilwalrusden.com> > wrote: > > > I actually don't care about the IETF process. What I do care about is > > > the potential for interoperability headaches later because of > > > undocumented collisions in EDNS0 option code interpretation. Avoiding > > > that sort of headache is the exact reason we have a registry. > > > > How would you feel about proposing more relaxed registry criteria to > > IANA (by way of an RFC), similar to how the ports registry works? > > In my personal, no-hat opinion, the registry rule could be made > first-come, first-served until (say) 50% of the code space was used > up. I see no reason not to do this. > > The current edns0-bis draft actually moves things in the opposite > direction: whereas now the rule is RFC Required, the current draft > makes things Standards Action. In my opinion (again no hat), this is > the wrong direction to be moving. > > > EDNS0 option codes don't appear to be in much demand, so exhaustion > > isn't as much of a concern. > > Right. And we could solve that worry by making the relaxed rule > automatically tighten after a certain number of the codes are gone > anyway, just the way we did for the DNSSEC algorithm numbers. > > A > > -- > Andrew Sullivan > ajs@anvilwalrusden.com > _______________________________________________ > dnsext mailing list > dnsext@ietf.org > https://www.ietf.org/mailman/listinfo/dnsext > -- Website: http://hallambaker.com/
- [dnsext] afasterinternet.com trial and draft-vand… Andrew Sullivan
- Re: [dnsext] afasterinternet.com trial and draft-… Wilmer van der Gaast
- Re: [dnsext] afasterinternet.com trial and draft-… Alex Bligh
- Re: [dnsext] afasterinternet.com trial and draft-… Colm MacCárthaigh
- Re: [dnsext] afasterinternet.com trial and draft-… Andrew Sullivan
- Re: [dnsext] afasterinternet.com trial and draft-… Colm MacCárthaigh
- Re: [dnsext] afasterinternet.com trial and draft-… Matthew Dempsky
- Re: [dnsext] afasterinternet.com trial and draft-… Matt McCutchen
- Re: [dnsext] afasterinternet.com trial and draft-… Alex Bligh
- Re: [dnsext] afasterinternet.com trial and draft-… Alex Bligh
- [dnsext] a lightweight process for assigning EDNS… Jim Reid
- Re: [dnsext] afasterinternet.com trial and draft-… SM
- Re: [dnsext] afasterinternet.com trial and draft-… Andrew Sullivan
- Re: [dnsext] a lightweight process for assigning … Livingood, Jason
- Re: [dnsext] afasterinternet.com trial and draft-… Wilmer van der Gaast
- Re: [dnsext] afasterinternet.com trial and draft-… Wilmer van der Gaast
- Re: [dnsext] afasterinternet.com trial and draft-… Andrew Sullivan
- Re: [dnsext] afasterinternet.com trial and draft-… Wilmer van der Gaast
- Re: [dnsext] afasterinternet.com trial and draft-… Ted Hardie
- Re: [dnsext] afasterinternet.com trial and draft-… Ted Hardie
- Re: [dnsext] afasterinternet.com trial and draft-… Andrew Sullivan
- Re: [dnsext] afasterinternet.com trial and draft-… Andrew Sullivan
- Re: [dnsext] afasterinternet.com trial and draft-… Ted Hardie
- Re: [dnsext] afasterinternet.com trial and draft-… Andrew Sullivan
- Re: [dnsext] afasterinternet.com trial and draft-… Masataka Ohta
- Re: [dnsext] afasterinternet.com trial and draft-… Alex Bligh
- Re: [dnsext] afasterinternet.com trial and draft-… Marc Lampo
- Re: [dnsext] afasterinternet.com trial and draft-… Tony Finch
- Re: [dnsext] afasterinternet.com trial and draft-… Jaidev Sridhar
- Re: [dnsext] afasterinternet.com trial and draft-… Phillip Hallam-Baker
- Re: [dnsext] a lightweight process for assigning … Phillip Hallam-Baker
- Re: [dnsext] a lightweight process for assigning … Nicholas Weaver
- Re: [dnsext] a lightweight process for assigning … Phillip Hallam-Baker
- Re: [dnsext] afasterinternet.com trial and draft-… Wilmer van der Gaast
- Re: [dnsext] afasterinternet.com trial and draft-… Wilmer van der Gaast
- Re: [dnsext] afasterinternet.com trial and draft-… SM
- Re: [dnsext] afasterinternet.com trial and draft-… Martin Barry
- [dnsext] Address privacy (was Re: afasterinternet… Masataka Ohta
- Re: [dnsext] afasterinternet.com trial and draft-… Marc Lampo
- Re: [dnsext] afasterinternet.com trial and draft-… Tony Finch
- Re: [dnsext] afasterinternet.com trial and draft-… Florian Weimer
- Re: [dnsext] afasterinternet.com trial and draft-… Edward Lewis
- Re: [dnsext] Address privacy (was Re: afasterinte… SM
- Re: [dnsext] afasterinternet.com trial and draft-… Ted Hardie
- Re: [dnsext] afasterinternet.com trial and draft-… Ted Hardie
- Re: [dnsext] afasterinternet.com trial and draft-… Nicholas Weaver
- Re: [dnsext] afasterinternet.com trial and draft-… Nicholas Weaver
- Re: [dnsext] afasterinternet.com trial and draft-… Ted Hardie
- Re: [dnsext] afasterinternet.com trial and draft-… Nicholas Weaver
- Re: [dnsext] afasterinternet.com trial and draft-… Ted Hardie
- Re: [dnsext] afasterinternet.com trial and draft-… Martin Barry
- Re: [dnsext] afasterinternet.com trial and draft-… bmanning
- Re: [dnsext] afasterinternet.com trial and draft-… Phillip Hallam-Baker
- Re: [dnsext] Address privacy (was Re: afasterinte… Masataka Ohta
- Re: [dnsext] afasterinternet.com trial and draft-… Wilmer van der Gaast
- Re: [dnsext] Address privacy (was Re: afasterinte… SM