Subject: [dnsext] [Errata Rejected] RFC6840 (4191)

From: RFC Errata System <[email-masked]>
Date: Mon, 12 Jan 2015 05:25:32 -0800 (PST)

The following errata report has been rejected for RFC6840,
"Clarifications and Implementation Notes for DNS Security (DNSSEC)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6840&eid=4191

--------------------------------------
Status: Rejected
Type: Editorial

Reported by: Edward Lewis <[email-masked]>
Date Reported: 2014-12-02
Rejected by: Brian Haberman (IESG)

Section: 5.11

Original Text
-------------
...

A signed zone MUST include a DNSKEY for each algorithm present in
      the zone's DS RRset and expected trust anchors for the zone.  The
      zone MUST also be signed with each algorithm (though not each key)
      present in the DNSKEY RRset.  

Corrected Text
--------------
A signed zone MUST include a DNSKEY for each algorithm present in
      the zone's DS RRset and expected trust anchors for the zone.  Each
      authoritative RRset in the zone MUST be signed with each 
      algorithm (though not each key) present in the DNSKEY RRset.  

Notes
-----
Zones aren't signed (per se), the data sets within them are.  But not cut point (NS) and glue.
 --VERIFIER NOTES-- 
 This erratum is being rejected as the nomenclature being updated is understood within the community and is used in other DNSSEC specifications.  

--------------------------------------
RFC6840 (draft-ietf-dnsext-dnssec-bis-updates-20)
--------------------------------------
Title               : Clarifications and Implementation Notes for DNS Security (DNSSEC)
Publication Date    : February 2013
Author(s)           : S. Weiler, Ed., D. Blacka, Ed.
Category            : PROPOSED STANDARD
Source              : DNS Extensions
Area                : Internet
Stream              : IETF
Verifying Party     : IESG