IETF Logo Mail Archive

RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Fri, 13 May 2011 20:25 UTC

Return-Path: <albert.e.manfredi@boeing.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 BB71AE0798 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 13:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 JvWmyKxt1FSF for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 13:25:47 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by ietfa.amsl.com (Postfix) with ESMTP id 39A60E06C8 for <ipv6@ietf.org>; Fri, 13 May 2011 13:25:47 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p4DKPdqY007265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 May 2011 13:25:40 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p4DKPcMS028743; Fri, 13 May 2011 15:25:39 -0500 (CDT)
Received: from XCH-MWHT-01.mw.nos.boeing.com (xch-mwht-01.mw.nos.boeing.com [134.57.113.35]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p4DKPcwN028706 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 13 May 2011 15:25:38 -0500 (CDT)
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.119.191]) by XCH-MWHT-01.mw.nos.boeing.com ([134.57.113.35]) with mapi; Fri, 13 May 2011 15:25:38 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
Date: Fri, 13 May 2011 15:25:36 -0500
Subject: RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Topic: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Index: AcwRqlMOOXddsDNERam6BZNa8DrfegAAQ6ZQ
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02A8E07651@XCH-MW-08V.mw.nos.boeing.com>
References: <201105131337.p4DDbdao009901@cichlid.raleigh.ibm.com><4462F666-D 0FD-45C1-AE71-0CD70580C110@gmail.com><201105131602.p4DG2L3L010708@cichlid.r aleigh.ibm.com><A4D9C64B-C35A-450D-A43D-D19EC61E6357@gmail.com> <4DCD9110.10000@sri.com>
In-Reply-To: <4DCD9110.10000@sri.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <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 20:25:47 -0000

Ed Jankiewicz wrote:

> 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.

I support SHOULD for DHCPv6 as well.

But responding to the above, purely parenthetically, would DOCSIS be out of the question in a SOHO network? If not, and I think not, then we have been hearing that cable networks do use DHCP. So it would become mandatory is SOHO nets that depend on cable broadband.

Bert

v2.23.0 | Report a Bug | By Email