DHCP: What is the diff between "client" and "your" IP?

[Technologov]

Hi,

Looking at DHCP RFC2131 - What is the diff between "client" and "your" IP?

ciaddr 4 Client IP address; only filled in if client is in
BOUND, RENEW or REBINDING state and can respond
to ARP requests.
yiaddr 4 'your' (client) IP address.

I read it, but still don't understand.
In reality clients often fill both fields with same value.
But is there any distinction ?

[GarryRicketson]

DHCP: What is the diff between "client" and "your" IP?

Edited:DHCP: What is the difference between client and your IP?

[dasein]

Punctuation problems render GarryR's suggested query terms above less than helpful, but his larger point is well taken: search before you post (especially if you imagine that you've got the chops to specify a new Internet protocol, which you apparently do).

Ironically enough, your question contains its own answer by citing RFC 2131. If you're not sure what "can respond to ARP requests" means, then you've identified a gap in your knowledge that you can fill with a few minutes at your favorite search engine. But when the spec contains limiting language for one field and not for the other, it's a pretty safe bet that that's the "difference."

[Technologov]

Both answers not very helpful.
And first search gives me exactly zero useful results. (Google is not _that_ good)

Anyway, "client IP" allows to query extra parameters about "your IP" from a different interface with a different IP, which I think is redundant. (since client can spoof IP).
But this thing is not very clear at first sight from an RFC. It took me several reads.

basically I think DHCP can work just as well without "client IP" field, getting away only with "your address" field.