[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IPsec and Fragmentation
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "M" == M C Nelson <netsec@panix.com> writes:
M> IPSEC WG,
M> I just want to add a parenthetic note, that PMTU seems to really be at
M> odds with the definition and philosophy of IP, i.e. IP in general, is
M> supposed to be able to fragment packets in route, and routes are in
M> general subject to change. I have some difficulty understanding why an
M> appropriate IP encryption standard that is supposed to become general
M> usage, would require such dissonances with the general case use of its
M> host architecture.
a) go read the PMTU spec.
b) routes changes, and the PMTU changes as a result.
c) IPv6 does not fragment packets. Deal with it, don't try and change
the way things have gone ahead.
I see that draft-richardson-ipsec-pmtu-discov-01.txt has expired. Please
read it.
I have some revisions that I didn't change, and I will resubmit
ASAP.
In the meantime, please see:
1. http://www.sandelman.ottawa.on.ca/SSW/ietf/draft-richardson-ipsec-pmtu-discovery-00.txt
2. grep'ing my
<A HREF="http://www.sandelman.ottawa.on.ca/ipsec/">archives</A. for "PMTU"
reveals the following: [yes, you will be able to search it very soon]
Please read these before posting. We have had extensive discussion.
1995/10/msg00218.html
1995/10/msg00222.html
1995/10/msg00223.html
1995/11/msg00135.html
1995/11/msg00139.html
1995/11/msg00140.html
1996/08/msg00004.html
1997/02/msg00110.html
1997/02/msg00197.html
1997/03/msg00129.html
1997/03/msg00133.html
1997/03/msg00159.html
1997/03/msg00170.html
1997/04/msg00197.html
1997/04/msg00198.html
1997/04/msg00200.html
1997/04/msg00203.html
1997/04/msg00228.html
1997/04/msg00230.html
1997/04/msg00231.html
1997/04/msg00227.html
1997/04/msg00236.html
1997/04/msg00237.html
1997/04/msg00238.html
1997/04/msg00239.html
1997/04/msg00240.html
1997/04/msg00243.html
1997/04/msg00244.html
1997/05/msg00003.html
1997/05/msg00002.html
1997/05/msg00004.html
1997/05/msg00127.html
1997/05/msg00165.html
1997/05/msg00166.html
1997/06/msg00001.html
1997/06/msg00053.html
1997/06/msg00146.html
1997/06/msg00147.html
1997/06/msg00150.html
1997/06/msg00155.html
1997/07/msg00125.html
1997/07/msg00230.html
1997/10/msg00043.html
1997/10/msg00130.html
1997/11/msg00011.html
1997/11/msg00012.html
1997/11/msg00029.html
1997/11/msg00031.html
1997/11/msg00063.html
1997/12/msg00002.html
1997/12/msg00019.html
1997/12/msg00055.html
1998/01/msg00010.html
1998/02/msg00127.html
1998/02/msg00150.html
1998/02/msg00120.html
1998/02/msg00139.html
1998/02/msg00204.html
1998/02/msg00203.html
1998/02/msg00216.html
1998/02/msg00233.html
1998/03/msg00120.html
1998/03/msg00118.html
1998/03/msg00148.html
1998/03/msg00147.html
1998/03/msg00151.html
1998/03/msg00152.html
1998/03/msg00154.html
1998/03/msg00159.html
1998/03/msg00170.html
1998/03/msg00184.html
1998/03/msg00207.html
1998/03/msg00212.html
1998/03/msg00213.html
1998/03/msg00214.html
1998/03/msg00220.html
1998/03/msg00233.html
1998/03/msg00265.html
1998/04/msg00167.html
1998/05/msg00071.html
1998/05/msg00188.html
1998/05/msg00189.html
1998/05/msg00212.html
1998/05/msg00253.html
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQB1AwUBNaEbm9iXVu0RiA21AQFW0gL+JMIU2Wcrbn3o3vmcwcKEZ0duEPxLhsQB
Sw2NEtD4vJlsGdDgIseJpGalRwFQGGG3yUySy/2YqCg9bsmNaGlpbAZ05b5exnF8
VPBev0BfMJNIInm1u2e70puwwMTUcAEZ
=WgKI
-----END PGP SIGNATURE-----
References: