idnits 2.17.1 draft-speakman-pgm-spec-07.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 3208 5 Title: PGM Reliable Transport Protocol Specification 6 Author(s): T. Speakman, J. Crowcroft, J. Gemmell, 7 D. Farinacci, S. Lin, D. Leshchiner, M. Luby, 8 T. Montgomery, L. Rizzo, A. Tweedly, N. Bhaskar, 9 R. Edmonstone, R. Sumanasekera, L. Vicisano 10 Status: Experimental 11 Date: December 2001 12 Mailbox: speakman@cisco.com, dino@procket.com, 13 steven@juniper.net, agt@cisco.com, 14 nbhaskar@cisco.com, redmonst@cisco.com, 15 rajitha@cisco.com, lorenzo@cisco.com, 16 j.crowcroft@cs.ucl.ac.uk, jgemmell@microsoft.com, 17 dleshc@tibco.com, luby@digitalfountain.com, 18 todd@talarian.com, luigi@iet.unipi.it 19 Pages: 111 20 Characters: 244637 21 Updates/Obsoletes/SeeAlso: None 23 I-D Tag: draft-speakman-pgm-spec-07.txt 25 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3208.txt 27 Pragmatic General Multicast (PGM) is a reliable multicast transport 28 protocol for applications that require ordered or unordered, 29 duplicate-free, multicast data delivery from multiple sources to 30 multiple receivers. PGM guarantees that a receiver in the group 31 either receives all data packets from transmissions and repairs, or is 32 able to detect unrecoverable data packet loss. PGM is specifically 33 intended as a workable solution for multicast applications with basic 34 reliability requirements. Its central design goal is simplicity of 35 operation with due regard for scalability and network efficiency. 37 This memo defines an Experimental Protocol for the Internet community. 38 It does not specify an Internet standard of any kind. Discussion and 39 suggestions for improvement are requested. Distribution of this memo 40 is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.