[rfc-dist] RFC 3740 on The Multicast Group Security Architecture

[rfc-editor at rfc-editor.org]

A new Request for Comments is now available in online RFC libraries.


        RFC 3740

        Title:      The Multicast Group Security Architecture
        Author(s):  T. Hardjono, B. Weis
        Status:     Informational
        Date:       March 2004
        Mailbox:    thardjono at verisign.com, bew at cisco.com
        Pages:      26
        Characters: 65531
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-msec-arch-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3740.txt


This document provides an overview and rationale of the multicast
security architecture used to secure data packets of large multicast
groups.  The document begins by introducing a Multicast Security
Reference Framework, and proceeds to identify the security services
that may be part of a secure multicast solution.

This document is a product of the Multicast Security Working Group of
the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

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

        help: ways_to_get_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
unlimited distribution.echo 
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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative