[dnsext] Re: [Technical Errata Reported] RFC4398 (2460)

Andrew Sullivan <ajs@shinkuro.com> Mon, 09 August 2010 15:39 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0D013A69CE; Mon, 9 Aug 2010 08:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.94
X-Spam-Level:
X-Spam-Status: No, score=-99.94 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_INFO=1.448, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUdq0zJBvk-Q; Mon, 9 Aug 2010 08:39:16 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id DB1D83A67AE; Mon, 9 Aug 2010 08:39:15 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1OiUOY-000GBN-BG for namedroppers-data0@psg.com; Mon, 09 Aug 2010 15:36:10 +0000
Received: from [208.86.224.201] (helo=mail.yitter.info) by psg.com with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <ajs@shinkuro.com>) id 1OiUOV-000GAp-Hn for namedroppers@ops.ietf.org; Mon, 09 Aug 2010 15:36:07 +0000
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 266081ECB41D; Mon, 9 Aug 2010 15:36:05 +0000 (UTC)
Date: Mon, 09 Aug 2010 11:36:03 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, rdroms.ietf@gmail.com, jari.arkko@piuha.net, ogud@ogud.com, paul@noc4.net, namedroppers@ops.ietf.org
Subject: [dnsext] Re: [Technical Errata Reported] RFC4398 (2460)
Message-ID: <20100809153603.GH47951@shinkuro.com>
References: <20100807204424.80CD6E06B3@rfc-editor.org> <8739upo3zw.fsf@mocca.josefsson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8739upo3zw.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

Thanks for checking this.  The erratum is fine.

On Sun, Aug 08, 2010 at 11:20:03AM +0200, Simon Josefsson wrote:
> Thanks for the report.  It appears correct to me.
> 
> /Simon
> 
> RFC Errata System <rfc-editor@rfc-editor.org> writes:
> 
> > The following errata report has been submitted for RFC4398,
> > "Storing Certificates in the Domain Name System (DNS)".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=4398&eid=2460
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Paul Freeman <paul@noc4.net>
> >
> > Section: 2
> >
> > Original Text
> > -------------
> > 2.  The CERT Resource Record
> >
> >    The CERT resource record (RR) has the structure given below.  Its RR
> >    type code is 37.
> >
> >                        1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
> >    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |             type              |             key tag           |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |   algorithm   |                                               /
> >    +---------------+            certificate or CRL                 /
> >    /                                                               /
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
> >
> > Corrected Text
> > --------------
> > 2.  The CERT Resource Record
> >
> >    The CERT resource record (RR) has the structure given below.  Its RR
> >    type code is 37.
> >
> >                         1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |             type              |             key tag           |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |   algorithm   |                                               /
> >    +---------------+            certificate or CRL                 /
> >    /                                                               /
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
> >
> > Notes
> > -----
> > In Section 2 (The CERT Resource Record) the table describing the wire format of the CERT RR is misaligned in such a way that it could lead to technical ambiguity of field positions within the packet structure.
> >
> > Instructions:
> > -------------
> > This errata is currently posted as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verified or
> > rejected. When a decision is reached, the verifying party (IESG)
> > can log in to change the status and edit the report, if necessary. 
> >
> > --------------------------------------
> > RFC4398 (draft-ietf-dnsext-rfc2538bis-09)
> > --------------------------------------
> > Title               : Storing Certificates in the Domain Name System (DNS)
> > Publication Date    : March 2006
> > Author(s)           : S. Josefsson
> > Category            : PROPOSED STANDARD
> > Source              : DNS Extensions
> > Area                : Internet
> > Stream              : IETF
> > Verifying Party     : IESG

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.