You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 2, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 2, 2026. It is now read-only.
Consider consolidating subsections for each Resource Record definition #6
Sections 5, 6, and 7, defining the NSEC5KEY, NSEC5, and NSEC5PROOF RRs respectively, could be tightened up by not using subsections for wire format and presentation format. Of course, each record would still have its own section.
The subsections break up the flow and, while convenient for external references, are also not really long enough that someone following an external reference that intended to focus on, say, presentation format, would have trouble finding what they were looking for in each consolidated section.
Relatedly, typographically it is kind of weird that lines like "The presentation format of the NSEC5 RDATA is as follows:" end in a colon that introduces paragraphs. I'd make them some kind of list, probably definition lists.
Activity
vttale commentedon Mar 7, 2017
Relatedly, typographically it is kind of weird that lines like "The presentation format of the NSEC5 RDATA is as follows:" end in a colon that introduces paragraphs. I'd make them some kind of list, probably definition lists.