[rfc-dist] RFC 4534 on Group Security Policy Token v1
rfc-editor at rfc-editor.org
Mon Jun 26 12:12:28 PDT 2006
A new Request for Comments is now available in online RFC libraries.
Title: Group Security Policy Token v1
Author: A Colegrove, H Harney
Status: Standards Track
Date: June 2006
Mailbox: acc at sparta.com,
hh at sparta.com
I-D Tag: draft-ietf-msec-policy-token-sec-06.txt
The Group Security Policy Token is a structure used to
specify the security policy and configurable parameters
for a cryptographic group, such as a secure multicast
group. Because the security of a group is composed of
the totality of multiple security services, mechanisms, and
attributes throughout the communications infrastructure,
an authenticatable representation of the features that
must be supported throughout the system is needed to ensure
consistent security. This document specifies the structure
of such a token. [STANDARDS TRACK]
This document is a product of the Multicast Security
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist