draft-ietf-bmwg-ospfconv-intraarea-09.txt   draft-ietf-bmwg-ospfconv-intraarea-10.txt 
Network Working Group Vishwas Manral Network Working Group Vishwas Manral
Internet Draft Netplane Systems Internet Draft Netplane Systems
Russ White Russ White
Cisco Systems Cisco Systems
Aman Shaikh Aman Shaikh
Expiration Date: December 2004 University of California Expiration Date: December 2004 University of California
File Name: draft-bmwg-ospfconv-intraarea-09.txt June 2004 File Name: draft-ietf-bmwg-ospfconv-intraarea-10.txt June 2004
Benchmarking Basic OSPF Single Router Control Plane Convergence Benchmarking Basic OSPF Single Router Control Plane Convergence
draft-ietf-bmwg-ospfconv-intraarea-09.txt draft-ietf-bmwg-ospfconv-intraarea-10.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet Drafts are working documents of the Internet Engineering Internet Drafts are working documents of the Internet Engineering
Task Force (IETF), its Areas, and its Working Groups. Note that other Task Force (IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet Drafts. groups may also distribute working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or obsoleted by months. Internet Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet other documents at any time. It is not appropriate to use Internet
Drafts as reference material or to cite them other than as a "working Drafts as reference material or to cite them other than as a "working
draft" or "work in progress". draft" or "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This document may not be modified, and derivative works of it may not Copyright Notice
be created, except to publish it as an RFC and to translate it into
languages other than English. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This draft provides suggestions for measuring OSPF single router This draft provides suggestions for measuring OSPF single router
control plane convergence. Its initial emphasis is on the control control plane convergence. Its initial emphasis is on the control
plane of single OSPF routers. We do not address forwarding plane plane of single OSPF routers. We do not address forwarding plane
performance. performance.
NOTE: Within this document, the word convergence relates to single NOTE: Within this document, the word convergence relates to single
router control plane convergence only. router control plane convergence only.
skipping to change at page 14, line 31 skipping to change at page 14, line 31
Thanks to Howard Berkowitz, (hcb@clark.net), for his encouragement Thanks to Howard Berkowitz, (hcb@clark.net), for his encouragement
and support. Thanks also to Alex Zinin (zinin@psg.net), Gurpreet and support. Thanks also to Alex Zinin (zinin@psg.net), Gurpreet
Singh (Gurpreet.Singh@SpirentCom.COM), and Yasuhiro Ohara Singh (Gurpreet.Singh@SpirentCom.COM), and Yasuhiro Ohara
(yasu@sfc.wide.ad.jp) for their comments as well. (yasu@sfc.wide.ad.jp) for their comments as well.
10. Normative References 10. Normative References
[OPSF]Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OPSF]Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[TERM]Manral, V., "OSPF Convergence Testing Terminology and Con- [TERM]Manral, V., "OSPF Convergence Testing Terminology and Con-
cepts", draft-ietf-bmwg-ospfconv-term-08, June 2004 cepts", draft-ietf-bmwg-ospfconv-term-10, June 2004
[CONSIDERATIONS] [CONSIDERATIONS]
Manral, V., "Considerations When Using Basic OSPF Convergence Manral, V., "Considerations When Using Basic OSPF Convergence
Benchmarks", draft-ietf-bmwg-ospfconv-applicability-06, June Benchmarks", draft-ietf-bmwg-ospfconv-applicability-07, June
2004 2004
[RFC2119] [RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997 Levels", BCP 14, RFC 2119, March 1997
11. Informative References 11. Informative References
[INTERCONNECT] [INTERCONNECT]
Bradner, S., McQuaid, J., "Benchmarking Methodology for Network Bradner, S., McQuaid, J., "Benchmarking Methodology for Network
skipping to change at page 16, line 5 skipping to change at page 16, line 5
riw@cisco.com riw@cisco.com
Aman Shaikh Aman Shaikh
AT&T Labs (Research) AT&T Labs (Research)
180, Park Av 180, Park Av
Florham Park, NJ 07932 Florham Park, NJ 07932
ashaikh@research.att.com ashaikh@research.att.com
13. Full Copyright Statement Intellectual Property Statement
Copyright (C) The Internet Society (2004). This document is subject The IETF takes no position regarding the validity or scope of any Intel-
to the rights, licenses and restrictions contained in BCP 78, and lectual Property Rights or other rights that might be claimed to pertain
except as set forth therein, the authors retain all their rights. to the implementation or use of the technology described in this docu-
ment or the extent to which any license under such rights might or might
not be available; nor does it represent that it has made any independent
effort to identify any such rights. Information on the procedures with
respect to rights in RFC documents can be found in BCP 78 and BCP 79.
This document and the information contained herein are provided on an Copies of IPR disclosures made to the IETF Secretariat and any
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS assurances of licenses to be made available, or the result of an attempt
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET made to obtain a general license or permission for the use of such
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, proprietary rights by implementers or users of this specification can be
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFOR- obtained from the IETF on-line IPR repository at
MATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES http://www.ietf.org/ipr.
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
14. Intellectual Property 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 stan-
dard. Please address the information to the IETF at ietf-ipr@ietf.org.
By submitting this Internet-Draft, I certify that any applicable Disclaimer of Warranty
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
The IETF takes no position regarding the validity or scope of any This document and the information contained herein are provided on an
Intellectual Property Rights or other rights that might be claimed to "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
pertain to the implementation or use of the technology described in IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
this document or the extent to which any license under such rights ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
might or might not be available; nor does it represent that it has INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMA-
made any independent effort to identify any such rights. Information TION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
on the procedures with respect to rights in RFC documents can be MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copyright Statement
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this specifica-
tion can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any Copyright (C) The Internet Society (2004). This document is subject to
copyrights, patents or patent applications, or other proprietary the rights, licenses and restrictions contained in BCP 78, and except as
rights that may cover technology that may be required to implement set forth therein, the authors retain all their rights.
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/