mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-22 10:10:06 +00:00
Code Issues Releases Wiki Activity

Update BIND 9 Style Guide

Greg Choules 2023-11-11 15:22:47 +00:00
parent ca0601a883
commit af73897f65
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
BIND-9-Style-Guide.md

@ -31,4 +31,16 @@ and Sphinx should automatically find its definition.
* Name server (not nameserver)
* Time-to-live
* RRset (not rrset)
* Failover (not fail-over)
* Failover (not fail-over)
Choules comments
Regarding "namespace" versus "name space". Many places, including IETF documents, RFCs and popular, trusted websites (or is it web sites? ;) ) use both/either almost interchangeably.
RFC 1034, for example, uses "namespace" once but "name space" 30 times. However, in other IETF documents (of which the RFCs are a set) "namespace" appears more often. So basically, go figure! I'd say either could be used, but be consistent. My personal choice would be **namespace**, but then I'm lazy and as it saves a whole character... ;)
Regarding "nameserver" versus "name server". Again, both are used, though "name server" might have the edge. Personally I'd go with **nameserver**.
Regarding "time-to-live" I'm a definite 'no' on hyphens. It's "time to live".
That's all, for now.