RFC-Ref is not longer maintained; use RFC browser at: http://zvon.org/comp/r/ref-RFC.html
RFC 2544:Benchmarking Methodology for Network Inte...
RFC-Ref

address


Click on the red underlined text to get to the source

... addressed to the hardware broadcast address are received. In bridges (or in bridge ...
... with 1% frames addressed to the hardware broadcast address. The frames sent to the broadcast address ...
... address. The frames sent to the broadcast address should be of a type that the router will not need to process. The aim of this test is to ...
... filter SHOULD be of the form: forward input_protocol_address to output_protocol_address ...
... forward input_protocol_address to output_protocol_address In bridges ...
... forward destination_hardware_address The DUT ...
... filters SHOULD be of the form: block input_protocol_address to output_protocol_address ...
... block input_protocol_address to output_protocol_address The 24 input and output protocol addresses ...
... address The 24 input and output protocol addresses SHOULD not be any that are represented in the test data stream. The last filter ...
... Filter Addresses ...
... Two sets of filter addresses are required, one for the single filter case and one for the 25 filter ...
... The single filter case should permit traffic from IP address 198.18.1.2 to IP address 198.19.65.2 and deny all other traffic ...
... traffic from IP address 198.18.1.2 to IP address 198.19.65.2 and deny all other traffic. ...


... Protocol addresses ...
... It is easier to implement these tests using a single logical stream of data, with one source protocol address and one destination protocol address ...
... address and one destination protocol address, and for some conditions like the filters described above, a practical requirement ...
... hardware for bridge tests) source and destination address pair. The tests SHOULD then be repeated with using a random destination address. While testing routers ...
... destination address pair. The tests SHOULD then be repeated with using a random destination address. While testing routers the addresses ...
... destination address. While testing routers the addresses SHOULD be random and uniformly distributed over a range of 256 networks ...
... range for bridges. The specific address ranges to use for IP are ...


... routing information necessary to forward the test stream, especially in the multiple address case, will be manually set up. At the start of each trial a routing ...
... update MUST include all of the network addresses that will be required for the trial. All of the addresses SHOULD resolve to the same "next-hop ...
... network addresses that will be required for the trial. All of the addresses SHOULD resolve to the same "next-hop". Normally this will be the address ...
... addresses SHOULD resolve to the same "next-hop". Normally this will be the address of the receiving side of the test equipment. This routing ...


... run using the same data rate being offered to each of the input ports. The addresses in the input data streams SHOULD be set so that a frame will be directed to each of the output ports ...


... This document does not address the issue of testing the effects of a mixed protocol environment other than to suggest that if such tests are wanted then frames SHOULD be distributed between all of the test ...


... This document does not address the issue of testing the effects of a mixed frame size environment other than to suggest that if such tests are wanted then frames SHOULD be distributed between all of the ...


... seconds to be sure that the learning has settled. Bridge learning frames are frames with source addresses that are the same as the destination addresses used by the test frames. Learning frames for ...
... frames are frames with source addresses that are the same as the destination addresses used by the test frames. Learning frames for other protocols are used to prime the address resolution tables in ...
... destination addresses used by the test frames. Learning frames for other protocols are used to prime the address resolution tables in the DUT. The formats of the learning frame that should be used are ...


... Address resolution ...
... The DUT SHOULD be able to respond to address resolution requests sent by the DUT wherever the protocol requires such a process. ...


... Editors' Addresses ...


