idnits 2.17.1 draft-ietf-rmt-author-guidelines-03.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 3269 5 Title: Author Guidelines for Reliable Multicast Transport 6 (RMT) Building Blocks and Protocol Instantiation 7 documents 8 Author(s): R. Kermode, L. Vicisano 9 Status: Informational 10 Date: April 2002 11 Mailbox: Roger.Kermode@motorola.com, lorenzo@cisco.com 12 Pages: 12 13 Characters: 25258 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-rmt-author-guidelines-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3269.txt 20 This document provides general guidelines to assist the authors of 21 Reliable Multicast Transport (RMT) building block and protocol 22 instantiation definitions. The purpose of these guidelines is to 23 ensure that any building block and protocol instantiation definitions 24 produced contain sufficient information to fully explain their 25 operation and use. In addition these guidelines provide directions to 26 specify modular and clearly defined RMT building blocks and protocol 27 instantiations that can be refined and augmented to safely create new 28 protocols for use in new scenarios for which any existing protocols 29 were not designed. 31 This document is a product of the Reliable Multicast Transport Working 32 Group of the IETF. 34 This memo provides information for the Internet community. It does 35 not specify an Internet standard of any kind. Distribution of this 36 memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.