Re: [Softwires] Why not use AFTR IPv6 address for the new DHCPv6 option?

lizhenqiang@chinamobile.com Sat, 02 July 2011 18:12 UTC

Return-Path: <lizhenqiang@chinamobile.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 677871F0C3E for <softwires@ietfa.amsl.com>; Sat, 2 Jul 2011 11:12:09 -0700 (PDT)
X-Quarantine-ID: <B7tdw3WJXLk6>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: 0.331
X-Spam-Level:
X-Spam-Status: No, score=0.331 tagged_above=-999 required=5 tests=[AWL=0.708, BAYES_00=-2.599, RELAY_IS_221=2.222]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7tdw3WJXLk6 for <softwires@ietfa.amsl.com>; Sat, 2 Jul 2011 11:12:08 -0700 (PDT)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFB81F0C39 for <softwires@ietf.org>; Sat, 2 Jul 2011 11:12:07 -0700 (PDT)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id A9D8DA7A7; Sun, 3 Jul 2011 02:12:06 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id A163DA7A3; Sun, 3 Jul 2011 02:12:06 +0800 (CST)
To: softwires@ietf.org
MIME-Version: 1.0
From: lizhenqiang@chinamobile.com
Date: Sun, 03 Jul 2011 02:12:04 +0800
Message-ID: <OFE849FE56.503D7D20-ON482578C1.0063FB84-482578C1.0063FB8F@chinamobile.com>
X-Mailer: Lotus Domino Web Server Release 6.5.6 March 06, 2007
X-MIMETrack: Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2011-07-03 02:12:06
MIME-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: quoted-printable
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-18236.001
X-TM-AS-Result: No--17.650-7.0-31-10
X-imss-scan-details: No--17.650-7.0-31-10;No--17.650-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No
Subject: Re: [Softwires] Why not use AFTR IPv6 address for the new DHCPv6 option?
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jul 2011 18:12:09 -0000

Thanks, Washam, I got the intense debate.

But for 6rd, the IPv4 address of the BR is recommended to use in the DHCP option. Thus, different options are recommended for different technologies. I want to know the reason. Using the similar method to do the similar thing is better, isn't it? So, shall we modify the specification of 6rd to use a FQDN for the BR configuration on CEs?

Best Regards,
Zhenqiang Li
2011-07-03 


----- Original Message ----- 
From: Washam Fan 
Sent: 2011-07-01  13:04:46 
To: lizhenqiang@chinamobile.com 
CC: softwires@ietf.org 
Subject: Re: [Softwires] Why not use AFTR IPv6 address for the new DHCPv6 option? 
 
Hi,

There was a debate between ip literal v.s. fqdn for this issue. Please
search the old mail archive to check it out. If I recall correctly, a
major argument would be, many ISPs prefer dns server to do load
balancing over dhcp server.

Thanks,
washam

2011/6/30   <lizhenqiang@chinamobile.com >:
> Hi All,
>
> One question about the new DHCPv6 option for AFTR discovery. Maybe I missed the previous discussion. Sorry for that.
> According to draft-ietf-softwire-ds-lite-tunnel-option, a FQDN is suggested to be deliveried in the new DHCPv6 option to the B4. When receiving the FQDN, B4 has to do the DNS resolution to get the AFTR IPv6 address. The FQDN of the AFTR has to be configured in the DNS server. So, I think delivering the IPv6 address of the AFTR directly to the B4 is better. We can use DHCPv6 option to do this. The address of the AFTR only needs to be configured in the DHCPv6 server.
>
> Best Regards,
> Zhenqiang Li
> 2011-06-30
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>