IETF Logo Mail Archive

RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 13 May 2011 15:42 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 8E10DE07A0 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 08:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300, 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 8lQk5OfIruMc for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 08:42:08 -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 06009E0792 for <ipv6@ietf.org>; Fri, 13 May 2011 08:42:07 -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 p4DFg4m3017552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 May 2011 10:42:05 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p4DFg4np017894; Fri, 13 May 2011 08:42:04 -0700 (PDT)
Received: from XCH-NWHT-09.nw.nos.boeing.com (xch-nwht-09.nw.nos.boeing.com [130.247.25.115]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p4DFg3Iw017889 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 13 May 2011 08:42:04 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-09.nw.nos.boeing.com ([130.247.25.115]) with mapi; Fri, 13 May 2011 08:42:03 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Thomas Narten <narten@us.ibm.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Date: Fri, 13 May 2011 08:42:01 -0700
Subject: RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Topic: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Index: AcwRczEPXGBVt65vSOWcpLl7lCRhkAAEQGlg
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6A665A44@XCH-NW-01V.nw.nos.boeing.com>
References: <201105131337.p4DDbdao009901@cichlid.raleigh.ibm.com>
In-Reply-To: <201105131337.p4DDbdao009901@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
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 15:42:08 -0000

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

Should be a SHOULD.

Fred

> 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