RE: [dhcwg] ID's: Interface Information Option

["Kostur, Andre" <[e-mail]>]

	-----Ursprüngliche Nachricht-----
> 	Von:	Kostur, Andre [SMTP:[e-mail]]
> 	Gesendet am:	Dienstag, 4. November 2003 00:15
> 	An:	'Rentschler, Markus'; [e-mail]
> 	Betreff:	RE: [dhcwg] ID's: DHCP Discovery Extensions /
> Interface Informati on Option
> 
> 
> 	Regarding: DHCP Interface Information Option 
> 
> 	- According to RFC 2131, a DHCP Server MUST NOT supply 
> a Parameter
> Request List option to a client (in OFFER, ACK, or NAK), thus a server
> cannot request this option.
> 
> 	[MR>]  Ok. Then a client that has multiple interfaces 
> SHOULD always
> send the Interface Information Option to the server, without 
> any request.
> That wouldn't violate the restriction you've mentioned.

Assuming that a client SHOULD always send the IIO to the server, what does
it fill it with in the original Discover?  At this point it has never
recieved a Server->Client packet.

What benefit does this particular option give over simply using the existing
Client Identifier (Opt 61) to encode such information? (Which still doesn't
address what happens on the original Discover)

You note in section 1:

   The relay agent information option [RFC 3046], which is added by
   a relay agent to a client's request to the server, contains in its
   Circuit ID sub option the number of the physical interface on which
   the relay received this client's request..

Keep in mind that devices using opt 82 aren't required to have a circuit ID.
The wording of the above should reflect that a device MAY add a circuit ID.
As well, the service cannot assume what the contents of a Circuit ID
represents.