--- 1/draft-ietf-dhc-dhcpv6-interop-00.txt	2006-02-04 23:03:00.000000000 +0100
+++ 2/draft-ietf-dhc-dhcpv6-interop-01.txt	2006-02-04 23:03:00.000000000 +0100
@@ -1,17 +1,17 @@
 
 Network Working Group                                           R. Droms
 Internet-Draft                                             Cisco Systems
-Expires: August 23, 2003                               February 22, 2003
+Expires: October 7, 2003                                   April 8, 2003
 
      Results from Interoperability Tests of DHCPv6 Implementations
-                  draft-ietf-dhc-dhcpv6-interop-00.txt
+                  draft-ietf-dhc-dhcpv6-interop-01.txt
 
 Status of this Memo
 
    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet-
    Drafts.
@@ -20,21 +20,21 @@
    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."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt.
 
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.
 
-   This Internet-Draft will expire on August 23, 2003.
+   This Internet-Draft will expire on October 7, 2003.
 
 Copyright Notice
 
    Copyright (C) The Internet Society (2003).  All Rights Reserved.
 
 Abstract
 
    This document publishes issues with the DHCPv6 protocols
    specifications, based on the results of interoperability testing
    among several implementations.
@@ -45,23 +45,22 @@
    Standard, and several related specifications have been published and
    will soon be submitted to the IESG for review.  Several
    implementations of DHCPv6 have been completed, and these
    implementations have been tested for interoperability.
 
    The purpose of this document is to provide a published record of the
    issues discovered through interoperability testing, for review and
    discussion by the appropriate IETF working groups.
 
    A course of action to correct problems with the DHCPv6 specifications
-   is proposed for many of the listed issues.  Any changes to the
-   specifications will be published to the appropriate working group
-   mailing lists.
+   is proposed for many of the listed issues.  These changes will be
+   made to the DHCPv6 specification prior to its publication as an RFC.
 
    The remainder of this documents lists specific issues, along with a
    summary of any discussion of the issue that has already occurred
    through e-mail and a proposed course of action to correct the issue.
 
    Throughout this document, unless otherwise qualified, section
    references and numbers refer to draft-ietf-dhc-dhcpv6-28.
 
 1. Response of servers to Renew and Rebind messages, sections 18.2.3 and
    18.2.4
@@ -263,22 +262,22 @@
          Servers MUST discard any received Renew message that meets any
          of the following conditions:
 
          +  the message MUST include a Server Identifier option
 
          +  the contents of the Server Identifier option MUST match the
             server's identifier
 
          +  ...
 
-      However, there should be a wording problem.  The first sentence
-      should read:
+      However, there is a wording problem.  The first sentence should
+      read:
 
          Servers MUST discard any received Renew message that fails to
          meet any of the following conditions:
 
    Resolution: Review and reword appropriate text in section 15 for
       consistency and correctness.
 
 8. Typographic error regarding MRC in section 18.1.6
 
    Issue: In the following line of Section 18.1.6: