rfc2357.txt

RFC 的详细文档！

Network Working Group                                          A. Mankin
Request for Comments: 2357                                       USC/ISI
Category: Informational                                       A. Romanow
                                                                     MCI
                                                              S. Bradner
                                                      Harvard University
                                                               V. Paxson
                                                                     LBL
                                                            With the TSV
                                                        Area Directorate
                                                               June 1998


       IETF Criteria for Evaluating Reliable Multicast Transport
                       and Application Protocols

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

Abstract

   This memo describes the procedures and criteria for reviewing
   reliable multicast protocols within the Transport Area (TSV) of the
   IETF.  Within today's Internet, important applications exist for a
   reliable multicast service.  Some examples that are driving reliable
   multicast technology are collaborative workspaces (such as
   whiteboard), data and software distribution, and (more speculatively)
   web caching protocols.  Due to the nature of the technical issues, a
   single commonly accepted technical solution that solves all the
   demands for reliable multicast is likely to be infeasible [RMMinutes
   1997].

   A number of reliable multicast protocols have already been developed
   to solve a variety of problems for various types of applications.
   [Floyd97] describes one widely deployed example.  How should these
   protocols be treated within the IETF and how should the IETF guide
   the development of reliable multicast in a direction beneficial for
   the general Internet?






Mankin, et. al.              Informational                      [Page 1]

RFC 2357             Evaluating Reliable Multicast             June 1998


   The TSV Area Directors and their Directorate have outlined a set of
   review procedures that address these questions and set criteria and
   processes for the publication as RFCs of Internet-Drafts on reliable
   multicast transport protocols.

1.0 Background on IETF Processes and Procedures

   In the IETF, work in an area is directed and managed by the Area
   Directors (ADs), who have authority over the chartering of working
   groups (WGs).

   In addition, ADs review individually submitted (not by WGs)
   Internet-Drafts about work that is relevant to their areas prior to
   publication as RFCs (Experimental, Informational or, in rare cases,
   Standards Track). The review is done according to the guidelines set
   out in the Internet Standards Process, RFC 2026 [InetStdProc96].

   The purpose of this document is to present the criteria that will be
   used by the TSV ADs in reviewing reliable multicast Internet-Drafts
   for any form of RFC publication.

   For I-Ds submitted for Standards Track publication, these criteria
   must be met or else the ADs will decline to support publication of
   the document, which suffices to prevent publication.  For I-Ds
   submitted as Experimental or Informational, these criteria must be
   met or else, at a minimum, the Ads will recommend publishing the I-D
   with an IESG note prepended stating that the protocol fails to comply
   with these criteria.

2.0 Introduction

   There is a strong application demand for reliable multicast.
   Widespread use of the Internet makes the economy of multicast
   transport attractive.  The current Internet multicast model offers
   best-effort many-to-many delivery service and offers no guarantees.
   One-to-many and few-to-few services may become more important in the
   future.  Reliable multicast transports add delivery guarantees, not
   necessarily like those of reliable unicast TCP, to the group-delivery
   model of multicast.  A panel of some major users of the Internet,
   convened at the 38th IETF, articulated reliable bulk transfer
   multicast as one of their most critical requirements [DiffServBOF97].
   Examples of applications that could use reliable bulk multicast
   transfer include collaborative tools, distributed virtual reality,
   and software upgrade services.

   To meet the growing demand for reliable multicast, there is a large
   number of protocol proposals.  A few were published as RFCs before
   the impact of congestion from reliable multicast was fully



Mankin, et. al.              Informational                      [Page 2]

RFC 2357             Evaluating Reliable Multicast             June 1998


   appreciated, and these should be deprecated [DeprRFCs].  Two surveys
   of other publications are [DiotCrow97], [Obraczka98].

   As we discuss in Section 3, the issues raised by reliable multicast
   are considerably more complex than those related to reliable unicast.
   In particular, in today's Internet, reliable multicast protocols
   could do great damage through causing congestion disasters if they
   are widely used and do not provide adequate congestion control.

   Because of the complexity of the technical issues, and the abundance
   of proposed solutions, we are putting in place review procedures that
   are more explicit than usual.  We compare this action with an IESG
   action taken in 1991, RFC 1264 [Routing91], when community experience
   with standard Internet dynamic routing protocols was still limited,
   and extra review was deemed necessary to assure that the protocols
   introduced would be effective, correct and robust.

   Section 3 describes in detail the nature of the particular challenges
   posed by reliable multicast. Section 4 describes the process for
   considering reliable multicast solutions. Section 5 details the
   additional requirements that need to be met by proposals to be
   published as Standards Track RFCs.

3.0 Issues in Reliable Multicast

   Two aspects of reliable multicast make standardization particularly
   challenging. First, the meaning of reliability varies in the context
   of different applications. Secondly, if special care is not taken,
   reliable multicast protocols can cause a particular threat to the
   operation of today's global Internet. These issues are discussed in
   detail in this section.

3.1 One or Many Reliable Multicast Protocols or Frameworks?

   Unlike reliable unicast, where a single transport protocol (TCP) is
   currently used to meet the reliable delivery needs of a wide range of
   applications, reliable multicast does not necessarily lend itself to
   a single application interface or to a single underlying set of
   mechanisms.  For unicast transport, the requirements for reliable,
   sequenced data delivery are fairly general.  TCP, the primary
   transport protocol for reliable unicast, is a mature protocol with
   delivery semantics that suit a wide range of applications.

   In contrast, different multicast applications have widely different
   requirements for reliability.  For example, some applications require
   that message delivery obey a total ordering while others do not.
   Some applications have many or all the members sending data while
   others have only one data source.  Some applications have replicated



