RFC3511防火墙性能基准测试方法借鉴.pdf资源-CSDN文库

版权申诉

182 浏览量 2021-12-25 23:01:03 上传评论收藏 167KB PDF 举报

资源推荐

资源详情

资源评论

测评技术体系

之测试方法篇

（测试文档）

RFC3511 Benchmarking Methodology for Firewall Performance ，2003.4

北京国信网安信息系统测评技术实验室

测评技术文章

第 2 页共 28 页

Benchmarking Methodology for Firewall Performance

RFC3511 ，2003.4

Network Working Group B. Hickman

Request for Comments: 3511 Spirent Communications

Category: Informational D. Newman

Network Test

S. Tadjudin

Spirent Communications

T. Martin

GVNW Consulting Inc

Status of this Memo

This memo provides information for the Internet community. It does not specify an

Internet standard of any kind. Distribution of this memo is unlimited.

Abstract

This document discusses and defines a number of tests that may be used to describe

the performance characteristics of firewalls. In addition to defining the tests, this

document also describes specific formats for reporting the results of the tests. This

document is a product of the Benchmarking Methodology Working Group (BMWG) of the

Internet Engineering Task Force (IETF).

1 INTRODUCTION · ·········································································································· 4

2 REQUIREMENTS ·········································································································· 4

3 SCOPE ·························································································································· 5

4 TEST SETUP ················································································································· 5

4.1 T

EST

ONSIDERATIONS

···························································································· 6

4.2 VIRTUAL CLIENTS /SERVERS ······················································································ 6

4.3 T

EST

RAFFIC

EQUIREMENTS

················································································· 6

4.4 DUT/SUT T

RAFFIC

LOWS

······················································································· 6

4.5 MULTIPLE CLIENT /SERVER TESTING ·········································································· 7

4.6 N

ETWORK

DDRESS

RANSLATION

(NAT) ································································· 7

4.7 R

ULE

ETS

·············································································································· 7

4.8 W

ACHING

·········································································································· 7

4.9 A

UTHENTICATION

······································································································ 7

4.10 TCP S

TACK

ONSIDERATIONS

·················································································· 8

5 BENCHMARKING TESTS ····························································································· 8

5.1 IP T

HROUGHPUT

······································································································ 8

5.1.1 Objective ········································································································· 8

5.1.2 Setup Parameters ··························································································· 8

测评技术文章

第 3 页共 28 页

5.1.3 Procedure ········································································································ 8

5.1.4 Measurement ·································································································· 8

5.1.5 Reporting Format ···························································································· 9

5.2 C

ONCURRENT

TCP C

ONNECTION

APACITY

····························································· 9

5.2.1 Objective ········································································································· 9

5.2.2 Setup Parameters ··························································································· 9

5.2.3 Procedure ······································································································ 10

5.2.4 Measurements ······························································································ 10

5.2.5 Reporting Format ·························································································· 11

5.3 M

AXIMUM

TCP C

ONNECTION

STABLISHMENT

ATE

··············································· 11

5.3.1 Objective ······································································································· 11

5.3.2 Setup Parameters ························································································· 12

5.3.3 Procedure ······································································································ 12

5.3.4 Measurements ······························································································ 12

5.3.5 Reporting Format ·························································································· 13

5.4 M

AXIMUM

TCP C

ONNECTION

EAR

OWN

ATE

····················································· 13

5.4.1 Objective ······································································································· 13

5.4.2 Setup Parameters ························································································· 14

5.4.3 Procedure ······································································································ 14

5.4.4 Measurements ······························································································ 14

5.4.5 Reporting Format ·························································································· 15

5.5 D

ENIAL

ERVICE

ANDLING

··············································································· 15

5.5.1 Objective ······································································································· 15

5.5.2 Setup Parameters ························································································· 15

5.5.3 5.5.3 Procedure ····························································································· 15

5.5.4 Measurements ······························································································ 16

5.5.5 Reporting Format ·························································································· 16

5.6 HTTP T

RANSFER

ATE

·························································································· 16

5.6.1 Objective ······································································································· 16

5.6.2 Setup Parameters ························································································· 16

5.6.3 Procedure ······································································································ 17

5.6.4 Measurements ······························································································ 17

5.6.5 Reporting Format ·························································································· 18

5.7 M

AXIMUM

HTTP T

RANSACTION

ATE

····································································· 19

5.7.1 Objective ······································································································· 19

5.7.2 Setup Parameters ························································································· 19

5.7.3 Procedure ······································································································ 19

5.7.4 Measurements ······························································································ 20

5.7.5 Reporting Format ·························································································· 20

5.8 I

LLEGAL

RAFFIC

ANDLING

···················································································· 20

5.8.1 Objective ······································································································· 20

5.8.2 Setup Parameters ························································································· 20

5.8.3 Procedure ······································································································ 21

5.8.4 Measurements ······························································································ 21

测评技术文章

第 4 页共 28 页

5.8.5 Reporting Format ·························································································· 21

5.9 IP F

RAGMENTATION

ANDLING

················································································ 21

5.9.1 Objective ······································································································· 21

5.9.2 Setup Parameters ························································································· 21

5.9.3 Procedure ······································································································ 22

5.9.4 Measurements ······························································································ 22

5.9.5 Reporting Format ·························································································· 23

5.10 L

ATENCY

················································································································ 23

5.10.1 Objective ······································································································· 23

5.10.2 Setup Parameters ························································································· 23

5.10.3 Network-layer procedure ··············································································· 23

5.10.4 Application layer procedure ·········································································· 24

