--- 1/draft-ietf-bfd-base-07.txt 2008-03-24 23:12:16.000000000 +0100 +++ 2/draft-ietf-bfd-base-08.txt 2008-03-24 23:12:16.000000000 +0100 @@ -1,19 +1,19 @@ Network Working Group D. Katz Internet Draft Juniper Networks D. Ward Cisco Systems -Expires: July, 2008 January, 2008 +Expires: September, 2008 March, 2008 Bidirectional Forwarding Detection - draft-ietf-bfd-base-07.txt + draft-ietf-bfd-base-08.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 @@ -312,22 +312,21 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Version (Vers) The version number of the protocol. This document defines protocol version 1. Diagnostic (Diag) A diagnostic code specifying the local system's reason for the - last session state change to states Down or AdminDown. Values - are: + last change in session state. Values are: 0 -- No Diagnostic 1 -- Control Detection Time Expired 2 -- Echo Function Failed 3 -- Neighbor Signaled Session Down 4 -- Forwarding Plane Reset 5 -- Path Down 6 -- Concatenated Path Down 7 -- Administratively Down 8 -- Reverse Concatenated Path Down @@ -1223,22 +1222,22 @@ The remote discriminator for this BFD session. This is the discriminator chosen by the remote system, and is totally opaque to the local system. This MUST be initialized to zero. If a period of a Detection Time passes without the receipt of a valid, authenticated BFD packet from the remote system, this variable MUST be set to zero. bfd.LocalDiag The diagnostic code specifying the reason for the most recent - local session state change to states Down or AdminDown. This - MUST be initialized to zero (No Diagnostic.) + change in the local session state. This MUST be initialized to + zero (No Diagnostic.) bfd.DesiredMinTxInterval The minimum interval, in microseconds, between transmitted BFD Control packets that this system would like to use at the current time. The actual interval is negotiated between the two systems. This MUST be initialized to a value of at least one second (1,000,000 microseconds) according to the rules described in section 6.8.3. The setting of this variable is otherwise outside the scope of this specification. @@ -2004,27 +2003,21 @@ Dave Ward Cisco Systems 170 W. Tasman Dr. San Jose, CA 95134 USA Phone: +1-408-526-4000 Email: dward@cisco.com Changes from the Previous Draft - A correction was made to the description of Demand mode in section - 6.6. Another correction was made to the interaction between timing - changes and the transmission of a Poll Sequence in section 6.8.3. - The requirement to clear bfd.RemoteDiscr when the remote system falls - silent was added to section 6.8.1. The continuing transmission of - Control packets in AdminDown state was added to section 6.8.16. All - other changes are purely editorial in nature. + All changes are purely editorial in nature. IPR Notice The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights. The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to @@ -2062,11 +2055,11 @@ 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 July, 2008. + This document expires in September, 2008.