IETF Logo Mail Archive

Re: proposed changes to ISAKMP/Oakley

"Michael C. Richardson" <mcr@sandelman.ottawa.on.ca> Mon, 20 October 1997 23:51 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id TAA26821 for ipsec-outgoing; Mon, 20 Oct 1997 19:51:17 -0400 (EDT)
Message-Id: <199710210005.UAA01689@istari.sandelman.ottawa.on.ca>
To: ipsec@tis.com
Subject: Re: proposed changes to ISAKMP/Oakley
In-reply-to: Your message of "Mon, 20 Oct 1997 14:32:47 PDT." <199710202132.OAA25509@pita.cisco.com>
Date: Mon, 20 Oct 1997 20:05:37 -0400
From: "Michael C. Richardson" <mcr@sandelman.ottawa.on.ca>
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

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


>>>>> "Derrell" == Derrell Piper <piper@cisco.com> writes:

    >> I would agree that this should be mandatory. If constraints
    >> (like proxy ids) are given during negotiation they must be
    >> respected by all parties to the negotiation. Any other WG
    >> members have an opinion either way?

    Derrell> I'd prefer mandatory and I think this belongs in the arch
    Derrell> document too.

  Please go read draft-richardson-ipsec-icmp-filter-00.txt.
  If you decide to select the option in 2.1, then please read
draft-richardson-ipsec-pmtu-discov-00.txt, and particularly think
about v6. 
  If you decide to pick option 2.4, ask yourself about R1 generating
ICMP host unreachable or net unreachable. 

  This is IPsecond work. 
  I'd prefer that the IPsec documents not preclude overspecify
policy. Let the VPN documents do that for gateways. Let's not forget
that IPsec is more than just VPN (or, will be, one hopes)

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson |   I do IPsec policy code for SSH <http://www.ssh.fi/>
 Personal: <A HREF="http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html">mcr@sandelman.ottawa.on.ca</A>. PGP key available.
 Corporate: <A HREF="http://www.sandelman.ottawa.on.ca/SSW/">sales@sandelman.ottawa.on.ca</A>. 


  





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

iQB1AwUBNEvxz6ZpLyXYhL+BAQF/GQMAkw7iM8da3x2esXD2u4ESIGcAL3EKYQMS
T1tuYSpZjv1kuV7/cAB6H/7Cw7gAgxXdfM31Ow0DshpgD4t8ZVPcIRchmckq3WLn
zzPx6yA4cU4KlKfEe8XaJhGagNQHZDgp
=I1SR
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email