Rémi Denis-Courmont wrote:
Le Monday 01 October 2007 20:50:00 ext Sam Hartman, vous avez écrit :
Hi. I opened a ticket with the secretariat a few weeks ago
complaining that I cannot reach www.ietf.org using a teredo address
either allocated through the Microsoft Teredo server or the Debian
teredo server.
This is annoying because glibc's source address selection algorithm
seems to prefer teredo addresses to v4 addresses. So, I get really
bad response times to www.ietf.org when using teredo.
To make a long short, that depends on your glibc version. As far as I
remember, RFC3484 was implemented in version 2.4. Configurable policy in
version 2.5, and Teredo in the default policy only very recently.
Because Teredo is not mentioned in RFC3484, I expect many other RFC3484
implementations do have the same issue. Unfortunately, even if they don't
have Teredo support themselves, they should still recognize the prefix for
source address selection...
I did write an I-D to allocate one new prefix, but then I realized that the
revised RFC3484 draft work already mentioned it, so I did not bother
submitting it.
Do you mean this I-D ?
http://tools.ietf.org/id/draft-arifumi-ipv6-rfc3484-revise-00.txt
This one includes mainly minor changes to RFC 3484.
I tried to talk about this I-D at Prague, but I couldn't have time
there. Though this I-D is expired now, I want to put this on the
table again.
Do you have any comments about this I-D ?
Now that we have 6man wg, is it a good idea to move from intarea to 6man ?
Thanks.
--
Arifumi Matsumoto
IP Technology Expert Team
Secure Communication Project
NTT Information Sharing Platform Laboratories
E-mail: arifumi(_at_)nttv6(_dot_)net
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf