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

minor changes

Browse source
This commit is contained in:
Aaron Kaplan 2013-04-02 17:40:28 +02:00
parent 7973c9dff3
commit 2e196fca5f
1 changed files with 1 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -205,7 +205,7 @@ The document does not describe the protocol (e.g. whois, HTTP REST or XMPP) used
<section title="bailiwick"> <section title="bailiwick">
<t>The bailiwick is the best estimate of the apex of the zone where this data is authoritative. String.</t> <t>The bailiwick is the best estimate of the apex of the zone where this data is authoritative. String.</t>
</section> </section>
</section> </section>
<section title="Additional Fields"> <section title="Additional Fields">
<t>Implementations MAY support the following fields:</t> <t>Implementations MAY support the following fields:</t>
<section title="x-sensor_id"> <section title="x-sensor_id">
@ -214,10 +214,6 @@ The document does not describe the protocol (e.g. whois, HTTP REST or XMPP) used
</section> </section>
<section title="Extended Fields">
<t>An x- prefixed key means that is an extension and a non-standard field defined by the implementation of the passive DNS.</t>
</section>
<!-- This PI places the pagebreak correctly (before the section title) in the text output. --> <!-- This PI places the pagebreak correctly (before the section title) in the text output. -->
<?rfc needLines="8" ?> <?rfc needLines="8" ?>
@ -238,9 +234,6 @@ The document does not describe the protocol (e.g. whois, HTTP REST or XMPP) used
<section anchor="Security" title="Security Considerations"> <section anchor="Security" title="Security Considerations">
<t>In some cases, Passive DNS output might contain confidential information and its access might be restricted. When an user is querying multiple Passive DNS and aggregating the data, the sensitivity of the data must be considered.</t> <t>In some cases, Passive DNS output might contain confidential information and its access might be restricted. When an user is querying multiple Passive DNS and aggregating the data, the sensitivity of the data must be considered.</t>
<t>Authentication and signing of the output MAY be implemented on the server via an extended field, namely x-signature-sha265 which contains a SHA256 signature of the output text, signed with the ssh-key of the server sending the answer.</t>
<t>All drafts are required to have a security considerations section.
See <xref target="RFC3552">RFC 3552</xref> for a guide.</t>
</section> </section>
</middle> </middle>
@ -291,20 +284,6 @@ The document does not describe the protocol (e.g. whois, HTTP REST or XMPP) used
&I-D.narten-iana-considerations-rfc2434bis; &I-D.narten-iana-considerations-rfc2434bis;
<!-- A reference written by by an organization not a person. -->
<reference anchor="DOMINATION"
target="http://www.example.com/dominator.html">
<front>
<title>Ultimate Plan for Taking Over the World</title>
<author>
<organization>Mad Dominators, Inc.</organization>
</author>
<date year="1984" />
</front>
</reference>
</references> </references>
<section anchor="app-additional" title="Additional Stuff"> <section anchor="app-additional" title="Additional Stuff">