idnits 2.17.1 draft-ietf-msec-gdoi-08.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3547 5 Title: The Group Domain of Interpretation 6 Author(s): M. Baugher, B. Weis, T. Hardjono, H. Harney 7 Status: Standards Track 8 Date: July 2003 9 Mailbox: mbaugher@cisco.com, bew@cisco.com, 10 thardjono@verisign.com, hh@sparta.com 11 Pages: 48 12 Characters: 108901 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-msec-gdoi-08.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3547.txt 19 This document presents an ISAMKP Domain of Interpretation (DOI) for 20 group key management to support secure group communications. The 21 GDOI manages group security associations, which are used by IPSEC and 22 potentially other data security protocols running at the IP or 23 application layers. These security associations protect one or more 24 key-encrypting keys, traffic-encrypting keys, or data shared by group 25 members. 27 This document is a product of the Multicast Security Working Group of 28 the IETF. 30 This is now a Proposed Standard Protocol. 32 This document specifies an Internet standards track protocol for 33 the Internet community, and requests discussion and suggestions 34 for improvements. Please refer to the current edition of the 35 "Internet Official Protocol Standards" (STD 1) for the 36 standardization state and status of this protocol. Distribution 37 of this memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.