[dhcwg] Multiple Provisioning Domains (future work mentioned in draft-ietf-dhc-dhcpv6-stateful-issues)
"Bernie Volz (volz)" <volz@cisco.com> Tue, 11 December 2012 22:39 UTC
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEAE21E808E for <dhcwg@ietfa.amsl.com>; Tue, 11 Dec 2012 14:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 JW3rv2F0ZxG1 for <dhcwg@ietfa.amsl.com>; Tue, 11 Dec 2012 14:39:31 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 6F71D1F0CB1 for <dhcwg@ietf.org>; Tue, 11 Dec 2012 14:39:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9585; q=dns/txt; s=iport; t=1355265571; x=1356475171; h=from:to:subject:date:message-id:mime-version; bh=a7l4a+PRQoPHNkC/NoKKAsh9DJmrT94UOqZyU50+eUA=; b=WOnoYg7LNQIVh8cxoI3Xu/2976spJUDx1hkk2apP9R77MFHmYNtMgKbN DpDTXmcPhSy+yniAq1aNCWGFZJx+is1Wz6w6KVs2P6ksiBe+Fjpw+2KKx YpjjKRtgaADnESzKd7WsKitHtPc20eMQhE1oiAxhsWm5iv/3gdoLYe6va Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAFC1x1CtJV2Y/2dsb2JhbABFgkm8BxZzgiABBC1EGgEqViYBBBuICZogkRGQQZAsYQOmT4JzgiI
X-IronPort-AV: E=McAfee;i="5400,1158,6923"; a="151880372"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 11 Dec 2012 22:39:30 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qBBMdUPm003927 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 11 Dec 2012 22:39:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.29]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Tue, 11 Dec 2012 16:39:30 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Multiple Provisioning Domains (future work mentioned in draft-ietf-dhc-dhcpv6-stateful-issues)
Thread-Index: Ac3X8EJJkzabn3NcQL+2USumBHFQCA==
Date: Tue, 11 Dec 2012 22:39:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E0F5E84B0@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.110]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E0F5E84B0xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] Multiple Provisioning Domains (future work mentioned in draft-ietf-dhc-dhcpv6-stateful-issues)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Dec 2012 22:39:33 -0000
On my "to-do" list that never seems to bubble to the top is a draft about multiple provisioning domains (this is related to the single provisioning domain that DHCPv6 assumes today explicitly mentioned in draft-ietf-dhc-dhcpv6-stateful-issues) ... a while back I had written to the DHC WG: I do know Ted wants to see an I-D regarding the multiple provisioning domains but I am not sure whether that would block draft-ietf-dhc-dhcpv6-stateful-issues-00 until available. I just haven't had much time to work on that ID -- the concept is fairly simple in that servers would have to include the provisioning domain identifier in their responses and clients would have to make decisions based on the provisioning identifier - Advertisements that have the same provisioning identifier are selected from pretty much as clients do today without this support and if multiple provisioning identifiers are present, a client can select one Advertisement from each set and fork separate transactions (when and why a client may want to do this need to be worked out - such as is it only done if one domain provides addresses and another prefixes, or should the client do it always). Now, while I guess I should submit something basic, I also wonder whether anyone has a need for this today and thus is it worth drafting something for a hypothetical situation that doesn't exist today and thus might not meet (future) real world requirements. There may also be unexpected issues that aren't addressed - one could be how different server's options would be integrated into a single configuration (this is much like the issues a client with multiple interfaces faces). If there is someone that believes they have a need for this or feels strongly that a draft to address this exist, please let me (or the WG) know so that perhaps we can partner on this draft and make use of those real world requirements. Thanks for your attention. - Bernie
- [dhcwg] Multiple Provisioning Domains (future wor… Bernie Volz (volz)
- Re: [dhcwg] Multiple Provisioning Domains (future… Ted Lemon
- Re: [dhcwg] Multiple Provisioning Domains (future… Bernie Volz (volz)
- Re: [dhcwg] Multiple Provisioning Domains (future… Andre Kostur