IETF Logo Mail Archive

Re: [dnsext] Fwd: New Version Notification - draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt

Matthijs Mekking <matthijs@nlnetlabs.nl> Wed, 24 April 2013 05:55 UTC

Return-Path: <matthijs@nlnetlabs.nl>
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 6E69621F9473 for <dnsext@ietfa.amsl.com>; Tue, 23 Apr 2013 22:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 sEQ2Avvxwrxh for <dnsext@ietfa.amsl.com>; Tue, 23 Apr 2013 22:55:41 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4660721F93AB for <dnsext@ietf.org>; Tue, 23 Apr 2013 22:55:41 -0700 (PDT)
Received: from [IPv6:2001:981:19be:1:8861:3604:3a45:47e3] ([IPv6:2001:981:19be:1:8861:3604:3a45:47e3]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r3O5tbYT087883 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <dnsext@ietf.org>; Wed, 24 Apr 2013 07:55:38 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=nlnetlabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r3O5tbYT087883
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1366782939; bh=CqsUUUDhvREGx8LjGEtlJk7v1fEZxRFOTWDep+y7kd0=; h=Date:From:To:Subject:References:In-Reply-To; b=qEXZ5rEZkEVGAnAJgS+J9gzrQ2JgWeh1L5aBbjxKw4VC6AKUkZ5+PB+dv2WoS6B0g EhEYYCWRePvyROp8Crx5vqEWCVMWNp1h1x5hrtflebSCsRHbxa8EU/3q83dAYNRd/w WVMKgXMY62B2YSvJXqt74VgQoPcM9yhYTKIJZlfk=
Message-ID: <517773D9.9030501@nlnetlabs.nl>
Date: Wed, 24 Apr 2013 07:55:37 +0200
From: Matthijs Mekking <matthijs@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: dnsext@ietf.org
References: <20130423123633.28301.36321.idtracker@ietfa.amsl.com> <4BBCB100-0E28-462F-8557-64ADB97F6E2E@hopcount.ca>
In-Reply-To: <4BBCB100-0E28-462F-8557-64ADB97F6E2E@hopcount.ca>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Wed, 24 Apr 2013 07:55:39 +0200 (CEST)
Subject: Re: [dnsext] Fwd: New Version Notification - draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt
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, 24 Apr 2013 05:55:42 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Joe,

On 04/23/2013 02:46 PM, Joe Abley wrote:
> Hi all,
> 
> I incorporated the text from Michael and Donald, and added text 
> describing the use case that triggered this work (as has been 
> described on this list before).
> 
> Given that these RRTypes, code-points assigned, have been
> implemented as specified by at least one DNS server vendor, I have
> not considered changing the presentation or encoding (or the number
> of) these RRTypes; it seems counter-productive to change the spec
> when there is already running code. I imagine any other related
> specification could proceed on its own merits.

The RRtypes may be implemented, but no such code has been officially
released. Before releasing, the specification should be stable (and if
we did, we would disable it by default and mark it experimental).

Therefore, I do not see this as an argument not to make changes in the
presentation or encoding of the RRtypes. If such changes are made, we
can quite easily adapt the code.

Best regards,
  Matthijs


> 
> If anybody has further suggestions for improvement (of this
> document, not of RFC6895) please let me know.
> 
> 
> Joe
> 
> Begin forwarded message:
> 
>> From: <internet-drafts@ietf.org> Subject: New Version
>> Notification - draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt
>> Date: 23 April 2013 08:36:33 EDT To: <jabley@teksavvy.ca>, 
>> <draft-jabley-dnsext-eui48-eui64-rrtypes@tools.ietf.org>, 
>> <joelja@bogus.com>
>> 
>> 
>> A new version (-03) has been submitted for 
>> draft-jabley-dnsext-eui48-eui64-rrtypes: 
>> http://www.ietf.org/internet-drafts/draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt
>>
>>
>>
>>
>> 
The IETF datatracker page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-jabley-dnsext-eui48-eui64-rrtypes/
>>
>>
>>
>> 
Diff from previous version:
>> http://www.ietf.org/rfcdiff?url2=draft-jabley-dnsext-eui48-eui64-rrtypes-03
>>
>>
>>
>> 
IETF Secretariat.
>> 
> 
> _______________________________________________ dnsext mailing list
>  dnsext@ietf.org https://www.ietf.org/mailman/listinfo/dnsext
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJRd3PZAAoJEA8yVCPsQCW5A8UIAL0EaJBffp2XjsIxS4c3ibKm
z+2wxJESirb5BbKhMMBEIbZ8cLIspOx8Uhk7G+TqVnZlInRdES0YBwY+2ptdIOrB
bKZHOAb601CtHBeYrfVl//JYR1waFQNbErtlpjLUcioNTWbG1Ho/AfCOA4VgMIOS
hQoOP31ZtNjTxlgsTwyS5GDp1KgSrMgHqOGaWfeRj8muBIFdxR3Pik5ktaIIodsN
GoXUHwBebci0ghvoJ4iopAJ8Cw5IrcuiKxh0lO5H9OnUeN2MPs96Mb+chR7GFovC
ZjDhjeiymbO+0nh4+MTp7Fj5FC5tCu48rA2ebCdzQhbvtWWoBu8G/2C9Gp4NCwE=
=Ho5z
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email