IETF Logo Mail Archive

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

Joe Abley <jabley@hopcount.ca> Tue, 23 April 2013 12:46 UTC

Return-Path: <jabley@hopcount.ca>
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 3E9E521F9663 for <dnsext@ietfa.amsl.com>; Tue, 23 Apr 2013 05:46:10 -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 ynXfHbmhLoFh for <dnsext@ietfa.amsl.com>; Tue, 23 Apr 2013 05:46:09 -0700 (PDT)
Received: from mail-da0-x236.google.com (mail-da0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1C121F965E for <dnsext@ietf.org>; Tue, 23 Apr 2013 05:46:09 -0700 (PDT)
Received: by mail-da0-f54.google.com with SMTP id s35so321879dak.41 for <dnsext@ietf.org>; Tue, 23 Apr 2013 05:46:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=x-received:from:content-type:content-transfer-encoding:subject:date :references:to:message-id:mime-version:x-mailer; bh=jwRa3rzgkj4P9rfqPNEo3DHW0hJ0k0o48/VtxgnbiwQ=; b=bPtkaVlN3/82tmATr2s35YGKbyEPLN3PFjl7IGa396NoGKn2mqPfKTW8CLMEuN7YnQ 9R5naqKu5C9B4R7QZpbzaxTI3hyRvAV/RcenaS6IL7vVz7291sG6VSlqiYXfhcaVi/3x L21m4z3GkpcFJgRTpVehfQ8jJ12UBIyUgewho=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:content-type:content-transfer-encoding:subject:date :references:to:message-id:mime-version:x-mailer:x-gm-message-state; bh=jwRa3rzgkj4P9rfqPNEo3DHW0hJ0k0o48/VtxgnbiwQ=; b=KHSHgq9sQrdG8Mi0am8wnw4MIGKZBNoxwMz3dyxrUoR/wy04gfO62KbpG+70cYE5UU WQ8/6PYO8cXbIa5D132+4nZU5O8irKgVrR7myDjoi6pHYXzYZAabSzLjrsFBRM1tqRRo ed1IX9o6VKDLskC1nClU42FZ7+iDLUfRkMe82Nj6KqiiagOIIHFBlxxCwBzxtvi0trXa KoOW6bx2XPtYeODmB8Q0AA/22K2ZYELb8TkVBocjLv20QWnk4xa9fHAiTfNcrXseA4He AISaDqgSPd8U7/3orWsb4aa4Ec9tUNZaIpBwHvuIMvTNGQTXQo+xT2R5m1rWyAzLXJVW 8pXA==
X-Received: by 10.68.177.33 with SMTP id cn1mr6240669pbc.189.1366721168890; Tue, 23 Apr 2013 05:46:08 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:f555:6e68:4ae:fce? ([2001:4900:1042:100:f555:6e68:4ae:fce]) by mx.google.com with ESMTPS id l4sm23907068pbo.6.2013.04.23.05.46.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 23 Apr 2013 05:46:07 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Apr 2013 08:46:03 -0400
References: <20130423123633.28301.36321.idtracker@ietfa.amsl.com>
To: "dnsext@ietf.org Group" <dnsext@ietf.org>
Message-Id: <4BBCB100-0E28-462F-8557-64ADB97F6E2E@hopcount.ca>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQk90wmNzvjsrlRSeAd1WjwO0NmtKI0dzTo9PSQFjxOOHWaDRq8nW8F+SMSYcmoTDVZrJigz
Subject: [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: Tue, 23 Apr 2013 12:46:10 -0000

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.

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.
>

v2.23.0 | Report a Bug | By Email