|
>On Fri, 21 May 2004, Eiffel Wu wrote:
>> As compared with the Teredo, Silkroad has the following >> strongpoints: >> >> 2. Silkroad can deploy without the support of relay, while the >> Teredo needs the relay which advertises the reachability of Teredo >> Prefix. > >That's not really true, I think. You can deploy Teredo using your >own, arbitrary prefix, ("internal Teredo server"), and to the rest of >the Internet, it looks like native IPv6 service. Cited from Teredo:
Teredo relays are IPv6 routers that advertise reachability of
the
Teredo service IPv6 prefix through the IPv6 routing protocols. Teredo address format:
+-------------+-------------+-------+------+-------------+ | Prefix | Server IPv4 | Flags | Port | Client IPv4 | +-------------+-------------+-------+------+-------------+ - Prefix: the 32 bit Teredo service prefix. - Server IPv4: the IPv4 address of a Teredo server. >> 3. Silkroad supports all types of NATs, while Teredo
doesn't support
>> symmetric NATs. > >Obviously, this could be added very easily to Teredo as well, but it >would require that Teredo servers would act as tunnel endpoints, and >there would not be direct tunneling. That would burden the servers to >that it would probably be undesirable. Whether or no, Teredo does not support symmetric NATs. |