Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
Ted Lemon <Ted.Lemon@nominum.com> Wed, 30 October 2013 22:16 UTC
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8CE11E827A for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2013 15:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level:
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GaXxtK5OmL4E for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2013 15:16:23 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1ED11E81E6 for <v6ops@ietf.org>; Wed, 30 Oct 2013 15:16:21 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUnGFMuupFF0QcwBRWkSYM5Shnx3tftge@postini.com; Wed, 30 Oct 2013 15:16:21 PDT
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 DDC231B82A4 for <v6ops@ietf.org>; Wed, 30 Oct 2013 15:16:17 -0700 (PDT)
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 ESMTPS id D5F83190043; Wed, 30 Oct 2013 15:16:17 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.03.0158.001; Wed, 30 Oct 2013 15:16:17 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
Thread-Index: Ac7VuHt2iFBL+1h3kE6ceyrynOvMOAAP9baA
Date: Wed, 30 Oct 2013 22:16:17 +0000
Message-ID: <38D115EE-C955-42ED-8437-543495EEA163@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD4CBA4@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AD4CBA4@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FF2A52FAF1FA61438A557A3C452103A0@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Dave Thaler <dthaler@microsoft.com>, "v6ops@ietf.org" <v6ops@ietf.org>, "draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org" <draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org>, "Ole Troan (otroan)" <otroan@cisco.com>
Subject: Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 22:16:30 -0000
On Oct 30, 2013, at 5:39 PM, Bernie Volz (volz) <volz@cisco.com> wrote: > This is a bit tricky to clarify. And, I am certain someone will have issues with my attempt; hopefully they can do better. One point of clarification that I found useful but was not universally applauded was the notion that if the protocol is or was in the Internet area, it's probably something you can configure with DHCP; if it's not, think carefully before using DHCP to configure it. This lets out a _lot_ of stuff that has options in DHCPv4. But I can't think of anything it excludes that I'd want to keep around. Of course, Mobile IPv6 is an Internet area protocol, and it's not entirely clear to me that it's configurable via DHCP, although there exist DHCP options to configure it.
- Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//R… Bernie Volz (volz)
- Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//R… Ted Lemon