Ed, there are a number of things to say.
First, behaviour 4 is mostly described by RFC4301, I believe.
Yes, section 8.2.1.
If you find it is not available, then you need to talk to your vendors.
Behaviour 3 (which, in IPv4 speak, is essentially not copying the DF
bit), is often necessary, but it can mess up the plpmtu mechanism.
Second, PLPMTUD was publiched by the pmtud WG as RFC4821.
This is the best suggestion.
I wrote about what Freeswan/Openswan KLIPS tried to do, which was a
variation of #3, because we wanted the network to work... it is at:
http://www.sandelman.ca/SSW/ietf/ipsec/fragment/draft-richardson-ipsec-fragment.txt
Most of these ideas were incorporated into RFC4821.
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] [email protected] http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
