idnits 2.17.1 draft-ietf-mmusic-mbus-transport-06.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 3259 5 Title: A Message Bus for Local Coordination 6 Author(s): J. Ott, C. Perkins, D. Kutscher 7 Status: Informational 8 Date: April 2002 9 Mailbox: jo@tzi.uni-bremen.de, csp@isi.edu, 10 dku@tzi.uni-bremen.de 11 Pages: 39 12 Characters: 84125 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-mmusic-mbus-transport-06.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3259.txt 19 The local Message Bus (Mbus) is a light-weight message-oriented 20 coordination protocol for group communication between application 21 components. The Mbus provides automatic location of communication 22 peers, subject based addressing, reliable message transfer and 23 different types of communication schemes. The protocol is layered 24 on top of IP multicast and is specified for IPv4 and IPv6. The IP 25 multicast scope is limited to link-local multicast. This document 26 specifies the Mbus protocol, i.e., message syntax, addressing and 27 transport mechanisms. 29 This document is a product of the Multiparty Multimedia Session 30 Control Working Group of the IETF. 32 This memo provides information for the Internet community. It does 33 not specify an Internet standard of any kind. Distribution of this 34 memo is unlimited. 36 This announcement is sent to the IETF list and the RFC-DIST list. 37 Requests to be added to or deleted from the IETF distribution list 38 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 39 added to or deleted from the RFC-DIST distribution list should 40 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 42 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 43 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 44 help: ways_to_get_rfcs. For example: 46 To: rfc-info@RFC-EDITOR.ORG 47 Subject: getting rfcs 49 help: ways_to_get_rfcs 51 Requests for special distribution should be addressed to either the 52 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 53 specifically noted otherwise on the RFC itself, all RFCs are for 54 unlimited distribution.echo 55 Submissions for Requests for Comments should be sent to 56 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 57 Authors, for further information.