5.10.5 Measurements ······························································································ 24

5.10.6 Network-layer reporting format ····································································· 24

5.10.7 Application-layer reporting format ································································· 25

6 REFERENCES · ··········································································································· 25

6.1 N

ORMATIVE

EFERENCES

······················································································· 25

6.2 I

NFORMATIVE

EFERENCES

···················································································· 25

7 SECURITY CONSIDERATIONS · ················································································ 25

8 APPENDIX A: HTTP (HYPERTEXT TRANSFER PROTOCOL) ································· 26

9 APPENDIX B: CONNECTION ESTABLISHMENT TIME MEASUREMENTS · ··········· 26

10 APPENDIX C: CONNECTION TEAR DOWN TIME MEASUREMENTS · ··············· 27

11 AUTHORS' ADDRESSES ························································································ 27

1 Introduction

This document provides methodologies for the performance benchmarking of firewalls.

It covers four areas: forwarding, connection, latency and filtering. In addition to defining

tests, this document also describes specific formats for reporting test results. A previous

document, "Benchmarking Terminology for Firewall Performance" [1], defines many of the

terms that are used in this document. The terminology document SHOULD be consulted

before attempting to make use of this document.

2 Requirements

In this document, the words that are used to define the significance of each particular

requirement are capitalized. These words are:

"MUST" ，This word, or the words "REQUIRED" and "SHALL" mean that the item is an

absolute requirement of the specification.

"SHOULD" ，This word or the adjective "RECOMMENDED" means that there may exist

valid reasons in particular circumstances to ignore this item, but the full implications

测评技术文章

第 5 页共 28 页

should be understood and the case carefully weighed before choosing a different course.

"MAY" ，This word or the adjective "OPTIONAL" means that this item is truly optional.

One vendor may choose to include the item because a particular marketplace requires it or

because it enhances the product, for example; another vendor may omit the same item.

An implementation is not compliant if it fails to satisfy one or more of the MUST

requirements. An implementation that satisfies all the MUST and all the SHOULD

requirements is said to be "unconditionally compliant"; one that satisfies all the MUST

requirements but not all the SHOULD requirements is said to be "conditionally compliant".

3 Scope

Firewalls can control access between networks. Usually, a firewall protects a private

network from public or shared network(s) to which it is connected. A firewall can be as

simple as a single device that filters packets or as complex as a group of devices that

combine packet filtering and application-level proxy and network translation services.

This document focuses on benchmarking firewall performance, wherever possible,

independent of implementation.

4 Test Setup

Test configurations defined in this document will be confined to dual-homed and

tri-homed as shown in figure 1 and figure 2 respectively.

Firewalls employing dual-homed configurations connect two networks. One interface

of the firewall is attached to the unprotected network [1], typically the public network

(Internet). The other interface is connected to the protected network [1], typically the

internal LAN. In the case of dual-homed configurations, servers which are made

accessible to the public (Unprotected) network are attached to the private (Protected)

network.

+----------+ +----------+

| | | +----------+ | | |

| Servers/ |----| | | |------| Servers/ |

| | |-------| DUT/SUT |--------| | |

+----------+ | | | | +----------+

Protected | +----------+ | Unprotected

Network | | Network

Figure 1 (Dual-Homed)

Tri-homed [1] configurations employ a third segment called a Demilitarized Zone

(DMZ). With tri-homed configurations, servers accessible to the public network are

attached to the DMZ. Tri-Homed configurations offer additional security by separating

server(s) accessible to the public network from internal hosts.

+----------+ +----------+

| | | +----------+ | | |

| Clients |----| | | |------| Servers/ |

+----------+ |-------| DUT/SUT |--------| | |

| | | | +----------+

| +----------+ |

Protected | | | Unprotected

Network | Network

剩余27页未读，继续阅读

评论收藏

内容反馈

版权申诉

cy18065918457

粉丝: 0
资源: 7万+

RFC3511防火墙性能基准测试方法借鉴.pdf

RFC3511防火墙性能基准测试方法.pdf

MIDH-S-TP-026移动终端触摸屏性能技术要求及测试方法V1.0---试运行版本借鉴.pdf

ASTMD429-81-橡胶性能测试方法标准——刚性基体粘着力测试借鉴.pdf

纺织品吸湿发热性能测试方法借鉴.pdf

RFC3511测试 .pdf

RFC2544性能测试方法及测试标准归纳.pdf

RFC 2889以太网转发性能测试实验.pdf

防火墙性能测试(RFC2544)

论文研究-路由器动态性能指标测试方法研究.pdf

RFC3550中文版.pdf

RFC3093_防火墙增进协议 (FEP).doc

RFC2544丢包率测试——信而泰网络测试仪实操.pdf

rfc3511 Firewall performance

SAP接口RFC[借鉴].pdf

Linux防火墙中RFC算法的应用(2).pdf

RFC 文档 （共74个）

RFC3918测试 .pdf

RFC2544网络基准测试

rfc5416.pdf

rfc2327_SDP.pdf

rfc5415.pdf

rfc3511.rar_RFC3511_RFC3511概述_rfc 3511_rfc35_什么是RFC3511

JDK 1.8 64位.rar

SoftCnKiller2.54.zip（因为要下载码，弃用不更新了）

编译好的64位pycdc.exe(支持python3.10和python3.11)

常用3D点云数据免费下载.rar

工程伦理的期末考试题库

ISO26262标准(中文版)下载.pdf

NFC-Reader-Tool-电脑版.zip

最新资源

RFC 文档（共74个）