Address Resolution Protocol - Revision history

Jnc: Chaos confusion fix

2023-12-12T16:14:42Z

Chaos confusion fix

← Older revision		Revision as of 16:14, 12 December 2023
Line 1:		Line 1:
	The '''Address Resolution Protocol''' (usually given as its acronym, '''ARP''') is a networking [[protocol]] which is used to translate from the [[address]]es used by the [[internetworking layer]] of a particular [[protocol suite\|protocol family]] (e.g. [[Chaosnet]], or the [[Internet Protocol]] of [[TCP/IP]]) to those used by a particular [[physical network]] (e.g. [[Ethernet]]), in cases where a non-trivial [[mapping]] is required between the addresses used by the internet protocol, and the addresses used by the physical network.		The '''Address Resolution Protocol''' (usually given as its acronym, '''ARP''') is a networking [[protocol]] which is used to translate from the [[address]]es used by the [[internetworking layer]] of a particular [[protocol suite\|protocol family]] (e.g. [[Chaosnet\|Chaos]], or the [[Internet Protocol]] of [[TCP/IP]]) to those used by a particular [[physical network]] (e.g. [[Ethernet]]), in cases where a non-trivial [[mapping]] is required between the addresses used by the internet protocol, and the addresses used by the physical network.

	==Background==		==Background==

Jnc: /* Background */ link MAC

2022-07-11T14:39:34Z

Background: link MAC

← Older revision		Revision as of 14:39, 11 July 2022
Line 5:		Line 5:
	Originally, all physical networks had addresses which were relatively short (e.g. 24 [[bit]]s in the [[ARPANET]]; 8 bits in the [[Chaosnet]] [[local area network\|LAN]]) and those were carried directly in the low order bits of the addresses of the internetworking layer of the particular protocol family.		Originally, all physical networks had addresses which were relatively short (e.g. 24 [[bit]]s in the [[ARPANET]]; 8 bits in the [[Chaosnet]] [[local area network\|LAN]]) and those were carried directly in the low order bits of the addresses of the internetworking layer of the particular protocol family.

	With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.		With the advent of the 10 Mbit/second Ethernet, which had 48-bit [[Media Access Control Address\|physical addresses]] (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.

	==External links==		==External links==

Jnc: /* Background */ move Ethernet address description to Ethernet

2022-07-11T02:42:39Z

Background: move Ethernet address description to Ethernet

← Older revision		Revision as of 02:42, 11 July 2022
Line 6:		Line 6:

	With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.		With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.

	The 48-bit physical address of the Ethernet is known as the '''[[Media Access Control Address]]''' (short: '''MAC Address''' or just: '''MAC'''), sometimes '''Ethernet Address''' or '''Hardware Address''' (the last is rather misleading if not explicitly used related to Ethernet networking).

	==External links==		==External links==

Vaxorcist: /* Background */ Corrected link

2022-07-09T07:52:40Z

Background: Corrected link

← Older revision		Revision as of 07:52, 9 July 2022
Line 7:		Line 7:
	With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.		With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.

	The 48-bit physical address of the Ethernet is known as the '''[[~~MAC Address\|~~Media Access Control Address]]''' (short: '''MAC Address''' or just: '''MAC'''), sometimes '''Ethernet Address''' or '''Hardware Address''' (the last is rather misleading if not explicitly used related to Ethernet networking).		The 48-bit physical address of the Ethernet is known as the '''[[Media Access Control Address]]''' (short: '''MAC Address''' or just: '''MAC'''), sometimes '''Ethernet Address''' or '''Hardware Address''' (the last is rather misleading if not explicitly used related to Ethernet networking).

	==External links==		==External links==

Vaxorcist: /* Background */ Changed wording / formatting

2022-07-03T17:58:22Z

Background: Changed wording / formatting

← Older revision		Revision as of 17:58, 3 July 2022
Line 7:		Line 7:
	With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.		With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.

	The 48-bit physical address of the Ethernet is known as the [['''MAC Address\|Media Access Control Address''']] (short: MAC Address or just: MAC), sometimes '''Ethernet Address''' or '''Hardware Address''' (rather misleading).		The 48-bit physical address of the Ethernet is known as the '''[[MAC Address\|Media Access Control Address]]''' (short: '''MAC Address''' or just: '''MAC'''), sometimes '''Ethernet Address''' or '''Hardware Address''' (the last is rather misleading if not explicitly used related to Ethernet networking).

	==External links==		==External links==

Vaxorcist: /* Background */ MAC Address added

2022-07-03T17:31:09Z

Background: MAC Address added

← Older revision		Revision as of 17:31, 3 July 2022
Line 6:		Line 6:

	With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.		With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.

			The 48-bit physical address of the Ethernet is known as the [['''MAC Address\|Media Access Control Address''']] (short: MAC Address or just: MAC), sometimes '''Ethernet Address''' or '''Hardware Address''' (rather misleading).

	==External links==		==External links==

Jnc: +cat

2021-11-06T12:28:33Z

+cat

← Older revision		Revision as of 12:28, 6 November 2021
Line 11:		Line 11:
	* [https://datatracker.ietf.org/doc/html/rfc826 An Ethernet Address Resolution Protocol] - protocol spec		* [https://datatracker.ietf.org/doc/html/rfc826 An Ethernet Address Resolution Protocol] - protocol spec

			[[Category: Network Protocols]]
	[[Category: Networking]]		[[Category: Networking]]

Jnc: Still needs an outline of the basic protocol mechanism, but this is a good start

2021-10-27T08:52:06Z

Still needs an outline of the basic protocol mechanism, but this is a good start

New page

The '''Address Resolution Protocol''' (usually given as its acronym, '''ARP''') is a networking [[protocol]] which is used to translate from the [[address]]es used by the [[internetworking layer]] of a particular [[protocol suite|protocol family]] (e.g. [[Chaosnet]], or the [[Internet Protocol]] of [[TCP/IP]]) to those used by a particular [[physical network]] (e.g. [[Ethernet]]), in cases where a non-trivial [[mapping]] is required between the addresses used by the internet protocol, and the addresses used by the physical network.

==Background==

Originally, all physical networks had addresses which were relatively short (e.g. 24 [[bit]]s in the [[ARPANET]]; 8 bits in the [[Chaosnet]] [[local area network|LAN]]) and those were carried directly in the low order bits of the addresses of the internetworking layer of the particular protocol family.

With the advent of the 10 Mbit/second Ethernet, which had 48-bit physical addresses (so that all Ethernet [[network interface]]s could be assigned a guaranteed-unique physical address at manufacturing time), this was no longer true. Use of static, manually-configured tables to hold the required mappings was clearly infeasible, so ARP was designed.

==External links==

* [https://datatracker.ietf.org/doc/html/rfc826 An Ethernet Address Resolution Protocol] - protocol spec

[[Category: Networking]]