Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem

"Bernie Volz (volz)" <volz@cisco.com> Wed, 30 October 2013 21:39 UTC

Return-Path: <volz@cisco.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 27F0121F9A37 for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2013 14:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
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 v98jAFyHu4cu for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2013 14:39:22 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 8D12C21F9D70 for <v6ops@ietf.org>; Wed, 30 Oct 2013 14:39:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2921; q=dns/txt; s=iport; t=1383169158; x=1384378758; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=n8bLYCHefZc9nDu5Vl6RD9rpSUW4DxET/zONrIYmy20=; b=YiGcu+aVQkPCzhDWSg97VZzzLNnN7Xu5F45sJ2BJoiTJPWRKfd30XXmh LWqRrI/ZDy2tNqnelKPKMirEmZ6EgCJTfH2qvpv6UfM4AqUZloQNVyoR9 5puuwFYtGLhGFbpcR84Druln8qRV/fw8BNuN0MSBFjzi5BwC9+LAQx8GY w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAAN8cVKtJXG+/2dsb2JhbABZgwc4VL9hgSoWdIIlAQEBBAEBAWsLDAYBCBEEAQEBChkELgsUCQkBBAENBQgTh1oDDw26dASMX4EngRgxDYMZgQ0DiQeNHo43hTeBaIE+gXE5
X-IronPort-AV: E=Sophos;i="4.93,604,1378857600"; d="scan'208";a="278706102"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-6.cisco.com with ESMTP; 30 Oct 2013 21:39:18 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9ULdITp010624 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 30 Oct 2013 21:39:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.27]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Wed, 30 Oct 2013 16:39:17 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>, Ted Lemon <mellon@fugue.com>
Thread-Topic: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
Thread-Index: Ac7VuHt2/xyVyKkzQgijPiRUOo/hzg==
Date: Wed, 30 Oct 2013 21:39:16 +0000
Message-ID: <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: [161.44.65.145]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org" <draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "Ole Troan (otroan)" <otroan@cisco.com>, Dave Thaler <dthaler@microsoft.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 21:39:27 -0000

I think we have to be a bit careful about "application". We certainly don't want DHCP to configure user based application information. But network configuration related to applications may be valid (although if there are other discovery techniques available, they may well be preferred).

DHCP SHOULD configure the network resources available for the client device to use (i.e., things needed to provide tnetwork connectivity and access to that network's services). It should not configure user specific services (i.e., there was some discussion about email (SMTP, POP, IMAP server) information as an example of something that would not be DHCP configured).

This is a bit tricky to clarify. And, I am certain someone will have issues with my attempt; hopefully they can do better.

- Bernie

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of Mark ZZZ Smith
Sent: Wednesday, October 30, 2013 4:06 PM
To: Ted Lemon
Cc: v6ops@ietf.org; Ole Troan (otroan); Dave Thaler; draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org
Subject: Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem





----- Original Message -----
> From: Ted Lemon <mellon@fugue.com>
> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
> Cc: Andrew Yourtchenko <ayourtch@cisco.com>; Lorenzo Colitti 
> <lorenzo@google.com>; 
> "draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org" 
> <draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org>; 
> "v6ops@ietf.org" <v6ops@ietf.org>; Ole Troan (otroan) 
> <otroan@cisco.com>; Dave Thaler <dthaler@microsoft.com>
> Sent: Wednesday, 30 October 2013 11:07 PM
> Subject: Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new 
> draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
> 
> On Oct 30, 2013, at 4:22 AM, Mark ZZZ Smith 
> <markzzzsmith@yahoo.com.au>
> wrote:
> 
>>  I think DHCPv6 is really solving the application layer configuration
> problem, which is independent of and not specific to the underlying 
> links and network layer parameters.
> 
> Actually DHCPv6 is a poor solution to that problem, because 
> application configuration is not typically network-specific.  This has 
> been discussed at some length recently on the IETF mailing list.
> 

I'll have to look that up. Thanks for letting me know.

I have recently been thinking a bit more about that in the context of the DHCPv6 option transparency draft I posted, and have started to wonder if LDAP or SLP style directories would be better, with a special well known directory branch to represent network or subnet local application parameters.

Thanks,
Mark.
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops