Browse Source

[1579] suggested change for an awkward comment line:

- s/NSEC3PARAMETER/NSEC3PARAM/
- "definitely" is too strong in this context
- add a space after a comma
- "zonefile" is awkward (there's no "zonefile" in this context)
- "NSEC3 method" is an awkward term
- "this zone signature" is also awkward
JINMEI Tatuya 13 years ago
parent
commit
ae40f56b7e
1 changed files with 4 additions and 3 deletions
  1. 4 3
      src/lib/datasrc/database.cc

+ 4 - 3
src/lib/datasrc/database.cc

@@ -907,9 +907,10 @@ DatabaseClient::Finder::findInternal(const Name& name, const RRType& type,
     const FoundRRsets found = getRRsets(name.toText(), final_types,
                                         !is_origin, NULL,
                                         type == RRType::ANY());
-    // verify whether the zonefile is signed by NSEC3 method
-    // If the NSEC3PARAMETER type exists in the zonefile,NSEC3 is definitly used
-    // in this zone signature.
+
+    // If an NSEC3PARAM RR exists at the zone apex, it's quite likely that
+    // the zone is signed with NSEC3.  (If not the zone is more or less broken,
+    // but it's caller's responsibility how to handle such cases).
     bool is_nsec3 = false;
     const FoundRRsets nsec3_found = getRRsets(origin_.toText(),
                                               NSEC3PARAM_TYPES(), false);