thanks for your answer. I have not written code for this. I am working on how to deploy IPV6 VPN and I want to use ULA in the VPN site to make the VPN gateway can make distinguish between the data flow of VPN--VPN and VPN--internet.
Best regards, Lawrence >-----Original Message----- >From: Brian E Carpenter [mailto:[EMAIL PROTECTED] >Sent: Tuesday, August 08, 2006 7:15 PM >To: Lawrence Zou >Cc: 'Mohacsi Janos'; [email protected] >Subject: Re: a question about ULA > >Lawrence Zou wrote: >> >> >> >> Best regards, >> >> Lawrence >> >> >>>-----Original Message----- >>>From: Mohacsi Janos [mailto:[EMAIL PROTECTED] >>>Sent: Tuesday, August 08, 2006 4:56 PM >>>To: Lawrence Zou >>>Cc: [email protected] >>>Subject: Re: a question about ULA >>> >>> >>> >>> >>> >>>On Tue, 8 Aug 2006, Lawrence Zou wrote: >>> >>> >>>>when i read RFC4193,I found it does not mentioned what >>> >>>should do when >>> >>>>the router that produced the ULA global ID reboot. >>>>Does it will produce another pseudo-random global id or it will >>>>recover the global id that it produced before it reboot? >>>> >>>>I ask this question because i think that in a site,it is >>> >>>very probably >>> >>>>that sometimes the device have to be rebooted, if each time the >>>>rebooted router produce a new ULA global id,all devices that >>> >>>attached >>> >>>>to the router have to renumbered , i do not think it is a happy >>>>process. >>> >>>This is not the expected operation. I believe more suitable >>>is: site administrator generates a pseudo-random global id and >>>configures on the routers. ULA does not give automatic router >>>configuration... >>>Regards, >> >> >> yes, i agree with you that maybe it will be more suitable the >> pseudo-random global id be generated by the administrator and >> configure on the router. so when the router reboot ,it will got the >> same configuration and not cause the renumbering process. >> >> so , is this the common concept in IPV6 WG about who produce the >> pseudo-random global id ? I did not see it in the RFC4193 >,or maybe >> i missed someting. >> thanks . > >Section 4.6 says: > > In order for hosts to autoconfigure Local IPv6 addresses, routers > have to be configured to advertise Local IPv6 /64 prefixes >in router > advertisements, or a DHCPv6 server must have been configured to > assign them. In order for a node to learn the Local IPv6 >address of > another node, the Local IPv6 address must have been installed in a > naming system (e.g., DNS, proprietary naming system, etc.) > For these > reasons, controlling their usage in a site is straightforward. > >To me this makes it clear that the prefix is static and is >configured into routers, DHCP servers, and DNS tables as >necessary. I assume that the site manager will just run the >algorithm in section 3.2.2 once. >BTW, has anybody written code for this? It would be a nice >little tool to have on a web site. > > Brian > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