Mankin, et. al.              Informational                      [Page 3]

RFC 2357             Evaluating Reliable Multicast             June 1998


   data, for example in an n-redundant file store, so that several
   members are capable of transmitting a data item, while for others all
   data originates at a single source.  Some applications are restricted
   to small fixed-membership multicast groups, while other applications
   need to scale dynamically to thousands or tens of thousands of
   members (or possibly more).  Some applications have stringent delay
   requirements, while others do not.  Some applications such as file-
   transfer are high-bandwidth, while other applications such as
   interactive collaboration tools are more likely to be bursty but use
   low bandwidth overall. Some applications will sometimes trade off
   less than complete reliability for more timely delivery. These
   requirements each impact the design of reliable multicast protocols
   in a different way.

   In addition, even for a specific application where the application's
   requirements for reliable multicast are well understood, there are
   many open questions about the underlying mechanisms for providing
   reliable multicast.  A key question concerns the robustness of the
   underlying reliable multicast mechanisms as the number of senders or
   the membership of the multicast group grows.

   One challenge to the IETF is to end up with the right match between
   applications' requirements and reliable multicast mechanisms.  While
   there is general agreement that a single reliable multicast protocol
   or framework is not likely to meet the needs of all Internet
   applications, there is less understanding and agreement about the
   exact relationship between application-specific requirements and more
   generic underlying reliable mutlicast protocols or mechanisms. There
   are also open questions about the appropriate integration between an
   application and an underlying reliable multicast framework, and the
   potential generality of a single applications interface for that
   framework.

3.2 Congestion Control

   A particular concern for the IETF is the impact of reliable multicast
   traffic on other traffic in the Internet in times of congestion, in
   particular the effect of reliable multicast traffic on competing TCP
   traffic.  The success of the Internet relies on the fact that best-
   effort traffic responds to congestion on a link (currently as
   indicated by packet drops) by reducing the load presented to the
   network.  Congestion collapse in today's Internet is prevented only
   by the congestion control mechanisms in TCP, standardized by RFC 2001
   [CongAvoid97, Jacobson88].

   There are a number of reasons to be particularly attentive to the
   congestion-related issues raised by reliable multicast proposals.
   Multicast applications in general have the potential to do more



Mankin, et. al.              Informational                      [Page 4]

RFC 2357             Evaluating Reliable Multicast             June 1998


   congestion-related damage to the Internet than do unicast
   applications.  One factor is that a single multicast flow can be
   distributed along a large, global multicast tree reaching throughout
   the entire Internet.

   Unreliable multicast applications such as audio and video are, at the
   moment, usually accompanied by a person at the receiving end, and
   people typically unsubscribe from a multicast group if congestion is
   so heavy that the audio or video stream is unintelligible.  Reliable
   multicast applications such as group file transfer applications, on
   the other hand, are likely to be between computers, with no humans in
   attendance monitoring congestion levels.

   In addition, reliable multicast applications do not necessarily have
   the natural time limitations typical of current unreliable multicast
   applications.  For a file transfer application, for example, the data
   transfer might continue until all of the data is transferred to all
   of the intended receivers, resulting in a potentially-unlimited
   duration for an individual flow.  Reliable multicast applications
   also have to contend with a potential explosion of complex patterns
   of control traffic (e.g., ACKs, NACKs, status messages).  The design
   of congestion control mechanisms for reliable multicast for large
   multicast groups is currently an area of active research.

   The challenge to the IETF is to encourage research and
   implementations of reliable multicast, and to enable the needs of
   applications for reliable multicast to be met as expeditiously as
   possible, while at the same time protecting the Internet from the
   congestion disaster or collapse that could result from the widespread
   use of applications with inappropriate reliable multicast mechanisms.
   Because of the setbacks and costs that could result from the
   widespread deployment of reliable multicast with inadequate
   congestion control, the IETF must exercise care in the
   standardization of a reliable multicast protocol that might see
   widespread use.

   The careful review and cautious acceptance procedures for proposals
   submitted as Internet-Drafts reflects our concern to meet the
   challenges described here.

4. IETF Process for Review and Publication of Reliable Multicast
   Protocol Specifications

   In the general case of individually submitted Internet-Drafts
   (proposals not produced by an IETF WG), the process of publication as
   some type of RFC is described in RFC 2026 (4.2.3) [InetStdProc96].
   This specifies that if the submitted Internet-Draft is closely
   related to work being done or expected to be done in the IETF, the



Mankin, et. al.              Informational                      [Page 5]

RFC 2357             Evaluating Reliable Multicast             June 1998


   ADs may recommend that the document be brought within the IETF and
   progressed in the IETF context.  Otherwise, the ADs may recommend
   that the Internet-Draft be published as an Experimental or
   Informational RFC, with or without an IESG annotation of its
   relationship to the IETF context.

   The procedure for Reliable Multicast proposal publication will have
   as its default RFC status Experimental, when the technical criteria
   listed in Section 5 are deemed to be fulfilled. Both the criteria and
   the procedure reflect the AD's technical assessment of the current
   state of reliable multicast technology.  It does not reflect the
   origins of the proposals, which we expect will be equally from
   commercial vendors with initial products and from researchers.

   Work on the development and engineering of protocols that may
   eventually meet the review criteria could take place either in the
   IRTF Reliable Multicast Research Group (http://www.irtf.org) or a
   focused short IETF WG with an Experimental product.

   When the work in reliable multicast technology has matured enough to
   be considered for standardization within the IETF, the TSV Area may
   charter appropriate working groups to develop standards track
   documents.  The criteria for evaluation of standards track technology
   will be at least as stringent as those described herein (next