Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

Thomas Narten <narten@us.ibm.com> Tue, 24 May 2011 00:10 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 A8EF6E07F2 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2011 17:10:35 -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=[AWL=0.000, 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 0lVIaVFlsZ+r for <ipv6@ietfa.amsl.com>; Mon, 23 May 2011 17:10:17 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 9BBAFE06DB for <ipv6@ietf.org>; Mon, 23 May 2011 17:10:17 -0700 (PDT)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e33.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p4O031mA001462 for <ipv6@ietf.org>; Mon, 23 May 2011 18:03:01 -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 p4O0AB6d135034 for <ipv6@ietf.org>; Mon, 23 May 2011 18:10:11 -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 p4O0AAYx028596 for <ipv6@ietf.org>; Mon, 23 May 2011 18:10:10 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-221-88.mts.ibm.com [9.65.221.88]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p4O0A9KS028586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 May 2011 18:10:10 -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 p4O0A4SA015678; Mon, 23 May 2011 20:10:09 -0400
Message-Id: <201105240010.p4O0A4SA015678@cichlid.raleigh.ibm.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
In-reply-to: <BANLkTin0CyuPJv7DYwn-XHi8aa42OSVwsw@mail.gmail.com>
References: <C9F53B85.11BE93%john_brzozowski@cable.comcast.com> <201105232010.p4NKAV9X012654@cichlid.raleigh.ibm.com> <53E999C4-E50D-49C9-9B02-8AD7B5641905@gmail.com> <BANLkTinByCkcvd6=wLE6=9h1xLX16AhPVQ@mail.gmail.com> <201105232111.p4NLBScJ013180@cichlid.raleigh.ibm.com> <BANLkTi=uTPff5Xgb=iCQP+w+x_irriNagQ@mail.gmail.com> <201105232348.p4NNmqHJ015491@cichlid.raleigh.ibm.com> <BANLkTin0CyuPJv7DYwn-XHi8aa42OSVwsw@mail.gmail.com>
Comments: In-reply-to Christopher Morrow <christopher.morrow@gmail.com> message dated "Mon, 23 May 2011 20:00:17 -0400."
Date: Mon, 23 May 2011 20:10:04 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
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: Tue, 24 May 2011 00:10:35 -0000

> I guess I was thinking that today you have a device, it either is
> configured to do dhcp or is manually configured or just is broken. In
> the v6 world you could just forget M&O and require someone to
> configure (via os config tweaks that already exist for v4 anyway)
> dhcpv6 if anything more complex than 'subnet + random address + defgw'
> are required (or if they just like DHCP over SLAAC).

Something like that. The key is that both are implemented. You can
then have defaults for whether or not they are enabled out of the box,
with switches to override the defaults.

But I'm thinking of zeroconfig in the general case. Just plug it into
the net, and it all just works. That means DHCP and SLAAC on by
default.

But zeroconfig isn't all that useful for some types of devices.  For
servers, routers, and other more "infrastructury" devices, it may be
fine to require some config before you plug the machine in.

Of course, manual config is always an option, in which case you turn
off SLAAC & DHCP (except for LL addrs).

Thomas