IETF Logo Mail Archive

RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 24 May 2011 17:51 UTC

Return-Path: <Fred.L.Templin@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 54D79E073D for <ipv6@ietfa.amsl.com>; Tue, 24 May 2011 10:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level:
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 yM7YyoIM3iAz for <ipv6@ietfa.amsl.com>; Tue, 24 May 2011 10:51:31 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id C7CA6E067F for <ipv6@ietf.org>; Tue, 24 May 2011 10:51:31 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p4OHpP46017843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 24 May 2011 12:51:28 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with SMTP id p4OHpOxH025242; Tue, 24 May 2011 10:51:24 -0700 (PDT)
Received: from XCH-NWHT-07.nw.nos.boeing.com (xch-nwht-07.nw.nos.boeing.com [130.247.25.111]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p4OHpFD4024832 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 24 May 2011 10:51:16 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-07.nw.nos.boeing.com ([130.247.25.111]) with mapi; Tue, 24 May 2011 10:51:15 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Thomas Narten <narten@us.ibm.com>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Date: Tue, 24 May 2011 10:51:14 -0700
Subject: RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Topic: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Index: AcwZhYqpNxrnfZgCRvibfhLVeAoBrQAtXSdA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6A6C9547@XCH-NW-01V.nw.nos.boeing.com>
References: <C9F53B85.11BE93%john_brzozowski@cable.comcast.com> <201105232010.p4NKAV9X012654@cichlid.raleigh.ibm.com>
In-Reply-To: <201105232010.p4NKAV9X012654@cichlid.raleigh.ibm.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: Bob Hinden <bob.hinden@gmail.com>, "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: Tue, 24 May 2011 17:51:32 -0000

Hi Thomas, 

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On 
> Behalf Of Thomas Narten
> Sent: Monday, May 23, 2011 1:11 PM
> To: Brzozowski, John
> Cc: ipv6@ietf.org; Bob Hinden
> Subject: Re: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
> 
> > Is the intention for the new text to relax the requirement for
> > auto-configuration?
> 
> No. SLAAC remains a MUST. DHCPv6 though is now a SHOULD.
> 
> For one thing, DHCP doesn't have an option configure on-link prefixes,
> so we still need SLAAC.

Not all links will necessarily require on-link prefixes. For
those, DHCPv6 alone may be sufficient.

Thanks - Fred
fred.l.templin@boeing.com

> What we should have done oh-so-long-ago is ensure that you could
> configure/operate a network with just DHCP (and no SLAAC at all) and
> vice versa, and than made both a MUST on hosts.  That way, operators
> truly have the choice as to which to use and everything would just
> work.
> 
> Thomas
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email