IETF Logo Mail Archive

Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Thomas Narten <narten@us.ibm.com> Fri, 13 May 2011 16:03 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8D35E069B for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 09:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zWg7-FSQj8wy for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 09:03:37 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 3B694E0685 for <ipv6@ietf.org>; Fri, 13 May 2011 09:03:37 -0700 (PDT)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p4DFnf01010522 for <ipv6@ietf.org>; Fri, 13 May 2011 09:49:41 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p4DG3P0T033168 for <ipv6@ietf.org>; Fri, 13 May 2011 10:03:25 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p4DG3LpY023152 for <ipv6@ietf.org>; Fri, 13 May 2011 10:03:24 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-244-19.mts.ibm.com [9.65.244.19]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p4DG2MRB018453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 May 2011 10:02:24 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p4DG2L3L010708; Fri, 13 May 2011 12:02:21 -0400
Message-Id: <201105131602.p4DG2L3L010708@cichlid.raleigh.ibm.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
In-reply-to: <4462F666-D0FD-45C1-AE71-0CD70580C110@gmail.com>
References: <201105131337.p4DDbdao009901@cichlid.raleigh.ibm.com> <4462F666-D0FD-45C1-AE71-0CD70580C110@gmail.com>
Comments: In-reply-to Bob Hinden <bob.hinden@gmail.com> message dated "Fri, 13 May 2011 08:55:48 -0700."
Date: Fri, 13 May 2011 12:02:21 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2011 16:03:37 -0000

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.

Thanks,
Thomas

v2.23.0 | Report a Bug | By Email