draft-ietf-bmwg-ospfconv-term-09.txt   draft-ietf-bmwg-ospfconv-term-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-term-09.txt June 2004 File Name: draft-ietf-bmwg-ospfconv-term-10.txt June 2004
OSPF Benchmarking Terminology and Concepts OSPF Benchmarking Terminology and Concepts
draft-bmwg-ospfconv-term-09.txt draft-ietf-bmwg-ospfconv-term-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 explains the terminology and concepts used in OSPF This draft explains the terminology and concepts used in OSPF
benchmarking. While some of these terms may be defined elsewhere, and benchmarking. While some of these terms may be defined elsewhere, and
we will refer the reader to those definitions in some cases, we also we will refer the reader to those definitions in some cases, we also
include discussions concerning these terms as they relate include discussions concerning these terms as they relate
specifically to the tasks involved in benchmarking the OSPF protocol. specifically to the tasks involved in benchmarking the OSPF protocol.
1. Specification of Requirements 1. Specification of Requirements
skipping to change at page 8, line 32 skipping to change at page 8, line 32
The authors would like to thank Howard Berkowitz (hcb@clark.net), The authors would like to thank Howard Berkowitz (hcb@clark.net),
Kevin Dubray, (kdubray@juniper.net), Scott Poretsky Kevin Dubray, (kdubray@juniper.net), Scott Poretsky
(sporetsky@avici.com), and Randy Bush (randy@psg.com) for their dis- (sporetsky@avici.com), and Randy Bush (randy@psg.com) for their dis-
cussion, ideas, and support. cussion, ideas, and support.
9. Normative References 9. Normative References
[BENCHMARK] [BENCHMARK]
Manral, V., "Benchmarking Basic OSPF Single Router Control Plane Manral, V., "Benchmarking Basic OSPF Single Router Control Plane
Convergence", draft-bmwg-ospfconv-intraarea-09, May 2004. Convergence", draft-bmwg-ospfconv-intraarea-10, May 2004.
[OSPF]Moy, J., "OSPF Version 2", RFC 2328, April 1998. [OSPF]Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[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
10. Informative References 10. Informative References
[OSPF-SCALING] [OSPF-SCALING]
skipping to change at page 10, line 5 skipping to change at page 9, line 38
riw@cisco.com riw@cisco.com
Aman Shaikh Aman Shaikh
University of California University of California
School of Engineering School of Engineering
1156 High Street 1156 High Street
Santa Cruz, CA 95064 Santa Cruz, CA 95064
aman@soe.ucsc.edu aman@soe.ucsc.edu
12. 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
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFOR-
MATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
13. Intellectual Property made to obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can be
obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
By submitting this Internet-Draft, I certify that any applicable The IETF invites any interested party to bring to its attention any
patent or other IPR claims of which I am aware have been disclosed, copyrights, patents or patent applications, or other proprietary rights
and any of which I become aware will be disclosed, in accordance with that may cover technology that may be required to implement this stan-
RFC 3668. dard. Please address the information to the IETF at ietf-ipr@ietf.org.
The IETF takes no position regarding the validity or scope of any Disclaimer of Warranty
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document 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.
Copies of IPR disclosures made to the IETF Secretariat and any This document and the information contained herein are provided on an
assurances of licenses to be made available, or the result of an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
attempt made to obtain a general license or permission for the use of IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
such proprietary rights by implementers or users of this specifica- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
tion can be obtained from the IETF on-line IPR repository at INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMA-
http://www.ietf.org/ipr. TION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF invites any interested party to bring to its attention any Full Copyright Statement
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement Copyright (C) The Internet Society (2004). This document is subject to
this standard. Please address the information to the IETF at ietf- the rights, licenses and restrictions contained in BCP 78, and except as
ipr@ietf.org. set forth therein, the authors retain all their rights.
 End of changes. 

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