--- 1/draft-ietf-bfd-v4v6-1hop-06.txt	2008-01-17 08:12:34.000000000 +0100
+++ 2/draft-ietf-bfd-v4v6-1hop-07.txt	2008-01-17 08:12:34.000000000 +0100
@@ -1,19 +1,19 @@
 
 Network Working Group                                           D. Katz
 Internet Draft                                         Juniper Networks
                                                                 D. Ward
                                                           Cisco Systems
-Expires: September, 2007                                    March, 2007
+Expires: July, 2008                                       January, 2008
 
                    BFD for IPv4 and IPv6 (Single Hop)
-                    draft-ietf-bfd-v4v6-1hop-06.txt
+                    draft-ietf-bfd-v4v6-1hop-07.txt
 
 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), its areas, and its working groups.  Note that
@@ -181,27 +181,27 @@
    A number of mechanisms are available to tunnel IPv4 and IPv6 over
    arbitrary topologies.  If the tunnel mechanism does not decrement the
    TTL or hop count of the network protocol carried within, the
    mechanism described in this document may be used to provide liveness
    detection for the tunnel.  The BFD Authentication mechanism SHOULD be
    used and is strongly encouraged.
 
 Normative References
 
    [BFD] Katz, D., and Ward, D., "Bidirectional Forwarding Detection",
-       draft-ietf-bfd-base-06.txt, March, 2007.
+       draft-ietf-bfd-base-07.txt, January, 2008.
 
    [BFD-GENERIC] Katz, D., and Ward, D., "Generic Application of BFD",
-       draft-ietf-bfd-generic-03.txt, March, 2007 .
+       draft-ietf-bfd-generic-04.txt, January, 2008.
 
    [GTSM] Gill, V., et al, "The Generalized TTL Security Mechanism
-       (GTSM)", RFC 3682, February 2004.
+       (GTSM)", RFC 5082, October, 2007.
 
    [KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate
        Requirement Levels", RFC 2119, March 1997.
 
 Security Considerations
 
    In this application, the use of TTL=255 on transmit and receive is
    viewed as supplying equivalent security characteristics to other
    protocols used in the infrastructure, as it is not trivially
    spoofable.  The security implications of this mechanism are further
@@ -261,30 +261,30 @@
    http://www.ietf.org/ipr.
 
    The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at ietf-
    ipr@ietf.org.
 
 Full Copyright Notice
 
-   Copyright (C) The IETF Trust (2007).
+   Copyright (C) The IETF Trust (2008).
 
    This document is subject to the rights, licenses and restrictions
    contained in BCP 78, and except as set forth therein, the authors
    retain all their rights.
 
    This document and the information contained herein are provided on an
    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 
 Acknowledgement
 
    Funding for the RFC Editor function is currently provided by the
    Internet Society.
 
-   This document expires in September, 2007.
+   This document expires in July, 2008.