--- 1/draft-ietf-dime-agent-overload-07.txt	2016-12-02 13:13:07.787770360 -0800
+++ 2/draft-ietf-dime-agent-overload-08.txt	2016-12-02 13:13:07.823771139 -0800
@@ -1,19 +1,19 @@
 
 Diameter Maintenance and Extensions (DIME)                    S. Donovan
 Internet-Draft                                                    Oracle
-Updates: RFC7683 (if approved)                          December 1, 2016
+Updates: RFC7683 (if approved)                          December 2, 2016
 Intended status: Standards Track
-Expires: June 4, 2017
+Expires: June 5, 2017
 
           Diameter Agent Overload and the Peer Overload Report
-                 draft-ietf-dime-agent-overload-07.txt
+                 draft-ietf-dime-agent-overload-08.txt
 
 Abstract
 
    This specification documents an extension to RFC 7683 (Diameter
    Overload Indication Conveyance (DOIC)) base solution.  The extension
    defines the Peer overload report type.  The initial use case for the
    Peer report is the handling of occurrences of overload of a Diameter
    agent.
 
 Requirements
@@ -30,21 +30,21 @@
    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 June 4, 2017.
+   This Internet-Draft will expire on June 5, 2017.
 
 Copyright Notice
 
    Copyright (c) 2016 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -82,21 +82,23 @@
        6.1.2.  OC-Peer-Algo  . . . . . . . . . . . . . . . . . . . .  14
      6.2.  OC-OLR AVP  . . . . . . . . . . . . . . . . . . . . . . .  14
        6.2.1.  OC-Report-Type AVP  . . . . . . . . . . . . . . . . .  15
      6.3.  SourceID  . . . . . . . . . . . . . . . . . . . . . . . .  15
      6.4.  Attribute Value Pair flag rules . . . . . . . . . . . . .  15
    7.  IANA  Considerations  . . . . . . . . . . . . . . . . . . . .  16
      7.1.  AVP codes . . . . . . . . . . . . . . . . . . . . . . . .  16
      7.2.  New registries  . . . . . . . . . . . . . . . . . . . . .  16
    8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
    9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
-   10. Normative References  . . . . . . . . . . . . . . . . . . . .  17
+   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
+     10.1.  Informative References . . . . . . . . . . . . . . . . .  17
+     10.2.  Normative References . . . . . . . . . . . . . . . . . .  17
    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17
 
 1.  Introduction
 
    This specification documents an extension to the Diameter Overload
    Indication Conveyance (DOIC) [RFC7683] base solution.  The extension
    defines the Peer overload report type.  The initial use case for the
    Peer report is the handling of occurrences of overload of a Diameter
    agent.
 
@@ -730,46 +732,45 @@
 
 9.  Acknowledgements
 
    Adam Roach and Eric McMurry for the work done in defining a
    comprehensive Diameter overload solution in draft-roach-dime-
    overload-ctrl-03.txt.
 
    Ben Campbell for his insights and review of early versions of this
    document.
 
-10.  Normative References
+10.  References
 
-   [I-D.ietf-dime-doic-rate-control]
-              Donovan, S. and E. Noel, "Diameter Overload Rate Control",
-              draft-ietf-dime-doic-rate-control-03 (work in progress),
-              March 2016.
+10.1.  Informative References
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
               <http://www.rfc-editor.org/info/rfc2119>.
 
-   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
-              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
-              DOI 10.17487/RFC5226, May 2008,
-              <http://www.rfc-editor.org/info/rfc5226>.
+   [RFC7068]  McMurry, E. and B. Campbell, "Diameter Overload Control
+              Requirements", RFC 7068, DOI 10.17487/RFC7068, November
+              2013, <http://www.rfc-editor.org/info/rfc7068>.
+
+10.2.  Normative References
+
+   [I-D.ietf-dime-doic-rate-control]
+              Donovan, S. and E. Noel, "Diameter Overload Rate Control",
+              draft-ietf-dime-doic-rate-control-03 (work in progress),
+              March 2016.
 
    [RFC6733]  Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
               Ed., "Diameter Base Protocol", RFC 6733,
               DOI 10.17487/RFC6733, October 2012,
               <http://www.rfc-editor.org/info/rfc6733>.
 
-   [RFC7068]  McMurry, E. and B. Campbell, "Diameter Overload Control
-              Requirements", RFC 7068, DOI 10.17487/RFC7068, November
-              2013, <http://www.rfc-editor.org/info/rfc7068>.
-
    [RFC7683]  Korhonen, J., Ed., Donovan, S., Ed., Campbell, B., and L.
               Morand, "Diameter Overload Indication Conveyance",
               RFC 7683, DOI 10.17487/RFC7683, October 2015,
               <http://www.rfc-editor.org/info/rfc7683>.
 
 Author's Address
 
    Steve Donovan
    Oracle
    7460 Warren Parkway, Suite 300