This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC166A754FDF243C0F93E9FEC
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

jonathan@dsg.stanford.edu wrote:
> <snip less-than-friendly arguments>

GENERIC is supposed to give a generic config that applies to most uses. 
Seeing that the IPv6 deployment rate is steady and will continue to be 
so in the future, I see no reason to leave it out. Given that in some 
areas, IPv6 is close to mainstream (think Japan, mobile networks, 
government support in a couple of other Asian countries as well, 
provider backing in Europe), I see no reason to leave it out, being 
pretty generic enough. IPsec however does not have this prospect (yet), 
so it makes sense to leave it out. If IPsec turns out to be common in 
the future, it should be added to GENERIC anyway, no matter what the 
cost is (assuming it's fully working, ofcourse). Besides this, IPsec in 
NetBSD is still somewhat shrouded in vagaries, at least it comes accross 
to me like that. As for now, IPsec should not end up in GENERIC, for the 
above reasons.

Hope this comment is of any help,
-- 
         Thomas E. Spanjaard
         tgen@netphreax.net

--------------enigC166A754FDF243C0F93E9FEC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iD8DBQFD+kpM6xCMwBJ+1+sRA16ZAKCBqg01Qk0uUwN5OsHD/12tiq1eFgCgkptc
+NkuVCg6QErD4rDeYN/Qwns=
=wm0E
-----END PGP SIGNATURE-----

--------------enigC166A754FDF243C0F93E9FEC--