IETF Logo Mail Archive

Re: [dnsext] a lightweight process for assigning EDNS option codes

"Livingood, Jason" <Jason_Livingood@cable.comcast.com> Wed, 31 August 2011 12:37 UTC

Return-Path: <jason_livingood@cable.comcast.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 6C4FA21F8B31 for <dnsext@ietfa.amsl.com>; Wed, 31 Aug 2011 05:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.706
X-Spam-Level:
X-Spam-Status: No, score=-102.706 tagged_above=-999 required=5 tests=[AWL=-1.271, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 1s2yoSL9ze0L for <dnsext@ietfa.amsl.com>; Wed, 31 Aug 2011 05:37:55 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id D01CB21F8B27 for <dnsext@ietf.org>; Wed, 31 Aug 2011 05:37:54 -0700 (PDT)
Received: from ([24.40.55.42]) by copdcimo01.cable.comcast.com with ESMTP id 5503630.51134156; Wed, 31 Aug 2011 06:45:15 -0600
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%11]) with mapi id 14.01.0289.001; Wed, 31 Aug 2011 08:39:21 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Jim Reid <jim@rfc1035.com>, Colm MacCárthaigh <colm@allcosts.net>
Thread-Topic: [dnsext] a lightweight process for assigning EDNS option codes
Thread-Index: AQHMZ7FlLPjBYtld2EOljN6M0mkcoZU25p6A
Date: Wed, 31 Aug 2011 12:39:21 +0000
Message-ID: <CA83A37B.37F3F%jason_livingood@cable.comcast.com>
In-Reply-To: <E31D7273-A34E-4DEB-A293-FBAFD536C2E3@rfc1035.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.12.0.110505
x-originating-ip: [24.40.55.70]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <836139C6791ECB45A076BD277D0683C7@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dnsext@ietf.org" <dnsext@ietf.org>
Subject: Re: [dnsext] a lightweight process for assigning EDNS option codes
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 12:37:55 -0000

There's always a registration path similar to ENUMservices, a la RFC 6117.
This allows for both an RFC-published path and non-RFC path to
registration. http://tools.ietf.org/html/rfc6117


Jason

On 8/31/11 3:41 AM, "Jim Reid" <jim@rfc1035.com> wrote:

>On 31 Aug 2011, at 04:23, Colm MacCárthaigh wrote:
>
>> How would you feel about proposing more relaxed registry criteria to
>> IANA (by way of an RFC), similar to how the ports registry works?
>
>Sounds like a good idea.
>
>> EDNS0 option codes don't appear to be in much demand, so exhaustion
>> isn't as much of a concern.
>
>A process comparable to the one for RRtype code assignment could take
>care of this. The expert review would provide a sanity check and rate
>limiter in case we started burning through EDNS option codes. What if
>marketroids were to decide these are more valuable for vanity purposes
>than new gTLDs?
>
>It's a pity RFC6195 didn't ring-fence some of the EDNS OPT code (and
>Extended RCODE?) number space for private use and/or experiments just
>like it did for the RRtype, CLASS and RCODE spaces.
>
>_______________________________________________
>dnsext mailing list
>dnsext@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsext

v2.23.0 | Report a Bug | By Email