Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 8427, "Representing DNS Messages in JSON", July 2018

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: art

---

Errata ID: 5570
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Stéphane Bortzmeyer
Date Reported: 2018-12-07
Held for Document Update by: Benjamin Kaduk
Date Held: 2019-01-25

Section 5.2 says:

"responseMessage": { "ID": 32784, "QR": 1, "AA": 1, "RCODE": 0,
                         "QDCOUNT": 1, "ANCOUNT": 1, "NSCOUNT": 1,

It should say:

"responseMessage": { "ID": 32784, "QR": 1, "AA": 1, "RCODE": 0,
                         "QDCOUNT": 1, "ANCOUNT": 2, "NSCOUNT": 1,

Notes:

ANCOUNT should, IMHO, be 2 and not 1. There are two resource records in the answer section.

True, the RFC explicitely says (section 8, 1st paragraph) that there can be a discrepancy between ANCOUNT and the actual number of records but I doubt this example was meant to illustrate this point.

Report New Errata