[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf
Subject:    Re: [dhcwg] Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for	Creating New DHCPv6
From:       Ted Lemon <ted.lemon () nominum ! com>
Date:       2013-09-22 14:15:59
Message-ID: DD3B2A6B-C19C-4BB4-9E04-3B3B0B8BFFBA () nominum ! com
[Download RAW message or body]

On Sep 19, 2013, at 7:01 PM, Kevin Darcy <kcd@chrysler.com> wrote:
> What would be the preferred way to provide a mixed list of IPv4 and =
IPv6 addresses, in a DHCPv6 option? IPv4-mapped addresses?

The preferred way would be not to do that.   I think there is a document =
floating around out there somewhere that uses IPv4-mapped addresses this =
way, but in general if you are configuring an IPv4 stack, you ought to =
be using DHCPv4.   Otherwise DHCPv6 winds up being a transition =
technology in perpetuum.

To be clear, you definitely should not expect a DHCPv6 client to do =
something meaningful with an arbitrary IPv4-mapped IPv6 address.   It's =
anybody's guess where this would clog the plumbing, but it almost =
certainly wouldn't work.

[prev in list] [next in list] [prev in thread] [next in thread]