[dhcwg] Using DHCPv6 to carry IPv4 information (rfc3315bis)

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 11 August 2016 14:52 UTC

Return-Path: <Fred.L.Templin@boeing.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 CDE8E12D10E for <dhcwg@ietfa.amsl.com>; Thu, 11 Aug 2016 07:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 OmyZTlZGHdDB for <dhcwg@ietfa.amsl.com>; Thu, 11 Aug 2016 07:52:09 -0700 (PDT)
Received: from ewa-mbsout-01.mbs.boeing.net (ewa-mbsout-01.mbs.boeing.net [130.76.20.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9904A12D5D0 for <dhcwg@ietf.org>; Thu, 11 Aug 2016 07:51:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u7BEpwSb024334; Thu, 11 Aug 2016 07:51:59 -0700
Received: from XCH15-05-04.nw.nos.boeing.com (xch15-05-04.nw.nos.boeing.com [137.137.100.67]) by ewa-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u7BEpqHT023920 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK) for <dhcwg@ietf.org>; Thu, 11 Aug 2016 07:51:52 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-04.nw.nos.boeing.com (2002:8989:6443::8989:6443) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 11 Aug 2016 07:51:51 -0700
Received: from XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) by XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) with mapi id 15.00.1178.000; Thu, 11 Aug 2016 07:51:52 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Thread-Topic: Using DHCPv6 to carry IPv4 information (rfc3315bis)
Thread-Index: AdHz34aGI+LQprMrSkCfQSO1Yij5YA==
Date: Thu, 11 Aug 2016 14:51:51 +0000
Message-ID: <02701956dfaf49bb85f95d6d6901a2e4@XCH15-05-05.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.137.12.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/_HNFaQ_J3NwVxcnBZ3DbmkJXm14>
Subject: [dhcwg] Using DHCPv6 to carry IPv4 information (rfc3315bis)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 11 Aug 2016 14:52:14 -0000

DHCPv6 can be used to carry IPv4 information in IPv4-mapped IPv6 addresses.
Therefore, I believe the following should be removed from rfc3315bis:

> 2) Section 1.2, the sentences: "[RFC3315] suggested that future work
>    might be to extend DHCPv6 to carry IPv4 address and configuration
>    information. However, the current consensus of the IETF is that
>    DHCPv4 should be used rather than DHCPv6 when conveying IPv4
>    configuration information to nodes." This text is at odds with the
>    AERO spec, where DHCPv6 is used to carry IPv4 configuration info in
>    environments where DHCPv4 mechanisms cannot be applied. Suggestion
>    is to remain silent on this subject and remove these two sentences,
>    then leave it for other documents to define mechanisms for carrying
>    IPv4 information in DHCPv6 messages.

Thanks - Fred
fred.l.templin@boeing.com