RE: DNSEXT WGLC: RFC2536bis and RFC2539bis

Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com> Sun, 25 December 2005 02:06 UTC

From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
Subject: RE: DNSEXT WGLC: RFC2536bis and RFC2539bis
Date: Sat, 24 Dec 2005 21:06:01 -0500
Lines: 28
Mime-Version: 1.0
Content-Type: text/plain
X-From: owner-namedroppers@ops.ietf.org Sun Dec 25 03:14:46 2005
Return-path: <owner-namedroppers@ops.ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0
To: namedroppers@ops.ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
X-Message-ID:
Message-ID: <20140418072120.2560.74234.ARCHIVE@ietfa.amsl.com>

Hi,

To make it easier to review these drafts, I have wdiff'ed them against the RFCs they propose to obsolete. The results are available at http://www.pothole.com/~dee3/. As described below, these are simple update RFCs and I would appreciate people looking at them.

Thanks,
Donald

-----Original Message-----
From: owner-namedroppers@ops.ietf.org [mailto:owner-namedroppers@ops.ietf.org] On Behalf Of Eastlake III Donald-LDE008
Sent: Tuesday, November 08, 2005 9:23 PM
To: namedroppers@ops.ietf.org
Subject: RE: DNSEXT WGLC: RFC2536bis and RFC2539bis

Hi,

As you might guess form the version numbers these drafts have been around for a fairly long time. The previous RFCs were tied to the SIG and KEY RRs only and reference only the old DNSSEC RFCs. The idea is that these updates are part of DNSSEC updating.

As far as I know, there isn't any technical difference between the RDATA format in these drafts and in the RFCs they update.

There is a minor technical addition in draft-ietf-dnsext-rfc2539bis-dhk-06.txt which has an additional pre-defined D-H group taken from IPSEC (and probably there are 1 or more further additional D-H groups specified in IPSEC or other IETF protocols that should be added).

...

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>