Re: [dnsext] afasterinternet.com trial and draft-vandergaast-edns-client-subnet-00

Ted Hardie <ted.ietf@gmail.com> Wed, 31 August 2011 15:58 UTC

Return-Path: <ted.ietf@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 0C92621F8CAE for <dnsext@ietfa.amsl.com>; Wed, 31 Aug 2011 08:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 fUDC58kjkVC7 for <dnsext@ietfa.amsl.com>; Wed, 31 Aug 2011 08:58:37 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5774C21F877F for <dnsext@ietf.org>; Wed, 31 Aug 2011 08:58:37 -0700 (PDT)
Received: by gwb20 with SMTP id 20so223585gwb.31 for <dnsext@ietf.org>; Wed, 31 Aug 2011 09:00:07 -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:content-transfer-encoding; bh=Iefa8oHBx8Ha87bDf0RwmlN5i1tCTTziHbGadRARm7M=; b=e2thylrTdwjjqdb2bjMhIciU6FmHXfsFcmvxyeQz2WNJ3sHbLDRMZSeBsSeooOBIC/ 18Oum/kPn6ds2XV1WrqRkXK7PZpV72nc1usf4S10Vxzs2K4+UBGwQADlUzCeQkrrISNJ 2oNkVyXKkOwQarMKc+h7IC4SITkKiQ27KjL2M=
MIME-Version: 1.0
Received: by 10.236.183.164 with SMTP id q24mr2981928yhm.117.1314806407798; Wed, 31 Aug 2011 09:00:07 -0700 (PDT)
Received: by 10.236.110.174 with HTTP; Wed, 31 Aug 2011 09:00:07 -0700 (PDT)
In-Reply-To: <20110831142557.GB99260@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> <CAMbvoa+Y7JByefPxYEnDH3WVDuK3CdVfyo2kgqNXHuG_W4M7VA@mail.gmail.com> <20110831142557.GB99260@shinkuro.com>
Date: Wed, 31 Aug 2011 09:00:07 -0700
Message-ID: <CA+9kkMCvqxh5sD3YHuhHZN9N-8_zx57FquoPamcGNdJL2d7VCA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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: Wed, 31 Aug 2011 15:58:38 -0000

On Wed, Aug 31, 2011 at 7:25 AM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> On Wed, Aug 31, 2011 at 02:43:59PM +0100, Wilmer van der Gaast wrote:
>
>> Which draft are you reading here exactly?
>
>>
>> For a new option code, only expert review will be required: "Expert
>> Review is required for allocation of an EDNS Option Code."
>
> Oh, phew, and stupid me.  I was really really surprised when I
> (thought I) saw what I did when I checked it earlier.  That'll teach
> me to do such readings in a hurry.
>
> You're quite right.  And (again no hat) expert review is, IMO, better
> than RFC required, but I'd still prefer FCFS.
>
> A
>

I think FCFS works fine for unbounded spaces, but I'm nervous about
a blended model where there are easy registrations up until exhaustion
looks likely, then
it gets restricted.  We have lots of evidence that this causes grumpiness
in the IP allocation side of the house. Expert review, with clear
instructions to reviewer
(e.g. that this is not duplicate functionality) seems more likely to
get what you want.

The trick is in the clear instructions to the reviewer, especially
when the reviewer
is actually a list with changing membership....

regards,

TEd