« Return to Thread: [ipsecme] #221: IPsec architecture and proprietary approaches

[ipsecme] #221: IPsec architecture and proprietary approaches

by Stephen Hanna :: Rate this Message:

| View in Thread

Here's the last issue for now. If you think that I missed any,
please let me know and we'll get them added.

Thanks,

Steve

-----Original Message-----
From: ipsecme issue tracker [mailto:trac@...]
Sent: Tuesday, March 20, 2012 7:06 PM
To: yaronf.ietf@...; draft-ietf-ipsecme-p2p-vpn-problem@...
Subject: [ipsecme] #221: IPsec architecture and proprietary approaches

#221: IPsec architecture and proprietary approaches

 In section 3.3, we should say that proprietary approaches may not
 implement all the checks in the IPsec architecture.

 Suggested Resolution: Add this to section 3.3.

--
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-ipsecme-p2p-vpn-
  yaronf.ietf@…          |  problem@…
     Type:  defect       |     Status:  new
 Priority:  normal       |  Milestone:
Component:  p2p-vpn-     |   Severity:  -
  problem                |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/ipsecme/trac/ticket/221>
ipsecme <http://tools.ietf.org/ipsecme/>

_______________________________________________
IPsec mailing list
IPsec@...
https://www.ietf.org/mailman/listinfo/ipsec

 « Return to Thread: [ipsecme] #221: IPsec architecture and proprietary approaches