--- a/draft-ietf-dime-erp-01.xml	Fri Aug 28 11:05:23 2009 +0900
+++ b/draft-ietf-dime-erp-01.xml	Fri Aug 28 17:53:44 2009 +0900
@@ -17,7 +17,7 @@
 ]>
 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
 <?rfc strict="yes"?>
-<?rfc comments="yes"?>
+<?rfc comments="no"?>
 <?rfc inline="yes"?>
 <?rfc editing="no"?>
 <?rfc toc="yes"?>
@@ -182,23 +182,6 @@
       (implicit bootstrapping) or during the first ERP exchange (explicit
       bootstrapping). Security considerations for this key distribution are
       detailed in <xref target="RFC5295"></xref>.</t>
-
-      <section title="Differences with previous version">
-        <t>In this version, the main difference is that we define a new
-        Diameter Application for ERP. This allows the routing of Diameter
-        messages containing ERP payload to the appropriate realm and server,
-        and permits more flexibility in the deployment of ERP : with the
-        previous design from version -00, the ER server had to be collocated
-        with the EAP server (Editor's note: well, it was not written clearly
-        in the document, but it was the only working situation), which might
-        result in some deployment and scalability issues.</t>
-
-        <t>The format of the newly defined AVP has also changed: we now define
-        two grouped AVP to transport the key request and key material. Grouped
-        AVP allow a more efficient parsing of the message, and keeps the
-        correlation of related information such as key name, key
-        lifetime...</t>
-      </section>
     </section>
 
     <section title="Terminology">