| Steve Kent, IPSEC SMIB, e-mail to ipsec@ans.net, August 10, 1994. |
....SA are defined in [RFC 1825] The separation of ISAKMP from a specific SA definition is important to ensure ISAKMP can establish SAs for all possible security functionality. Each security function will be required to maintain a database of current SAs. This list is based upon an e mail message [Kent94] to the IPSEC mail list from Steve Kent. The authors welcome input on what are meaningful security attributes for an SA. 1. SAID.INBOUND 2. SAID.OUTBOUND 3. ENCAPSULATION 4. INBOUND CRITERIA (a) IP DESTINATION ADDRESS (b) IP SOURCE ADDRESS (c) NEXT PROTOCOL (d) IP SECURITY LABEL (e) ....
Steve Kent, IPSEC SMIB, e-mail to ipsec@ans.net, August 10, 1994.
....an SA using the ISAKMP components will be described in this section. Maughan Patrick Schertler draft nsa isakmp 00.txt, ps [Page 12] INTERNET DRAFT ISAKMP March 20, 1995 9 Conclusions A Protocol State Diagram B Security Association Attributes This appendix is an exact copy of an e mail message [Kent94] to the IPSEC mail list from Steve Kent and is reproduced here to start a discussion on SA attributes. Inclusion in this appendix is not a wholesale endorsement. The following is a set of possible parameters for each security association (SA) e.g. candidate MIB data items where each SA has its ....
Steve Kent, IPSEC SMIB, e-mail to ipsec@ans.net, August 10, 1994.
No context found.
Steve Kent, IPSEC SMIB, e-mail to ipsec@ans.net, August 10, 1994.
No context found.
Steve Kent, IPSEC SMIB, e-mail to ipsec@ans.net, August 10, 1994.
No context found.
Steve Kent, IPSEC SMIB, e-mail to ipsec@ans.net, August 10, 1994.
No context found.
Steve Kent, IPSEC SMIB, e-mail to ipsec@ans.net, August 10, 1994.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC