Re: [dhcwg] Fw: Assigning IPv4-compatible IPv6 addresses via DHCPv6server

"Bernie Volz (volz)" <volz@cisco.com> Thu, 10 March 2011 14:38 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAE553A69E5 for <dhcwg@core3.amsl.com>; Thu, 10 Mar 2011 06:38:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.433
X-Spam-Level:
X-Spam-Status: No, score=-9.433 tagged_above=-999 required=5 tests=[AWL=-1.235, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, J_CHICKENPOX_53=0.6, J_CHICKENPOX_56=0.6, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWXWYvnLarLh for <dhcwg@core3.amsl.com>; Thu, 10 Mar 2011 06:38:22 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 90D693A69D7 for <dhcwg@ietf.org>; Thu, 10 Mar 2011 06:38:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=15207; q=dns/txt; s=iport; t=1299767980; x=1300977580; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=YuakEax8ftxhSGIcJpvMEeohz6Mz22m69D8xPwxXyyM=; b=UQO1PWjd/aA5FsgtoakNUJmYaG+dzt/Jk23VLpDpBusPHfhiRjP6YTjT /Qphfq1fI0OkVRa+fEpma2erMR7vLw7dpKLJ5wr62RTXGiYQf+oAzCYDC YLBlNH1VX/YkfBrf6t2F62YWEf2PUcI6dh1Z/9ZteU07OyKyqSK5Osr9H 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvQAAMpxeE2tJXG+/2dsb2JhbACCW5V7Do4ed6RenD2FYgSFJIpvgxY
X-IronPort-AV: E=Sophos; i="4.62,296,1297036800"; d="scan'208,217"; a="224420782"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rtp-iport-2.cisco.com with ESMTP; 10 Mar 2011 14:39:39 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2AEddn5007193; Thu, 10 Mar 2011 14:39:39 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 10 Mar 2011 08:39:40 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBDF30.FC5C96C3"
Date: Thu, 10 Mar 2011 08:39:38 -0600
Message-ID: <D9B5773329187548A0189ED65036678906777FF3@XMB-RCD-101.cisco.com>
In-Reply-To: <OFD9E3FEB8.6C138E39-ON4825784F.000C2757-4825784F.000CDF5A@zte.com.cn>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] Fw: Assigning IPv4-compatible IPv6 addresses via DHCPv6server
Thread-Index: AcveyambkYdfZxK9QZeiOclZMc+8TQAZSzKQ
References: <OFD9E3FEB8.6C138E39-ON4825784F.000C2757-4825784F.000CDF5A@zte.com.cn>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: hu.yuxing@zte.com.cn, robertyabad@yahoo.com
X-OriginalArrivalTime: 10 Mar 2011 14:39:40.0011 (UTC) FILETIME=[FCA24BB0:01CBDF30]
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Fw: Assigning IPv4-compatible IPv6 addresses via DHCPv6server
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 10 Mar 2011 14:38:27 -0000

Are you asking about this as a general question or regarding a specific
server?

 

For Cisco Network Registrar's DHCP (DHCPv6) server, as the low 32-bits
of the IPv6 address are the IPv4 address and if you don't really care to
do anything special, you could probably define a prefix that has a /120
range (for a /24 IPv4 subnet) [or /112 for a /16, ...) and the server
would then allocate the IPv6 addresses. CNR just doesn't care what
prefixes you define (it is perfectly happy with assigning addresses out
of a 0::a01:200/120 prefix if you wanted to assign 10.1.2.0/24 addresses
- you can even enter this as ::10.1.2.0/120 - you might have to take
some special actions to avoid assigning the all-zero's and all-one's
addresses - such as by creating garbage reservations for those
addresses).

 

Or, if you want more intelligence, you could do this if you wrote an
extension that did the allocation of the IPv6 address.

 

But there is no specific/special support for IPv4 compatible IPv6
addresses. 

 

I suspect that other DHCPv6 servers could be configured to assign these
addresses as well?

 

Note that RFC 4291 deprecates these addresses:

 

   The "IPv4-Compatible IPv6 address" is now deprecated because the

   current IPv6 transition mechanisms no longer use these addresses.

   New or updated implementations are not required to support this

   address type.

 

-          Bernie

 

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of hu.yuxing@zte.com.cn
Sent: Wednesday, March 09, 2011 9:19 PM
To: robertyabad@yahoo.com
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Fw: Assigning IPv4-compatible IPv6 addresses via
DHCPv6server

 


I am trying to configure DHCPv6 server to assign IPv4-compatible IPv6
addresses for dual stack hosts. The server must be configured by
administrator with IPv6 prefix. The generated IPv6 addresses must be
created like :

IPv6_prefix + IPv4_address+........

Is that possible to make DHCPv6 server capable to do that without
configuring DHCPv6 clients? 

------------------------------------------------------------------------
------------------------------------------------ 

Hi,Robert 

    IPv4-compatible IPv6 addresses take the form ::/96+IPv4
address/32,they are only used to dynamically tunnel IPv6 packets over
IPv4 networks(Automatic tunnel).In windows os,it is created by a
command: netsh interface ipv6 set state v4compat=enabled,and it is
generated by the IPv4 address of the host. 
    So, I dont kown if you are talking about this ? Maybe you are
talking about IPv4-mapped IPv6 address,then the IPv6_prefix would not be
fixed,and the client would not recognize it if you didnt configure
anything.But which OS support this? 

Regards 
     

 
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail
is solely property of the sender's organization. This mail communication
is confidential. Recipients named above are obligated to maintain
secrecy and are not permitted to disclose the contents of this
communication to others.
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
originator of the message. Any views expressed in this message are those
of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam
system.