[dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013

"Bernie Volz (volz)" <volz@cisco.com> Sat, 14 December 2013 15:11 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 038611ADF26 for <dhcwg@ietfa.amsl.com>; Sat, 14 Dec 2013 07:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YkRzvnzphUg4 for <dhcwg@ietfa.amsl.com>; Sat, 14 Dec 2013 07:11:19 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 91CB01AE124 for <dhcwg@ietf.org>; Sat, 14 Dec 2013 07:11:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10303; q=dns/txt; s=iport; t=1387033861; x=1388243461; h=from:to:subject:date:message-id:mime-version; bh=vMTqkUfEbY+pehJBW1l7o4bHAEK/m0XidosZBB70LPM=; b=InIGrmtzGQmW2ANPKRcodM3bMLn0e16QJzH9gwcwIZIBIUDPGYKup2yL EKb6mEQebuW6gMIiuO5E4KzMpZzcukIdbmRJjpVU+5SRgCjy1ThaTqm7I 4iumDye6Cj6BaniszAGsSVtic9H6Ko81sMjJQgoBGnC6Fe3O/84q/rr+Q 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFALl0rFKtJXG+/2dsb2JhbABZgkZEOFW4YYEbFnSCJwEELV4BKlYmAQQbh3yjFKZdF45og1uBEwSqKoFsgT6CKg
X-IronPort-AV: E=Sophos;i="4.95,485,1384300800"; d="scan'208,217";a="6788750"
Received: from rcdn-core2-3.cisco.com ([]) by alln-iport-2.cisco.com with ESMTP; 14 Dec 2013 15:10:47 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com []) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBEFAlac028415 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sat, 14 Dec 2013 15:10:47 GMT
Received: from xmb-rcd-x04.cisco.com ([]) by xhc-rcd-x14.cisco.com ([]) with mapi id 14.03.0123.003; Sat, 14 Dec 2013 09:10:46 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac743qQ8LugREmTXTeyq+h7sadwKJg==
Date: Sat, 14 Dec 2013 15:10:46 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADE84D3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1ADE84D3xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
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: Sat, 14 Dec 2013 15:11:36 -0000

This is to announce the results of the WGLC on draft-ietf-dhc-dhcpv4-over-dhcpv6-03.

There were discussions on several topics and a list of nits, so a new draft will be needed.

Our determination of the rough consensus is that this work should advance. However, as a new draft is required and as a WGLC on the related draft-ietf-dhc-v4configuration-03 is in progress, we will await an updated draft and the outcome of the WGLC on draft-ietf-dhc-v4configuration-03 before finalizing on next steps.

The authors are requested to publish an updated draft to address the points raised during the WGLC.

Given (at least) two people's concerns about this work (which are probably more directed at the conclusion of draft-ietf-dhc-v4configuration), we should remember the original issue was how to configure IPv4 stacks on IPv6 islands. The WG consensus for that was, I believe, clearly to use DHCPv4. And while draft-ietf-dhc-dhcpv4-over-dhcpv6 solves this when 'native' IPv4 communication is not possible, it is not always required - i.e., if 'native' DHCPv4 (over IPv4) is usable. So, the appropriate conclusions from both sets of work are l believe:

1.       Use DHCPv4 for IPv4 configuration.

2.       Use DHCPv4 'as is' when possible.

3.       Use draft-ietf-dhc-dhcpv4-over-dhcpv6 when DHCPv4 'as is' is not possible (i.e., no ability to get native IPv4 packets to a DHCPv4 relay or server).

-          Bernie & Tomek