IETF Logo Mail Archive

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

"Bernie Volz (volz)" <volz@cisco.com> Fri, 12 August 2016 19:47 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 C0D2512DA8F for <dhcwg@ietfa.amsl.com>; Fri, 12 Aug 2016 12:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.768
X-Spam-Level:
X-Spam-Status: No, score=-15.768 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 P7IcLH8WYSvr for <dhcwg@ietfa.amsl.com>; Fri, 12 Aug 2016 12:47:34 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A212912D11A for <dhcwg@ietf.org>; Fri, 12 Aug 2016 12:47:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1663; q=dns/txt; s=iport; t=1471031253; x=1472240853; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=WoNBIj+i1SQxhRye1OISXaNeqPiH8w3aYNFTJ3qaMl4=; b=hGuEQLW3kYl8OqhAYt1U0x7gBy04ojh4AhO9k/GE8aZOGZ1QV30grejs I9jy09GlEBk8fd9bw3s7jc+ivSzMaX43r/JauX0SrJcbOrHjUbbN1Obed cjdh0MMek7f5VdtseuJv+VoqutLT9gkWgeSJr/Rtw5ncuNFZeikxWskRh U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AkAwBjJ65X/4gNJK1eg0RWfAe5KoF9JIV5AoFIOBQBAQEBAQEBXSeEXgEBBAEBATg0EAcEAgEIEQQBAR8JBycLFAkIAQEEARIIiCEIDr9oAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWKd4IQiAsFk2OFWQGPDYp8hE6MNYN3AR42g3puAYYrfwEBAQ
X-IronPort-AV: E=Sophos;i="5.28,512,1464652800"; d="scan'208";a="137263382"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Aug 2016 19:47:32 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u7CJlWeN015774 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 12 Aug 2016 19:47:32 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 12 Aug 2016 14:47:32 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Fri, 12 Aug 2016 14:47:32 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Thread-Topic: Using DHCPv6 to carry IPv4 information (rfc3315bis)
Thread-Index: AdHz34aGI+LQprMrSkCfQSO1Yij5YAA8ZaXQ
Date: Fri, 12 Aug 2016 19:47:32 +0000
Message-ID: <837598b81a60421d9f9dcffefc2da7db@XCH-ALN-003.cisco.com>
References: <02701956dfaf49bb85f95d6d6901a2e4@XCH15-05-05.nw.nos.boeing.com>
In-Reply-To: <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: [10.98.1.195]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/FD7XDTJysK8QSHYmei25FG9GMXs>
Subject: Re: [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: Fri, 12 Aug 2016 19:47:36 -0000

Fred:

I think this concept is still true and I'm not in favor of changing the text. It is really more a statement about DHCPv6 does not replace DHCPv4 for IPv4. There are isolated instances where some v4 configuration information may be provided.


Regarding AERO, I'm not sure where this is specified and I suspect that are IPv4-compatible IPv6 address?

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Templin, Fred L
Sent: Thursday, August 11, 2016 10:52 AM
To: <dhcwg@ietf.org> <dhcwg@ietf.org>
Subject: [dhcwg] Using DHCPv6 to carry IPv4 information (rfc3315bis)

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


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email