diff --git a/i-d/pdns-qof.txt b/i-d/pdns-qof.txt
index a8130bd..2027bc7 100644
--- a/i-d/pdns-qof.txt
+++ b/i-d/pdns-qof.txt
@@ -98,8 +98,8 @@ Table of Contents
    Passive DNS replication, F Weimer - 17th Annual FIRST Conference on
    Computer Security.  Since then multiple Passive DNS implementations
    evolved over time.  Users of these Passive DNS servers query a server
-   (often via WHOIS [RFC3912] or HTTP and ReST), parse the results and
-   process them in other applications.
+   (often via WHOIS [RFC3912] or HTTP REST [REST]), parse the results
+   and process them in other applications.
 
    There are multiple implementation of Passive DNS software.  Users of
    passive DNS query each implementation and aggregate the results for
@@ -123,9 +123,9 @@ Internet-Draft     Passive DNS - Common Output Format      December 2013
    separate parser for each individual server. passivedns-client
    [PDNSCLIENT]currently implements multiple parsers due to a lack of
    standardization.  The document does not describe the protocol (e.g.
-   WHOIS [RFC3912], HTTP REST or XMPP) nor the query format used to
-   query the Passive DNS.  Neither does this document describe "pre-
-   recursor" Passive DNS Systems.
+   WHOIS [RFC3912], HTTP REST [REST]) nor the query format used to query
+   the Passive DNS.  Neither does this document describe "pre-recursor"
+   Passive DNS Systems.
 
 1.1.  Requirements Language
 
@@ -354,6 +354,10 @@ Internet-Draft     Passive DNS - Common Output Format      December 2013
               DNSParse, ISC, and VirusTotal.", 2013, <https://github.com
               /chrislee35/passivedns-client>.
 
+   [REST]     "Representational State Transfer (REST)", 2000,
+              <http://www.ics.uci.edu/~fielding/pubs/dissertation/
+              rest_arch_style.htm>.
+
 7.3.  Informative References
 
    [I-D.narten-iana-considerations-rfc2434bis]
@@ -376,6 +380,20 @@ Appendix A.  Appendix
 
 Authors' Addresses
 
+
+
+
+
+
+
+
+
+
+Dulaunoy, et al.          Expires June 28, 2014                 [Page 7]
+
+Internet-Draft     Passive DNS - Common Output Format      December 2013
+
+
    Alexandre Dulaunoy
    CIRCL
    41, avenue de la gare
@@ -387,13 +405,6 @@ Authors' Addresses
    URI:   http://www.circl.lu/
 
 
-
-
-Dulaunoy, et al.          Expires June 28, 2014                 [Page 7]
-
-Internet-Draft     Passive DNS - Common Output Format      December 2013
-
-
    Leon Aaron Kaplan
    CERT.at
    Karlsplatz 1/2/9
@@ -430,17 +441,6 @@ Internet-Draft     Passive DNS - Common Output Format      December 2013
 
 
 
-
-
-
-
-
-
-
-
-
-
-
 
 
 
diff --git a/i-d/pdns-qof.xml b/i-d/pdns-qof.xml
index c2d027e..ad01723 100644
--- a/i-d/pdns-qof.xml
+++ b/i-d/pdns-qof.xml
@@ -136,7 +136,7 @@
 
   <middle>
     <section title="Introduction">
-     <t>Passive DNS is a technique described by Florian Weimer in 2005 in Passive DNS replication, F Weimer - 17th Annual FIRST Conference on Computer Security. Since then multiple Passive DNS implementations evolved over time. Users of these Passive DNS servers query a server (often via <xref target="RFC3912">WHOIS</xref> or HTTP and ReST), parse the results and process them in other applications.</t>
+     <t>Passive DNS is a technique described by Florian Weimer in 2005 in Passive DNS replication, F Weimer - 17th Annual FIRST Conference on Computer Security. Since then multiple Passive DNS implementations evolved over time. Users of these Passive DNS servers query a server (often via <xref target="RFC3912">WHOIS</xref> or HTTP <xref target="REST">REST</xref>), parse the results and process them in other applications.</t>
      <t>
     There are multiple implementation of Passive DNS software. Users of passive DNS query each implementation and aggregate the results for their search. This document describes the output format of three Passive DNS Systems which are in use today and which already share a nearly identical output format.
 
@@ -144,7 +144,7 @@
 The benefit of having a consistent Passive DNS output format is that multiple client implementations can query different servers without having to have a separate parser for each
 individual server. <xref target="PDNSCLIENT">passivedns-client</xref>currently implements multiple parsers due to a lack of standardization.
 
-The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</xref>, HTTP REST or XMPP) nor the query format used to query the Passive DNS. Neither does this document describe "pre-recursor" Passive DNS Systems.
+The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</xref>, HTTP <xref target="REST">REST</xref>) nor the query format used to query the Passive DNS. Neither does this document describe "pre-recursor" Passive DNS Systems.
      </t>
 
       <section title="Requirements Language">
@@ -296,6 +296,13 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
             <date year="2013"/>
           </front>
         </reference>
+        <reference anchor="REST" target="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">
+          <front>
+            <title>Representational State Transfer (REST)</title>
+            <author fullname="Roy Thomas Fielding"/>
+            <date year="2000"/>
+          </front>
+        </reference>
     </references>
 
     <references title="Informative References">