Key RARP limitations
RARP is a user process but works over link layer directly =>
- RARP server system dependent
- Needs to interface with link layer driver directly => separate filters and direct access to hardware needed
Returns only IP address
- Booting and configuration params not returned even though there is space in packet
- Host needs ICMP and TFTP to complete booting
Can’t relay RARP requests to a central server.
- Need RARP server per broadcast domain