Commercial Internet Protocol Security Option (cipso) Charter


NOTE: This charter is accurate as of the 31st IETF Meeting in San Jose. It may now be out-of-date. (Consider this a "snapshot" of the working group from that meeting.) Up-to-date charters for all active working groups can be found elsewhere in this Web server.

Chair(s)

Security Area Director(s):

Mailing List Information

Description of Working Group

The Commercial Internet Protocol Security Option Working Group is chartered to define an IP security option that can be used to pass security information within and between security domains. This new security option will be modular in design to provide developers with a single software environment which can support multiple security domains.

The CIPSO protocol will support a large number of security domains. New security domains will be registered with the Internet Assigned Numbers Authority (IANA) and will be available with minimal difficulty to all parties.

There is currently in progress another IP security option referred to as IPSO (RFC 1108). IPSO is designed to support the security labels used by the US Department of Defense. CIPSO will be designed to provide labeling for the commercial, US civilian and non-US communities.

The Trusted Systems Interoperability Group (TSIG) has developed a document which defines a structure for the proposed CIPSO option. The working group will use this document as a foundation for developing an IETF CIPSO specification.

Goals and Milestones

Ongoing
Review outstanding comments/issues from mailing list. Continue the process to advance the Draft Standard to a Standard.
Done
Review and approve the charter for the IETF CIPSO Working Group. Review revised TSIG CIPSO Specification.
Done
Review outstanding comments/issues from mailing list. Continue work on specification and prepare it for submission as an Internet-Draft by the end of May.
Jul 91
Review outstanding comments/issues from mailing list. The specification will be submitted to the IESG for consideration as a Proposed Standard.
Mar 92
Submit specification to the IESG for consideration as a Draft Standard. There must be at least two interoperable implementations by this time.

No Current Internet-Drafts

No Request for Comments