[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dhcwg] about mip6-hiopt I-D



 In your previous mail you wrote:

=> I was on holidays for one week so I am catching old mails.
   
   The parameters covers the policy and specific home/local HA
  information. So, this information will be delivered to the DHCP
  server from the NAS, and finally to the MN.
   
=> I only disagree about the word "the" before DHCP server because
DHCP includes support of parallel/multiple servers.

   Therefore, I don't think that iterative DHCP query to the remote
  DHCP servers is an efficient way for home network information
  discovery.

=> I don't understand the "iterative" here: nothing in DHCP is iterative,
requests are sent in parallel (because of the multicast) and multiple
replies are merged by clients (this can be complex but is a part of
the design).

   The home network parameters are a specific information to the
  requesting MN and different from the DNS server information which is
  usually shared to all nodes.
   
=> I agree but I can't see why you say this.

   2. I remeber that we already had a discussion on this as below. You
  proposed this concept as a name of agent-concep, that is, if the
  relay can answer to the request, it replies to the MN as a server,
  otherwise it acts as a relay and forwards the request to the other
  servers/relays.
   
=> this is the most efficient way to implement a direct reply but
as I said you have not to enter into implementation details: you
should specify the result (in term of service) and keep enough
flexibility to allow any reasonable way to provide it.

Note you don't answer to my message in the DHC WG list...

Thanks

Francis.Dupont at fdupont.fr
_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg