RE: Path MTU Discovery

Stephen Kent <kent@bbn.com> Thu, 27 February 1997 00:23 UTC

Received: from cnri by ietf.org id aa23701; 26 Feb 97 19:23 EST
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa00284; 26 Feb 97 19:23 EST
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id TAA21066 for ipsec-outgoing; Wed, 26 Feb 1997 19:05:14 -0500 (EST)
X-Sender: kent@po1.bbn.com
Message-Id: <v03007814af3a7e0b8e75@[128.89.0.110]>
In-Reply-To: <c=US%a=_%p=msft%l=RED-74-MSG-970222011832Z-4004@INET-05-IMC.microsoft.com >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 26 Feb 1997 18:57:41 -0500
To: "S 'ipsec@tis.com'" <ipsec@tis.com>
From: Stephen Kent <kent@bbn.com>
Subject: RE: Path MTU Discovery
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

Folks,

	The working with me on the AH, ESP, and IPSEC Architecture
documentshave been meeting this week to work on PMTU issues.  We will have
an analysis of the issues available soon, addressing the questions raised
on the list over the last few weeks, and providing some rationales for
preferred approaches to dealing with this potentially tricky problem in
both hosts and gateways. Stay tuned.

Steve