> -----邮件原件----- > 发件人: WashamFan [mailto:[email protected]] > 发送时间: 2010年3月2日 11:00 > 收件人: Xu Xiaohu > 抄送: 'Dayong Guo'; [email protected]; 'DHC WG' > 主题: Re: [Softwires] FW: New Version Notification for > draft-guo-softwire-6rd-ipv6-config-00 > > Hi, > > > > > Since the SP network is IPv4-only, IMO, DHCPv6 server and > > > > DNSv6 server would be deployed in 6rd CE LAN side. In that > > > > case, DHCPv4 options defined in this draft would be not > > > > justified. > > > > > > If a given DHCPv6 server is deployed in a customer site, its IPv6 address > > should > > > be a 6rd IPv6 address. In this case, the DHCP relay agent will > > relay the > > > information-request message to the 6rd CPE of that site, rather > > than to > > the > > > 6rd border relay. > > > > The "customer" site mentioned above is a 6rd site which is actually deployed > > by the SP and is used for holding IPv6 servers (e.g., DHCPv6 servers, > > NTP > > servers and DNS servers etc). > > > > For the small-sized sites, do you believe they should deploy their own > > DHCPv6 servers? > > My concern is, if DHCPv6 is deployed within 6rd CE LANs, extensions > to DHCPv4 defined in the draft would not apply. If DHCPv6 server > deployed in 6rd CE WAN, that is where your draft fits in, I guess. > > But how come DHCPv6 server is deployed in 6rd CE WAN which > is IPv4-only SP network?
The IPv6 servers (e.g., DHCPv6 servers) could be deployed in a 6rd ” customer” site which is actually owned by the SP. Xiaohu _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
