Re: multiple payloads via "ID_LIST"

["Michael C. Richardson" <mcr@xxxxxxxxxxxxxxxxxxxxxx>]

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


>>>>> "Scott" == Scott G Kelly <skelly@redcreek.com> writes:
    Scott> I agree that we should work on a more comprehensive solution. However,
    Scott> we need this capability yesterday, and I'm sure other vendors do

  Okay, but tell us the policy you are currently unable to express, which
you *need* to express *now*. (Ideally, have your customer tell us the policy)

  I'm trying to do: "if it ain't broke don't fix it" here, so we can get
the time required to discuss a new payload and resolve whatever other issues
that might need resolving for a 1.1 of ISAKMP. 
  (No, I don't want to push a 1.1 any time soon)

  I should also point out that you can implement something custom: the vendor
IDs and private payload space should provide for this. That way we'll
have some experience in the field before we write something down as a
standard.

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson |         Firewalls, TCP/IP and Unix administration
 Personal: http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html
 Corporate: http://www.sandelman.ottawa.on.ca/SSW/
	ON HUMILITY: To err is human, to moo bovine.



  
 

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

iQB1AwUBNgg4wtiXVu0RiA21AQH15QMAlrBcqget6fDLlPGOXZjw/EbEMdcsNm/X
kzf2VMLcVqbEzO2YorH7HYt0DwV9hrJuRnmZoJNXPKYR0REWINoWSdTv3ZXV4jFl
FfVWAgmO3RhHRiDQeFAuLvyPjIGu/r0v
=ZsTs
-----END PGP SIGNATURE-----