[dhcwg] Naming conventions for DHCPv[46] options

[Ralph Droms <rdroms at cisco.com>]

During my review of draft-ietf-capwap-dhc-ac-option, it occurred to me  
that we should establish some BCP for naming options that have  
essentially identical DHCPv4 and DHCPv6 counterparts.  For example,  
RFC 5192 (DHCP options for PANA auth agents) uses the same name,  
OPTION_PANA_AGENT, for both the DHCPv4 and DHCPv6 options. draft-ietf- 
ecrit-dhc-lost-discovery-03.txt (DHCP options for LOST discovery),  
uses OPTION_V4_LOST and OPTION_V6_LOST.  draft-ietf-capwap-dhc-ac- 
option uses OPTION_CAPWAP_AC_V4 and OPTION_CAPWAP_AC_V6.

I don't have a strong preference.  Using the same name for both  
options seems sensible for the IANA listing of option codes, as the  
DHCPv4 and DHCPv6 options are listed separately.  Using different  
names seems sensisble for developers, as different names for the two  
option codes would be needed if the same application supplies both  
DHCPv4 and DHCPv6 services.

Any opinions from the WG?

- Ralph

_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg