[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IPSEC Charter - New Draft f

                      IPSEC Charter - New Draft for Review

IPSECers,

Jim Zmuda has volunteered to serve as co-chair of our working group.
He has been providing significant contributions to our effort and 
his help as co-chair will be greatly appreciated.


Below is a slightly updated draft of the IPSEC charter for review.


Regards,

Paul

----------------------------------------------------------------
                 2/3/93 Draft of IPSEC Charter
----------------------------------------------------------------

Internet Protocol Security Protocol (ipsec)

Charter 
 
Chair(s):
     Paul Lambert  <paul_lambert@email.mot.com>
     Jim Zmuda    <zmuda@mls1.hac.com>
Security Area Director(s) 
     Steve Crocker  <crocker@tis.com>
 
Mailing lists: 
     General Discussion:ipsec@ans.net
     To Subscribe:      ipsec-request@ans.net
     Archive:           ftp.ans.net:~/pub/archive/ipsec

Description of Working Group:

Rapid advances in communication technology have accentuated the need for 
security in the Internet.  The IP Security Protocol Working Group 
(IPSEC) will develop mechanisms to protect client protocols of IP.  The 
IPSEC Working Group will develop a security protocol in the network 
layer to provide cryptographic security services that will flexibly 
support combinations of authentication, integrity, access control, and 
confidentiality.  The protocol formats for the IP Security Protocol 
(IPSP) will be independent of the cryptographic algorithm.  The 
preliminary goals will specifically pursue host-to-host security 
followed by subnet-to-subnet and host-to-subnet topologies.

The working group will examine the relationship of network security the 
suite of IP protocols.  This investigation will include the examination 
of IP as a client of IPSP running over IP.  Recommendations documented 
in the IPSP specification will provide guidelines to protect the IP 
suite of protocols.

The cryptographic encapsulation may hide information that is useful to 
network.  This information may include security labels, addresses, and 
protocol identifiers.  The working group will examine the mapping of 
encapsulated protocol information onto unprotected fields and guidelines 
for any required Rpeek-throughS of information.

Protocol and cryptographic techniques will also be developed to support 
the key management requirements of the IPSP.  The key management will be 
specified as an application layer protocol that is independent of the 
lower layer security protocol.  The protocol will initially support 
public key based techniques.  Flexibility in the protocol will allow 
eventual support of Key Distribution Center (KDC -- such as Kerberos) 
and manual distribution approaches.

Goals and Milestones: 

   Mar 94 Post as an Internet-Draft a preliminary version of the IP 
          Security Protocol.

   Mar 94 Review pilot experiments with cryptographic network security.  
          Discuss, debate, and refine the framework for IPSP based on 
          pilot experiments.  Demonstrate interoperable implementations.

   Mar 94 Establish baseline design goals for Internet Key 
          Management.

   Mar 94 Post preliminary text (as RFC) of Internet Key Management
          to include service primatives and basic assumtions.

   Jul 94 Update the IPSP Internet-Draft.  Include preliminary text on 
          labels, Rpeek-through,S and protection of IP suite.

   Jul 94 Update Key Management and release as Internet Draft

   Nov 94 Report on Pilot Implementations of the IP Security Protocol
           and Key Management Protocol, Update as needed.

   Mar 95 Submit the IP Security Protocol to the IESG for consideration 
          as a Proposed Standard.

   Mar 95. Submit the Internet Key Management Protocol to the IESG for 
          consideration as a Proposed Standard.