NOTE: This charter is accurate as of the 29th IETF Meeting in Seattle. 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.
Commercial Internet Protocol Security Option (CIPSO) Charter
- Ron Sharp <firstname.lastname@example.org>
Mailing List Information
- General Discussion <email@example.com>
- To Subscribe <firstname.lastname@example.org>
- Archive <email@example.com>
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
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
Goals and Milestones
- Review outstanding comments/issues from mailing list. Continue the process to advance the Draft Standard to a Standard.
- Review and approve the charter for the IETF CIPSO Working Group. Review revised TSIG CIPSO Specification.
- 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 1991
- Review outstanding comments/issues from mailing list. The specification will be submitted to the IESG for consideration as a Proposed Standard.
- Mar 1992
- Submit specification to the IESG for consideration as a Draft Standard. There must be at least two interoperable implementations by this time.