Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2010-04-22 Thread Aurelien Jarno
Tore Anderson a écrit : * Marco d'Itri Agreed. Can the libc maintainers please comment on this issue? The next Debian release will be used in a period in which more and more sites will deploy IPv6 and we must be sure to not make them less reliable for the people adopting transition

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2010-04-21 Thread Tore Anderson
* Marco d'Itri Agreed. Can the libc maintainers please comment on this issue? The next Debian release will be used in a period in which more and more sites will deploy IPv6 and we must be sure to not make them less reliable for the people adopting transition mechanisms. Just adding some

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2010-04-17 Thread Tore Anderson
Hi, another update here: Ubuntu has also applied the patch to their libc package, see https://bugs.launchpad.net/555210, and it will as I understand it be part of their release that's due in a couple of weeks. It would be great if Debian could also apply the patch. That is clearly the

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2010-04-17 Thread Marco d'Itri
On Apr 17, Tore Anderson t...@fud.no wrote: It would be great if Debian could also apply the patch. That is clearly the behaviour that will serve end users the best. Agreed. Can the libc maintainers please comment on this issue? The next Debian release will be used in a period in which more

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2010-04-06 Thread Tore Anderson
Just a little update here: Fedora has commited the change and it'll be part of F13. See https://bugzilla.redhat.com/show_bug.cgi?id=577626. I have tested their patch (attached) and it works as expected. It would really be fantastic if this could be commited to Debian as well! Best regards, --

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2010-04-04 Thread Tore Anderson
Hi, The current practise of scoping RFC 3484-addresses as site-local is causing real operational problems on today's internet, and is inhibiting the rollout of IPv6 on the content side: Consider a setup where an end user has his computer on a LAN with RFC 1918-based private IPv4 addresses (using

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2008-03-05 Thread Aurelien Jarno
Remi Denis-Courmont a écrit : Package: libc6 Version: 2.7-9 Severity: normal Tags: patch Hello, Rule 2 of the Destination Address Selection algorithm in RFC3484 specifies: | Rule 2: Prefer matching scope. | If Scope(DA) = Scope(Source(DA)) and Scope(DB) Scope(Source(DB)),

Bug#468801: libc6: RFC3484 scoping rules should only affect IPv6, not IPv4

2008-03-01 Thread Remi Denis-Courmont
Package: libc6 Version: 2.7-9 Severity: normal Tags: patch Hello, Rule 2 of the Destination Address Selection algorithm in RFC3484 specifies: | Rule 2: Prefer matching scope. | If Scope(DA) = Scope(Source(DA)) and Scope(DB) Scope(Source(DB)), | then prefer DA. Similarly, if