adulau/pdns-qof
1
0
Fork 0
mirror of https://github.com/adulau/pdns-qof.git synced 2024-10-06 06:21:41 +00:00
Code Issues Projects Releases Packages Wiki Activity

typos

Browse source
This commit is contained in:
Aaron Kaplan 2013-12-25 15:53:35 +01:00
parent 3199474826
commit 4c9db947d9
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
i-d/pdns-qof.txt
View file

@ -157,7 +157,7 @@ Internet-Draft Passive DNS - Common Output Format December 2013
DNS Database from cache poisoning attacks [CACHEPOISONING]. Another DNS Database from cache poisoning attacks [CACHEPOISONING]. Another
limitiation that clients querying the database need to be aware of is limitiation that clients querying the database need to be aware of is
that each query simply gets an snapshot-answer of the time of that each query simply gets an snapshot-answer of the time of
querying. Clients MUST NOT rely on consistent answers. Not must querying. Clients MUST NOT rely on consistent answers. Nor must
they assume that answers must be identical across multiple Passive they assume that answers must be identical across multiple Passive
DNS Servers. DNS Servers.
@ -178,8 +178,8 @@ Internet-Draft Passive DNS - Common Output Format December 2013
3.1. Overview and Example 3.1. Overview and Example
The intent of this output format is to be easily parseable by The intent of this output format is to be easily parsable by scripts.
scripts. Every implementation MUST support the JSON output format. Every implementation MUST support the JSON output format.
A sample output using the JSON format: A sample output using the JSON format:

2
i-d/pdns-qof.xml
View file

@ -166,7 +166,7 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
<section title="Common Output Format"> <section title="Common Output Format">
<t>The formatting of the answer follows the <xref target="RFC4627">JSON</xref> format. The order of the fields is not significant for the same resource type. That means, the same name tuple plus timing information identifies a unique answer per server.</t> <t>The formatting of the answer follows the <xref target="RFC4627">JSON</xref> format. The order of the fields is not significant for the same resource type. That means, the same name tuple plus timing information identifies a unique answer per server.</t>
<section title="Overview and Example"> <section title="Overview and Example">
<t>The intent of this output format is to be easily parseable by scripts. Every implementation MUST support the JSON output format.</t> <t>The intent of this output format is to be easily parsable by scripts. Every implementation MUST support the JSON output format.</t> <!-- note: it is "parsable" if you want to be really nit-picking. See: https://en.wiktionary.org/wiki/parsable -->
<figure><preamble>A sample output using the JSON format:</preamble><artwork><![CDATA[ <figure><preamble>A sample output using the JSON format:</preamble><artwork><![CDATA[
... (list of )... ... (list of )...
{ "count": 97167, { "count": 97167,