Recent changes to this wiki:

Update descriptipon for efficientip
diff --git a/index.mdwn b/index.mdwn
index 133081d..a12a4cb 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -64,7 +64,7 @@ Send links to webmaster at dnsrpz.info to be added below.
 | Vendor | Product | Notes |
 |--------|---------|-------|
 | [BlueCat](https://www.bluecatnetworks.com) | [BlueCat DNS](https://www.bluecatnetworks.com/products/dns/) | BlueCat provides both their own protection policies for customers as well as the ability for customers to add their own zones.  Here is a landing page: [BlueCat RPZ](https://www.bluecatnetworks.com/products/threat-protection/bluecat-response-policies/).
-| [EfficientIP](http://www.efficientip.com) | [SolidServer](http://www.efficientip.com/products/dns-firewall/) allows inforporation of external policies through a GUI |
+| [EfficientIP](http://www.efficientip.com) | [SolidServer](http://www.efficientip.com/products/dns-firewall/) | SolidServer allows inforporation of external policies through a GUI |
 | [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
 | [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ support is included in BIND version 9.8 and later. |
 | [Knot](https://www.knot-dns.cz/) | policy.rpz [module](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) | Partial support explained [here](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) |

Add efficientip
diff --git a/index.mdwn b/index.mdwn
index 9f16cd6..133081d 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -58,11 +58,13 @@ Send links to webmaster at dnsrpz.info to be added below.
 | [SURBL](http://www.surbl.org) | [Data Feed](http://www.surbl.org/df) |
 | [ThreatStop](http://www.threatstop.com/) | [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [announcement](http://lists.redbarn.org/pipermail/dnsfirewalls/2012-June/000122.html) |
 
+
 ## Products that can utilize DNS RPZ
 
 | Vendor | Product | Notes |
 |--------|---------|-------|
 | [BlueCat](https://www.bluecatnetworks.com) | [BlueCat DNS](https://www.bluecatnetworks.com/products/dns/) | BlueCat provides both their own protection policies for customers as well as the ability for customers to add their own zones.  Here is a landing page: [BlueCat RPZ](https://www.bluecatnetworks.com/products/threat-protection/bluecat-response-policies/).
+| [EfficientIP](http://www.efficientip.com) | [SolidServer](http://www.efficientip.com/products/dns-firewall/) allows inforporation of external policies through a GUI |
 | [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
 | [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ support is included in BIND version 9.8 and later. |
 | [Knot](https://www.knot-dns.cz/) | policy.rpz [module](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) | Partial support explained [here](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) |

fix video URL for SWITCH.
diff --git a/index.mdwn b/index.mdwn
index 89f9aa8..9f16cd6 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -32,7 +32,7 @@ Policy zones published by a multiple providers (see below) can be checked in ord
  * Case studies:
    * SpamHaus' [DTU Environment](spamhaus-rpz-case-study.pdf)
    * LBNL [Video](https://www.youtube.com/watch?v=Kd39y50eC_g)
-   * SWITCH [Blog](https://securityblog.switch.ch/2015/05/07/protect-your-network-with-dns-firewall/) and [Video](https://tube.switch.ch/videos/f622b623)
+   * SWITCH [Blog](https://securityblog.switch.ch/2015/05/07/protect-your-network-with-dns-firewall/) and [Video](https://tube.switch.ch/videos/f3831a07)
  * ISC BIND 9 reference implementation
    * [ISC Technical Note](https://kb.isc.org/getAttach/21/AA-00512/rpz.txt)
    * ISC's [Knowledge Base](https://kb.isc.org/category/110/0/10/Software-Products/BIND9/Features/DNSRPZ/) articles

Added entry for PowerDNS.
diff --git a/index.mdwn b/index.mdwn
index 9fbdcdc..89f9aa8 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -66,6 +66,7 @@ Send links to webmaster at dnsrpz.info to be added below.
 | [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
 | [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ support is included in BIND version 9.8 and later. |
 | [Knot](https://www.knot-dns.cz/) | policy.rpz [module](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) | Partial support explained [here](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) |
+| [PowerDNS](https://www.powerdns.com/) | [PowerDNS Recursor](https://www.powerdns.com/recursor.html) 4.0.0 and higher | [Introduction](https://blog.powerdns.com/2016/06/28/response-policy-zone-support-in-powerdns-recursor/) |
 
 ## Related services
 

Added 4 links from Matthias Seitz <matthias.seitz@switch.ch>.
diff --git a/index.mdwn b/index.mdwn
index 7531e41..9fbdcdc 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -31,7 +31,9 @@ Policy zones published by a multiple providers (see below) can be checked in ord
    * Hugo Connery's [introduction](RPZ-History-Usage-Research.pdf) to RPZ, with some history.
  * Case studies:
    * SpamHaus' [DTU Environment](spamhaus-rpz-case-study.pdf)
- * ISC BIND 9
+   * LBNL [Video](https://www.youtube.com/watch?v=Kd39y50eC_g)
+   * SWITCH [Blog](https://securityblog.switch.ch/2015/05/07/protect-your-network-with-dns-firewall/) and [Video](https://tube.switch.ch/videos/f622b623)
+ * ISC BIND 9 reference implementation
    * [ISC Technical Note](https://kb.isc.org/getAttach/21/AA-00512/rpz.txt)
    * ISC's [Knowledge Base](https://kb.isc.org/category/110/0/10/Software-Products/BIND9/Features/DNSRPZ/) articles
    * Administrator Reference Manual (ARM)
@@ -62,7 +64,8 @@ Send links to webmaster at dnsrpz.info to be added below.
 |--------|---------|-------|
 | [BlueCat](https://www.bluecatnetworks.com) | [BlueCat DNS](https://www.bluecatnetworks.com/products/dns/) | BlueCat provides both their own protection policies for customers as well as the ability for customers to add their own zones.  Here is a landing page: [BlueCat RPZ](https://www.bluecatnetworks.com/products/threat-protection/bluecat-response-policies/).
 | [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
-| [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ support in include in BIND version 9.8 and later. |
+| [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ support is included in BIND version 9.8 and later. |
+| [Knot](https://www.knot-dns.cz/) | policy.rpz [module](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) | Partial support explained [here](http://knot-resolver.readthedocs.io/en/latest/modules.html#c.policy.rpz) |
 
 ## Related services
 

Vernon asked me to remove old link.
diff --git a/index.mdwn b/index.mdwn
index 8e5726e..7531e41 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -36,7 +36,6 @@ Policy zones published by a multiple providers (see below) can be checked in ord
    * ISC's [Knowledge Base](https://kb.isc.org/category/110/0/10/Software-Products/BIND9/Features/DNSRPZ/) articles
    * Administrator Reference Manual (ARM)
      * [ISC's BIND ARM](https://kb.isc.org/article/AA-00845/0/BIND-9.9-Administrator-Reference-Manual-ARM.html)
-     * [Vernon's copy](http://ss.vix.su/~vjs/rpz-arm.html)
  * Hugo Connery's Roadmap to Accellerate Adoption: [[RPZ-Building-Momentum.pdf]]
  * April Lorenzen's [Virtual Server for RPZ](https://github.com/secure411dotorg/rpzone) on github
  * Hugo Connery's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github - aka RPZLA

Add IETF Draft link
diff --git a/index.mdwn b/index.mdwn
index dde23f2..8e5726e 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -23,6 +23,7 @@ Policy zones published by a multiple providers (see below) can be checked in ord
  * Paul Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
  * Paul Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
  * Discussion [mailing list](http://lists.redbarn.org/mailman/listinfo/dnsfirewalls)
+ * <b>New!</b> [IETF Draft](https://tools.ietf.org/html/draft-vixie-dns-rpz-00)
  * Presentations
    * Hugo Connery's [MAAWG Presentation](https://www.youtube.com/watch?v=ChyrkCFpkNg)
    * Barry Greene's [DNS RPZ introduction](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC

Add BlueCat; reorder alphabetically
diff --git a/index.mdwn b/index.mdwn
index ad03584..dde23f2 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -60,12 +60,13 @@ Send links to webmaster at dnsrpz.info to be added below.
 
 | Vendor | Product | Notes |
 |--------|---------|-------|
-| [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ was added in version 9.8.  Did you know that all previous versions have reached End-Of-Life status? |
+| [BlueCat](https://www.bluecatnetworks.com) | [BlueCat DNS](https://www.bluecatnetworks.com/products/dns/) | BlueCat provides both their own protection policies for customers as well as the ability for customers to add their own zones.  Here is a landing page: [BlueCat RPZ](https://www.bluecatnetworks.com/products/threat-protection/bluecat-response-policies/).
 | [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
+| [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ support in include in BIND version 9.8 and later. |
 
 ## Related services
 
 | Provider | Service |
 |----------|---------|
-| [SecurityZones](http://securityzones.net/) | Provides product marketing and sales for some of the providers above |
 | [Deteque](http://www.deteque.com/) | Has provided integration consulting for some of the DNS RPZ providers above |
+| [SecurityZones](http://securityzones.net/) | Provides product marketing and sales for some of the providers above |

Updated SpamHaus entry to not be DBL-specific
Fixed typo in SpamHaus URL.
diff --git a/index.mdwn b/index.mdwn
index bf3688e..ad03584 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -52,7 +52,7 @@ Send links to webmaster at dnsrpz.info to be added below.
 | [DissectCyber](https://service.dissectcyber.com/) | [rpzone.us](https://service.dissectcyber.com/rpz) |
 | [FarsightSecurity](https://www.farsightsecurity.com/) | [Newly Observed Domains](https://www.farsightsecurity.com/Services/NOD/) and [example](http://www.redbarn.org/node/18) |
 | [InternetIdentity](http://internetidentity.com/) | [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/) |
-| [SpamHaus](http://www.spamhaus.com/) | [DBL](http://www.spamhaus.org/news/article/669/) |
+| [SpamHaus](http://www.spamhaus.org/) | Several of their popular blocklists are available via RPZ.  [Article](http://www.spamhaus.org/news/article/669) [Pricing](https://www.spamhaustech.com/pricing) |
 | [SURBL](http://www.surbl.org) | [Data Feed](http://www.surbl.org/df) |
 | [ThreatStop](http://www.threatstop.com/) | [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [announcement](http://lists.redbarn.org/pipermail/dnsfirewalls/2012-June/000122.html) |
 

Added Hugo's YouTube video
diff --git a/index.mdwn b/index.mdwn
index a7f339a..bf3688e 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -24,6 +24,7 @@ Policy zones published by a multiple providers (see below) can be checked in ord
  * Paul Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
  * Discussion [mailing list](http://lists.redbarn.org/mailman/listinfo/dnsfirewalls)
  * Presentations
+   * Hugo Connery's [MAAWG Presentation](https://www.youtube.com/watch?v=ChyrkCFpkNg)
    * Barry Greene's [DNS RPZ introduction](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
    * Paul Vixie's and Rod Rasmussen's June 2012 Webinar - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](RPZ-2012-06-26-Slides.pdf)
    * Hugo Connery's [introduction](RPZ-History-Usage-Research.pdf) to RPZ, with some history.

Width
diff --git a/local.css b/local.css
index 9f659ba..f846e32 100644
--- a/local.css
+++ b/local.css
@@ -16,7 +16,7 @@
 /* variables copy pasted from the corporate website */
 body {
 background-color: #EFFFFF;
-width: 600px;
+max-width: 800px;
 margin: 10px 40px;
 }
 .pageheader {

Change color
diff --git a/local.css b/local.css
index 48687a4..9f659ba 100644
--- a/local.css
+++ b/local.css
@@ -15,7 +15,7 @@
  *  */
 /* variables copy pasted from the corporate website */
 body {
-background-color: #EFEFFF;
+background-color: #EFFFFF;
 width: 600px;
 margin: 10px 40px;
 }

Try to set fixed width.
diff --git a/local.css b/local.css
index a456ca9..48687a4 100644
--- a/local.css
+++ b/local.css
@@ -14,6 +14,11 @@
  * 0% is opaque, 100% is transparent
  *  */
 /* variables copy pasted from the corporate website */
+body {
+background-color: #EFEFFF;
+width: 600px;
+margin: 10px 40px;
+}
 .pageheader {
   padding: 8px 8px 8px 8px;
   position: relative;

More table / prettiness
diff --git a/index.mdwn b/index.mdwn
index 4ddced3..a7f339a 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -40,7 +40,7 @@ Policy zones published by a multiple providers (see below) can be checked in ord
  * Hugo Connery's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github - aka RPZLA
  * Hugo Connery's [proposal on standardizing zone feedback](rpz-fbz.txt)
 
-# RPZ ecosystem
+# Ecosystem
 
 Send links to webmaster at dnsrpz.info to be added below.
 
@@ -57,13 +57,14 @@ Send links to webmaster at dnsrpz.info to be added below.
 
 ## Products that can utilize DNS RPZ
 
-
 | Vendor | Product | Notes |
 |--------|---------|-------|
-| [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ was added in version 9.8.  Note that all previous versions have reached End-Of-Life status. |
+| [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ was added in version 9.8.  Did you know that all previous versions have reached End-Of-Life status? |
 | [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
 
 ## Related services
 
- * [SecurityZones](http://securityzones.net/) – product marketing/sales
- * [Deteque](http://www.deteque.com) – Deteque has provided integration consulting to some of the DNS RPZ providers
+| Provider | Service |
+|----------|---------|
+| [SecurityZones](http://securityzones.net/) | Provides product marketing and sales for some of the providers above |
+| [Deteque](http://www.deteque.com/) | Has provided integration consulting for some of the DNS RPZ providers above |

fix table
diff --git a/index.mdwn b/index.mdwn
index d4d6aa4..4ddced3 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -59,6 +59,7 @@ Send links to webmaster at dnsrpz.info to be added below.
 
 
 | Vendor | Product | Notes |
+|--------|---------|-------|
 | [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ was added in version 9.8.  Note that all previous versions have reached End-Of-Life status. |
 | [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
 

turn products into a table
diff --git a/index.mdwn b/index.mdwn
index 9aeca66..d4d6aa4 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -57,10 +57,10 @@ Send links to webmaster at dnsrpz.info to be added below.
 
 ## Products that can utilize DNS RPZ
 
- * [ISC BIND 9](http://www.isc.org/downloads/bind/)
-    * RPZ was added in version 9.8.  (Note: All previous versions have reached End-Of-Life status.)
- * [InfoBlox](http://www.infoblox.com)'s [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall)
-    * The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs)
+
+| Vendor | Product | Notes |
+| [ISC](https://www.isc.org/) | [BIND 9](http://www.isc.org/downloads/bind/) | RPZ was added in version 9.8.  Note that all previous versions have reached End-Of-Life status. |
+| [InfoBlox](http://www.infoblox.com) | [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall) | The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs) |
 
 ## Related services
 

Update ISC and Infoblox entry
diff --git a/index.mdwn b/index.mdwn
index e5baa45..9aeca66 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -58,8 +58,9 @@ Send links to webmaster at dnsrpz.info to be added below.
 ## Products that can utilize DNS RPZ
 
  * [ISC BIND 9](http://www.isc.org/downloads/bind/)
-    * The feature was added to version 9.8, and all prior versions are now deprecated or EOL.  Anyone running a prior version of BIND 9 should consider upgrading to keep up with security updates.
- * [InfoBlox](http://www.infoblox.com)'s [DNS Firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
+    * RPZ was added in version 9.8.  (Note: All previous versions have reached End-Of-Life status.)
+ * [InfoBlox](http://www.infoblox.com)'s [DNS Firewall](www.infoblox.com/products/infrastructure-security/dns-firewall)
+    * The DNS engine is based on BIND 9 (with enhancements).  Add providers or manage your own list with a GUI.  [video](http://www.youtube.com/embed/Ij8ZNhF4XBs)
 
 ## Related services
 

Change providers into a table for readability
diff --git a/index.mdwn b/index.mdwn
index bd690a3..e5baa45 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -46,12 +46,14 @@ Send links to webmaster at dnsrpz.info to be added below.
 
 ## Providers of reputation data (in alphabetical order)
 
-  * [DissectCyber](https://service.dissectcyber.com/): [rpzone.us](https://service.dissectcyber.com/rpz)
-  * [FarsightSecurity](https://www.farsightsecurity.com/): [Newly Observed Domains](https://www.farsightsecurity.com/Services/NOD/) and [example](http://www.redbarn.org/node/18) 
-  * [InternetIdentity](http://internetidentity.com/): [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
-  * [SpamHaus](http://www.spamhaus.com/): [DBL](http://www.spamhaus.org/news/article/669/)
-  * [SURBL](http://www.surbl.org): [Data Feed](http://www.surbl.org/df)
-  * [ThreatStop](http://www.threatstop.com/): [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [announcement](http://lists.redbarn.org/pipermail/dnsfirewalls/2012-June/000122.html)
+| Provider | Service |
+|----------|---------|
+| [DissectCyber](https://service.dissectcyber.com/) | [rpzone.us](https://service.dissectcyber.com/rpz) |
+| [FarsightSecurity](https://www.farsightsecurity.com/) | [Newly Observed Domains](https://www.farsightsecurity.com/Services/NOD/) and [example](http://www.redbarn.org/node/18) |
+| [InternetIdentity](http://internetidentity.com/) | [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/) |
+| [SpamHaus](http://www.spamhaus.com/) | [DBL](http://www.spamhaus.org/news/article/669/) |
+| [SURBL](http://www.surbl.org) | [Data Feed](http://www.surbl.org/df) |
+| [ThreatStop](http://www.threatstop.com/) | [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [announcement](http://lists.redbarn.org/pipermail/dnsfirewalls/2012-June/000122.html) |
 
 ## Products that can utilize DNS RPZ
 

More cleanup
diff --git a/index.mdwn b/index.mdwn
index fa24a04..bd690a3 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -8,15 +8,15 @@ This website is made available to keep up with information about this feature.
 
 # Why is RPZ useful?
 
-The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to keep using the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure at domain registries or ISPs is not fast enough to be effective.  Using RPZ, a network or DNS administrator can implement their own protection policies base based on reputation feeds from security service providers on a near-real-time basis.
+The prime motivation for creating this feature was to protect users from badness on the Internet related to known-malicious global identifiers such as host names, domain names, IP addresses, or nameservers.  Criminals tend to keep using the same identifiers until they are taken away from them.  Unfortunately, the Internet security industry's ability to take down criminal infrastructure at domain registries, hosting providers or ISPs is not timely enough to be effective.  Using RPZ, a network or DNS administrator can implement their own protection policies base based on reputation feeds from security service providers on a near-real-time basis.
 
-Examples:
+Examples include:
 
- * If you know a bad hostname or domain name, you can block people from accessing it or redirect them to a walled garden.
- * If you know a bad IP address or subnet, you can block users from accessing hostnames that reference it.
- * If you know a nameserver that doesn't host anything except bad domains, you can block users from accessing DNS information hosted by those nameservers.
+ * If one knows a bad hostname or domain name, one can block clients from accessing it or redirect them to a walled garden.
+ * If one know a bad IP address or subnet, one can block clients from accessing hostnames that reference it.
+ * If one knows a nameserver that doesn't host anything except bad domains, one can block clients from accessing DNS information hosted by those nameservers.
 
-Multiple policy zones published by a number of providers (see below) can be checked before a normal answer from the global DNS is used.
+Policy zones published by a multiple providers (see below) can be checked in order before a normal answer from the global DNS is used.  White lists can also be maintained by a local administrator to prevent false positives for key infrastructure.
 
 # Pointers to resources
 
@@ -24,7 +24,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
  * Paul Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
  * Discussion [mailing list](http://lists.redbarn.org/mailman/listinfo/dnsfirewalls)
  * Presentations
-   * Barry Greene's [DNSRPZ introduction](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
+   * Barry Greene's [DNS RPZ introduction](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
    * Paul Vixie's and Rod Rasmussen's June 2012 Webinar - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](RPZ-2012-06-26-Slides.pdf)
    * Hugo Connery's [introduction](RPZ-History-Usage-Research.pdf) to RPZ, with some history.
  * Case studies:
@@ -44,17 +44,16 @@ Multiple policy zones published by a number of providers (see below) can be chec
 
 Send links to webmaster at dnsrpz.info to be added below.
 
-## Providers of reputation data
+## Providers of reputation data (in alphabetical order)
 
   * [DissectCyber](https://service.dissectcyber.com/): [rpzone.us](https://service.dissectcyber.com/rpz)
+  * [FarsightSecurity](https://www.farsightsecurity.com/): [Newly Observed Domains](https://www.farsightsecurity.com/Services/NOD/) and [example](http://www.redbarn.org/node/18) 
   * [InternetIdentity](http://internetidentity.com/): [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
   * [SpamHaus](http://www.spamhaus.com/): [DBL](http://www.spamhaus.org/news/article/669/)
   * [SURBL](http://www.surbl.org): [Data Feed](http://www.surbl.org/df)
   * [ThreatStop](http://www.threatstop.com/): [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [announcement](http://lists.redbarn.org/pipermail/dnsfirewalls/2012-June/000122.html)
-  * [FarsightSecurity](https://www.farsightsecurity.com/): [Newly Observed Domains](https://www.farsightsecurity.com/Services/NOD/) and [example](http://www.redbarn.org/node/18) 
- * Add yourself here - contact webmaster @ dnsrpz.info
 
-## Products that can use RPZ
+## Products that can utilize DNS RPZ
 
  * [ISC BIND 9](http://www.isc.org/downloads/bind/)
     * The feature was added to version 9.8, and all prior versions are now deprecated or EOL.  Anyone running a prior version of BIND 9 should consider upgrading to keep up with security updates.

Fix typo, make prettier
diff --git a/index.mdwn b/index.mdwn
index 78bd43e..fa24a04 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -2,9 +2,9 @@
 
 [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone) knows.
 
-<b>D</b>omain <b>N</b>ame <b>S</b>ervice <b>R</b>esponse <b>P</b>olicy <b>Z</b>ones (DNS RPZ) is a method that allows a nameserver administrator to overlay custom information on top of the global DNS to provide alternate responses to queries.  It is currently implemented in the ISC BIND nameserver (9.8 or later).  Another generic name for the DNS RPZ functionalit is "DNS firewall".
+<b>D</b>omain <b>N</b>ame <b>S</b>ervice <b>R</b>esponse <b>P</b>olicy <b>Z</b>ones (DNS RPZ) is a method that allows a nameserver administrator to overlay custom information on top of the global DNS to provide alternate responses to queries.  It is currently implemented in the ISC BIND nameserver (9.8 or later).  Another generic name for the DNS RPZ functionality is "DNS firewall".
 
-This website is made available to keep up with implementation and examples of this feature.
+This website is made available to keep up with information about this feature.
 
 # Why is RPZ useful?
 
@@ -38,7 +38,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
  * Hugo Connery's Roadmap to Accellerate Adoption: [[RPZ-Building-Momentum.pdf]]
  * April Lorenzen's [Virtual Server for RPZ](https://github.com/secure411dotorg/rpzone) on github
  * Hugo Connery's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github - aka RPZLA
- * Hugo Connery's proposal on standardizing zone feedback: [[rpz-fbz.txt]]
+ * Hugo Connery's [proposal on standardizing zone feedback](rpz-fbz.txt)
 
 # RPZ ecosystem
 

Web page refresh / reorg
diff --git a/index.mdwn b/index.mdwn
index ae429a9..78bd43e 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -2,72 +2,65 @@
 
 [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone) knows.
 
-<b>D</b>omain <b>N</b>ame <b>S</b>ervice <b>R</b>esponse <b>P</b>olicy <b>Z</b>ones (DNS RPZ) is a method that allows a nameserver administrator to overlay custom information on top of the global DNS to provide alternate responses to queries.  It is currently implemented in the ISC BIND nameserver (9.8 or later).
+<b>D</b>omain <b>N</b>ame <b>S</b>ervice <b>R</b>esponse <b>P</b>olicy <b>Z</b>ones (DNS RPZ) is a method that allows a nameserver administrator to overlay custom information on top of the global DNS to provide alternate responses to queries.  It is currently implemented in the ISC BIND nameserver (9.8 or later).  Another generic name for the DNS RPZ functionalit is "DNS firewall".
 
-# Why is RPZ useful?
+This website is made available to keep up with implementation and examples of this feature.
 
-The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure at registries or ISPs is not fast enough.  Using RPZ, an administrator can implement their own protection policies or receive automated reputation updates feeds from security providers that maintain reputation information.
+# Why is RPZ useful?
 
+The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to keep using the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure at domain registries or ISPs is not fast enough to be effective.  Using RPZ, a network or DNS administrator can implement their own protection policies base based on reputation feeds from security service providers on a near-real-time basis.
 
 Examples:
 
  * If you know a bad hostname or domain name, you can block people from accessing it or redirect them to a walled garden.
  * If you know a bad IP address or subnet, you can block users from accessing hostnames that reference it.
- * If you know a nameserver that doesn't host anything except bad domains, you can block users from accessing DNS information hosted by those nameservers.
+ * If you know a nameserver that doesn't host anything except bad domains, you can block users from accessing DNS information hosted by those nameservers.
 
 Multiple policy zones published by a number of providers (see below) can be checked before a normal answer from the global DNS is used.
 
 # Pointers to resources
 
- * Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
- * Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
- * The email discussion [list](http://lists.redbarn.org/mailman/listinfo/dnsfirewalls)
+ * Paul Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
+ * Paul Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
+ * Discussion [mailing list](http://lists.redbarn.org/mailman/listinfo/dnsfirewalls)
  * Presentations
-   * [Barry Greene](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
-   * Webinar - June 2012 Vixie/Rasmussen - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](RPZ-2012-06-26-Slides.pdf)
- * [ISC Technical Note](https://kb.isc.org/getAttach/21/AA-00512/rpz.txt)
- * ISC's [Knowledge Base](https://kb.isc.org/category/110/0/10/Software-Products/BIND9/Features/DNSRPZ/) articles
- * BIND ARM
-   * ISC's [BIND ARM](https://kb.isc.org/article/AA-00845/0/BIND-9.9-Administrator-Reference-Manual-ARM.html)
-   * Vernon's [copy](http://ss.vix.su/~vjs/rpz-arm.html)
- * A [more verbose](RPZ-History-Usage-Research.pdf) introduction to RPZ, with some history.
-
-# Case studies
-
- * [DTU Environment](spamhaus-rpz-case-study.pdf)
-
-# Notes
-
- * April's [virtual server for RPZ](https://github.com/secure411dotorg/rpzone) on github
- * Hugo's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github
+   * Barry Greene's [DNSRPZ introduction](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
+   * Paul Vixie's and Rod Rasmussen's June 2012 Webinar - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](RPZ-2012-06-26-Slides.pdf)
+   * Hugo Connery's [introduction](RPZ-History-Usage-Research.pdf) to RPZ, with some history.
+ * Case studies:
+   * SpamHaus' [DTU Environment](spamhaus-rpz-case-study.pdf)
+ * ISC BIND 9
+   * [ISC Technical Note](https://kb.isc.org/getAttach/21/AA-00512/rpz.txt)
+   * ISC's [Knowledge Base](https://kb.isc.org/category/110/0/10/Software-Products/BIND9/Features/DNSRPZ/) articles
+   * Administrator Reference Manual (ARM)
+     * [ISC's BIND ARM](https://kb.isc.org/article/AA-00845/0/BIND-9.9-Administrator-Reference-Manual-ARM.html)
+     * [Vernon's copy](http://ss.vix.su/~vjs/rpz-arm.html)
+ * Hugo Connery's Roadmap to Accellerate Adoption: [[RPZ-Building-Momentum.pdf]]
+ * April Lorenzen's [Virtual Server for RPZ](https://github.com/secure411dotorg/rpzone) on github
+ * Hugo Connery's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github - aka RPZLA
+ * Hugo Connery's proposal on standardizing zone feedback: [[rpz-fbz.txt]]
 
 # RPZ ecosystem
 
+Send links to webmaster at dnsrpz.info to be added below.
+
 ## Providers of reputation data
 
   * [DissectCyber](https://service.dissectcyber.com/): [rpzone.us](https://service.dissectcyber.com/rpz)
   * [InternetIdentity](http://internetidentity.com/): [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
   * [SpamHaus](http://www.spamhaus.com/): [DBL](http://www.spamhaus.org/news/article/669/)
   * [SURBL](http://www.surbl.org): [Data Feed](http://www.surbl.org/df)
-  * [ThreatStop](http://www.threatstop.com/): [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [note](https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
-  * [FarsightSecurity](https://www.farsightsecurity.com/): [Newly Observed Domains](http://www.redbarn.org/node/18) 
+  * [ThreatStop](http://www.threatstop.com/): [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [announcement](http://lists.redbarn.org/pipermail/dnsfirewalls/2012-June/000122.html)
+  * [FarsightSecurity](https://www.farsightsecurity.com/): [Newly Observed Domains](https://www.farsightsecurity.com/Services/NOD/) and [example](http://www.redbarn.org/node/18) 
+ * Add yourself here - contact webmaster @ dnsrpz.info
 
 ## Products that can use RPZ
 
- * [ISC BIND](http://www.isc.org/downloads/bind/) - versions 9.8 and higher
+ * [ISC BIND 9](http://www.isc.org/downloads/bind/)
+    * The feature was added to version 9.8, and all prior versions are now deprecated or EOL.  Anyone running a prior version of BIND 9 should consider upgrading to keep up with security updates.
  * [InfoBlox](http://www.infoblox.com)'s [DNS Firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
 
 ## Related services
 
  * [SecurityZones](http://securityzones.net/) – product marketing/sales
  * [Deteque](http://www.deteque.com) – Deteque has provided integration consulting to some of the DNS RPZ providers
-
-# Feedback Zones
-
-Standardizing feedback mechanisms for reputation data providers:
-
-* DRAFT document [[rpz-fbz.txt]]
-
-# Process: Building RPZ Deployment
-
-* [[RPZ-Building-Momentum.pdf]]

Clean up provider listings
diff --git a/index.mdwn b/index.mdwn
index f4795fe..ae429a9 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -45,12 +45,12 @@ Multiple policy zones published by a number of providers (see below) can be chec
 
 ## Providers of reputation data
 
-  * [DissectCyber](https://service.dissectcyber.com/)'s [rpzone.us](https://service.dissectcyber.com/rpz)
-  * [InternetIdentity's DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
-  * [SpamHaus](http://www.spamhaus.com/)'s [DBL](http://www.spamhaus.org/news/article/669/)
-  * [SURBL](http://www.surbl.org)'s [Data Feed](http://www.surbl.org/df)
-  * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [note](https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
-  * [FarsightSecurity](https://www.farsightsecurity.com/)'s [Newly Observed Domains](http://www.redbarn.org/node/18) 
+  * [DissectCyber](https://service.dissectcyber.com/): [rpzone.us](https://service.dissectcyber.com/rpz)
+  * [InternetIdentity](http://internetidentity.com/): [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
+  * [SpamHaus](http://www.spamhaus.com/): [DBL](http://www.spamhaus.org/news/article/669/)
+  * [SURBL](http://www.surbl.org): [Data Feed](http://www.surbl.org/df)
+  * [ThreatStop](http://www.threatstop.com/): [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [note](https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
+  * [FarsightSecurity](https://www.farsightsecurity.com/): [Newly Observed Domains](http://www.redbarn.org/node/18) 
 
 ## Products that can use RPZ
 

Added Farsight Security Inc Newly Observed Domains
diff --git a/index.mdwn b/index.mdwn
index f30272f..f4795fe 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -50,6 +50,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
   * [SpamHaus](http://www.spamhaus.com/)'s [DBL](http://www.spamhaus.org/news/article/669/)
   * [SURBL](http://www.surbl.org)'s [Data Feed](http://www.surbl.org/df)
   * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [note](https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
+  * [FarsightSecurity](https://www.farsightsecurity.com/)'s [Newly Observed Domains](http://www.redbarn.org/node/18) 
 
 ## Products that can use RPZ
 

diff --git a/index.mdwn b/index.mdwn
index 9eae223..f30272f 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -21,7 +21,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
 
  * Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
  * Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
- * The email discussion list [archives](https://lists.isc.org/mailman/listinfo/dnsrpz-interest)
+ * The email discussion [list](http://lists.redbarn.org/mailman/listinfo/dnsfirewalls)
  * Presentations
    * [Barry Greene](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
    * Webinar - June 2012 Vixie/Rasmussen - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](RPZ-2012-06-26-Slides.pdf)

cleaner
diff --git a/index.mdwn b/index.mdwn
index 465360b..9eae223 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -65,7 +65,8 @@ Multiple policy zones published by a number of providers (see below) can be chec
 
 Standardizing feedback mechanisms for reputation data providers:
 
-* DRAFT document [[]]
+* DRAFT document [[rpz-fbz.txt]]
+
 # Process: Building RPZ Deployment
 
 * [[RPZ-Building-Momentum.pdf]]

attachment upload
diff --git a/rpz-fbz.txt b/rpz-fbz.txt
new file mode 100644
index 0000000..917fcb1
--- /dev/null
+++ b/rpz-fbz.txt
@@ -0,0 +1,448 @@
+
+
+
+Network Working Group                                    H. Connery, Ed.
+Internet-Draft                           Technical University of Denmark
+Intended status: Informational                                 June 2013
+Expires: December 3, 2013
+
+
+                          DNSRPZ Feedback Zone
+
+
+Abstract
+
+   DNS Response Policy Zone (RPZ) Feedback Zone (RPZ-FBZ) is a mechanism
+   for an organisation using RPZ to provide feedback to anyone, though
+   principally to the source RPZ zone maintainer, about how resource
+   records in an RPZ zone are being used in DNS filtering.
+
+Status of this Memo
+
+   By submitting this Internet-Draft, each author represents that any
+   applicable patent or other IPR claims of which he or she is aware
+   have been or will be disclosed, and any of which he or she becomes
+   aware will be disclosed, in accordance with Section 6 of BCP 79.
+
+   Internet-Drafts are working documents of the Internet Engineering
+   Task Force (IETF).  Note that other groups may also distribute
+   working documents as Internet-Drafts.  The list of current Internet-
+   Drafts is at http://datatracker.ietf.org/drafts/current/.
+
+   Internet-Drafts are draft documents valid for a maximum of six months
+   and may be updated, replaced, or obsoleted by other documents at any
+   time.  It is inappropriate to use Internet-Drafts as reference
+   material or to cite them other than as "work in progress."
+
+   This Internet-Draft will expire on December 3, 2013.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Connery                 Expires December 3, 2013                [Page 1]
+
+Internet-Draft            DNSRPZ Feedback Zone                 June 2013
+
+
+Table of Contents
+
+   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
+     1.1.  Nomenclature  . . . . . . . . . . . . . . . . . . . . . . . 3
+     1.2.  RPZ Data Flow . . . . . . . . . . . . . . . . . . . . . . . 3
+     1.3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . 3
+   2.  Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
+     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . 4
+     2.2.  Resource Records  . . . . . . . . . . . . . . . . . . . . . 4
+     2.3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . 4
+     2.4.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . 5
+   3.  Mechanics . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
+     3.1.  Aging . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
+     3.2.  Frequency . . . . . . . . . . . . . . . . . . . . . . . . . 6
+     3.3.  Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . 6
+   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
+   5.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . 7
+   6.  Informative References  . . . . . . . . . . . . . . . . . . . . 7
+   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 7
+   Intellectual Property and Copyright Statements  . . . . . . . . . . 8
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Connery                 Expires December 3, 2013                [Page 2]
+
+Internet-Draft            DNSRPZ Feedback Zone                 June 2013
+
+
+1.  Introduction
+
+   DNS Response Policy Zone (RPZ) [DNSRPZ] allows customizable DNS based
+   filtering by recursive DNS resolvers.  An implementation of RPZ may
+   involve multiple data sources for use in DNS filtering.  These zones
+   may be internal and/or externally sourced.
+
+   RPZ Feedback Zone (RPZ-FBZ) allows an organization using RPZ zones to
+   gather information about how RPZ data is being used for DNS filtering
+   within their organization and selectively make that information to
+   others.
+
+1.1.  Nomenclature
+
+   RPZ is a reputation data ecosystem in which domain name lookup is
+   filtered for domains with a poor reputation.
+
+   There are two key classes of actors in the use of RPZ.  From the
+   perspective of reputation data providers they are:
+
+   o  Organizations using RPZ to filter DNS: Reputation Data Consumers
+      (RD-C)
+
+   o  Organisations supplying data to RD-C's: Reputation Data Providers
+      (RD-P)
+
+1.2.  RPZ Data Flow
+
+   RD-C's receive data from RD-P's which have derived their data from a
+   collection of intelligence sources.
+
+   +---------+ DNS   +----------+  RPZ     +------+      +---------+
+   | RD-C    | <---> | RD-C     | <------- | RD-P | <--- | RD-P    |
+   | Clients | Query | Resolver |  Data    |      |      | Sources |
+   +---------+       +----------+          +------+      +---------+
+
+                          RPZ in Normal Operation
+
+                                 Figure 1
+
+1.3.  Motivation
+
+   When an RD-C uses external data from an RD-P, the RD-P has no general
+   method of knowing which elements of their dataset(s) are supporting
+   DNS filtering.  Access to this data enables RD-P's to improve their
+   data based on its usage.
+
+   RPZ-FBZ provides a mechanism whereby this potentially valuable data
+
+
+
+Connery                 Expires December 3, 2013                [Page 3]
+
+Internet-Draft            DNSRPZ Feedback Zone                 June 2013
+
+
+   may be supplied by the RD-C to the RD-P, and/or to others.
+
+   +---------+ DNS   +----------+  RPZ     +------+      +---------+
+   | RD-C    | <---> | RD-C     | <------- | RD-P | <--- | RD-P    |
+   | Clients | Query | Resolver |  Data    |      |      | Sources |
+   +---------+       |          |          |  ^   |      +---------+
+                     |    |     | Feedback |  |   |
+                     |     -->  | -------> |--    |
+                     |          | Data     |      |
+                     +----------+          +------+
+
+                         RPZ with Feedback Zone(s)
+
+                                 Figure 2
+
+
+2.  Mechanism
+
+2.1.  Overview
+
+   The RPZ-FBZ mechansim is based on identifying 'hits' from each client
+   DNS resolution response which resulted in data from an RPZ zone being
+   used, rather than normal DNS recursion.  Dynamic DNS (DDNS) is

(Diff truncated)
diff --git a/index.mdwn b/index.mdwn
index a21c8e6..465360b 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -61,6 +61,11 @@ Multiple policy zones published by a number of providers (see below) can be chec
  * [SecurityZones](http://securityzones.net/) – product marketing/sales
  * [Deteque](http://www.deteque.com) – Deteque has provided integration consulting to some of the DNS RPZ providers
 
+# Feedback Zones
+
+Standardizing feedback mechanisms for reputation data providers:
+
+* DRAFT document [[]]
 # Process: Building RPZ Deployment
 
 * [[RPZ-Building-Momentum.pdf]]

attachment upload
diff --git a/RPZ-Building-Momentum.pdf b/RPZ-Building-Momentum.pdf
index 64b4ed4..4739f6f 100644
Binary files a/RPZ-Building-Momentum.pdf and b/RPZ-Building-Momentum.pdf differ

added link to the list archives
diff --git a/index.mdwn b/index.mdwn
index c5f33db..a21c8e6 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -21,6 +21,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
 
  * Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
  * Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
+ * The email discussion list [archives](https://lists.isc.org/mailman/listinfo/dnsrpz-interest)
  * Presentations
    * [Barry Greene](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
    * Webinar - June 2012 Vixie/Rasmussen - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](RPZ-2012-06-26-Slides.pdf)

attachment upload
diff --git a/RPZ-Building-Momentum.pdf b/RPZ-Building-Momentum.pdf
index 25fbec6..64b4ed4 100644
Binary files a/RPZ-Building-Momentum.pdf and b/RPZ-Building-Momentum.pdf differ

attachment upload
diff --git a/RPZ-Building-Momentum.pdf b/RPZ-Building-Momentum.pdf
index 30c0c07..25fbec6 100644
Binary files a/RPZ-Building-Momentum.pdf and b/RPZ-Building-Momentum.pdf differ

Renamed 'softcom' to 'DTU Environment' (where did 'softcom' come from?)
diff --git a/index.mdwn b/index.mdwn
index 4e8724e..c5f33db 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -33,7 +33,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
 
 # Case studies
 
- * [Softcom](spamhaus-rpz-case-study.pdf)
+ * [DTU Environment](spamhaus-rpz-case-study.pdf)
 
 # Notes
 

Uploaded RPZ-History-Usage-Research.pdf and referenced it
diff --git a/index.mdwn b/index.mdwn
index e9988a6..4e8724e 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -29,6 +29,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
  * BIND ARM
    * ISC's [BIND ARM](https://kb.isc.org/article/AA-00845/0/BIND-9.9-Administrator-Reference-Manual-ARM.html)
    * Vernon's [copy](http://ss.vix.su/~vjs/rpz-arm.html)
+ * A [more verbose](RPZ-History-Usage-Research.pdf) introduction to RPZ, with some history.
 
 # Case studies
 

attachment upload
diff --git a/RPZ-History-Usage-Research.pdf b/RPZ-History-Usage-Research.pdf
new file mode 100644
index 0000000..134311e
Binary files /dev/null and b/RPZ-History-Usage-Research.pdf differ

diff --git a/index.mdwn b/index.mdwn
index 004efbf..e9988a6 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -6,7 +6,7 @@
 
 # Why is RPZ useful?
 
-The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure at registries or ISPs is not fast enough.  Using RPZ, an administrator can implement their own proteciton policies or receive automated reputation updates feeds from security providers that mintain reputaiton information.
+The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure at registries or ISPs is not fast enough.  Using RPZ, an administrator can implement their own protection policies or receive automated reputation updates feeds from security providers that maintain reputation information.
 
 
 Examples:

Per Ferg
diff --git a/index.mdwn b/index.mdwn
index 3f54ead..004efbf 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -44,7 +44,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
 ## Providers of reputation data
 
   * [DissectCyber](https://service.dissectcyber.com/)'s [rpzone.us](https://service.dissectcyber.com/rpz)
-  * [InternetIdentity](http://www.internetidentity.com/)'s [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
+  * [InternetIdentity's DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
   * [SpamHaus](http://www.spamhaus.com/)'s [DBL](http://www.spamhaus.org/news/article/669/)
   * [SURBL](http://www.surbl.org)'s [Data Feed](http://www.surbl.org/df)
   * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [note](https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)

Fix ThreatStop typo
diff --git a/index.mdwn b/index.mdwn
index bed5bd1..3f54ead 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -47,8 +47,7 @@ Multiple policy zones published by a number of providers (see below) can be chec
   * [InternetIdentity](http://www.internetidentity.com/)'s [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
   * [SpamHaus](http://www.spamhaus.com/)'s [DBL](http://www.spamhaus.org/news/article/669/)
   * [SURBL](http://www.surbl.org)'s [Data Feed](http://www.surbl.org/df)
-  * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
-(https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
+  * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm) and [note](https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
 
 ## Products that can use RPZ
 

change description wording
diff --git a/index.mdwn b/index.mdwn
index 48b2d77..bed5bd1 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -6,7 +6,8 @@
 
 # Why is RPZ useful?
 
-The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure is not fast enough to avoid further damage.  Using RPZ, an administrator can speed up the adoption of blocking policies by preventing users from accessing their DNS information.
+The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure at registries or ISPs is not fast enough.  Using RPZ, an administrator can implement their own proteciton policies or receive automated reputation updates feeds from security providers that mintain reputaiton information.
+
 
 Examples:
 

Add version info.
diff --git a/index.mdwn b/index.mdwn
index ac7ef0e..48b2d77 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -2,7 +2,7 @@
 
 [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone) knows.
 
-<b>D</b>omain <b>N</b>ame <b>S</b>ervice <b>R</b>esponse <b>P</b>olicy <b>Z</b>ones (DNS RPZ) is a method that allows a nameserver administrator to overlay custom information on top of the global DNS to provide alternate responses to queries.  It is currently implemented in the ISC BIND nameserver.
+<b>D</b>omain <b>N</b>ame <b>S</b>ervice <b>R</b>esponse <b>P</b>olicy <b>Z</b>ones (DNS RPZ) is a method that allows a nameserver administrator to overlay custom information on top of the global DNS to provide alternate responses to queries.  It is currently implemented in the ISC BIND nameserver (9.8 or later).
 
 # Why is RPZ useful?
 

Change margin
diff --git a/local.css b/local.css
index 9411262..a456ca9 100644
--- a/local.css
+++ b/local.css
@@ -149,7 +149,7 @@ pre {
   box-shadow: 0px 0px 2px #1a1a1a; }
 
 #content, #comments, #footer {
-  margin: 1em 2em; }
+  margin: 1em 1em; }
 
 #pageinfo {
   border-color: gray; }

Try some font size changes.
diff --git a/local.css b/local.css
index 5ce70d1..9411262 100644
--- a/local.css
+++ b/local.css
@@ -94,7 +94,7 @@ input#searchbox {
 .pageheader .actions ul li a, input[type="submit"] {
   margin: 0.2em;
   padding: 0.2em;
-  font-size: 1.01em;
+  font-size: 1.0em;
   background: gray;
   color: black;
   border-style: solid;
@@ -117,7 +117,7 @@ body {
   *font-size: small;
   color: black;
   background: white;
-  font-size: 1.01em; }
+  font-size: 1.0em; }
 
 a {
   text-decoration: none;
@@ -157,7 +157,7 @@ pre {
 #editcontent, #editmessage {
   width: 90%;
   background: #f2f2f2;
-  font-size: 1.01em;
+  font-size: 1.0em;
   font-family: Consolas, Monaco, "DejaVu Sans Mono", "Bitstream Vera Sans Mono", "Courier New", monospace;
   line-height: 1.4em;
   padding: .5em;
@@ -186,18 +186,18 @@ label[for="editmessage"] {
   border-top: 1px solid gray; }
 
 .inlineheader {
-  font-size: 1.1em;
+  font-size: 1.0em;
   border-top: 2px solid gray; }
 
 /* Smaller headings for inline pages */
 .inlinepage h1 {
-  font-size: 1.1em; }
+  font-size: 1.0em; }
 
 .inlinepage h2 {
-  font-size: 1.01em; }
+  font-size: 1.0em; }
 
 .inlinepage h3 {
-  font-size: 1.01em; }
+  font-size: 1.0em; }
 
 div.recentchanges {
   border-style: none; }
@@ -232,7 +232,7 @@ span.pagelinks {
 span.pagelinks a, span.tags a {
   margin: 0.2em;
   padding: 0.2em;
-  font-size: 1.01em;
+  font-size: 1.0em;
   background: #e6e6e6;
   color: black;
   border-style: solid;

Some highlighting and rewording.
diff --git a/index.mdwn b/index.mdwn
index 0919046..ac7ef0e 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,6 +1,8 @@
-# What is it? (ask [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone))
+# What is it?
 
-DNS RPZ is a method implemented in ISC BIND 9 to give an administrator the ability to modify the responses given to queries utilizing specially crafted zone files that overlay information the global DNS.
+[Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone) knows.
+
+<b>D</b>omain <b>N</b>ame <b>S</b>ervice <b>R</b>esponse <b>P</b>olicy <b>Z</b>ones (DNS RPZ) is a method that allows a nameserver administrator to overlay custom information on top of the global DNS to provide alternate responses to queries.  It is currently implemented in the ISC BIND nameserver.
 
 # Why is RPZ useful?
 

Changes examples text to be more simple. Testing SSL.
diff --git a/index.mdwn b/index.mdwn
index 01df456..0919046 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -8,9 +8,9 @@ The prime motivation for creating this feature was to protect users from badness
 
 Examples:
 
- * If one knows that a hostname or domain name is bad and has no good purpose, the result of a query for that name can be withheld or rewritten to prevent a user from access the service pointed to by that name (email, website).
- * If one knows that an IP address or subnet has no good use, one can configure a policy such that any DNS looup with results in an address in that space can be blocked or redirected.
- * If one knows that a DNS server serves only bad names, one can configure a policy such that any DNS information that is served by that nameserver is blocked or rewritten.
+ * If you know a bad hostname or domain name, you can block people from accessing it or redirect them to a walled garden.
+ * If you know a bad IP address or subnet, you can block users from accessing hostnames that reference it.
+ * If you know a nameserver that doesn't host anything except bad domains, you can block users from accessing DNS information hosted by those nameservers.
 
 Multiple policy zones published by a number of providers (see below) can be checked before a normal answer from the global DNS is used.
 

diff --git a/index.mdwn b/index.mdwn
index f0f35c3..01df456 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,10 +1,8 @@
-# DNS Response Policy Zones (RPZ)
-
-## What is it? (ask [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone))
+# What is it? (ask [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone))
 
 DNS RPZ is a method implemented in ISC BIND 9 to give an administrator the ability to modify the responses given to queries utilizing specially crafted zone files that overlay information the global DNS.
 
-## Why is RPZ useful?
+# Why is RPZ useful?
 
 The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure is not fast enough to avoid further damage.  Using RPZ, an administrator can speed up the adoption of blocking policies by preventing users from accessing their DNS information.
 
@@ -16,31 +14,31 @@ Examples:
 
 Multiple policy zones published by a number of providers (see below) can be checked before a normal answer from the global DNS is used.
 
-## Pointers to resources
+# Pointers to resources
 
  * Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
  * Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
  * Presentations
    * [Barry Greene](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
-   * Webinar - June 2012 Vixie/Rasmussen - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](2012-06-26-Slides.pdf)
+   * Webinar - June 2012 Vixie/Rasmussen - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](RPZ-2012-06-26-Slides.pdf)
  * [ISC Technical Note](https://kb.isc.org/getAttach/21/AA-00512/rpz.txt)
  * ISC's [Knowledge Base](https://kb.isc.org/category/110/0/10/Software-Products/BIND9/Features/DNSRPZ/) articles
  * BIND ARM
    * ISC's [BIND ARM](https://kb.isc.org/article/AA-00845/0/BIND-9.9-Administrator-Reference-Manual-ARM.html)
    * Vernon's [copy](http://ss.vix.su/~vjs/rpz-arm.html)
 
-## Case studies
+# Case studies
 
  * [Softcom](spamhaus-rpz-case-study.pdf)
 
-## Notes
+# Notes
 
  * April's [virtual server for RPZ](https://github.com/secure411dotorg/rpzone) on github
  * Hugo's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github
 
-## RPZ ecosystem
+# RPZ ecosystem
 
-### Providers of reputation data
+## Providers of reputation data
 
   * [DissectCyber](https://service.dissectcyber.com/)'s [rpzone.us](https://service.dissectcyber.com/rpz)
   * [InternetIdentity](http://www.internetidentity.com/)'s [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
@@ -49,17 +47,16 @@ Multiple policy zones published by a number of providers (see below) can be chec
   * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
 (https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
 
-### Products that can use RPZ
+## Products that can use RPZ
 
  * [ISC BIND](http://www.isc.org/downloads/bind/) - versions 9.8 and higher
  * [InfoBlox](http://www.infoblox.com)'s [DNS Firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
 
-### Related services
+## Related services
 
  * [SecurityZones](http://securityzones.net/) – product marketing/sales
  * [Deteque](http://www.deteque.com) – Deteque has provided integration consulting to some of the DNS RPZ providers
 
-## Process: Building RPZ Deployment
+# Process: Building RPZ Deployment
 
 * [[RPZ-Building-Momentum.pdf]]
-

Uplevel most content
diff --git a/index.mdwn b/index.mdwn
index f0f35c3..7f1817c 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,10 +1,8 @@
-# DNS Response Policy Zones (RPZ)
-
-## What is it? (ask [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone))
+# What is it? (ask [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone))
 
 DNS RPZ is a method implemented in ISC BIND 9 to give an administrator the ability to modify the responses given to queries utilizing specially crafted zone files that overlay information the global DNS.
 
-## Why is RPZ useful?
+# Why is RPZ useful?
 
 The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure is not fast enough to avoid further damage.  Using RPZ, an administrator can speed up the adoption of blocking policies by preventing users from accessing their DNS information.
 
@@ -16,7 +14,7 @@ Examples:
 
 Multiple policy zones published by a number of providers (see below) can be checked before a normal answer from the global DNS is used.
 
-## Pointers to resources
+# Pointers to resources
 
  * Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
  * Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
@@ -29,18 +27,18 @@ Multiple policy zones published by a number of providers (see below) can be chec
    * ISC's [BIND ARM](https://kb.isc.org/article/AA-00845/0/BIND-9.9-Administrator-Reference-Manual-ARM.html)
    * Vernon's [copy](http://ss.vix.su/~vjs/rpz-arm.html)
 
-## Case studies
+# Case studies
 
  * [Softcom](spamhaus-rpz-case-study.pdf)
 
-## Notes
+# Notes
 
  * April's [virtual server for RPZ](https://github.com/secure411dotorg/rpzone) on github
  * Hugo's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github
 
-## RPZ ecosystem
+# RPZ ecosystem
 
-### Providers of reputation data
+## Providers of reputation data
 
   * [DissectCyber](https://service.dissectcyber.com/)'s [rpzone.us](https://service.dissectcyber.com/rpz)
   * [InternetIdentity](http://www.internetidentity.com/)'s [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
@@ -49,17 +47,17 @@ Multiple policy zones published by a number of providers (see below) can be chec
   * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
 (https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
 
-### Products that can use RPZ
+## Products that can use RPZ
 
  * [ISC BIND](http://www.isc.org/downloads/bind/) - versions 9.8 and higher
  * [InfoBlox](http://www.infoblox.com)'s [DNS Firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
 
-### Related services
+## Related services
 
  * [SecurityZones](http://securityzones.net/) – product marketing/sales
  * [Deteque](http://www.deteque.com) – Deteque has provided integration consulting to some of the DNS RPZ providers
 
-## Process: Building RPZ Deployment
+# Process: Building RPZ Deployment
 
 * [[RPZ-Building-Momentum.pdf]]
 

More header tweaks
diff --git a/local.css b/local.css
index 4bd3996..5ce70d1 100644
--- a/local.css
+++ b/local.css
@@ -18,7 +18,7 @@
   padding: 8px 8px 8px 8px;
   position: relative;
   overflow: hidden;
-  background: #ffffff;
+  background: #e8e8ff;
   border-color: gray;
   border-style: none none solid none;
   border-width: 1px; }
@@ -35,7 +35,6 @@ h1, h2, h3, h4, h5, h6 {
   color: #202020; }
 
 .header {
-  background: #f0f0ff;
   font-size: 150%; }
 
 h1 {

More style
diff --git a/local.css b/local.css
index 96bf617..4bd3996 100644
--- a/local.css
+++ b/local.css
@@ -32,10 +32,11 @@
 
 h1, h2, h3, h4, h5, h6 {
   font-weight: bold;
-  color: gray; }
+  color: #202020; }
 
 .header {
-  font-size: 200%; }
+  background: #f0f0ff;
+  font-size: 150%; }
 
 h1 {
   font-size: 150%;

Update css.
diff --git a/local.css b/local.css
index 7fb10df..96bf617 100644
--- a/local.css
+++ b/local.css
@@ -42,15 +42,15 @@ h1 {
   border-top: 4px solid gray; }
 
 h2 {
-  font-size: 140%;
+  font-size: 130%;
   border-top: 3px solid gray; }
 
 h3 {
-  font-size: 130%;
+  font-size: 110%;
   border-top: 2px solid gray; }
 
 h4 {
-  font-size: 120%;
+  font-size: 110%;
   border-top: 1px solid gray; }
 
 h5, h6 {

Try ISC local.css.
diff --git a/local.css b/local.css
index 29cabe4..7fb10df 100644
--- a/local.css
+++ b/local.css
@@ -1,439 +1,311 @@
-
-/*
- *
- * 	- Nom: Theme Wiki NanoBlogger Francophone Gris Clair
- * 	- Description : Une page avec un bandeau superieur pour le titre, un bandeau inferieur pour les informations 
- * 	et la modification de la page.
- * 	Contenu interieur auto adaptable.
- *	- Auteur : Blankoworld
- *	- Lien : http://blankoworld.homelinux.com/demo/ikiwiki/contraste/
+/*********************************
+ *  public wiki theme for ikiwiki
  *
- */
-
-body, html {
-	height: 100%;
-	width: 100%;
-	margin: 0;
-	padding: 0;
-	background-color: white;
-	color: black;
-	font-family: Verdana, Arial, Helvetica, sans-serif;
-	font-size:12px;
-}
+ * by Danny Castonguay
+ *********************************/
+/* # HSLA(hue, saturation, lightness,alpha)
+ * ## hue
+ * R:0, O:30, Y:60, G:115, cyan:180, B:220, I:260, V:280, pink:300
+ * ## saturation
+ * 0% is gray, 100% is pure color
+ * ## lightness
+ * 0% is black, 100% is white
+ * ## alpha
+ * 0% is opaque, 100% is transparent
+ *  */
+/* variables copy pasted from the corporate website */
+.pageheader {
+  padding: 8px 8px 8px 8px;
+  position: relative;
+  overflow: hidden;
+  background: #ffffff;
+  border-color: gray;
+  border-style: none none solid none;
+  border-width: 1px; }
+
+.pageheader .header {
+  float: left; }
+
+.title {
+  color: black;
+  font-weight: bold; }
+
+h1, h2, h3, h4, h5, h6 {
+  font-weight: bold;
+  color: gray; }
+
+.header {
+  font-size: 200%; }
 
 h1 {
-	width: 95%;
-	margin-left: 1%;
-	padding: 0 0 0 1%;
-	border-bottom: medium solid black;
-	font-size: 160%;
-}
+  font-size: 150%;
+  border-top: 4px solid gray; }
 
 h2 {
-	width: 90%;
-	margin-left: 2%;
-	padding: 0 0 0 1%;
-	border-bottom: medium solid black;
-	border-left: medium solid black;
-	font-size: 150%;
-}
+  font-size: 140%;
+  border-top: 3px solid gray; }
 
 h3 {
-	width: 85%;
-	margin-left: 3%;
-	padding: 0 0 0 1%;
-	border-bottom: medium solid black;
-	border-left: medium solid black;
-	font-size: 140%;
-}
+  font-size: 130%;
+  border-top: 2px solid gray; }
 
 h4 {
-	width: 80%;
-	margin-left: 4%;
-	padding: 0 0 0 1%;
-	border-bottom: medium solid black;
-	border-left: medium solid black;
-	font-size: 130%;
-}
-
-h5 {
-	width: 75%;
-	margin-left: 5%;
-	padding: 0 0 0 1%;
-	border-bottom: medium solid black;
-	border-left: medium solid black;
-	font-size: 120%;
-}
-
-h6 {
-	width: 70%;
-	margin-left: 6%;
-	padding: 0 0 0 1%;
-	border-bottom: medium solid black;
-	border-left: medium solid black;
-	font-size: 110%;
-}
-
-pre {
-	width: 90%;
-	margin-left: auto;
-	margin-right: auto;
-	overflow: auto;
-	color: black;
-	font-weight: normal;
-	background-color:#eeeeee;
-	padding:2mm;
-	border:2px solid #999999;
-	border-right:1px solid #cccccc;
-	border-bottom:1px solid #cccccc;
-}
-
-code {
-}
+  font-size: 120%;
+  border-top: 1px solid gray; }
+
+h5, h6 {
+  font-size: 110%; }
+
+#searchform {
+  position: absolute;
+  top: 0.5em;
+  right: 2em; }
+
+input#searchbox {
+  border: none;
+  padding: .5em;
+  border-style: solid;
+  border-width: 2px;
+  border-color: gray;
+  -moz-border-radius: 4px;
+  -webkit-border-radius: 4px;
+  border-radius: 4px;
+  -moz-box-shadow: inset 2px 2px 2px #1a1a1a;
+  -webkit-box-shadow: inset 2px 2px 2px #1a1a1a;
+  box-shadow: inset 2px 2px 2px #1a1a1a; }
+
+.pageheader .actions {
+  position: absolute;
+  bottom: 0;
+  right: 2em;
+  width: 100%;
+  text-align: right; }
+
+.pageheader .actions ul {
+  border-style: none; }
+
+.actions ul {
+  padding: 1em;
+  border-style: none; }
+
+.pageheader .actions ul li {
+  padding: 0; }
+
+.pageheader .actions ul li a, input[type="submit"] {
+  margin: 0.2em;
+  padding: 0.2em;
+  font-size: 1.01em;
+  background: gray;
+  color: black;
+  border-style: solid;
+  border-width: 2px;
+  border-color: gray;
+  -moz-border-radius: 4px;
+  -webkit-border-radius: 4px;
+  border-radius: 4px; }
+  .pageheader .actions ul li a:hover, input[type="submit"]:hover {
+    background: #1980e6;
+    color: white; }
+
+div.toggleable#attachments {
+  margin: 1em; }
+

(Diff truncated)
Add files website files to git.
diff --git a/RPZ-2012-06-26-Slides.pdf b/RPZ-2012-06-26-Slides.pdf
new file mode 100644
index 0000000..60df074
Binary files /dev/null and b/RPZ-2012-06-26-Slides.pdf differ
diff --git a/RPZ-Building-Momentum.pdf b/RPZ-Building-Momentum.pdf
new file mode 100644
index 0000000..30c0c07
Binary files /dev/null and b/RPZ-Building-Momentum.pdf differ
diff --git a/index.mdwn b/index.mdwn
new file mode 100644
index 0000000..f0f35c3
--- /dev/null
+++ b/index.mdwn
@@ -0,0 +1,65 @@
+# DNS Response Policy Zones (RPZ)
+
+## What is it? (ask [Wikipedia](http://en.wikipedia.org/wiki/Response_policy_zone))
+
+DNS RPZ is a method implemented in ISC BIND 9 to give an administrator the ability to modify the responses given to queries utilizing specially crafted zone files that overlay information the global DNS.
+
+## Why is RPZ useful?
+
+The prime motivation for creating this feature was to protect users from badness on the Internet based on global identifiers such as host names or the IP addresses or nameservers that the host names point to.  Criminals tend to re-use the same identifiers until they are taken away from them.  Unfortunately, the security industry's ability to take down criminal infrastructure is not fast enough to avoid further damage.  Using RPZ, an administrator can speed up the adoption of blocking policies by preventing users from accessing their DNS information.
+
+Examples:
+
+ * If one knows that a hostname or domain name is bad and has no good purpose, the result of a query for that name can be withheld or rewritten to prevent a user from access the service pointed to by that name (email, website).
+ * If one knows that an IP address or subnet has no good use, one can configure a policy such that any DNS looup with results in an address in that space can be blocked or redirected.
+ * If one knows that a DNS server serves only bad names, one can configure a policy such that any DNS information that is served by that nameserver is blocked or rewritten.
+
+Multiple policy zones published by a number of providers (see below) can be checked before a normal answer from the global DNS is used.
+
+## Pointers to resources
+
+ * Vixie's [Taking Back the DNS](http://www.circleid.com/posts/20100728_taking_back_the_dns/) blog entry
+ * Vixie's [DNS Firewalls in Action](http://www.circleid.com/posts/20120103_dns_firewalls_in_action_rpz_vs_spam/) blog entry
+ * Presentations
+   * [Barry Greene](http://www.slideshare.net/BarryRGreene/binds-new-security-feature-dnsrpz-the-quotdns-firewallquot) –  ISC
+   * Webinar - June 2012 Vixie/Rasmussen - [recording](https://internetconsortevents.webex.com/internetconsortevents/lsr.php?AT=pb&SP=EC&rID=5421832&rKey=6621fe8070465de0%20), [slides](2012-06-26-Slides.pdf)
+ * [ISC Technical Note](https://kb.isc.org/getAttach/21/AA-00512/rpz.txt)
+ * ISC's [Knowledge Base](https://kb.isc.org/category/110/0/10/Software-Products/BIND9/Features/DNSRPZ/) articles
+ * BIND ARM
+   * ISC's [BIND ARM](https://kb.isc.org/article/AA-00845/0/BIND-9.9-Administrator-Reference-Manual-ARM.html)
+   * Vernon's [copy](http://ss.vix.su/~vjs/rpz-arm.html)
+
+## Case studies
+
+ * [Softcom](spamhaus-rpz-case-study.pdf)
+
+## Notes
+
+ * April's [virtual server for RPZ](https://github.com/secure411dotorg/rpzone) on github
+ * Hugo's [RPZ Log Analysis](https://github.com/yesxorno/rpzla) on github
+
+## RPZ ecosystem
+
+### Providers of reputation data
+
+  * [DissectCyber](https://service.dissectcyber.com/)'s [rpzone.us](https://service.dissectcyber.com/rpz)
+  * [InternetIdentity](http://www.internetidentity.com/)'s [DNS firewall](http://internetidentity.com/dns-firewall-implementation-options/)
+  * [SpamHaus](http://www.spamhaus.com/)'s [DBL](http://www.spamhaus.org/news/article/669/)
+  * [SURBL](http://www.surbl.org)'s [Data Feed](http://www.surbl.org/df)
+  * [ThreatStop](http://www.threatstop.com/)'s [DNS firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
+(https://lists.isc.org/pipermail/dnsrpz-interest/2012-June/000122.html)
+
+### Products that can use RPZ
+
+ * [ISC BIND](http://www.isc.org/downloads/bind/) - versions 9.8 and higher
+ * [InfoBlox](http://www.infoblox.com)'s [DNS Firewall](http://www.prweb.com/releases/2013/2/prweb10466833.htm)
+
+### Related services
+
+ * [SecurityZones](http://securityzones.net/) – product marketing/sales
+ * [Deteque](http://www.deteque.com) – Deteque has provided integration consulting to some of the DNS RPZ providers
+
+## Process: Building RPZ Deployment
+
+* [[RPZ-Building-Momentum.pdf]]
+
diff --git a/spamhaus-rpz-case-study.pdf b/spamhaus-rpz-case-study.pdf
new file mode 100644
index 0000000..29bc226
Binary files /dev/null and b/spamhaus-rpz-case-study.pdf differ

Copy file from sec.isc.org (Internal)
diff --git a/local.css b/local.css
new file mode 100644
index 0000000..29cabe4
--- /dev/null
+++ b/local.css
@@ -0,0 +1,439 @@
+
+/*
+ *
+ * 	- Nom: Theme Wiki NanoBlogger Francophone Gris Clair
+ * 	- Description : Une page avec un bandeau superieur pour le titre, un bandeau inferieur pour les informations 
+ * 	et la modification de la page.
+ * 	Contenu interieur auto adaptable.
+ *	- Auteur : Blankoworld
+ *	- Lien : http://blankoworld.homelinux.com/demo/ikiwiki/contraste/
+ *
+ */
+
+body, html {
+	height: 100%;
+	width: 100%;
+	margin: 0;
+	padding: 0;
+	background-color: white;
+	color: black;
+	font-family: Verdana, Arial, Helvetica, sans-serif;
+	font-size:12px;
+}
+
+h1 {
+	width: 95%;
+	margin-left: 1%;
+	padding: 0 0 0 1%;
+	border-bottom: medium solid black;
+	font-size: 160%;
+}
+
+h2 {
+	width: 90%;
+	margin-left: 2%;
+	padding: 0 0 0 1%;
+	border-bottom: medium solid black;
+	border-left: medium solid black;
+	font-size: 150%;
+}
+
+h3 {
+	width: 85%;
+	margin-left: 3%;
+	padding: 0 0 0 1%;
+	border-bottom: medium solid black;
+	border-left: medium solid black;
+	font-size: 140%;
+}
+
+h4 {
+	width: 80%;
+	margin-left: 4%;
+	padding: 0 0 0 1%;
+	border-bottom: medium solid black;
+	border-left: medium solid black;
+	font-size: 130%;
+}
+
+h5 {
+	width: 75%;
+	margin-left: 5%;
+	padding: 0 0 0 1%;
+	border-bottom: medium solid black;
+	border-left: medium solid black;
+	font-size: 120%;
+}
+
+h6 {
+	width: 70%;
+	margin-left: 6%;
+	padding: 0 0 0 1%;
+	border-bottom: medium solid black;
+	border-left: medium solid black;
+	font-size: 110%;
+}
+
+pre {
+	width: 90%;
+	margin-left: auto;
+	margin-right: auto;
+	overflow: auto;
+	color: black;
+	font-weight: normal;
+	background-color:#eeeeee;
+	padding:2mm;
+	border:2px solid #999999;
+	border-right:1px solid #cccccc;
+	border-bottom:1px solid #cccccc;
+}
+
+code {
+}
+
+a {
+	color: darkblue;
+	text-decoration: underline;
+}
+
+a:active {
+	color: darkblue;
+	border: thin inset gray;
+}
+
+a:visited {
+	color: gray;
+	text-decoration: none;
+}
+
+a:hover {
+	text-decoration: underline;
+}
+
+div#pageheader {
+	height: 60px;
+	width: 100%;
+	background-color: #999999;
+}
+
+div#pageheader span {
+	position: relative;
+	top: 16px;
+	left: 26px;
+	color: white;
+	font-weight: bold;
+	font-size: 200%;
+}
+
+div#pageheader form {
+	position: absolute;
+	margin: 0;
+	padding: 0;
+	top: 1%;
+	right: 1%;
+}
+
+div#pageheader form input {
+	border: medium solid black;
+	background-color: white;
+	color: black;
+	font-weight: bold;
+	text-align: left;
+	background-image: url(/demo/ikiwiki/contraste/htdocs/wikiicons/search-bg.gif);
+	background-repeat: no-repeat;
+	background-position: top right;
+}
+
+div.header {
+	position: absolute;
+	height: 20px;
+	width: 100%;
+	padding: 0;
+	top: 60px;
+	left: 0;
+	line-height: 20px;
+	background-color: #999999;
+	font-size: 14px;
+}
+
+div.header span {
+	position: relative;
+	top: 0;
+	left: 5px;
+	color: white;
+}
+
+div.header a {
+	color: white;
+	text-decoration: none;
+}
+
+div.header a:hover {
+	text-decoration: underline;
+}
+
+div#sidebar {
+	position: absolute;
+	height: 28px;
+	width: 100%;
+	top: 80px;
+	left: 0;
+	padding: 0;
+	margin: 0;
+	background-color: #999999;
+	color: white;
+	border-top: 1px solid black;
+	border-bottom: 1px solid black;
+}
+
+div#sidebar ul {
+	height: 28px;
+	margin: 0;
+	padding: 0;
+	list-style-type: none;
+	text-align: left;

(Diff truncated)
initial commit
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..eecda60
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+/.ikiwiki