One document matched: draft-ietf-rmt-design-space-01.txt

Differences from draft-ietf-rmt-design-space-00.txt

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


        RFC 2887

        Title:      The Reliable Multicast Design Space for Bulk Data
                    Transfer 
        Author(s):  M. Handley, S. Floyd, B. Whetten, R. Kermode,
                    L. Vicisano, M. Luby
        Status:     Informational
        Date:       August 2000
        Mailbox:    mjh@aciri.org, floyd@aciri.org,
                    whetten@talarian.com, Roger.Kermode@motorola.com,
                    lorenzo@cisco.com, luby@digitalfountain.com 
        Pages:      22
        Characters: 51135
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-rmt-design-space-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2887.txt


The design space for reliable multicast is rich, with many possible
solutions having been devised.  However, application requirements
serve to constrain this design space to a relatively small solution
space. This document provides an overview of the design space and the
ways in which application constraints affect possible solutions.

This document is a product of the Reliable Multicast Transport 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.