Reliable Multicast Transport Building Block: Tree Auto-Configuration
draft-sjkoh-rmt-bb-tree-config-03

Document Type Expired Internet-Draft (tsv)
Author Seok Koh 
Last updated 2005-12-11 (latest revision 2004-01-07)
Stream Independent Submission
Intended RFC status Informational
Formats
Expired & archived
pdf htmlized bibtex
Stream ISE state (None)
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Action Holders
(None)
Telechat date
Responsible AD Allison Mankin
IESG note There is a note of concern from an RMT WG Chair in the ballot comments:  these documents retain all the RMT WG boilerplate.  History:  they were not handled by the WG because the authors stopped work on them (stopped doing any updates, did not appear for over a year), so their work item was dropped by consensus.
Send notices to lorenzo@cisco.com, mankin@psg.com

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sjkoh-rmt-bb-tree-config-03.txt

Abstract

The Reliable Multicast Transport (RMT) Working Group has been chartered to standardize reliable multicast transport services and protocol instantiations, which include the tree-based ACK (TRACK) protocol. This document is concerned with defining the building block for auto-configuration of the logical ACK-tree. According to the charter, a building block is 'a coarse-grained modular component that is common to multiple protocols along with abstract APIs that define a building block's access methods and their arguments.' The TRACK BB mechanisms [5] will operate on the logical ACK-tree that is configured by this TREE BB in the TRACK PI sessions. This document is made based on the guidelines for the RMT BB [2] and the recommendations for TREE BB [4].

Authors

Seok Koh (sjkoh@knu.ac.kr)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)