Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Wes Beebee <wbeebee@cisco.com> Fri, 13 May 2011 17:46 UTC

Return-Path: <wbeebee@cisco.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 8A61EE073D for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 10:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.135
X-Spam-Level:
X-Spam-Status: No, score=-7.135 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 UYaXpr9WiCk4 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 10:45:59 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by ietfa.amsl.com (Postfix) with ESMTP id 49908E0764 for <ipv6@ietf.org>; Fri, 13 May 2011 10:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wbeebee@cisco.com; l=3487; q=dns/txt; s=iport; t=1305308759; x=1306518359; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=CJHmHNBq3hG1kQyfYlVYksUvO5lQQhzq8p5nslvA2+w=; b=miLOf7xf3dyI4+FiJNlIFxqnt6pDUv1Pi5JTnTikp1c4hn3lZRUIV93h jUAPWH6LBDCAbHXCa3z0t7lBuE5M7qQb+CFVrTud16nycqY479KjpJLt2 HgeRQuk5Aol+jRf1NeIcx9/2i4SiKqgNWwz2OJHt3sJ4EMGVTOfUn7cQ0 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmMGAL9tzU2tJV2c/2dsb2JhbACCZIY7nAZjAneIcJ58ng2GFQSQBoQ4hmmDbQ
X-IronPort-AV: E=Sophos; i="4.64,365,1301875200"; d="scan'208,217"; a="232942911"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rtp-iport-1.cisco.com with ESMTP; 13 May 2011 17:45:58 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p4DHjwYl030352; Fri, 13 May 2011 17:45:58 GMT
Received: from xmb-rcd-201.cisco.com ([72.163.62.208]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 13 May 2011 12:45:58 -0500
Received: from 161.44.175.134 ([161.44.175.134]) by XMB-RCD-201.cisco.com ([72.163.62.208]) with Microsoft Exchange Server HTTP-DAV ; Fri, 13 May 2011 17:45:57 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Fri, 13 May 2011 13:45:56 -0400
Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
From: Wes Beebee <wbeebee@cisco.com>
To: Cameron Byrne <cb.list6@gmail.com>, Thomas Narten <narten@us.ibm.com>
Message-ID: <C9F2E694.12C3E9%wbeebee@cisco.com>
Thread-Topic: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Index: AcwRlZx62FmSYIBMt0+ZoOJ5cP/lsQ==
In-Reply-To: <BANLkTinGw5fOSAvCYikkBYA3P-wAUo7JWw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3388139157_1141138"
X-OriginalArrivalTime: 13 May 2011 17:45:58.0008 (UTC) FILETIME=[9DAD4780:01CC1195]
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 17:46:00 -0000

>> New:
>>
>>        <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.  Some operators have indicated that they do
>>        not intend to support stateless address autoconfiguration on
>>        their networks and will require all address assignments be
>>        made through DHCPv6. On such networks, devices that support
>>        only stateless address autoconfiguration will be unable to
>>        automatically configure addresses. Consequently all hosts
>>        SHOULD implement address configuration via DHCP.</t>
>>
>>
>> Is this acceptable?
>>
>> Please respond yes or no. Given the WG's previous hesitation to having
>> DHCPv6 be a SHOULD, it is important that we get a clear indication of
>> whether or not the WG supports this change.
>>

> Yes. I support the new text.

+1 

Note that this is a MUST for equipment in Cable networks, although I do
understand that there will be significant networks that won¹t rely on DHCPv6
in other deployment scenarios.

- Wes