IETF Logo Mail Archive

Re: [dhcwg] AD Evaluation: draft-ietf-dhc-dhcpv6-unknown-msg

Ted Lemon <ted.lemon@nominum.com> Mon, 03 February 2014 15:24 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 957701A012B for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 07:24:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wX3UyYU1FG3h for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 07:24:15 -0800 (PST)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id C2E5F1A002A for <dhcwg@ietf.org>; Mon, 3 Feb 2014 07:24:15 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUu+0n6Rm872izyHjCo9eIJaH3NX3AB5e@postini.com; Mon, 03 Feb 2014 07:24:16 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BBF681B830A for <dhcwg@ietf.org>; Mon, 3 Feb 2014 07:24:15 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 9CE42190052; Mon, 3 Feb 2014 07:24:15 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Feb 2014 07:24:15 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <0B24D33F-07DA-4726-BD30-DBCCE93B4560@gmail.com>
Date: Mon, 03 Feb 2014 10:24:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <BD6B4063-5383-41A6-BCAD-CB39E50AB112@nominum.com>
References: <52EBC3EA.1020104@innovationslab.net> <CFA19E62-0F9A-4358-AB7C-E4A910BF4874@nominum.com> <0B24D33F-07DA-4726-BD30-DBCCE93B4560@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Brian Haberman <brian@innovationslab.net>, draft-ietf-dhc-dhcpv6-unknown-msg@tools.ietf.org
Subject: Re: [dhcwg] AD Evaluation: draft-ietf-dhc-dhcpv6-unknown-msg
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 15:24:19 -0000

On Feb 3, 2014, at 10:03 AM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> I'm imagining a scenario in which a device is doing DHCP-PD and has a DHCPv6 client for local configuration.  Don't underestimate implementors; jsut because they haven't gotten it wrong in the past doesn't mean we shouldn't consider the case.

Right, but if they are that creative, it's unlikely we will be able to stop them.

> I'm assuming this entire document will be absorbed into RFC3315bis at some point?  Idle thought - is it worth publishing this document now when it will likely be superseded by RFC3315bis?

Yes, the working group considered that question, and decided to publish.

v2.23.0 | Report a Bug | By Email