-----BEGIN PGP SIGNED MESSAGE-----


  Gee, I thought 4.4 did Path MTU discovery, and thus NetBSD did.
  My impression, from reading the code is that we almost do, but
don't.

  icmp_input() sees NEEDFRAG on line 606, sets the code to
PRC_MSGSIZE, and calls tcp_ctlinput() (indirectly via inetsw).
  tcp_ctlinput() finds the PCB via in_pcbnotify() and gets it to call
tcp_notify (line 428)
  tcp_notify, however, is only interested if there is an error that
would cause us to shut the connection down.
  Grep'ing for nextmtu, reveals only the one on line 607 of ip_icmp.c.

  Or, did I miss something?

   :!mcr!:            |  Network security programming, currently
   Michael Richardson | on contract with DataFellows F-Secure IPSec
 WWW: mcr@sandelman.ottawa.on.ca. PGP key available.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBM62RTaZpLyXYhL+BAQFQHwMApdkePtLMCQYCGVIW7QAxiFeChgtxwLwx
STN4v7eUJ9+798jii7BOmeh2T+lQRGtEVdgJOoizmVpsf4JtlWIVSEIZHO0n8FqM
gelyDFo3vAYuJrPawc2HwN9IiwBKMkqW
=BXHY
-----END PGP SIGNATURE-----