Just thought this would be of interest to the firewalls group interested
in firewall performance testing. It doesn't address firewalls
specifically but is a good reference and may even have some
applicability. I know what I'm reading on the toilet this weekend (The
best place for peace and [relative] quiet :). The URL works.
RFC Editor wrote:
>
> A new Request for Comments is now available in online RFC libraries.
>
> RFC 1944:
>
> Title: Benchmarking Methodology for Network Interconnect
> Devices
> Author: S. Bradner & J. McQuaid
> Date: May 1996
> Mailbox: sob @
harvard .
edu, jmcquaid @
baynetworks .
com
> Pages: 30
> Characters: 66,061
> Updates/Obsoletes: none
>
> URL: ftp://ds.internic.net/rfc/rfc1944.txt
>
> This document discusses and defines a number of tests that may be used
> to describe the performance characteristics of a network
> interconnecting device. In addition to defining the tests this
> document also describes specific formats for reporting the results of
> the tests. Appendix A lists the tests and conditions that we believe
> should be included for specific cases and gives additional information
> about testing practices. Appendix B is a reference listing of maximum
> frame rates to be used with specific frame sizes on various media and
> Appendix C gives some examples of frame formats to be used in testing.
> This RFC is the product of the Benchmarking Methodology Working Group
> of the IETF.
>
> This memo provides information for the Internet community. This memo
> does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST @
CNRI .
RESTON .
VA .
US .
Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST @
ISI .
EDU .
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info @
ISI .
EDU with the message body
> help: ways_to_get_rfcs. For example:
>
> To: rfc-info @
ISI .
EDU
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to admin @
DS .
INTERNIC .
NET .
Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR @
ISI .
EDU .
Please consult RFC 1543, Instructions to RFC
> Authors, for further information.
>
> Joyce K. Reynolds
> USC/Information Sciences Institute
>
> ...
>
> Below is the data which will enable a MIME compliant Mail Reader
> implementation to automatically retrieve the ASCII version
> of the RFCs.
>
> ---------------------------------------------------------------
>
> Content-Type: text/plain
> Content-ID: <960517094846 .
RFC @
ISI .
EDU>
>
> SEND /rfc/rfc1944.txt
>
> ---------------------------------------------------------------
>
> Content-Type: text/plain
> Content-ID: <960517094846 .
RFC @
ISI .
EDU>
--
Adam Safier
CSC-SED-Infosec
asafier @
csc .
com
"Oh No! You did exactly what I told you to do!"
- Cartoon caption, author unknown (but I'm looking. :)
The above are my own opinions,
and I'm proud to live in a country where I'm free to express them!
Follow-Ups:
|
|
