Re: [dhcwg] Adoption call for draft-shen-dhc-client-port-03 - Respond by October 24, 2016

["Naiming Shen (naiming)" <[e-mail]>]

Support the adoption as a co-author.

We have encountered this issue in scalable wireless controllers.

This dhc draft/extension is better than the other approaches:
 (1) have a front-end process to cache and remember the
     dhcp client information, when the return message
     comes back from the DHCP/DHCPv6 server, will
     do the match and dispatch the message to the correct process.
     This sort of defeats the purpose of using multi-processes
 (2) each relay process uses a different IP addresses.
     it's probably fine for IPv6 addresses, but for
     IPv4, that's not a good solution. And this also
     puts the restriction on the relay to server domain
     has to be a private IP address domain.
     Besides, the multiple IP addresses increases the
     operational management and provisioning, and the
     mechanism can be prone to user errors.



and it’s optional for dhcp relay.

thanks.
- Naiming

On Oct 7, 2016, at 7:44 AM, Bernie Volz (volz) <[e-mail]<mailto:[e-mail]>> wrote:

Hi:

This message initiates a two week long WG adoption call (respond by Oct 24, 2016) on:

Title: Generalized Source UDP Port of DHCP Relay
Pages: 7
Date: 2016-08-19
Document: draft-shen-dhc-client-port-03
Link: https://tools.ietf.org/html/draft-shen-dhc-client-port-03

This was presented at the Berlin IETF-96 (see https://www.ietf.org/proceedings/96/slides/slides-96-dhc-3.pdf) The hum after the presentation for adoption was soft for adoption, and silent against.

Substantive comments and statements of support for adopting this document should be directed to the mailing list. Minor editorial suggestions can be sent to the authors. The co-chairs will determine the consensus after October 24, 2016.

-          Tomek & Bernie

_______________________________________________
dhcwg mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/dhcwg