Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

I support the idea of making DHCPv6 a SHOULD, and like the text revision 
proposed by Bob as amended by Ralph.

As to the clarification of what to do in the event of inconsistent 
information when both methods are used, I agree that RFC 4862 covers 
it.   If pushed, citing that RFC would be better than incorporating text.

The comment from Tim that the DHCPv6 man not be of use in SOHO 
deployments, I think SHOULD still leaves enough wiggle room for a 
variety of implementations with different feature sets.

On 5/13/2011 12:22 PM, Ralph Droms wrote:
> On May 13, 2011, at 12:02 PM 5/13/11, Thomas Narten wrote:
>
>> Bob,
>>
>> Bob Hinden<bob.hinden@gmail.com>  writes:
>>
>>> While I support changing the requirement to a SHOULD, I would prefer
>>> the text to be something like:
>>>      	<t>  DHCPv6<xref target='RFC3315' />  can be used to obtain and
>>> 	configure addresses. In general, a network may provide for the
>>> 	configuration of addresses through Router Advertisements,
>>> 	DHCPv6 or both.   There will be a wide range of IPv6 deployment models
>>>         and differences in address assignment requirements.  Consequently all hosts
>>> 	SHOULD implement address configuration via DHCP.</t>
>>> It's not just about what some operators may or may not do.  For
>>> example enterprises, governments, etc. will also have specific
>>> requirements.
>> I like this text better than what I proposed as well.
> Here's my contribution, trying to make an explicit link between the last two sentences:
>
>          <t>  DHCPv6<xref target='RFC3315' />  can be used to obtain and
> 	configure addresses. In general, a network may provide for the
> 	configuration of addresses through Router Advertisements,
> 	DHCPv6 or both.  There will be a wide range of IPv6 deployment
> 	models and differences in address assignment requirements,
> 	some of which may require DHCPv6 for address assignment.
> 	Consequently all hosts SHOULD implement address configuration
> 	via DHCPv6.</t>
>
>> Thanks,
>> Thomas
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
Edward J Jankiewicz, Senior Technical Advisor
ESG/ISD - Center for Navigation and Survivability Systems
SRI International, Inc.
edward.jankiewicz@sri.com
Direct:  443-502-5815
Google Voice:  908-718-1335