... C.2.2 Protocol Addresses ...
... Two sets of addresses must be defined: first the addresses assigned to the router ...
... Two sets of addresses must be defined: first the addresses assigned to the router ports ...
... to the router ports, and second the address that are to be used in the frames themselves and in the routing updates. ...
... The network addresses 192.18.0.0 through 198.19.255.255 are have been assigned to the BMWG by the IANA ...
... were to be accidentally connected to part of the Internet. The specific use of the addresses is detailed below. ...
... C.2.2.1 Router port protocol addresses ...
... IP Class C network addresses from 198.18.1.0 to 198.18.64.0 have been assigned for use on the "input" ports. A second series from ...
... network. For example, a two port DUT would have an IP address of 198.18.1.1 on one port and 198.19.1.1 on the other port ...
... connection to the DUT. The management access address for the DUT is assumed to be the first of the "input" ports ...
... C.2.2.2 Frame addresses ...
... network routing (the reboot time test for example). The IP address used in the test frame is that of node 2 on the appropriate Class ...
... A series of Class C network addresses from 198.18.65.0 to 198.18.254.0 has been assigned for use as the networks accessible ...
... In most protocols a procedure is used to determine the mapping between the protocol node address and the MAC address. The Address Resolution Protocol (ARP ...
... between the protocol node address and the MAC address. The Address Resolution Protocol (ARP) is used to perform this function in TCP/IP ...
... node address and the MAC address. The Address Resolution Protocol (ARP) is used to perform this function in TCP/IP. ...
... TCP/IP. No such procedure is required in XNS or IPX because the MAC address is used as the protocol node address ...
... MAC address is used as the protocol node address. In the ideal case the tester would be able to respond to ARP ...
... router will cache the MAC address of the requesting device. The ARP request should be sent 5 seconds before the test frame stream ...
... (see section C.24). This update includes the network addresses that are reachable through a phantom router on the network ...
... full mesh test, one destination network address is present in the routing update ...
... i.e. "input" port #1 and "output" port #1. Addresses must be changed if the frame is to be used for other ports. ...
... FF FF FF dest MAC address send to broadcast address ...
... MAC address send to broadcast address 06 xx xx xx xx xx xx set to source MAC address ...
... broadcast address 06 xx xx xx xx xx xx set to source MAC address 12 08 06 ARP type ...
... 16 08 00 protocol type IP = 800 18 06 hardware address length 48 bits on Ethernet ...
... on Ethernet 19 04 protocol address length 4 octets for IP ...
... IP 20 00 01 opcode request = 1 22 xx xx xx xx xx xx source MAC address 28 xx xx xx xx source IP address ...
... 22 xx xx xx xx xx xx source MAC address 28 xx xx xx xx source IP address 32 FF FF ...
... FF FF requesting DUT's MAC address 38 xx xx xx xx DUT's IP address ...
... MAC address 38 xx xx xx xx DUT's IP address ...
... FF FF FF dest MAC address is broadcast 06 xx xx xx xx xx xx source hardware address ...
... MAC address is broadcast 06 xx xx xx xx xx xx source hardware address 12 08 00 type ...
... 24 C4 8D header checksum 26 xx xx xx xx source IP address 30 xx xx xx destination IP address ...
... 26 xx xx xx xx source IP address 30 xx xx xx destination IP address 33 FF host ...
... IP 48 00 00 0 50 xx xx xx net 1 IP address 53 00 net not node ...
... IP 68 00 00 0 70 xx xx xx net 2 IP address 73 00 net not node ...
... IP 88 00 00 0 90 xx xx xx net 3 IP address 93 00 net not node ...
... IP 108 00 00 0 110 xx xx xx net 4 IP address 113 00 net not node ...
... IP 128 00 00 0 130 00 net 5 IP address 133 00 net not node ...
... IP 148 00 00 0 150 xx xx xx net 6 IP address 153 00 net not node ...
... HEADER offset data (hex) description 00 xx xx xx xx xx xx set to dest MAC address 06 xx xx xx xx xx xx set to source MAC address ...
... 00 xx xx xx xx xx xx set to dest MAC address 06 xx xx xx xx xx xx set to source MAC address 12 08 00 type ...
... 24 C4 8D header checksum* 26 xx xx xx xx set to source IP address** 30 xx xx xx xx set to destination IP address** ...
... 26 xx xx xx xx set to source IP address** 30 xx xx xx xx set to destination IP address** -- UDP ...



Google
Web
RFC-Ref