6 Jan 2006 00:43
RE: draft-forte-dhc-passive-dad-00.txt - client ID support
Barr Hibbs <rbhibbs <at> pacbell.net>
2006-01-05 23:43:03 GMT
2006-01-05 23:43:03 GMT
sorry to have taken so long to reply to you, Andrea.... comments are in-line.... --Barr > -----Original Message----- > From: Andrea G Forte > Sent: Monday, December 05, 2005 10:00 > > >>[Andrea] > >>We know exactly from which Relay Agent/network > >>segment the request came from (or where a rogue > >>user is located). Usually the DHCP server looks > >>at the 'giaddr' field to tell from which Relay > >>Agent the request is coming from. The 'giaddr' > >>field contains the IP address of the Relay Agent > >>nearest to the *client* requesting the IP address. > >> > >>>From RFC 3046: > >>" [...] the relay agent SHALL forward any > >>received DHCP packet with a valid non-zero giaddr > >>WITHOUT adding any relay agent options. Per RFC > >>2131, it shall also NOT modify the giaddr value." > >> > >>Also, I do not see why the AUC can't just send > >>the information directly to the DHCP server > >>without involving any Relay Agent. > >>(Continue reading)
implementations which don't support multiple IAs
but this is far from to be the rule.
Which RFC define or recommend it? Why?
=> RFC 3315 which defines IAs. As there should be at least one IA per
used type (NA/TA/PD) and per client interface, and IAs are identified
by IAIDs, this suggests multiple IAs are common...
Regards
Francis.Dupont <at> point6.net
PS: TAHI DHCPv6 tests have a multiple IA configuration flag (I remember
because this flag is not documented so I'd to find what it is
RSS Feed