--pgp-sign-Multipart_Sun_Feb__6_00:39:32_2005-1
Content-Type: text/plain; charset=US-ASCII

>>>>> "bp" == Bryan Phillippe <bp009@terran.org> writes:

    bp> configurable via sysctl (or make it dependent on
    bp> net.inet6.ip6.v6only) would be better.

my vote would be to make good decisions, and not punting too much to
sysctl.  It's not appropriate to expect sysadmins to be intimately
familiar with all these minute details, and I don't want to see magic
sysctl.conf files that the user doesn't know what they do passed about
like modem init strings in the BBS days.

I think an ICMP unreachable should kill a TCP connection attempt
immediately.  It's not just IPv6---it's also a problem with firewalls.
Linux responds to PF's ``administratively unreachable'' message
immediately:

sakima:~$ telnet 192.168.1.114
Trying 192.168.1.114...
telnet: connect to address 192.168.1.114: No route to host

while NetBSD just sits there.  With the new behavior, nothing stops
you from retrying at the application layer, and most applications
where it makes sense already do that.

--pgp-sign-Multipart_Sun_Feb__6_00:39:32_2005-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQCVAwUAQgWtlInCBbTaW/4dAQLnEgP8CSvdk80GnWI5pr9jm0mM+ikiVz903NL7
4a+jjU4Goaof1BPARItspw4FxXRMDgU7AuqH1NCVzw6IbQPVznwXsZ0KogAi0+fO
jdSGWI+hRW4FF0FJBR7+O6dWPAnMWz3I4M/RpG1kh+MO94TpBoPmAKKN6MYJNnP9
Qb2pgebJg1o=
=wkFl
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Sun_Feb__6_00:39:32_2005-1--